[kmymoney] [Bug 457987] New: AqBanking - Benutzer anlegen funktioniert nicht
https://bugs.kde.org/show_bug.cgi?id=457987 Bug ID: 457987 Summary: AqBanking - Benutzer anlegen funktioniert nicht Product: kmymoney Version: 5.0.6 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: onlinebanking Assignee: kmymoney-de...@kde.org Reporter: katzepa...@gmx.de Target Milestone: --- Created attachment 151373 --> https://bugs.kde.org/attachment.cgi?id=151373&action=edit HBIC-Benutzer-Einrichtung SUMMARY AqBanking - Benutzer anlegen funktioniert nicht *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Einstellungen 2. AqBanking einrichten 3. Benutzer anlegen OBSERVED RESULT KMyMoney läuft durch ohne Fehlermeldung. Dann soll ich das Fenster schließen und dann habe ich die Wahl zwischen Weiter, dann läuft der Vorgang wieder durch oder Abbrechen und dann wird kein Benutzer anlegt. EXPECTED RESULT ein neuer Benutzer ist in der Liste angelegt SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION 11:01:49 Server-Zertifikat abrufen 11:01:49 Verbindung vorbereiten 11:01:49 Mit Server verbinden... 11:01:49 Using GnuTLS default ciphers. 11:01:49 TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD 11:01:49 Verbunden. 11:01:49 Verbindung beendet. 11:01:49 Zertifikat erhalten 11:01:49 Systemkennung abrufen 11:01:49 HBCI-Aufträge werden ausgeführt 11:01:49 AqHBCI gestartet 11:01:49 There are no tan method descriptions (yet), trying One-Step TAN. 11:01:49 Aufträge werden kodiert 11:01:49 Aufträge werden gesendet 11:01:49 Using GnuTLS default ciphers. 11:01:50 TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD 11:01:50 Warte auf Antwort 11:01:50 Antwort erhalten 11:01:50 HBCI: 3060 - Bitte beachten Sie die enthaltenen Warnungen/Hinweise. (M) 11:01:50 HBCI: 0020 - Auftrag ausgeführt. (S) 11:01:50 HBCI: 3050 - BPD nicht mehr aktuell, aktuelle Version enthalten. (S) 11:01:50 HBCI: 3920 - Zugelassene Zwei-Schritt-Verfahren für den Benutzer. (S) 11:01:50 HBCI: 0020 - Der Auftrag wurde ausgeführt. (S) 11:01:50 Dialog wurde nicht abgebrochen, PIN scheint gültig zu sein 11:01:50 Aufträge werden kodiert 11:01:50 Aufträge werden gesendet 11:01:50 Using GnuTLS default ciphers. 11:01:50 TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD 11:01:50 Warte auf Antwort 11:01:50 Antwort erhalten 11:01:50 HBCI: 0010 - Nachricht entgegengenommen. (M) 11:01:50 HBCI: 0100 - Dialog beendet. (M) 11:01:50 Dialog wurde nicht abgebrochen, PIN scheint gültig zu sein 11:01:50 AqHBCI abgeschlossen. 11:01:50 Anforderung der Kontenliste 11:01:50 HBCI-Aufträge werden ausgeführt 11:01:50 AqHBCI gestartet 11:01:50 There are no tan method descriptions (yet), trying One-Step TAN. 11:01:50 Aufträge werden kodiert 11:01:50 Aufträge werden gesendet 11:01:50 Using GnuTLS default ciphers. 11:01:50 TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD 11:01:50 Warte auf Antwort 11:01:51 Antwort erhalten 11:01:51 HBCI: 3060 - Bitte beachten Sie die enthaltenen Warnungen/Hinweise. (M) 11:01:51 HBCI: 3050 - BPD nicht mehr aktuell, aktuelle Version enthalten. (S) 11:01:51 HBCI: 3920 - Zugelassene Zwei-Schritt-Verfahren für den Benutzer. (S) 11:01:51 HBCI: 0020 - Der Auftrag wurde ausgeführt. (S) 11:01:51 Dialog wurde nicht abgebrochen, PIN scheint gültig zu sein 11:01:51 Aufträge werden kodiert 11:01:51 Aufträge werden gesendet 11:01:51 Using GnuTLS default ciphers. 11:01:51 TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD 11:01:51 Warte auf Antwort 11:01:51 Antwort erhalten 11:01:51 HBCI: 0010 - Nachricht entgegengenommen. (M) 11:01:51 HBCI: 0100 - Dialog beendet. (M) 11:01:51 Dialog wurde nicht abgebrochen, PIN scheint gültig zu sein 11:01:51 AqHBCI abgeschlossen. 11:01:51 Vorgang abgeschlossen, Sie können das Fenster nun schließen. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457987] AqBanking - Benutzer anlegen funktioniert nicht
https://bugs.kde.org/show_bug.cgi?id=457987 Sylvia changed: What|Removed |Added CC||katzepa...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457987] AqBanking - Benutzer anlegen funktioniert nicht
https://bugs.kde.org/show_bug.cgi?id=457987 --- Comment #2 from Sylvia --- Hallo Thomas, vielen, vielen Dank, dass Du so schnell geantwortet hast. Wie von Dir geraten, habe ich folgendes heruntergeladen (Installation war wohl nicht nötig): 64 bit * download portable package[1] (compressed archive with portable installation) [1][2] Datei.kmy ist angelegt.Geldinstitut DKB Girokonto ist angelegt. Unter Einstellungen gibt es kein AqBanking mehr (ich denke, das liegt an der neueren Version?).Rechte Maus auf das Konto und "Konto zuordnen" ausgewählt.Es erscheint eine Auswahl von "kbanking" und "ofximporter".ofximporter - In der Liste scheinen nur amerikanische Banken zu sein, DKB (Deutsche Kreditbank) ist nicht dabei.Deshalb kbanking angeklickt. Dann passiert nichts mehr. Es geht kein Fenster auf.Fehlt noch ein Plugin oder oder oder? Ich habe keinerlei IT-Kenntnisse, deshalb muss ich nachfragen. Im Handbuch ist leider auch nicht beschrieben, wie HBCI eingerichtet wird. Ich habe in vielen Foren versucht Antworten zu finden, aber leider beziehen die sich oft auf ältere Versionen und AqBanking soll ja nun im Tool implementiert sein. LG Sylvia *Gesendet:* Mittwoch, 17. August 2022 um 21:49 Uhr *Von:* "Thomas Baumgart" *An:* katzepa...@gmx.de *Betreff:* [kmymoney] [Bug 457987] AqBanking - Benutzer anlegen funktioniert nichthttps://bugs.kde.org/show_bug.cgi?id=457987 Thomas Baumgart changed: What |Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED |NEEDSINFO --- Comment #1 from Thomas Baumgart --- ich versuchs mal auf Deutsch: ich vermute, dass die Version 5.0.6 zu alt ist, weil "KMyMoney version 5.0.7 is now available. It provides online banking access according to the new PSD2 regulations". 5.0.6 kann also noch garnicht mit den neuen PSD2 Methoden umgehen. Versuche doch mal eine aktuellere Version. Die findest Du unter https://kmymoney.org/snapshots.php . Hilft das? -- You are receiving this mail because: You are on the CC list for the bug. You reported the bug. 1. https://download.opensuse.org/repositories/windows:/mingw:/win64:/snapshots/openSUSE_Leap_15.3/noarch/mingw64-kmymoney5-portable-5.1+20220812+git.5b03a22-lp153.198.2.noarch.rpm 2. https://kmymoney.org/snapshots.php#n1 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457987] AqBanking - Benutzer anlegen funktioniert nicht
https://bugs.kde.org/show_bug.cgi?id=457987 --- Comment #4 from Sylvia --- Dieser Beitrag ist aus dem Jahr 2012 und bezieht sich auf die KMyMoney Version 4.5.3-2. Das hatte ich im Internet auch schon gefunden. Hilft mir bei meiner Version 5.1.3 auf Windows10 in keinster Weise weiter. Danke, dass Sie jedesmal schnell geantwortet haben. Das halte ich Ihnen zugute. Aber für den Endnutzer ist dieses Tool dann doch wohl nicht geeignet, wenn es so schwierig ist Ihre Software lauffähig zu bekommen. Ich sollte wohl besser auf eine Alternative zurückgreifen. Vielen Dank nochmals und alles Gute.Sylvia *Gesendet:* Freitag, 19. August 2022 um 21:49 Uhr *Von:* "Ralf Habacker" *An:* katzepa...@gmx.de *Betreff:* [kmymoney] [Bug 457987] AqBanking - Benutzer anlegen funktioniert nichthttps://bugs.kde.org/show_bug.cgi?id=457987 Ralf Habacker changed: What |Removed |Added CC| |ralf.habac...@freenet.de --- Comment #3 from Ralf Habacker --- Auf https://www.linux-community.de/ausgaben/linuxuser/2012/02/home-banking-mit-kmymoney/ z.B. wird beschrieben, wie das Onlinebanking konfiguriert wird. -- You are receiving this mail because: You reported the bug. You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457987] AqBanking - Benutzer anlegen funktioniert nicht
https://bugs.kde.org/show_bug.cgi?id=457987 --- Comment #6 from Sylvia --- Hallo Ralf, Hallo Thomas, Ich habe es jetzt endlich geschafft. Es ließ mir doch keine Ruhe und so habe ich weiter nach dem Fehler gesucht. Letztendlich lag es an Resten der 1. Installation, die trotz CCCleaner nicht gelöscht wurden. Nun habe ich nur noch die portable Version und alles funktioniert. Vielen Dank für die Hilfe und Euer Engagement. VG Sylvia -- Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.Am 24.08.22, 17:38 schrieb Ralf Habacker : https://bugs.kde.org/show_bug.cgi?id=457987 Bug 457987 depends on bug 458133, which changed state. Bug 458133 Summary: Missing dokumentation for online banking https://bugs.kde.org/show_bug.cgi?id=458133 What |Removed |Added Status|REPORTED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug. You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439217] Change the wording in SDDM settings
https://bugs.kde.org/show_bug.cgi?id=439217 --- Comment #7 from Sylvia --- (In reply to Nate Graham from comment #6) > What sort of alternative wording would you suggest? Since it will be a plain text file, maybe «save» or »store»? «Export» could also work, I think. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439217] Change the wording in SDDM settings
https://bugs.kde.org/show_bug.cgi?id=439217 --- Comment #9 from Sylvia --- (In reply to Nate Graham from comment #8) > The fact that the action writes data to a file is an implementation detail > that the user will not know or care about. I don't think any of those > proposed changes are better than what we have now. :/ Well, since the user is likely to get the impression that his information might be sent somewhere else online, I think it's important they understand what that button actually does. Phrasing is important. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439217] Change the wording in SDDM settings
https://bugs.kde.org/show_bug.cgi?id=439217 --- Comment #13 from Sylvia --- (In reply to Nate Graham from comment #12) > See what you think of that ^ Perfect! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438241] Old splash screens don't show up
https://bugs.kde.org/show_bug.cgi?id=438241 --- Comment #2 from Sylvia --- (In reply to Nate Graham from comment #1) > Just splash screens, or other things too? > > Also, what do you mean by "Old" splash screens? When were they installed? > And did you use the Get New Stuff window to install them, or were they > installed by another method? I mean previously installed. Like, it will show the ones I just installed or from a few days ago but not from a week or two ago. I found the same with Plasma Styles, but now I'm experiencing issues in general with Get New Stuff so I'm not sure if it happens with other modules or not. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 438241] Old splash screens don't show up
https://bugs.kde.org/show_bug.cgi?id=438241 --- Comment #4 from Sylvia --- (In reply to Nate Graham from comment #3) > But were they installed from Get New Stuff, or from elsewhere? Yes, all my themes have been installed through Get New Stuff. I've been testing other items like Icons and Plasma themes, and I don't have the same problem. They all show all the themes installed and have an option to delete/uninstall. Now I can confirm this issue only affects Splash screens. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439217] New: Change the wording in SDDM settings
https://bugs.kde.org/show_bug.cgi?id=439217 Bug ID: 439217 Summary: Change the wording in SDDM settings Product: systemsettings Version: 5.22.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_sddm Assignee: k...@davidedmundson.co.uk Reporter: lailah...@gmail.com CC: k...@david-redondo.de, plasma-b...@kde.org Target Milestone: --- SUMMARY Most users will understand the phrase "synchronise settings" as an online activity, that is syncing your config against a user or server elsewhere. A better wording could prevent this confusion. OBSERVED RESULT Use of the word «synchronise» EXPECTED RESULT A better wording that makes the process and result clearer. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 KDE Spin (Linux kernel 5.12.12-300) (available in About System) KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439217] Change the wording in SDDM settings
https://bugs.kde.org/show_bug.cgi?id=439217 --- Comment #2 from Sylvia --- (In reply to David Edmundson from comment #1) > Was this how you associated it? Yes, I did. I went to the KDE Telegram group to ask. Some users there had no problem understanding what "synchronise settings" means, but others agreed that it could be confusing. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432157] New: Any plans to port it to iOS or iPadOS?
https://bugs.kde.org/show_bug.cgi?id=432157 Bug ID: 432157 Summary: Any plans to port it to iOS or iPadOS? Product: krita Version: 4.4.2 Platform: MacPorts Packages OS: macOS Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: lailah...@gmail.com Target Milestone: --- SUMMARY I noticed there are versions for Android & Mac, but not for iOS or iPadOS, though they're very popular for drawing & painting. ADDITIONAL INFORMATION Would you consider creating a version or port for these systems? I'm willing to help, with testing, coding or both. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432157] Any plans to port it to iOS or iPadOS?
https://bugs.kde.org/show_bug.cgi?id=432157 --- Comment #2 from Sylvia --- (In reply to Halla Rempt from comment #1) > Hi Sylvia, > > This is a bug tracker, not a support forum. And no, we are not planning a > port to iOS or iPadOS because Apple's terms for their app store are not > compatible with free and open source software. > > Please check > https://docs.krita.org/en/untranslatable_pages/reporting_bugs.html on what > is a bug and how bugs should be reported. I know perfectly well how a bug report works, I've been doing so for 15 years. Thank you very much. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438005] New: No delete button in Splash screen module
https://bugs.kde.org/show_bug.cgi?id=438005 Bug ID: 438005 Summary: No delete button in Splash screen module Product: systemsettings Version: 5.21.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: kcm_splashscreen Assignee: plasma-b...@kde.org Reporter: lailah...@gmail.com Target Milestone: --- SUMMARY There's no delete or uninstall button for splash screens, and the "installed themes" section only shows the newly installed. STEPS TO REPRODUCE 1. Open System Settings 2. Click on Appearance => Splash screen 3. Try to uninstall undesired or outdated splash screens OBSERVED RESULT EXPECTED RESULT No button or option to delete/uninstall SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 (available in About System) KDE Plasma Version: 5.21 KDE Frameworks Version: 5.82 Qt Version: Not available ADDITIONAL INFORMATION It's been a long time this issue is there. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438241] New: Old splash screens don't show up
https://bugs.kde.org/show_bug.cgi?id=438241 Bug ID: 438241 Summary: Old splash screens don't show up Product: systemsettings Version: 5.21.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: kcm_splashscreen Assignee: plasma-b...@kde.org Reporter: lailah...@gmail.com Target Milestone: --- SUMMARY Old or previously installed splash screens don't show up in the Installed list/tab from "Get new stuff" STEPS TO REPRODUCE 1. Open Get new Stuff 2. Select to show installed only 3. Check the splash screens in the list OBSERVED RESULT Splash screens listed as «installed» are much less than the actually installed ones EXPECTED RESULT Show ALL the installed splash screens SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 KDE Spin KDE Plasma Version: 5.21 KDE Frameworks Version: 5.82 Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415857] New: System Settings crashes when changing configuration
https://bugs.kde.org/show_bug.cgi?id=415857 Bug ID: 415857 Summary: System Settings crashes when changing configuration Product: systemsettings Version: 5.17.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lailah...@gmail.com Target Milestone: --- Application: systemsettings5 (5.17.4) Qt Version: 5.12.5 Frameworks Version: 5.64.0 Operating System: Linux 5.3.16-300.fc31.x86_64 x86_64 Distribution: Fedora 31 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: I was configuring different parts of my desktop such as Plasma style and Colours. If I switch between tabs or configure things too quickly the app will crash. Same if I'm trying looks and apply more than once different styles, the app will crash. No other strange behaviour is noticed. Not using Aurorae engine. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f39a7c17800 (LWP 2047))] Thread 13 (Thread 0x7f3978af1700 (LWP 2894)): #0 0x7f39abe38a6f in poll () from /lib64/libc.so.6 #1 0x7f39aa07a79e in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f39aa07a8d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f39ac3beda3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f39ac368cfb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f39ac1c13a5 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f39ab4a2119 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7f39ac1c24f6 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f39aa9cb4e2 in start_thread () from /lib64/libpthread.so.0 #9 0x7f39abe43693 in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7f397affd700 (LWP 2892)): #0 0x7f39abe38a6f in poll () from /lib64/libc.so.6 #1 0x7f39aa07a79e in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f39aa07a8d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f39ac3beda3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f39ac368cfb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f39ac1c13a5 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f39ab4a2119 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7f39ac1c24f6 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f39aa9cb4e2 in start_thread () from /lib64/libpthread.so.0 #9 0x7f39abe43693 in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7f3963fff700 (LWP 2193)): #0 0x7f39abe38a6f in poll () from /lib64/libc.so.6 #1 0x7f39aa07a79e in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f39aa07a8d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f39ac3beda3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f39ac368cfb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f39ac1c13a5 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f39ac1c24f6 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7f39aa9cb4e2 in start_thread () from /lib64/libpthread.so.0 #8 0x7f39abe43693 in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7f39792f2700 (LWP 2191)): #0 0x7f39abe38a6f in poll () from /lib64/libc.so.6 #1 0x7f39aa07a79e in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f39aa07a8d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f39ac3beda3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f39ac368cfb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f39ac1c13a5 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f39ac1c24f6 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7f39aa9cb4e2 in start_thread () from /lib64/libpthread.so.0 #8 0x7f39abe43693 in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7f3979d02700 (LWP 2190)): #0 0x7f39aa0c69d4 in g_mutex_lock () from /lib64/libglib-2.0.so.0 #1 0x7f39aa07a206 in g_main_context_check () from /lib64/libglib-2.0.so.0 #2 0x7f39aa07a742 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f39aa07a8d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f39ac3beda3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f39ac368cfb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f39ac1c13a5 in QThread::exec() (
[konsole] [Bug 375490] New: Konsole crashes
https://bugs.kde.org/show_bug.cgi?id=375490 Bug ID: 375490 Summary: Konsole crashes Product: konsole Version: 15.12.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: sgel...@rtr.tu-darmstadt.de Target Milestone: --- Application: konsole (15.12.3) Qt Version: 5.6.2 Frameworks Version: 5.26.0 Operating System: Linux 4.1.36-44-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: tried to oben the konsole from the starter in the panel, also with Alt-F2 it crashes. - Unusual behavior I noticed: I can't start also other programs from time to time. An Logout and restart of the windowmanager helps. The crash can be reproduced sometimes. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f33f08db800 (LWP 6698))] Thread 3 (Thread 0x7f33d5ae0700 (LWP 6700)): #0 0x7f33f020fbfd in poll () at /lib64/libc.so.6 #1 0x7f33e794b422 in () at /usr/lib64/libxcb.so.1 #2 0x7f33e794d00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f33dc041a59 in QXcbEventReader::run() () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f33ec5d3a29 in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #5 0x7f33e72f40a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f33f021802d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f33dcd29700 (LWP 6699)): #0 0x7f33e6bc0488 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7f33e6bc0d80 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f33e6bc0f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f33ec7e619b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f33ec793bbb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f33ec5cef5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f33ea9a3295 in QDBusConnectionManager::run() () at /usr/lib64/libQt5DBus.so.5 #7 0x7f33ec5d3a29 in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #8 0x7f33e72f40a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f33f021802d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f33f08db800 (LWP 6698)): [KCrash Handler] #6 0x7f33ec5bd4f7 in QList::~QList() () at /usr/lib64/libQt5Core.so.5 #7 0x7f33ec7db4e5 in (anonymous namespace)::clear(QVariant::Private*) () at /usr/lib64/libQt5Core.so.5 #8 0x7f33ea9a7a0c in QList::dealloc(QListData::Data*) [clone .isra.7] () at /usr/lib64/libQt5DBus.so.5 #9 0x7f33ea9bb6bb in QDBusMessage::~QDBusMessage() () at /usr/lib64/libQt5DBus.so.5 #10 0x7f33ea9ad92c in QDBusActivateObjectEvent::~QDBusActivateObjectEvent() () at /usr/lib64/libQt5DBus.so.5 #11 0x7f33ea9ad999 in QDBusActivateObjectEvent::~QDBusActivateObjectEvent() () at /usr/lib64/libQt5DBus.so.5 #12 0x7f33ec797993 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #13 0x7f33ec7e6af3 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /usr/lib64/libQt5Core.so.5 #14 0x7f33e6bc0c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #15 0x7f33e6bc0ed8 in () at /usr/lib64/libglib-2.0.so.0 #16 0x7f33e6bc0f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #17 0x7f33ec7e617c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #18 0x7f33ec793bbb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #19 0x7f33ec79baa6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #20 0x7f33f0503e87 in kdemain () at /usr/lib64/libkdeinit5_konsole.so #21 0x7f33f0154b25 in __libc_start_main () at /lib64/libc.so.6 #22 0x004007ee in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377277] New: Plasma refuses to open any application after a while being logged in as a user
https://bugs.kde.org/show_bug.cgi?id=377277 Bug ID: 377277 Summary: Plasma refuses to open any application after a while being logged in as a user Product: plasmashell Version: 5.8.6 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: sgel...@rtr.tu-darmstadt.de Target Milestone: 1.0 We have about 40 Opensuse Clients in our Network and switched lately from Opensuse 13.1 to Opensuse Leap 42.2. At the moment we are using the LTS Version of Plasma5: 5.8.6 but it also happened with older versions. When a user is logged in for quite a while it is not more possible to start any application graphically. When I try to start in a console, we always get this error equal which application (firefox, libreoffice, dolphin, konsole, ...) : testuser@test:~> thunderbird & [2] 3580 testuser@test:~> No protocol specified Error: cannot open display: :0 [2]+ Exit 1 thunderbird After relogin of the user everything works fine again. Not very practicable during the working day ;-) It is really an annoying bug for the users. We are using a NFS Fileserver (Debian Jessie) and for Single Sign on Authentication a LDAP Server (Debian Jessie). Unfortunately I can`t find anything in the logs like a crash or something. Please tell me what information you need to debug this behavior. Thanks! -- You are receiving this mail because: You are watching all bug changes.
