Processed: filelight: missing Breaks+Replaces: filelight-l10n

2018-10-24 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 + filelight-l10n
Bug #911783 [filelight] filelight: missing Breaks+Replaces: filelight-l10n
Added indication that 911783 affects filelight-l10n

-- 
911783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#911781: kmail and akoinadi not working correctly - deleted mails appear again

2018-10-24 Thread Hans-J. Ullrich
Package: kmail
Version: 4:18.08.1-1
Severity: important

Dear Maintainer,

sadlly the playing together between kamial and akonadi is going worse from 
version to version. 
At first, when you want to delete mails, the deletion was lasting a long time. 

Then soime versions later, mails in inbox folder could not be deleted when 
deleting them fast or if you wanted to delete several mails in one stap (mark 
all, then delete). Either kmail hanged in a loop or the delted mails appeared 
again, whgen you clicked anotherfolder, then clicking inbox again. Sometimes 
akonadi had to be complete restartetd , to get kmail initialised.

All these things I reported in the forums, but things did not imporove.

And today, there is this:

1. Move a bunsch of unread mails from inbox to trash in kamil.

2. Empty the trash.

3. Click on any other folkder i.e. inbox.

4. click now trash again.

5. Tadaaa! Most mails appear again!

Mails also appear after restart of kmail, restart akonadi or reboot. Even after 
some days they appear again!

I set this report to "important" because IMHO this is a security hole, too. 
Maybe I want to have important mnails deleted for security reasons or what ever 
- and then they are not gone? This is not good!

Please, if this is not a kmail problem, but an akonadi issue (what I can not 
verify), it would be nice, if you could inform those maintainers.

Thank you for reading and any help!


Best regards

Hans




  

-e System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.18.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kmail depends on:
ii  akonadi-server   4:18.08.1-1+b1
ii  kdepim-runtime   4:18.08.1-1
ii  kio  5.49.0-1
ii  libc62.27-6
ii  libgcc1  1:8.2.0-8
ii  libgpgmepp6  1.12.0-4
ii  libkf5akonadiagentbase5  4:18.08.1-1+b1
ii  libkf5akonadicontact54:18.08.1-1
ii  libkf5akonadicore5abi2   4:18.08.1-1+b1
ii  libkf5akonadimime5   4:18.08.1-2
ii  libkf5akonadisearch-bin  4:18.08.1-1+b1
ii  libkf5akonadisearch-plugins  4:18.08.1-1+b1
ii  libkf5akonadisearchdebug54:18.08.1-1+b1
ii  libkf5akonadisearchpim5  4:18.08.1-1+b1
ii  libkf5akonadiwidgets5abi14:18.08.1-1+b1
pn  libkf5bookmarks5 
ii  libkf5calendarcore5abi2  4:18.08.1-1
ii  libkf5calendarutils5 4:18.08.1-1
pn  libkf5codecs5
pn  libkf5completion5
pn  libkf5configcore5
ii  libkf5configgui5 5.49.0-1
ii  libkf5configwidgets5 5.49.0-1
ii  libkf5contacts5  4:18.08.1-1
ii  libkf5coreaddons55.49.0-1
ii  libkf5crash5 5.49.0-1
ii  libkf5dbusaddons55.49.0-1
ii  libkf5followupreminder5  4:18.08.1-1
ii  libkf5grantleetheme-plugins  18.08.1-1
ii  libkf5gravatar5abi2  4:18.08.1-1
ii  libkf5guiaddons5 5.49.0-1
ii  libkf5i18n5  5.49.0-1
ii  libkf5iconthemes55.49.0-1
ii  libkf5identitymanagement518.08.1-1
ii  libkf5itemmodels55.49.0-1
ii  libkf5itemviews5 5.49.0-1
ii  libkf5jobwidgets55.49.0-1
ii  libkf5kcmutils5  5.49.0-1
ii  libkf5kiocore5   5.49.0-1
ii  libkf5kiofilewidgets55.49.0-1
ii  libkf5kiowidgets55.49.0-1
ii  libkf5kontactinterface5  18.08.1-1
ii  libkf5ksieveui5  4:18.08.1-1
ii  libkf5libkdepim-plugins  4:18.08.1-1
ii  libkf5libkdepim5 4:18.08.1-1
ii  libkf5libkdepimakonadi5  4:18.08.1-1
ii  libkf5libkleo5   4:18.08.1-1
ii  libkf5mailcommon5abi24:18.08.1-1
ii  libkf5mailtransport5 18.08.1-2
ii  libkf5mailtransportakonadi5  18.08.1-2
ii  libkf5messagecomposer5abi1   4:18.08.1-1
ii  libkf5messagecore5abi1   4:18.08.1-1
ii  libkf5messagelist5abi1   4:18.08.1-1
ii  libkf5messageviewer5abi1 4:18.08.1-1
ii  libkf5mime5abi1  18.08.1-1
ii  libkf5mimetreeparser5abi14:18.08.1-1
ii  libkf5notifications5 5.49.0-1
ii  libkf5notifyconfig5  5.49.0-1
ii  libkf5parts5 5.49.0-1
ii  libkf5pimcommon5abi2 4:18.08.1-1
ii  libkf5pimcommonakonadi5abi1  4:18.08.1-1
ii  libkf5pimtextedit5abi2   18.08.1-1
ii  libkf5sendlater5 4:18.08.1-1
ii  libkf5service-bin5.49.0-1
ii  libkf5service5   5.49.0-1
ii  libkf5sonnetui5  5.49.0-1
ii  libkf5templateparser54:18.08.1-1
ii  libkf5textwidgets5   5.49.0-1
ii  libkf5tnef5  4:18.08.1-1
ii  libkf5wallet-bin 5.49.0-1
ii  libkf5wallet55.49.0-1
ii  libkf5webengineviewer5abi1   4:18.08.1-1

Bug#910852: libqt5webengine5: Akregator crashes very often, WebEngine related

2018-10-24 Thread Martin Steigerwald
Dmitry Shachnev - 19.10.18, 17:48:
> Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=400028
> 
> On Fri, Oct 19, 2018 at 11:49:45AM +0200, Martin Steigerwald wrote:
> > Unfortunately Akregator still crashes with Qt 5.11.2 packages.
> > 
> > Maybe heise.de is a quite good way to reproduce it, in case that
> > tracking script stuff is somehow related:
> > 
> > http://www.heise.de/open/news/news-atom.xml
> 
> I have reported this bug to Qt upstream, but they say it is not their
> bug, but a thread safety issue in libkf5webengineviewer5. So I have
> now filed a bug to KDE.

Here further links to upstream bug reports.

Bug which the bug 400028 you marked a duplicate of:

[Bug 371511] kontact/akregator crashes while trying to open a link from 
the
list (middle click)
https://bugs.kde.org/371511

Another upstream bug report:
[akregator] [Bug 397866] akregator crashes when closing the rightmost 
tab
https://bugs.kde.org/397866

Thanks
-- 
Martin



Processed: tagging 910873

2018-10-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 910873 - patch
Bug #910873 [src:calligra] calligra: FTBFS with poppler 0.69.0-1
Bug #911502 [src:calligra] calligra FTBFS 'memCheck' is not a member of 'Object'
Removed tag(s) patch.
Removed tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
910873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910873
911502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: tagging 910873, reassign 911502 to src:calligra, forcibly merging 910873 911502

2018-10-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 910873 - pending
Bug #910873 [src:calligra] calligra: FTBFS with poppler 0.69.0-1
Removed tag(s) pending.
> reassign 911502 src:calligra calligra/1:3.1.0+dfsg-3
Bug #911502 [calligra] calligra FTBFS 'memCheck' is not a member of 'Object'
Bug reassigned from package 'calligra' to 'src:calligra'.
No longer marked as found in versions calligra/1:3.1.0+dfsg-3.
Ignoring request to alter fixed versions of bug #911502 to the same values 
previously set
Bug #911502 [src:calligra] calligra FTBFS 'memCheck' is not a member of 'Object'
Marked as found in versions calligra/1:3.1.0+dfsg-3.
> forcemerge 910873 911502
Bug #910873 [src:calligra] calligra: FTBFS with poppler 0.69.0-1
Bug #911502 [src:calligra] calligra FTBFS 'memCheck' is not a member of 'Object'
Severity set to 'serious' from 'normal'
Added tag(s) ftbfs and patch.
Merged 910873 911502
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
910873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910873
911502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems