Created attachment 757 [details]
Evolution 3.1.91 missing message pane

Evolution 3.1.91 missing message pane

I am still having this problem and I can't convert my main laptop until it is resolved.  I could use GNOME (because it works under GNOME) but I am mostly a KDE user.  Any help would be welcome . . .

This still applies with evolution-3.1.92-1.mga2

Strangely, I have freshly installed now 4 different machines with Mageia Cauldron - coming from Mandriva Cooker.  On two of the machines I have this problem with existing /home folder and existing Evolution data - yes on one machine - Evolution works fine under KDE (converted from an existing .evolution folder)
I can not for the life of me figure out why!

(In reply to comment #3)
> This still applies with evolution-3.1.92-1.mga2
> 
> Strangely, I have freshly installed now 4 different machines with Mageia
> Cauldron - coming from Mandriva Cooker.  On two of the machines I have this
> problem with existing /home folder and existing Evolution data - yes on one
> machine - Evolution works fine under KDE (converted from an existing .evolution
> folder)
> I can not for the life of me figure out why!

I guess no one has a clue, and that that's why no one replied

cauldron has evolution-3.3.2-1.mga2 now

Is the problem still there with that version?

If so and if you use evolution for the same e-mail boxes on all 4 machines, does it help to uninstall evolution, replace your bugged .evolution (save that bugged one somewhere first) with the one from the machine without the problem and then reinstall evolution?

Keywords: (none) => NEEDINFO
CC: (none) => marja11
Summary: Evolution 3.1.91 has disply problems under KDE => Evolution 3.1.92 has display problems under KDE
Source RPM: evolution-3.1.91-1.mga2 => evolution-3.1.92-1.mga2

I can confirm that the problem still exists (on three separate machines) with latest Cauldron updates (evolution-3.3.2-1.mga2)

>If so and if you use evolution for the same e-mail boxes on all 4 machines,
>does it help to uninstall evolution, replace your bugged .evolution (save that
>bugged one somewhere first) with the one from the machine without the problem
>and then reinstall evolution?

I Tried that without improvement - same problem.  I am stuck using GNOME on the machines which I need mail - bummer.

Do you see any messages that could explain why it goes wrong when you start evolution in KDE from the command line in a console?

Is there any difference in the themes you use? Do you use gtk-qt, if so on which machine(s) ?

Keywords: NEEDINFO => (none)
Summary: Evolution 3.1.92 has display problems under KDE => Evolution 3.3.2 has display problems under KDE
Source RPM: evolution-3.1.92-1.mga2 => evolution-3.3.2-1.mga2

When I start evolution from a console in Gnome - no errors happen.

When I start evolution from a console in KDE - I get the following error about 30 times:

filter-CRITICAL **: e_filter_option_add: assertion `find_option (option, value) == NULL' failed

Nothing else.

I have removed ~/.kde and started the KDE desktop fresh (default settings) which does not help.  I tried with both gtk-qt and without - no change.

Very odd.

(In reply to comment #7)
> When I start evolution from a console in Gnome - no errors happen.
> 
> When I start evolution from a console in KDE - I get the following error about
> 30 times:
> 
> filter-CRITICAL **: e_filter_option_add: assertion `find_option (option, value)
> == NULL' failed
> 
> Nothing else.
> 

Well, at least that's a message that gives a lot of hits when you google it. I don't know what it means and I don't have time to check the google-hits now, though.

I forgot to ask (don't know whether it makes any difference, but to complete the report as much as possible): What kind of mailboxes do you have (imap/pop3)?

I will google that (did that before but could not find anything applicable)

Related to mailboxes - I have a mixture, on one machine mostly POP and the other mostly IMAP

I also get this error with IceWM.
I'm using pop3, and I'm having mailbox previously working with evolution 2.3. It seems that evolution 's migration process is having some troubles.

CC: (none) => nicolas

I've been looking at those google links, but the only one that at first sight seemed to be about the same problem, was about evolution 2.x. 

Searching bugzilla.gnome.org for:

filter-CRITICAL **: e_filter_option_add: assertion `find_option (option, value)
== NULL' failed

gave zarro bugs.

@ Nicolas
Do you have those missing message panes (see description and attachments), too

Yesterday at night I investigated further into this problem and have the following problems :

- with a user without any previous evolution use and stored mail, I get this exact problem. The message list doesn't seem to display, but when you click here and there mail body is displaying in the required frame.
- with a user with an existing .evolution directory (with mails, address etc...) on the first run the migration process seems to move everything to .local/share/evolution but once evolution launched, I can see subfolders' list but when clicking on it I get a frame with red border telling "folder_name doesn't exist" (when it obviously does).

I downloaded the source code to try self compilation but it request for gnome-desktop-3 package (and devel) which doesn't seem  to be included in mageia 2 alpha 1, or my repositories are not configured well.

(In reply to comment #12)

> I downloaded the source code to try self compilation but it request for
> gnome-desktop-3 package (and devel) which doesn't seem  to be included in
> mageia 2 alpha 1, or my repositories are not configured well.

Would that be gnome-desktop3-3.3.2-1.mga2.i586.rpm?

So without the dash after "gnome-desktop"

Summary: Evolution 3.3.2 has display problems under KDE => Evolution 3.3.2 has display problems under KDE and IceWM

I'll take a look at my configured repositories and try to install this as soon as I'm back home.

So with a home made evolution 3.3.2 I get exactly the same problem.

So maybe it has nothing to do directly with Evolution, but something with GTK or themes ??  Evolution works just fine under Gnome and XFE . . .  Something in KDE has changed which is causing this . . .

Is this ever gonna get fixed??  I have to use Gnome Classic (now that Gnome 3 is borked with the clutter problem - REAL slow!) - and I can't use KDE because of this bug - things are not looking good here.

@ Nicholas

Thanks for trying with a self-compiled evolution :) 

@ Robert

Yes, you're right, it is possible the bug isn't in Evolution itself. 

If we can help it, it'll get fixed.

Is there anything different about the graphic cards between your machines (with and without bug)?

@ Robert & Nicholas

Can you please try whether the bug is there too, with different themes?

cc'ing maintainers of KDE and of IceWM

@ mikala 
@ zezinho

Do you have any ideas?

CC: (none) => balcaen.john, lists.jjorge

Here is what I get .... worst than before :(

GConf-WARNING **: Client failed to connect to the D-BUS daemon:
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.
Erreur GConf : Aucun service D-BUS en cours d'exécution


** WARNING **: La connexion est fermée

** WARNING **: La connexion est fermée

** WARNING **: La connexion est fermée

GConf-WARNING **: Client failed to connect to the D-BUS daemon:
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.
Erreur GConf : Aucun service D-BUS en cours d'exécution


GConf-WARNING **: Client failed to connect to the D-BUS daemon:
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.
process 15736: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1200.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace
Abandon

I can't reproduce here.
Evolution is running fine here on a Cauldron with latest updates installed

CC: (none) => oliver.bgr

Created attachment 1424 [details]
Evolution without any problems

Are you trying this under KDE?

Robert> could you uninstall oxygen-gtk3 & try again please ?

@Robert: yes, KDE 4.7.97

@mikala: On my system oxygen-gtk3 is NOT installed, I will install it and test again.

Confirming: when oxygen-gtk3 is installed, I'm getting the same issues as the reporter. After uninstalling it again it works.

In the terminal I'm getting the following output when oxygen-gtk3 is installed:

----->   snip   <-----
[oli@beteigeuze ~]$ evolution                                                                                                               
                                                                                                                                            
evolution-mail-WARNING **: search_address_in_addressbooks: Unable to open addressbook 'Persönlich': Cannot open book: db error 0xffff8702 (DB_RUNRECOVERY: Fatal error, run database recovery)                                                                                          
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
Oxygen::WidgetLookup::find - context: 0x7f8a5e4bb9c0 type: MessageList - no match found
----->   snip   <-----

(In reply to comment #25)
> Confirming: when oxygen-gtk3 is installed, I'm getting the same issues as the
> reporter. After uninstalling it again it works.

Thanks a lot, Oliver :)

Changing the summary

cc'ing Hugo Pereira Da Costa (oxygen-gtk dev)

@ Hugo

Do you mind looking at this issue?

CC: (none) => hugo
Summary: Evolution 3.3.2 has display problems under KDE and IceWM => Evolution 3.3.2 has display problems with oxygen-gtk3

Yes will look into it. It's actually a duplicate of an existing bug on bugs.kde.org.
We're on it.

The corresponding KDE bug:

https://bugs.kde.org/show_bug.cgi?id=292278

THANK YOU - THANK YOU - THANK YOU!!

That fixed it!  Now I can go back to KDE !!  I've been using Gnome 3 since this bug was reported (but recently had to switch to Gnome Classic because Gnome 3 is REAL slow now!)

I am so glad we found the culprit!  Thanks again!

Note (to mageia packagers) that the "fix" proposed at https://bugs.kde.org/show_bug.cgi?id=292278 is a workaround, not a fix, and also affects other applications. So I'd advise against patching the code, and would rather wait for a proper fix (that only address the issue with evolution).

(In reply to comment #30)
> Note (to mageia packagers) that the "fix" proposed at
> https://bugs.kde.org/show_bug.cgi?id=292278 is a workaround, not a fix, and
> also affects other applications. So I'd advise against patching the code, and
> would rather wait for a proper fix (that only address the issue with
> evolution).

@ Hugo

Thanks a lot :)

@ Juancho

Despite having to wait for upstream to come with a proper fix, already assigning to you, because I think you're watching upstream and will know of a good fix faster than any bug squad member. Please assign back if you don't agree with this line of thought.

Keywords: (none) => UPSTREAM
Assignee: bugsquad => juan.baptiste

Not sure if this is related, but since I have removed oxygen-gtk3 - Evolution works fine now, but when I try and highlight text, there is no visual cue of the highlighting (it highlights but I can't see what I have highlighted!) - Strange

Anybody else have the highlighting problem described in previous comment (32?)

Yes, the problem seems to be, the Highlighting is using white colour as background, which can't be seen on white background.

Can I change the colors?

I don't know, I don't usually use evolution. But since it is a GNOME application, it should be changable via GNOME's equivalent of KDE's systemsettings (if there is such a thing).

(sorry for the noise don't know what happen :/)

Blocks: (none) => 4300

Created attachment 1504 [details]
Strange display without oxygen-gtk3

Created attachment 1505 [details]
Strange display without oxygen-gtk3

Since latest updates in Cauldron the display of Evolution is strange under KDE again (without oxygen-gtk3 installed) - I get black headers (see attachments) - but highlighting works now . . . one thing fixed, another broken.

For the oxygen-gtk3 issue, this is now fixed in repository (thanks to Ruslan Kabatsayev, the other main oxygen-gtk dev).

A new "minor" release of oxygen-gtk3 will appear on the servers tomorrow, which includes the fix.

  oxygen-gtk3-1.0.1

Good News, Bad News - the latest oxygen-gtk3 does fix the original problem, but as mentioned in comment #40 (and on the attached screenshots) - a new display problem is introduced.

Not sure if it is oxygen-gtk related, but just as annoying . . .

@Robert: in comment 40 you mention that this was "without oxygen-gtk3 installed". You confirm ? If yes, this is not an oxygen-gtk3 problem.

@Hugo - Agreed.  I had to remove oxygen-gtk3 to use Evolution in KDE until the fix was posted - and this other display issue exists with ot without oxygen-gtk3

Should I post a new bug??

Yes please.

Please test new oxygen rpm.

I have test the newest in Cauldron (oxygen-gtk-1.2.1-2.mga2) - no luck.

(In reply to comment #47)
> I have test the newest in Cauldron (oxygen-gtk-1.2.1-2.mga2) - no luck.
No, you should check oxygen-gtk3-1.0.1, especially liboxygen-gtk3-1.0.1

you have said it works with oxygen-gtk3 no ? so closing, thanks

the new bug still about evolution is bug 4544

Status: NEW => RESOLVED
Resolution: (none) => FIXED