Bug 531088
Summary: | [abrt] crash detected in mail-notification-5.4-16.fc12 [PATCH] | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Serge Pavlovsky <pal666> | ||||||||||||||||||
Component: | mail-notification | Assignee: | Dmitry Butskoy <dmitry> | ||||||||||||||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||
Severity: | medium | Docs Contact: | |||||||||||||||||||
Priority: | low | ||||||||||||||||||||
Version: | 14 | CC: | adam.bruce, adamsonj, adellam, afgonzaga, akshayvyas29, alexandruz, alex.ploumistos, ame.fedora, angel13880, aquarichy, aslowik, attila.kanto, biorochi, bmillett, bobkaiser1, boumehdi.az, brandon.gardner, bunzon, cgranade, comhal, czenda1985, dalinhuang, dchand3, dmitryburstein, dmitry, dmitry, e.liger, erik-fedora, esteban.registrado, fedora, fgvandeuveren, fonya, ganesh.rajaiyan, ian, izartova, jayburrill, je.fenix, jendrik, jfbeltran, jgutierrez, jik, jyuille5, kamil.kulik, leayuda, linuxghost, lukaszlucka, maxime.tierre, maxx, mike, m.l.grzeszczuk, ms, myemail, nphilipp, oded, openhoat, ortizsantini, pavel1r, pavel.lisy, pdupre, peter.fuchs, peter.verthez, philec, raizdepi, ray, rbinkhor, redhat, Robert-Martin, rodriguez.rodriguez.manolo, ronaldcanete, rosen, russ+bugzilla-redhat, samuelyogi, slybloty, ssabcew, steinach2810, stephan, topke63, unix63, vf.duret, vincent.tavier, ykt, zhhuan | ||||||||||||||||||
Target Milestone: | --- | Keywords: | Triaged | ||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||||||
OS: | Linux | ||||||||||||||||||||
Whiteboard: | abrt_hash:866700e2ffcf2a76e73a90c310fb3f16e870a7c9 | ||||||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||
Last Closed: | 2012-08-16 22:31:34 UTC | Type: | --- | ||||||||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||||||||
Documentation: | --- | CRM: | |||||||||||||||||||
Verified Versions: | Category: | --- | |||||||||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||
Embargoed: | |||||||||||||||||||||
Attachments: |
|
Description
Serge Pavlovsky
2009-10-26 20:40:52 UTC
Created attachment 366156 [details]
File: backtrace
I send this Bug report, If any more info is needed , please reply! F12 has the same version as for the previous fedora releases, hence it could be some compilation or environment-related bug. Unfortunately, currently I don't have any F12 system around me yet. Does this bug appear on F11 or F10 (with the same MN config)? i dont have older systems Sometime it even eat up 100% CPU on my system. Basically I uses a windows live mail (POP3) and Gmail. Well, how it is reproduced? Every time, or sometimes etc... While upstream sleeps, we could try to locate the issue. Could you test on what mailbox type it is happen - ie. try to configure MN to use pop3 only, then gmail only etc... and see how it influences? (In reply to comment #6) > Well, how it is reproduced? Every time, or sometimes etc... > > While upstream sleeps, we could try to locate the issue. Could you test on what > mailbox type it is happen - ie. try to configure MN to use pop3 only, then > gmail only etc... and see how it influences? It is the Win live mail with POP3. Gmail alone seems more stable. When the WLM cannot connect or the internet drop and reconnect, I press the icon to update (I set it in the settings), then it crashes. I searched out some ubuntu threads, they also have some instability of this piece of software. i dont even know when it happened, i just have record in abrt This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping *** Bug 537623 has been marked as a duplicate of this bug. *** *** Bug 539483 has been marked as a duplicate of this bug. *** *** Bug 539456 has been marked as a duplicate of this bug. *** *** Bug 524482 has been marked as a duplicate of this bug. *** It seems that something goes wrong since F12, but the source is not changed comparing to F11. We have "memory fault" errors at different code places... I'll try to contact upstream for this issue. Try to run MN from cmdline with malloc check set: MALLOC_CHECK_=2 mail-notification and provide backtrace if it aborted. Currently no more ideas... *** Bug 538287 has been marked as a duplicate of this bug. *** *** Bug 539627 has been marked as a duplicate of this bug. *** *** Bug 539629 has been marked as a duplicate of this bug. *** *** Bug 539984 has been marked as a duplicate of this bug. *** *** Bug 540109 has been marked as a duplicate of this bug. *** *** Bug 540645 has been marked as a duplicate of this bug. *** *** Bug 541047 has been marked as a duplicate of this bug. *** *** Bug 541487 has been marked as a duplicate of this bug. *** *** Bug 542904 has been marked as a duplicate of this bug. *** *** Bug 542930 has been marked as a duplicate of this bug. *** *** Bug 543361 has been marked as a duplicate of this bug. *** *** Bug 543462 has been marked as a duplicate of this bug. *** *** Bug 543617 has been marked as a duplicate of this bug. *** *** Bug 543896 has been marked as a duplicate of this bug. *** *** Bug 544058 has been marked as a duplicate of this bug. *** *** Bug 544606 has been marked as a duplicate of this bug. *** *** Bug 544859 has been marked as a duplicate of this bug. *** *** Bug 545613 has been marked as a duplicate of this bug. *** *** Bug 547262 has been marked as a duplicate of this bug. *** *** Bug 547273 has been marked as a duplicate of this bug. *** *** Bug 548220 has been marked as a duplicate of this bug. *** *** Bug 548809 has been marked as a duplicate of this bug. *** *** Bug 550159 has been marked as a duplicate of this bug. *** *** Bug 550202 has been marked as a duplicate of this bug. *** There is no response from the upstream author. Hence I would recommend to swicth to gnubiff or some other mail notification tools, until someone will solve this issue. It could be very useful if someone can run: MALLOC_CHECK_=2 mail-notification from cmdline, and attach gdb backtrace here... *** Bug 550275 has been marked as a duplicate of this bug. *** *** Bug 550894 has been marked as a duplicate of this bug. *** *** Bug 550970 has been marked as a duplicate of this bug. *** *** Bug 551208 has been marked as a duplicate of this bug. *** Ok, I'm running MALLOC_CHECK_=2 mail-notification from the cmdline, will update when/if if cores again. *** Bug 551885 has been marked as a duplicate of this bug. *** *** Bug 552145 has been marked as a duplicate of this bug. *** Not sure this is the same crash, let me know if it's not and I'll report a new bug. rbinkhorst@buffy autofs.null.pointer.reference]$ MALLOC_CHECK_=2 mail-notification (mail-notification:26522): GLib-GObject-CRITICAL **: g_object_class_find_property: assertion `G_IS_OBJECT_CLASS (class)' failed (mail-notification:26522): GLib-GObject-CRITICAL **: g_param_spec_get_name: assertion `G_IS_PARAM_SPEC (pspec)' failed Segmentation fault (core dumped) Backtrace will be attached shortly. Created attachment 381783 [details]
Backtrace
*** Bug 552315 has been marked as a duplicate of this bug. *** *** Bug 552678 has been marked as a duplicate of this bug. *** For comment #47: It is yet another SIGSEGV crash... I hoped to catch some malloc-related bug, bu specifying MALLOC_CHECK_=2, which causes program to abort() at the appropriate peace of code. But we see SIGSEGV instead of SIGABRT... In other words, it looks like not malloc-related issue. Sad... Any other ideas? (Upstream still stalled, other distros have no any patches for this yet...) *** Bug 553937 has been marked as a duplicate of this bug. *** *** Bug 554216 has been marked as a duplicate of this bug. *** *** Bug 555342 has been marked as a duplicate of this bug. *** *** Bug 559748 has been marked as a duplicate of this bug. *** *** Bug 562464 has been marked as a duplicate of this bug. *** *** Bug 562653 has been marked as a duplicate of this bug. *** *** Bug 565401 has been marked as a duplicate of this bug. *** Would this be the same as this upstream bug: https://bugs.launchpad.net/mail-notification/+bug/248125 --------- From upstream bug ------------- 0x08074333 in mn_g_object_clone (object=0xb5f12180, property_name=0x8097939 "flags") at src/mn-util.c:1179 1179 g_value_init(¶meter->value, G_PARAM_SPEC_VALUE_TYPE(pspec)); --------- From my backtrace ------------- #0 mn_g_object_clone (object=0x12b5000, property_name=<value optimized out>) at src/mn-util.c:1179 1179 g_value_init(¶meter->value, G_PARAM_SPEC_VALUE_TYPE(pspec)); ------------------------------------------ From the author: "It looks like an invalid object is passed to mn_g_object_clone(), but looking at the code and at the backtrace I have no idea why. If you're able to reproduce this crash, could you please run MN from a terminal with the -i option and send me the resulting output?" I'm also running mn with the -i flag now to gather more information on what I'm seeing. Comment ----- I think I lost network connectivity when this crashed. *** Bug 573051 has been marked as a duplicate of this bug. *** How to reproduce ----- 1. have mail-notification setup to check several accounts, including google mail and other IMAP accounts. 2. configure mail-notification to start on gnome session login 3. login to gnome, mail-notification will fail to connect to one or more accounts and crash Thanks. Is it a stably reproduced? Could you report this at the upstream site? See https://bugs.launchpad.net/mail-notification/+bugs It seems that the upstream development is stalled long ago, but such a report could help others who try to solve this issue. Interesting since my mail-notification just monitors a local mbox that I sync with offlineimap. And it's just one account. I don't think my crashes have anything to do with network, IMAP or login to accounts since it also crashes on a simple local mbox. Having said that I have no solution either so I hope your upstream report uncovers the underlying problem. Any thoughts on the relation to the bug I mentioned before? https://bugs.launchpad.net/mail-notification/+bug/248125 *** Bug 577849 has been marked as a duplicate of this bug. *** Comment ----- I'm not sure if is reproducible, but I switched from a Compiz-enabled desktop to GNOME shell from the "Desktop Effects" panel, and it crashed. How to reproduce ----- 1. Do nothing Comment ----- Nothing, just crashed Comment ----- Switch from gnome-shell to compiz. *** Bug 583686 has been marked as a duplicate of this bug. *** *** Bug 586402 has been marked as a duplicate of this bug. *** *** Bug 587064 has been marked as a duplicate of this bug. *** *** Bug 588587 has been marked as a duplicate of this bug. *** *** Bug 589077 has been marked as a duplicate of this bug. *** *** Bug 590533 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-18.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- I used the desktop effects dialog to switch from compiz to gnome shell. Package: mail-notification-5.4-18.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Seems to happen if you mess about changing desktop effects settings for long enough. Changing to F13: This is definitely still present in the current release. Ok, I can reliably duplicate it: I start off in compiz mode. I have configured it to check a single GMail account and there is one unread message in my inbox. I have the click action configured to update the status: System --> Prefs --> Mail Notification --> Status Icon --> Click Action --> Update the mail status The icon should be in the notification area showing one unread message. Now switch from compiz to gnome-shell. After it changes, click on the mail-notification icon. Bam! Crashes every time. This is where it crashes: Thread 1 (Thread 2476): #0 mn_mail_icon_set_tip_widget (self=0x0, tip_widget=0x1afe320 [GtkVBox]) at build/src/mn-mail-icon.c:789 No locals. #1 0x0000000000425de5 in mn_shell_update_tooltip (self=0x1947110 [MNShell]) at build/src/mn-shell.c:1065 vbox = 0x1afe320 [GtkVBox] From what I can see, mn_shell_update_tooltip() passes self->icon into mn_mail_icon_set_tip_widget() and after you change desktop modes from gnome-shell to compiz or the other way round, self->icon is always null. I've tried checking for null, but that just feels like a band-aid to cover up something more fundamental and I lack the ability to debug this further. All the GObject stuff is popping my head. :-( *** Bug 592263 has been marked as a duplicate of this bug. *** Right, so just spent another couple of hours slaving over a hot debugger trying to figure this out. I apologise in advance for incorrect or confusing terminology -- this is absolutely my first exposure to raw GTK and GObject. Here's what I think is happening: 1. The icon is created and mn_shell->icon is a pointer to it. That is made a weak reference. 2. When you switch window managers between compiz and gnome-shell, the mail-notification applet is terminated (we get a destroy signal from the icon.) This doesn't happen when switching between metacity and compiz. Don't ask me why. 3. In the handler for the destroy signal, we just go right ahead and construct another icon. The mn_shell->icon pointer now points to our new icon. This seems to work fine (the applet reappears in the new window manager.) 4. In the mean time, GTK queues up a delete event to dispose of the old icon in the event dispatch thread. This tries to nullify all the weak references to the old icon, which of course includes mn_shell->icon that now points to our new icon. Disaster! The pointer to the new icon is now null, so all further updates fail in obvious spectacular fashion. See stack traces above, etc. Now I just need to figure out how to fix it... Ok, that was easier than I thought it would be (thank the gods!) Please find attached a new mail-notification patch and a patch for your SPEC file. This works for me, please give it try and see if it works for you. :-) Created attachment 414679 [details]
Mail Notification patch to fix crash when switching window managers.
Created attachment 414680 [details]
Patch to add the above patch to the Mail Notification SPEC file.
Just in case it matters, these patches are against the F-13 branch. For what it's worth, the applet was crashing on me constantly back when I was still trying to use it. (long time ago) I only use Gnome, never Compiz. So whatever Mat Booth may have just fixed is probably not what brought me to this bugzilla. (In reply to comment #86) > For what it's worth, the applet was crashing on me constantly back when I was > still trying to use it. (long time ago) I only use Gnome, never Compiz. So > whatever Mat Booth may have just fixed is probably not what brought me to this > bugzilla. The patch I have attached to this ticket should fix the problem originally reported. It's probably just coincidence that the crash can be reproduced by switching window managers -- I've got no idea what other circumstances can cause GNOME to dispose a tray icon. So once again, I'd appreciate it if someone can try my patch. I can build and host an RPM, if anybody would like. If an RPM could be made for F12, I'd be willing to give it a try. It won't take me long to discover whether the crash I was experiencing is still happening. (In reply to comment #88) > If an RPM could be made for F12, I'd be willing to give it a try. It won't take > me long to discover whether the crash I was experiencing is still happening. Please pick your architecture from this scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=2199851 Note that I don't have any F12 boxes, so I haven't tested this build myself. *** Bug 593603 has been marked as a duplicate of this bug. *** A build for F13 is ready: http://kojipkgs.fedoraproject.org/packages/mail-notification/5.4/20.fc13/ It includes Mat Booth's patch as well. Please check whether it improves the situation for F13 or not. (In reply to comment #91) > A build for F13 is ready: > http://kojipkgs.fedoraproject.org/packages/mail-notification/5.4/20.fc13/ > > It includes Mat Booth's patch as well. > > Please check whether it improves the situation for F13 or not. Thanks for applying my patch. That build has fixed the compiz->gnome-shell crash on F13 for me. :-) Package: mail-notification-5.4-18.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.update the applet 2. 3. *** Bug 597148 has been marked as a duplicate of this bug. *** *** Bug 605268 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-20.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Apparently, mail-notification crashed as it was autopatically checking for new mail. Package: mail-notification-5.4-20.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- I have the mail-notification to check for new mail when clicking the tray icon. I click the tray icon to check for new mail, and it crashes. Package: mail-notification-5.4-20.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Had received one message and read it. I think that another message came in soon after that. Around that time mail-notification crashed. *** Bug 608565 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-20.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- mail-notification just crashed. Package: mail-notification-5.4-20.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Crashed doing automatic mail check. Bug 605268 and bug 597148 are crashes in mn_shell_unix_quit_signal_watch_cb whereas this bug was a crash in mn_mail_icon_set_tip_widget. Are you sure they are duplicates of this one? This bug ticket collects all the crashes. According to all the backtraces, there are a lot of places where it happens. Upstream still stalled. *** Bug 609683 has been marked as a duplicate of this bug. *** *** Bug 610927 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-21.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- mail-notification crashed again, doing an automatic mail check. I have it checking 5 custom smtp (pop) mail accounts, no gmail. Package: mail-notification-5.4-21.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- mail-notification crashed while doing the automatic check. *** Bug 612656 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-21.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Logged into Gnome. I think it crashed doing an automatic mail check. *** Bug 613295 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-21.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Automatic check. Package: mail-notification-5.4-21.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Automatic check. *** Bug 614458 has been marked as a duplicate of this bug. *** *** Bug 614733 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-21.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Crashed on automatic smtp mail check. *** Bug 614940 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-21.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Crashed again doing an automatic mail check on 5 POP smtp mail accounts. *** Bug 615975 has been marked as a duplicate of this bug. *** *** Bug 616306 has been marked as a duplicate of this bug. *** *** Bug 617135 has been marked as a duplicate of this bug. *** *** Bug 619563 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-21.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Restart the computer 2. When the desktop appears, the mai-notification icon will appear on the toolbar, but it will be blinking. 3. *** Bug 622337 has been marked as a duplicate of this bug. *** *** Bug 622027 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-21.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Inet comes back, mail-notification go away 2. 3. Package: mail-notification-5.4-21.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Another mail-notificaton crash. *** Bug 624766 has been marked as a duplicate of this bug. *** *** Bug 626221 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-21.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Automatic mail check. Package: mail-notification-5.4-21.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Crash on automatic check. Package: mail-notification-5.4-21.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Network gone, mail-notification too 2. 3. Package: mail-notification-5.4-21.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Start mail-notification 2.restart Networkmanager 3.click update Package: mail-notification-5.4-21.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Internet connection was dropped. Satellite ISP. 2. 3. *** Bug 628150 has been marked as a duplicate of this bug. *** *** Bug 628155 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-21.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Start mail-notification 2.restart Networkmanager 3.click update Package: mail-notification-5.4-21.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.net comes mail-notification gone 2. 3. *** Bug 630399 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-21.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Start program, with no net 2.Turn on net 3. Package: mail-notification-5.4-21.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Crashed while I was away. Satellite ISP may have dropped connection. Package: mail-notification-5.4-21.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Notbook is comes back from hibernate 2. Net is becomes available 3. mail-notification gone Package: mail-notification-5.4-21.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) Comment ----- Bug before and after upgrade from Fedora 10 to 13. *** Bug 635693 has been marked as a duplicate of this bug. *** Dmitry: What about the patch Mat posted? Are you going to apply it? Seems it may help with at least some crashes. Ahh, sorry it seems we have it, I should have looked into spec file first. I've configured mail-notification to check a single local Maildir directory. I never change between compiz and gnome-shell. I never click on the tray icon. In fact, I never do anything relevant at all. The crash normally happens when I'm asleep and not using the computer. I get up in the morning and see the crash report. This has happened across several releases, though it does seem to crash slightly less often now (F12 on x86_64). It is possible that the network goes down and comes back up when the crash occurs. It's certainly not related to any user action on my part. I am seeing it every new start of OS - my theory is that mail-notification checks email sooner that wi-fi connection is established (m-n should probably ask NetworkManager for connection information status first), and then crashes. (In reply to comment #144) > Dmitry: What about the patch Mat posted? Are you going to apply it? Seems it > may help with at least some crashes. My patch has been applied. It fixed the nautilus->gnome-shell crash. Unfortunately I haven't been able to reproduce any other crash. It never crashes for me now... :-/ Package: mail-notification-5.4-21.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Internet connection may have dropped. 2. 3. Package: mail-notification-5.4-21.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Crashed around the time that the Gnome desktop loaded after login. 2. 3. *** Bug 637637 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-21.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- message name resolition impossible (use pop.free.fr) with a wifi connection *** Bug 639822 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-21.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Apparently due to a DNS issue on boot Package: mail-notification-5.4-21.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Mail-notification crashed while trying to update after a DNS misconfiguration 2. 3. Package: mail-notification-5.4-21.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Satellite ISP was not operational. 2.Internet connection was restored. 3.Crash happened within 1 or 2 minutes of restored connection. Package: mail-notification-5.4-21.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Machine was idle. Satellite ISP may have had an interrupt. 2. 3. I just tried to investigate this bug. I'm only using the evolution backend of mail-notification and not encountering the crashes mentioned in this bug report. Could somebody who can reproduce this crash perform the following command: MALLOC_CHECK_=2 G_SLICE=always-malloc G_DEBUG=fatal-criticals mail-notification When the program crashes a new stacktrace should be generated by abrt. Please add this new stacktrace to this bug report. Further I would like you know more about how you people have configured mail-notification. What type of accounts are configured, the number of mailboxes and the number of unread mails which are in those mailboxes at the moment of the crash Package: mail-notification-5.4-21.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Start KDE4 2. 3. Could anybody who's having this problem please execute the following command and report back the output once the program has crashed: MALLOC_CHECK_=2 G_SLICE=always-malloc G_DEBUG=fatal-criticals mail-notification --enable-info Thanks in advance *** Bug 643230 has been marked as a duplicate of this bug. *** (In reply to comment #160) > Could anybody who's having this problem please execute the following command > and report back the output once the program has crashed: > > MALLOC_CHECK_=2 G_SLICE=always-malloc G_DEBUG=fatal-criticals mail-notification > --enable-info > > Thanks in advance newman ~ $ MALLOC_CHECK_=2 G_SLICE=always-malloc G_DEBUG=fatal-criticals mail-notification Segmentation fault (core dumped) Sorry... How to reproduce: Disconnect from internet, start m-n, m-n shows it can't connect to remote servers (e.g. IMAP), turn connection on, select "Update" from m-n applets's context menu -> crash. Reproducible for you? *** Bug 643829 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-16.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. could not retrieve emails, hostname resolution failed (because of no internet connection) 2. press update 3. nothing happend, until it crashes Any viable option to m-n (except gnu-biff)? Package: mail-notification-5.4-16.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1.Net come back 2. 3. I ran the command MALLOC_CHECK_=2 G_SLICE=always-malloc G_DEBUG=fatal-criticals mail-notification It crashed after several days, saying GLib-GObject-CRITICAL **: g_object_class_find_property: assertion `G_IS_OBJECT_CLASS (class)' failed I've appended the backtraces from the core file. I'll save the core file for a while in case it can provide any more information. I configured mail-notification to read a single mailbox in the Maildir format. I don't know how many messages were in the mailbox at the point when mail-notification crashed; it was somewhere between 0 and 110. Thread 4 (Thread 10101): #0 0x00000035b7ad5353 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00000035b963ca0c in g_main_context_poll (context=0x1316c10, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2904 #2 g_main_context_iterate (context=0x1316c10, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2586 #3 0x00000035b963d075 in IA__g_main_loop_run (loop=0x131eb90) at gmain.c:2799 #4 0x00000035c3247560 in link_io_thread_fn (data=<value optimized out>) at linc.c:396 #5 0x00000035b9662134 in g_thread_create_proxy (data=0x12d0d40) at gthread.c:635 #6 0x00000035b8606a3a in start_thread (arg=0x7f54c34f5710) at pthread_create.c:297 #7 0x00000035b7ade77d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #8 0x0000000000000000 in ?? () Thread 3 (Thread 10099): #0 0x00000035b7ad5353 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00000035b963ca0c in g_main_context_poll (context=0x1279f00, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2904 #2 g_main_context_iterate (context=0x1279f00, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2586 #3 0x00000035b963d075 in IA__g_main_loop_run (loop=0x128b680) at gmain.c:2799 #4 0x000000352334beb7 in IA__gtk_main () at gtkmain.c:1218 #5 0x000000000042c0a1 in main (argc=<value optimized out>, argv=<value optimized out>) at src/mn-main.c:542 Thread 2 (Thread 11880): #0 0x00000035b7ad5353 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00000035c962c73f in poll_func (ufds=0x1433850, nfds=2, timeout=-1, userdata=0x1360cd0) at pulse/thread-mainloop.c:75 #2 0x00000035c961cae6 in pa_mainloop_poll (m=0x1546350) at pulse/mainloop.c:879 #3 0x00000035c961dea9 in pa_mainloop_iterate (m=0x1546350, block=<value optimized out>, retval=0x0) at pulse/mainloop.c:961 #4 0x00000035c961df60 in pa_mainloop_run (m=0x1546350, retval=0x0) at pulse/mainloop.c:979 #5 0x00000035c962c64b in thread (userdata=0x14557b0) at pulse/thread-mainloop.c:94 #6 0x00000035ca238838 in internal_thread_func (userdata=0x13f1dd0) at pulsecore/thread-posix.c:72 #7 0x00000035b8606a3a in start_thread (arg=0x7f54b9fae710) at pthread_create.c:297 #8 0x00000035b7ade77d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #9 0x0000000000000000 in ?? () Thread 1 (Thread 19875): #0 0x00000035b7a326c5 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x00000035b7a33ea5 in abort () at abort.c:92 #2 0x00000035b964344a in IA__g_logv (log_domain=<value optimized out>, log_level=<value optimized out>, format=<value optimized out>, args1= 0x7f54c3ef59b0) at gmessages.c:549 #3 0x00000035b96434e3 in IA__g_log (log_domain=<value optimized out>, log_level=<value optimized out>, format=<value optimized out>) at gmessages.c:569 #4 0x00000035b9e0efcf in IA__g_object_class_find_property (class=0x1279f00, property_name=0x45079e "uri") at gobject.c:511 #5 0x000000000042d5d3 in mn_g_object_clone (object=0x15728e0, property_name= 0x45079e "uri") at src/mn-util.c:1173 #6 0x000000000043e596 in mn_vfs_message_new_from_message (message=0x15728e0, dir_uri=<value optimized out>, filename=<value optimized out>, flags= MN_MESSAGE_NEW) at build/src/mn-vfs-message.c:265 #7 0x0000000000431e03 in mn_maildir_mailbox_backend_scan_directory (self= 0x128b440 [MNMaildirMailboxBackend], check_id=1875, dir=<value optimized out>, new=1, messages=<value optimized out>, num_errors=<value optimized out>, err=0x7f54c3ef5cf8) at build/src/mn-maildir-mailbox-backend.c:294 #8 0x0000000000432154 in ___7_mn_maildir_mailbox_backend_check (backend= 0x128b440 [MNMaildirMailboxBackend], check_id=1875) at build/src/mn-maildir-mailbox-backend.c:378 #9 0x0000000000443076 in ___d_mn_vfs_mailbox_reentrant_check (mailbox= 0x12f2d60 [MNCustomVFSMailbox], check_id=1875) at build/src/mn-vfs-mailbox.c:651 #10 0x00000000004422f4 in mn_reentrant_mailbox_reentrant_check (info=0x156cee0) at build/src/mn-reentrant-mailbox.c:271 #11 mn_reentrant_mailbox_check_thread_cb (info=0x156cee0) at build/src/mn-reentrant-mailbox.c:246 #12 0x00000035b9662134 in g_thread_create_proxy (data=0x13c7380) at gthread.c:635 #13 0x00000035b8606a3a in start_thread (arg=0x7f54c3ef6710) at pthread_create.c:297 #14 0x00000035b7ade77d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #15 0x0000000000000000 in ?? () Package: mail-notification-5.4-16.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- Package: mail-notification-5.4-16.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Star program woth session startup 2. dhcp ip request takes too much time 3. mail-notification crash Just updated to F-14 and m-n is not crashing on every login as it used to. Perhaps update for other Fedora versions is a good idea. Thanks for the info, I give it a try! *** Bug 652589 has been marked as a duplicate of this bug. *** *** Bug 652608 has been marked as a duplicate of this bug. *** *** Bug 654079 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-25.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Démarrage du pc 2. 3. *** Bug 656025 has been marked as a duplicate of this bug. *** *** Bug 658112 has been marked as a duplicate of this bug. *** *** Bug 659162 has been marked as a duplicate of this bug. *** *** Bug 661225 has been marked as a duplicate of this bug. *** *** Bug 662150 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-25.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Come back from suspend 2. net come back 3. crash Package: mail-notification-5.4-25.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Went into screensaver 2. had crashed when I got back Comment ----- Maybe pc went to suspend which created network disconnect. I notice mail-notification crashes a lot when there is no network. Package: mail-notification-5.4-25.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Demarrage du pc 2. 3. Package: mail-notification-5.4-25.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. net go 2.net come 3. Package: mail-notification-5.4-25.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.boot 2. 3. Package: mail-notification-5.4-25.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. start program 2. no net connection 3. force update *** Bug 666741 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-25.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. net go net come 2. 3. Package: mail-notification-5.4-25.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. i connected PC to internet 2. pressed "Update" in mail notification icon 3. crash message appeared *** Bug 670513 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-25.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. net down 2. net come too connect 3. crash Comment ----- as usual :( Package: mail-notification-5.4-25.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Net connection flapping 2. 3. Package: mail-notification-5.4-25.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.It just happened in the backgound 2. 3. Package: mail-notification-5.4-25.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. not sure... just loged on, the crash happened after some seconds... Package: mail-notification-5.4-25.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. that's it... crash.. 2. 3. Package: mail-notification-5.4-25.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Can't connect to imap server 2. 3. Comment ----- Connect to imap server disabled by firewall, mail-notification crashed Package: mail-notification-5.4-25.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.unknown 2. 3. mail-notification-5.4-26.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/mail-notification-5.4-26.fc14 mail-notification-5.4-26.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. *** Bug 681186 has been marked as a duplicate of this bug. *** *** Bug 682501 has been marked as a duplicate of this bug. *** *** Bug 684223 has been marked as a duplicate of this bug. *** *** Bug 684527 has been marked as a duplicate of this bug. *** *** Bug 690188 has been marked as a duplicate of this bug. *** *** Bug 695146 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-26.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open a HD 720p BDRip with VLC 2. Crash 3. Package: mail-notification-5.4-26.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Just connect to net, with local dns 2. 3. Comment ----- The inet connection not worked, because I've not dns recursor. I started one, and mail-notification goes to death Package: mail-notification-5.4-26.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. come back from suspend 2. 3. *** Bug 702783 has been marked as a duplicate of this bug. *** *** Bug 704300 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-26.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Come back from hibernate 2. connect to net 3. crash Package: mail-notification-5.4-26.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. Estaba instalando OpenSuse en una máquina virtual con VMware Player. This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Please do not close this bug! It can be reproduce in the Fedora 14 too! *** Bug 710895 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-26.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. changing wifi interface IP address 2. 3. Package: mail-notification-5.4-26.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. The usual. Net goes, net come, crash 2. 3. Package: mail-notification-5.4-26.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Just click to upgrade, upgrade, upgrade, and crash 2. 3. Package: mail-notification-5.4-26.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.surfing net 2. 3. *** Bug 720125 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-26.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. just crash nothing extraordinary 2. 3. Package: mail-notification-5.4-41.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- during an update with no mail box configured Package: mail-notification-5.4-26.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Remove unused wireless module 2. no net, crash 3. Package: mail-notification-5.4-26.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. PC come back from suspend 2. Net come back 3. mail-notification crash Package: mail-notification-5.4-26.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. net goes, net come 2. crash 3. Package: mail-notification-5.4-41.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- i don't know why or how it crashed Package: mail-notification-5.4-41.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- I don't know how it crashed *** Bug 737601 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-26.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. using net 2. suspend, go other place 3. using net, changing ISP *** Bug 742148 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-26.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. using net 2. suspend, go other place 3. using net, changing ISP Package: mail-notification-5.4-45.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Editing a gmail account *** Bug 753516 has been marked as a duplicate of this bug. *** *** Bug 756289 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-26.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. using a wlan 2. suspend 3. using another wlan, crash *** Bug 758514 has been marked as a duplicate of this bug. *** Package: mail-notification-5.4-26.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Just turn on computer, and using 2. crash 3. Comment ----- i don't have any inet access at this time. *** Bug 759873 has been marked as a duplicate of this bug. *** *** Bug 765608 has been marked as a duplicate of this bug. *** *** Bug 784276 has been marked as a duplicate of this bug. *** *** Bug 785064 has been marked as a duplicate of this bug. *** *** Bug 796185 has been marked as a duplicate of this bug. *** Come back from sleep, crash backtrace_rating: 4 Package: mail-notification-5.4-48.fc16 OS Release: Fedora release 16 (Verne) Created attachment 566627 [details]
File: backtrace
Try to using without net backtrace_rating: 4 Package: mail-notification-5.4-48.fc16 OS Release: Fedora release 16 (Verne) Created attachment 569388 [details]
File: backtrace
*** Bug 804266 has been marked as a duplicate of this bug. *** loading pcb (pcb-0.20110918-3.fc16.x86_64) backtrace_rating: 4 Package: mail-notification-5.4-48.fc16 OS Release: Fedora release 16 (Verne) Created attachment 571979 [details]
File: backtrace
Come back from sleep. Net went, net came, mail-notification crash backtrace_rating: 4 Package: mail-notification-5.4-48.fc16 OS Release: Fedora release 16 (Verne) Created attachment 575705 [details]
File: backtrace
*** Bug 810621 has been marked as a duplicate of this bug. *** I terminated the gnome 3 session and this error appeared. backtrace_rating: 4 Package: mail-notification-5.4-55.fc17 OS Release: Fedora release 17 (Beefy Miracle) *** Bug 831524 has been marked as a duplicate of this bug. *** *** Bug 835458 has been marked as a duplicate of this bug. *** *** Bug 844053 has been marked as a duplicate of this bug. *** *** Bug 847543 has been marked as a duplicate of this bug. *** This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping *** Bug 866179 has been marked as a duplicate of this bug. *** *** Bug 870444 has been marked as a duplicate of this bug. *** *** Bug 877702 has been marked as a duplicate of this bug. *** *** Bug 879746 has been marked as a duplicate of this bug. *** *** Bug 889990 has been marked as a duplicate of this bug. *** *** Bug 894963 has been marked as a duplicate of this bug. *** *** Bug 907510 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 954656 *** |