[kmail2] [Bug 373136] New: attachments received not always shown when set to "Use Global Setting" - kmail 5.3.3

2016-12-01 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=373136 Bug ID: 373136 Summary: attachments received not always shown when set to "Use Global Setting" - kmail 5.3.3 Product: kmail2 Version: 5.3.2 Platform: openSUSE RPMs

[kmail2] [Bug 373189] New: Kmail2 v 5.3.3 - identify emails with attachments

2016-12-02 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=373189 Bug ID: 373189 Summary: Kmail2 v 5.3.3 - identify emails with attachments Product: kmail2 Version: 5.3.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED S

[kontact] [Bug 449597] Reminder not appearing on actual date (due to suspending actually dismissing the notification)

2022-02-12 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=449597 BingMyBong changed: What|Removed |Added CC||bingmyb...@btinternet.com Summary

[Reminder Daemon] [Bug 453298] kalendarac: Notifications miss option to remind later with other time duration than 5 minutes

2022-05-30 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=453298 BingMyBong changed: What|Removed |Added CC||bingmyb...@btinternet.com --- Comment #1 from

[Reminder Daemon] [Bug 455498] New: Reminder crashes on dismissal

2022-06-17 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=455498 Bug ID: 455498 Summary: Reminder crashes on dismissal Product: Reminder Daemon Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity:

[kmail2] [Bug 404052] Crash during/after filtering inbox, probably related to Qt WebEngine integration

2022-10-06 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=404052 BingMyBong changed: What|Removed |Added CC|bingmyb...@btinternet.com | -- You are receiving this mail because: You are

[plasmashell] [Bug 452075] Wallpaper reset to default and all widgets disappear after new start

2023-02-01 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=452075 --- Comment #24 from BingMyBong --- On Wednesday, 1 February 2023 10:13:11 GMT avery...@protonmail.com wrote: > https://bugs.kde.org/show_bug.cgi?id=452075 > > avery...@protonmail.com changed: > >W

[kdeplasma-addons] [Bug 465275] New: Inconsistent Weather Report V1.0 settings on different logins on the same machine

2023-02-04 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=465275 Bug ID: 465275 Summary: Inconsistent Weather Report V1.0 settings on different logins on the same machine Classification: Plasma Product: kdeplasma-addons Version: 5.26.90 Pl

[kdeplasma-addons] [Bug 465275] Inconsistent Weather Report V1.0 settings on different logins on the same machine

2023-02-04 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=465275 --- Comment #1 from BingMyBong --- Created attachment 155939 --> https://bugs.kde.org/attachment.cgi?id=155939&action=edit Appearance setting on Config on login 2 -- You are receiving this mail because: You are watching all bug changes.

[kmail2] [Bug 453240] kmail not downloading emails immediately on launch

2022-05-13 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=453240 --- Comment #3 from BingMyBong --- (In reply to Christophe Giboudeaux from comment #2) > In KMail settings, Accounts / Receiving there's a "Retrieval Options" menu > for each account, Is the "Check mail on startup" box

[Akonadi] [Bug 283682] KMail duplicates filtered messages

2022-04-27 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #231 from BingMyBong --- (In reply to r.kunschke from comment #228) > The problem is still present in kmail for a long time. I have filters for > using bogofilter in kmail. > Is there any workaround or something? Or a filter

[kmail2] [Bug 453240] New: kmail not downloading emails immediately on launch

2022-04-30 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=453240 Bug ID: 453240 Summary: kmail not downloading emails immediately on launch Product: kmail2 Version: 5.20.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Sev

[Reminder Daemon] [Bug 455498] Reminder crashes on dismissal

2022-06-20 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=455498 --- Comment #1 from BingMyBong --- Update: This also fails on Dismiss after you have pressed remind in 5 minutes a few times. My original report was for pressing Dismiss on its first reminder -- You are receiving this mail because: You are watching

[plasmashell] [Bug 452075] Wallpaper reset to default and all widgets disappear after new start

2022-08-23 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=452075 BingMyBong changed: What|Removed |Added CC||bingmyb...@btinternet.com Ever confirmed|0

[Reminder Daemon] [Bug 455498] Reminder crashes on dismissal

2022-08-25 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=455498 BingMyBong changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[kontact] [Bug 449597] Reminder not appearing on actual date (due to suspending actually dismissing the notification)

2022-03-09 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=449597 BingMyBong changed: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail

[plasmashell] [Bug 423864] Updated "Confirm Logout" setting not applied on logout until next login session

2021-02-01 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423864 --- Comment #5 from BingMyBong --- (In reply to David Edmundson from comment #3) > Fixed for 5.20 Hi, i'm using 5.20.5 and its still not working. i've tried removing the widget and reinstalling but its the same result, Logout = shutd

[plasmashell] [Bug 423864] Updated "Confirm Logout" setting not applied on logout until next login session

2021-02-01 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423864 --- Comment #6 from BingMyBong --- (In reply to BingMyBong from comment #5) > (In reply to David Edmundson from comment #3) > > Fixed for 5.20 > > Hi, i'm using 5.20.5 and its still not working. i've tried removing the >

[plasmashell] [Bug 363318] Lock / Logout Widget

2021-02-01 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=363318 BingMyBong changed: What|Removed |Added CC||bingmyb...@btinternet.com Resolution

[plasmashell] [Bug 424426] Logout defaults to shutting down once pressed

2021-02-01 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424426 BingMyBong changed: What|Removed |Added CC||richard.l...@gmail.com --- Comment #16 from

[plasmashell] [Bug 432511] shutdown icon stays even if configured to be not shown

2021-02-18 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=432511 BingMyBong changed: What|Removed |Added CC||bingmyb...@btinternet.com --- Comment #1 from

[plasmashell] [Bug 432511] shutdown icon stays even if configured to be not shown

2021-02-18 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=432511 --- Comment #2 from BingMyBong --- Created attachment 135816 --> https://bugs.kde.org/attachment.cgi?id=135816&action=edit Display of Lock only configured -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 432511] shutdown icon stays even if configured to be not shown

2021-02-18 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=432511 --- Comment #3 from BingMyBong --- Created attachment 135817 --> https://bugs.kde.org/attachment.cgi?id=135817&action=edit Display of Logout & Lock configured -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 432511] shutdown icon stays even if configured to be not shown

2021-02-18 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=432511 --- Comment #4 from BingMyBong --- Created attachment 135818 --> https://bugs.kde.org/attachment.cgi?id=135818&action=edit Display of Shutdown & Lock configured -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 423051] Usable taskbar appearing on SDDM login screen after logout

2021-02-18 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423051 BingMyBong changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[plasmashell] [Bug 424408] Multiple coredumps with every login/logout

2020-09-14 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424408 --- Comment #20 from BingMyBong --- My plasmashell crashes seem to have stopped. All i've done today is "KillUserProcesses=yes in /etc/systemd/logind.conf" and "sudo systemctl disable --now lvm2-monitor" and rebooted. I

[plasmashell] [Bug 424426] Logout defaults to shutting down once pressed

2020-09-15 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424426 --- Comment #2 from BingMyBong --- Same result in latest opensuse release Plasma 5.19.5 and Frameworks 5.73.0 opensuse:tumbleweed:20200910 Qt: 5.15.0 KDE Frameworks: 5.73.0 - KDE Plasma: 5.19.5 - kwin 5.19.5 kmail2 5.15.1 (20.08.1) - akonadiserver

[plasmashell] [Bug 424426] Logout defaults to shutting down once pressed

2020-09-17 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424426 BingMyBong changed: What|Removed |Added Version|5.19.3 |5.19.5 -- You are receiving this mail because

[kdeconnect] [Bug 438944] New: Cannot pair - no available devices

2021-06-20 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=438944 Bug ID: 438944 Summary: Cannot pair - no available devices Product: kdeconnect Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity:

[kdeconnect] [Bug 438944] Cannot pair - no available devices

2021-06-20 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=438944 --- Comment #2 from BingMyBong --- (In reply to Arnim Laeuger from comment #1) > I faced the same issue with the same configuration for current opensuse > tumbleweed: > - The desktop application kdeconnect-settings doesn't show any de

[kdeconnect] [Bug 438944] Cannot pair - no available devices

2021-06-20 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=438944 --- Comment #4 from BingMyBong --- (In reply to Arnim Laeuger from comment #3) > (In reply to BingMyBong from comment #2) > > I have > > multiple logins on my desktop and i paired with each one and my phone listed > > the devicenam

[kdeconnect] [Bug 438944] Cannot pair - no available devices

2021-06-20 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=438944 BingMyBong changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[kdeconnect] [Bug 438953] New: Connected/Rememberd Device lists on phone no longer shows desktop login ID

2021-06-20 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=438953 Bug ID: 438953 Summary: Connected/Rememberd Device lists on phone no longer shows desktop login ID Product: kdeconnect Version: unspecified Platform: openSUSE RPMs

[kdeconnect] [Bug 439031] New: Not getting any notifications of emails/sms etc from phone

2021-06-22 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=439031 Bug ID: 439031 Summary: Not getting any notifications of emails/sms etc from phone Product: kdeconnect Version: unspecified Platform: Other OS: Linux S

[kdeconnect] [Bug 439031] Not getting any notifications of emails/sms etc from phone

2021-06-22 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=439031 BingMyBong changed: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail

[kdeconnect] [Bug 439031] Not getting any notifications of emails/sms etc from phone

2021-07-03 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=439031 BingMyBong changed: What|Removed |Added CC||bingmyb...@btinternet.com -- You are receiving

[kdeconnect] [Bug 438953] Connected/Rememberd Device lists on phone no longer shows desktop login ID

2021-07-03 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=438953 BingMyBong changed: What|Removed |Added CC||bingmyb...@btinternet.com -- You are receiving

[kdeconnect] [Bug 439031] Not getting any notifications of emails/sms etc from phone

2021-07-07 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=439031 BingMyBong changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[kdeconnect] [Bug 438953] Connected/Rememberd Device lists on phone no longer shows desktop login ID

2021-07-07 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=438953 --- Comment #1 from BingMyBong --- WORKAROUND Rename default hostname in kdeconnect setting on desktop to a unique name for all logins that are connecting to phone. eg: Hostname-user1 Hostname-user2 Hostname-user3 -- You are receiving this mail

[frameworks-kglobalaccel] [Bug 423774] Coredump While Logging Out

2020-10-20 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423774 --- Comment #4 from BingMyBong --- Still happening with this release opensuse:tumbleweed:20201014 Qt: 5.15.1 KDE Frameworks: 5.75.0 - KDE Plasma: 5.20.0 - kwin 5.20.0 kmail2 5.15.2 (20.08.2) - akonadiserver 5.15.2 (20.08.2) - Kernel: 5.8.14-1

[plasmashell] [Bug 424426] Logout defaults to shutting down once pressed

2020-10-21 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424426 BingMyBong changed: What|Removed |Added Version|5.19.5 |5.20.1 --- Comment #3 from BingMyBong --- Still

[plasmashell] [Bug 424426] Logout defaults to shutting down once pressed

2020-10-21 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424426 --- Comment #5 from BingMyBong --- (In reply to David Edmundson from comment #4) > and just to confirm, if you do this from kickoff etc. everything works fine? Yes, i can logout normally via the menus. -- You are receiving this mail because: You

[frameworks-kglobalaccel] [Bug 423774] Coredump While Logging Out

2020-10-21 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423774 --- Comment #6 from BingMyBong --- (In reply to Yaroslav Sidlovsky from comment #5) > Looks like this bug somehow was caused by nouveau. > I see that Kamil Páral (from Fedora issue) using it too. (In reply to vindicator from comment #0) >

[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB

2020-10-27 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=389848 --- Comment #156 from BingMyBong --- (In reply to Nate Graham from comment #155) > *** Bug 427480 has been marked as a duplicate of this bug. *** good work with dealing with all the duplicates. this started in 2018 - anyone know why its not be

[plasmashell] [Bug 424408] New: Multiple coredumps with every login/logout

2020-07-19 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424408 Bug ID: 424408 Summary: Multiple coredumps with every login/logout Product: plasmashell Version: 5.19.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severi

[plasmashell] [Bug 424408] Multiple coredumps with every login/logout

2020-07-19 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424408 BingMyBong changed: What|Removed |Added CC||bingmyb...@btinternet.com -- You are receiving

[plasmashell] [Bug 424426] New: Logout defaults to shutting down once pressed

2020-07-19 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424426 Bug ID: 424426 Summary: Logout defaults to shutting down once pressed Product: plasmashell Version: 5.19.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Sev

[plasmashell] [Bug 424426] Logout defaults to shutting down once pressed

2020-07-19 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424426 BingMyBong changed: What|Removed |Added CC||bingmyb...@btinternet.com -- You are receiving

[plasmashell] [Bug 424408] Multiple coredumps with every login/logout

2020-07-23 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424408 --- Comment #2 from BingMyBong --- (In reply to Nate Graham from comment #1) > Can you attach a backtrace from one of the crash reports? The fact that > something is crashing over and over again is obviously a problem, but we > need to know th

[plasmashell] [Bug 424408] Multiple coredumps with every login/logout

2020-07-24 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424408 --- Comment #4 from BingMyBong --- (In reply to Christoph Feck from comment #3) > You can use gdb on a coredump file to get the backtrace. For details, > Hopefully, you didn't remove the all yet, and the binaries are still the > same. &g

[plasmashell] [Bug 424408] Multiple coredumps with every login/logout

2020-07-24 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424408 --- Comment #5 from BingMyBong --- Created attachment 130366 --> https://bugs.kde.org/attachment.cgi?id=130366&action=edit backtrace file Full backtrace -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 424408] Multiple coredumps with every login/logout

2020-07-24 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424408 --- Comment #6 from BingMyBong --- Created attachment 130367 --> https://bugs.kde.org/attachment.cgi?id=130367&action=edit backtrace file plasmashell 1 backtrace file plasmashell 1 -- You are receiving this mail because: You are watching

[plasmashell] [Bug 424408] Multiple coredumps with every login/logout

2020-07-24 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424408 --- Comment #7 from BingMyBong --- Created attachment 130368 --> https://bugs.kde.org/attachment.cgi?id=130368&action=edit backtrace file plasmashell 2 backtrace file plasmashell 2 -- You are receiving this mail because: You are watching

[plasmashell] [Bug 424408] Multiple coredumps with every login/logout

2020-07-24 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424408 --- Comment #8 from BingMyBong --- I've added 3 backtrace (full) files for the following files: gdb-drkonqi-backtrace-full gdb-plasmashell-3058-backtrace-full gdb-plasmashell-1548-backtrace-full They are for the following files i will attach the

[plasmashell] [Bug 424408] Multiple coredumps with every login/logout

2020-07-29 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424408 --- Comment #10 from BingMyBong --- (In reply to Nate Graham from comment #9) > Thanks. The backtraces are beyond my ability to interpret, so I'll hand it > off to other more experience devs at this point. Thanks. I'd like to add

[plasmashell] [Bug 424408] Multiple coredumps with every login/logout

2020-08-02 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424408 --- Comment #15 from BingMyBong --- (In reply to Nate Graham from comment #14) > I'm able to reproduce the same crash here in my everything-built-from-source > plasma session. I am seeing crashes in kglobalaccel and kactivitymanagerd. &

[okular] [Bug 425076] New: Print to File - can't print a specific page(s)

2020-08-06 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=425076 Bug ID: 425076 Summary: Print to File - can't print a specific page(s) Product: okular Version: 1.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severit

[okular] [Bug 425076] Print to File - can't print a specific page(s)

2020-08-06 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=425076 BingMyBong changed: What|Removed |Added CC||bingmyb...@btinternet.com -- You are receiving

[plasmashell] [Bug 424408] Multiple coredumps with every login/logout

2020-08-14 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424408 --- Comment #16 from BingMyBong --- Since yesterdays upgrade to plasma-frameworks 5.73, lots of the other coredumps from kglobalaccel5, kdeconnectd, kactivitymanage, klauncher etc have ceased. But i still get the logout coredumps from plasmashell and

[plasmashell] [Bug 424426] Logout defaults to shutting down once pressed

2020-08-14 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424426 --- Comment #1 from BingMyBong --- Same result in latest opensuse release Plasma 5.19.4 and Frameworks 5.73.0 opensuse:tumbleweed:20200812 Qt: 5.15.0 KDE Frameworks: 5.73.0 - KDE Plasma: 5.19.4 - kwin 5.19.4 kmail2 5.14.3 (20.04.3) - akonadiserver

[plasmashell] [Bug 422726] The shutdown / logout widget does not respond on first click

2020-08-14 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=422726 BingMyBong changed: What|Removed |Added CC||bingmyb...@btinternet.com --- Comment #10 from

[plasmashell] [Bug 422726] The shutdown / logout widget does not respond on first click

2020-08-14 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=422726 --- Comment #11 from BingMyBong --- (In reply to BingMyBong from comment #10) > (In reply to Andrey from comment #8) > > (In reply to tromzy from comment #3) > > > Actually it's not a Wayland-specific problem, since it also hap

[plasmashell] [Bug 424408] Multiple coredumps with every login/logout

2020-08-14 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424408 --- Comment #17 from BingMyBong --- (In reply to BingMyBong from comment #16) > Since yesterdays upgrade to plasma-frameworks 5.73, lots of the other > coredumps from kglobalaccel5, kdeconnectd, kactivitymanage, klauncher etc > have ceased. &

[plasmashell] [Bug 424408] Multiple coredumps with every login/logout

2020-08-15 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424408 --- Comment #19 from BingMyBong --- (In reply to BingMyBong from comment #17) > (In reply to BingMyBong from comment #16) > > Since yesterdays upgrade to plasma-frameworks 5.73, lots of the other > > coredumps from kglobalacce

[plasmashell] [Bug 424426] Logout defaults to shutting down once pressed

2020-11-06 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424426 --- Comment #7 from BingMyBong --- (In reply to Bug Janitor Service from comment #6) > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least > 15 days. Please provide the requested information as soon a

[plasmashell] [Bug 424426] Logout defaults to shutting down once pressed

2020-11-09 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424426 --- Comment #9 from BingMyBong --- (In reply to Christoph Feck from comment #8) > The Bug Janitor cannot know if the comment you added provides the requested > information; please change the status next time you do. > > New information wa

[plasmashell] [Bug 424408] Multiple coredumps with every login/logout

2020-11-15 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424408 --- Comment #33 from BingMyBong --- (In reply to Nate Graham from comment #31) > Is there more to do here, or can this be closed? I'm still getting coredumps but this could be a separate/new issue. I now get 9 instances of core.qdbus, one ins

[Akonadi] [Bug 476617] New: postgresql16 fails to run after DB update from postgresql13 - errors from akonadictl start

2023-11-06 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=476617 Bug ID: 476617 Summary: postgresql16 fails to run after DB update from postgresql13 - errors from akonadictl start Classification: Frameworks and Libraries Product: Akonadi Version: 5.2

[Akonadi] [Bug 476617] postgresql16 fails to run after DB update from postgresql13 - errors from akonadictl start

2023-11-06 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=476617 --- Comment #2 from BingMyBong --- (In reply to Christophe Marin from comment #1) > (In reply to BingMyBong from comment #0) > > There's a small misunderstanding here. Akonadi doesn't use the system > postgres but runs its own

[systemsettings] [Bug 447817] New: SDDM - "Others.." - no cursor placement

2022-01-02 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=447817 Bug ID: 447817 Summary: SDDM - "Others.." - no cursor placement Product: systemsettings Version: 5.23.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severi

[kmail2] [Bug 431539] New: Kmail crash after configuring Expire on a folder

2021-01-13 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=431539 Bug ID: 431539 Summary: Kmail crash after configuring Expire on a folder Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED

[kmail2] [Bug 431539] Kmail crash after configuring Expire on a folder

2021-01-13 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=431539 BingMyBong changed: What|Removed |Added Version|unspecified |5.16.1 -- You are receiving this mail because

[kmail2] [Bug 431539] Kmail crash after configuring Expire on a folder

2021-01-13 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=431539 --- Comment #1 from BingMyBong --- (In reply to BingMyBong from comment #0) "Retrieving messages..." should read "Retrieving Folder Contents" -- You are receiving this mail because: You are watching all bug changes.

[kmail2] [Bug 423385] New: Filtering leaves one email behind

2020-06-22 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423385 Bug ID: 423385 Summary: Filtering leaves one email behind Product: kmail2 Version: 5.14.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal

[plasmashell] [Bug 423391] New: Logout function no longer works

2020-06-23 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423391 Bug ID: 423391 Summary: Logout function no longer works Product: plasmashell Version: 5.19.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major

[plasmashell] [Bug 423391] Logout function no longer works

2020-06-23 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423391 BingMyBong changed: What|Removed |Added CC||bingmyb...@btinternet.com --- Comment #3 from

[plasmashell] [Bug 423391] Logout function no longer works

2020-06-23 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423391 --- Comment #7 from BingMyBong --- (In reply to David Edmundson from comment #4) > Found it :/ > > As a temporary workaround you can enable "confirm shutdown options" and > it'll work again I had to log out via the menu

[plasmashell] [Bug 423391] Logout function no longer works

2020-06-23 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423391 --- Comment #9 from BingMyBong --- (In reply to Paul from comment #8) > @BingMyBong > > Can't replicate that one... > > Left for the full 30sec countdown, system logs out. > > Log back in and repeated, several tim

[plasmashell] [Bug 423786] New: Lots of journal records related to sddm-greeter breeze "errors"

2020-07-02 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423786 Bug ID: 423786 Summary: Lots of journal records related to sddm-greeter breeze "errors" Product: plasmashell Version: 5.19.2 Platform: openSUSE RPMs OS: Linux

[frameworks-kglobalaccel] [Bug 423774] Coredump While Logging Out

2020-07-03 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423774 BingMyBong changed: What|Removed |Added CC||bingmyb...@btinternet.com --- Comment #1 from

[frameworks-kglobalaccel] [Bug 423774] Coredump While Logging Out

2020-07-03 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423774 --- Comment #2 from BingMyBong --- I can confirm this happens in opensuse:tumbleweed:20200622 (Qt: 5.15.0 KDE Frameworks: 5.71.0 - KDE Plasma: 5.19.1 - kwin 5.19.1 kmail2 5.14.2 (20.04.2) - akonadiserver 5.14.2 (20.04.2) - Kernel: 5.7.2-1-default

[systemsettings] [Bug 423863] New: Change to "Confirm Logout " is not applied until next login session

2020-07-04 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423863 Bug ID: 423863 Summary: Change to "Confirm Logout " is not applied until next login session Product: systemsettings Version: 5.19.2 Platform: Other OS: Linux

[systemsettings] [Bug 423863] Change to "Confirm Logout " is not applied until next login session

2020-07-04 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423863 BingMyBong changed: What|Removed |Added CC||bingmyb...@btinternet.com Platform

[systemsettings] [Bug 423863] Change to "Confirm Logout " is not applied until next login session

2020-07-04 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423863 BingMyBong changed: What|Removed |Added Resolution|--- |MOVED Status|REPORTED

[plasmashell] [Bug 423864] New: Updated "Confirm Logout" setting not applied on logout until next login session

2020-07-04 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423864 Bug ID: 423864 Summary: Updated "Confirm Logout" setting not applied on logout until next login session Product: plasmashell Version: 5.19.2 Platform: openSUSE RPMs

[plasmashell] [Bug 423864] Updated "Confirm Logout" setting not applied on logout until next login session

2020-07-04 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423864 --- Comment #1 from BingMyBong --- (In reply to BingMyBong from comment #0) > SUMMARY > Changing "Confirm Logout" is not immediately active, you have to logout, log > back in and then the confirmation change works as configured. >

[plasmashell] [Bug 423051] Usable taskbar appearing on SDDM login screen after logout

2020-07-05 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423051 --- Comment #1 from BingMyBong --- Created attachment 129915 --> https://bugs.kde.org/attachment.cgi?id=129915&action=edit Show taskbar on sddm login screen -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 423051] Usable taskbar appearing on SDDM login screen after logout

2020-07-05 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423051 BingMyBong changed: What|Removed |Added CC||bingmyb...@btinternet.com -- You are receiving

[plasmashell] [Bug 423051] Usable taskbar appearing on SDDM login screen after logout

2020-07-11 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423051 --- Comment #2 from BingMyBong --- I've also ex[rinced a full desktop after logging out and leaving the screen to go into screen saver mode at the login prompt. The only way out is Ctrl,Ctrl,Backspace and then reboot which clears things for

[kontact] [Bug 449597] New: Reminder not appearing on actual date

2022-02-04 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=449597 Bug ID: 449597 Summary: Reminder not appearing on actual date Product: kontact Version: 5.19.1 Platform: Other OS: Linux Status: REPORTED Severity: normal

[kmail2] [Bug 425531] New: Filter on incoming emails, leaves last one in inbox

2020-08-18 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=425531 Bug ID: 425531 Summary: Filter on incoming emails, leaves last one in inbox Product: kmail2 Version: 5.14.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Se

[kmail2] [Bug 425531] Filter on incoming emails, leaves last one in inbox

2020-08-19 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=425531 --- Comment #2 from BingMyBong --- (In reply to Wolfgang Bauer from comment #1) > Isn't this the same as bug#423385? > > *** This bug has been marked as a duplicate of bug 423385 *** oh damn.. apologies... -- You are receiving thi

[plasmashell] [Bug 424408] Multiple coredumps with every login/logout

2020-11-26 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424408 --- Comment #34 from BingMyBong --- I've "fixed" most of my coredumps on logout (replaced qdbus with qdbus-qt5) so i'm just left with these ones -rw-r-+ 1 root root 769148 Nov 26 15:58 cor

[plasmashell] [Bug 424426] Logout defaults to shutting down once pressed

2020-12-06 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424426 --- Comment #13 from BingMyBong --- (In reply to David Edmundson from comment #11) > Hypothetically, would it also fix your bug to have the lock/logout widgets > have explicit actions for shutdown and logout that you can enable/disable? If i

[kmail2] [Bug 365119] KMail 2 does not add distribution lists/contact groups from KAdressbook properly (simple word, not addresses), or names are wrong

2022-11-13 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=365119 BingMyBong changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO

[kwin] [Bug 15329] Placement policy 'Remember'

2022-11-28 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=15329 BingMyBong changed: What|Removed |Added CC||bingmyb...@btinternet.com --- Comment #77 from

[kmail2] [Bug 400567] Choosing mail signature from a file deletes the selected file causing data loss

2022-12-01 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=400567 BingMyBong changed: What|Removed |Added Version|5.9.2 |5.21.3 Component|general

[kmail2] [Bug 400145] New: Kmail Crash during manual filter

2018-10-22 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=400145 Bug ID: 400145 Summary: Kmail Crash during manual filter Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonq

[kmail2] [Bug 382102] kmail not checking for emails on startup

2018-10-26 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=382102 BingMyBong changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[kmail2] [Bug 398835] "Mark Thread Read" working as and when it feels like

2018-10-26 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=398835 --- Comment #2 from BingMyBong --- (In reply to BingMyBong from comment #1) > More Info: The emails left as unread (ie. blue text) are identified as > "read" (ie. black text) if you close kmail and reopen it so it just seems > th

  1   2   3   >