[Bug 1741931] Re: Cannot enable Jean-Yves Lefort's Mail Notification plugin in Evolution

2019-12-10 Thread Christian Romberg
I don't believe you'll ever get this bug fixed by just complaining about it here. Get someone assigned or do something yourself. That's how I think open source should work. A patch is above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1741931] Re: Cannot enable Jean-Yves Lefort's Mail Notification plugin in Evolution

2019-08-07 Thread Christian Romberg
Yes, see above. It’s not in the repos though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741931 Title: Cannot enable Jean-Yves Lefort's Mail Notification plugin in Evolution To manage

[Bug 1741931] Re: Cannot enable Jean-Yves Lefort's Mail Notification plugin in Evolution

2018-05-07 Thread Christian Romberg
I just noticed that my patch file is kinda back to front. So if you decide to use it, it will tell you that the file is already patched. But if you specify the option -R ("patch -R -p0 < mail-notification.diff"), things should work. My bad xD Anyways, here are patched deb packages. **

[Bug 1741931] Re: Cannot enable Jean-Yves Lefort's Mail Notification plugin in Evolution

2018-05-07 Thread Christian Romberg
And the mail-notification package... ** Attachment added: "mail-notification_5.4.dfsg.1-14build10_amd64.deb" https://bugs.launchpad.net/ubuntu/+source/mail-notification/+bug/1741931/+attachment/5135529/+files/mail-notification_5.4.dfsg.1-14build10_amd64.deb -- You received this bug

[Bug 1741931] Re: Cannot enable Jean-Yves Lefort's Mail Notification plugin in Evolution

2018-05-07 Thread Christian Romberg
Lol for the "I am very skilled" I'm (obviously) also not very skilled, at least I never really learned how to create patch files correctly. But at least I know for a fact that the patch I created was for the plugin source, not for the shared object file which you tried to patch. I think (don't

[Bug 1741931] Re: Cannot enable Jean-Yves Lefort's Mail Notification plugin in Evolution

2018-02-08 Thread Christian Romberg
Ok, chased those function names down and changed them all, and now the plugin loads successfully. However, a new error has arisen, which is that once I select "evolution" as the mail provider for mail- notification, it tries to embed a table with the available mail folders using a GtkSocket, which

[Bug 1741931] Re: Cannot enable Jean-Yves Lefort's Mail Notification plugin in Evolution

2018-02-08 Thread Christian Romberg
It seems I'm onto something. I changed the source files I got from apt, and I get a new message saying that the symbol camel_message_info_message_id was unavailable. I think I might be able to fix this -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1741931] Re: Cannot enable Jean-Yves Lefort's Mail Notification plugin in Evolution

2018-02-07 Thread Christian Romberg
I suspect the cause of this problem to be a function rename. I'm not 150% sure, but I think camel_message_info_uid got renamed to camel_message_info_get_uid. Can anyone confirm this? I tried recompiling the mail notification plugin but the build system is kinda broken and the source code I tried

[Bug 1741931] Re: Cannot enable Jean-Yves Lefort's Mail Notification plugin in Evolution

2018-01-25 Thread Christian Romberg
Same here. Also Ubuntu 17.10, same command line output -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741931 Title: Cannot enable Jean-Yves Lefort's Mail Notification plugin in Evolution To manage

[Bug 820709] Re: "Burn Several Disks' button doesn't work.

2018-01-19 Thread Christian Romberg
Same here, Ubuntu 17.04 with Brasero 3.12.1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/820709 Title: "Burn Several Disks' button doesn't work. To manage notifications about this bug go to: