[konversation] [Bug 478116] New: Konversation does not apply the color settings immediately
https://bugs.kde.org/show_bug.cgi?id=478116 Bug ID: 478116 Summary: Konversation does not apply the color settings immediately Classification: Applications Product: konversation Version: 1.9.23083 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: ircview Assignee: argo...@gmail.com Reporter: sascha.gas...@gmx.de CC: konversation-de...@kde.org Target Milestone: --- SUMMARY Konversation does not apply the color setting changes for the existing text but only for new text. The background color ist changed instantly but not the text. STEPS TO REPRODUCE 1. Change some color settings 2. Apply OBSERVED RESULT The text color does not change. EXPECTED RESULT The text color should change immediately. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 39 (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 442149] New: caption buggy in many sections
https://bugs.kde.org/show_bug.cgi?id=442149 Bug ID: 442149 Summary: caption buggy in many sections Product: kinfocenter Version: 5.22.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sascha.gas...@gmx.de CC: hubn...@gmail.com Target Milestone: --- Created attachment 141371 --> https://bugs.kde.org/attachment.cgi?id=141371=edit Caption that looks buggy SUMMARY The caption on the right side is buggy in many sections. See also the screenshot as an example. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux distribution: OpenSUSE Tumbleweed KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 442148] New: Settings dialog to wide
https://bugs.kde.org/show_bug.cgi?id=442148 Bug ID: 442148 Summary: Settings dialog to wide Product: kontact Version: 5.18.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: sascha.gas...@gmx.de Target Milestone: --- Created attachment 141370 --> https://bugs.kde.org/attachment.cgi?id=141370=edit Screenshot of minimal size SUMMARY The settings dialog of kontact is to wide and I can not make it smaller. It's more than 2300 px. I added a screenshot of the minimal size. My display has a 4k resolution and no high DPI. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux Distribution: OpenSUSE Tumbleweed KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This behavior is not new. I have watched it since I have my 4k display. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436408] New: Okular crashes when opening docx file
https://bugs.kde.org/show_bug.cgi?id=436408 Bug ID: 436408 Summary: Okular crashes when opening docx file Product: okular Version: 21.04.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: sascha.gas...@gmx.de Target Milestone: --- Application: okular (21.04.0) Qt Version: 5.15.2 Frameworks Version: 5.81.0 Operating System: Linux 5.11.16-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.21.4 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I clicked on a docx file in an other application and it tried to open it with Okular. I wonder if Okular has a buggy file type checking or no check at all when it tries to open a file. There are many bug reports related to this. E.g.: 426020 425725 417241 415261 408851 408818 406738 But this is only an assumption. The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f25b88f3880 (LWP 506243))] [KCrash Handler] #6 0x7f25b445f990 in Okular::Generator::image (this=, request=0x7f25b445fb00 ) at /usr/src/debug/okular-21.04.0-1.1.x86_64/core/generator.cpp:330 #7 0x7f25b464763a in Layers::notifySetup (this=0x565370bcf290) at /usr/src/debug/okular-21.04.0-1.1.x86_64/part/layers.cpp:63 #8 0x7f25b4441a32 in Okular::Document::openDocument (this=this@entry=0x565370777a00, docFile=..., url=..., _mime=..., password=...) at /usr/src/debug/okular-21.04.0-1.1.x86_64/core/document.cpp:2412 #9 0x7f25b45aacc5 in Okular::Part::doOpenFile (this=this@entry=0x5653707720d0, mimeA=..., fileNameToOpenA=..., isCompressedFile=isCompressedFile@entry=0x7ffef36101d7) at /usr/src/debug/okular-21.04.0-1.1.x86_64/part/part.cpp:1391 #10 0x7f25b45ad4fb in Okular::Part::openFile (this=0x5653707720d0) at /usr/src/debug/okular-21.04.0-1.1.x86_64/part/part.cpp:1509 #11 0x7f25bc6a4105 in KParts::ReadOnlyPartPrivate::openLocalFile (this=this@entry=0x565370642f70) at /usr/src/debug/kparts-5.81.0-1.2.x86_64/src/readonlypart.cpp:180 #12 0x7f25bc6a843f in KParts::ReadOnlyPart::openUrl (this=0x5653707720d0, url=...) at /usr/src/debug/kparts-5.81.0-1.2.x86_64/src/readonlypart.cpp:141 #13 0x7f25b45ab8c3 in Okular::Part::openUrl (this=, _url=..., swapInsteadOfOpening=) at /usr/src/debug/okular-21.04.0-1.1.x86_64/part/part.cpp:1741 #14 0x56536eb8843d in Shell::openUrl (this=, url=..., serializedOptions=...) at /usr/src/debug/okular-21.04.0-1.1.x86_64/shell/shell.cpp:289 #15 0x56536eb8d72e in Shell::openDocument (this=0x56537076f5a0, url=..., serializedOptions=...) at /usr/src/debug/okular-21.04.0-1.1.x86_64/shell/shell.cpp:240 #16 0x56536eb84abe in Shell::openDocument (serializedOptions=..., url=..., this=0x56537076f5a0) at /usr/src/debug/okular-21.04.0-1.1.x86_64/shell/okular_main.cpp:165 #17 Okular::main (serializedOptions=..., paths=...) at /usr/src/debug/okular-21.04.0-1.1.x86_64/shell/okular_main.cpp:166 #18 main (argc=, argv=0x7ffef3610760) at /usr/src/debug/okular-21.04.0-1.1.x86_64/shell/main.cpp:95 [Inferior 1 (process 506243) detached] Possible duplicates by query: bug 435462, bug 433909, bug 426020, bug 425725, bug 421603. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409634] Color theme name translations
https://bugs.kde.org/show_bug.cgi?id=409634 --- Comment #3 from Sascha Gaspar --- Yes, I update the system since many month. But I don't want to delete all my settings. May be I have to live with this for a while. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409790] New: KDevelop crash while moving subwindow
https://bugs.kde.org/show_bug.cgi?id=409790 Bug ID: 409790 Summary: KDevelop crash while moving subwindow Product: kdevelop Version: 5.3.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: sascha.gas...@gmx.de Target Milestone: --- Application: kdevelop (5.3.2) Qt Version: 5.13.0 Frameworks Version: 5.59.0 Operating System: Linux 5.1.16-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I tried to move/seperate the projects-side-bar and moved the main window. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f037a84aa80 (LWP 948))] Thread 29 (Thread 0x7f02f9ffb700 (LWP 14549)): #0 0x7f0387a93e05 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f038a9f8fbf in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x560536e11780) at thread/qwaitcondition_unix.cpp:146 #2 0x7f038a9f8fbf in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x560536e11860, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f038a9f90a9 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x560536e133f8, mutex=0x560536e11860, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7f038707e610 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f0387081f3a in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f038707d87e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f038708017b in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f038a9f3112 in QThreadPrivate::start(void*) (arg=0x7f02e40034e0) at thread/qthread_unix.cpp:360 #9 0x7f0387a8dfaa in start_thread () at /lib64/libpthread.so.0 #10 0x7f038a67c73f in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7f02fa7fc700 (LWP 14548)): #0 0x7f0387a93e05 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f038a9f8fbf in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x560536e11780) at thread/qwaitcondition_unix.cpp:146 #2 0x7f038a9f8fbf in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x560536e11860, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f038a9f90a9 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x560536e133f8, mutex=0x560536e11860, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7f038707e610 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f0387081f3a in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f038707d87e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f038708017b in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f038a9f3112 in QThreadPrivate::start(void*) (arg=0x7f02f0003ae0) at thread/qthread_unix.cpp:360 #9 0x7f0387a8dfaa in start_thread () at /lib64/libpthread.so.0 #10 0x7f038a67c73f in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7f02faffd700 (LWP 14547)): #0 0x7f0387a93e05 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f038a9f8fbf in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x560536e11780) at thread/qwaitcondition_unix.cpp:146 #2 0x7f038a9f8fbf in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x560536e11860, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f038a9f90a9 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x560536e133f8, mutex=0x560536e11860, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7f038707e610 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f0387081f3a in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f038707d87e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f038708017b in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f038a9f3112 in QThreadPrivate::start(void*) (arg=0x7f02ec0038e0) at thread/qthread_unix.cpp:360 #9 0x7f0387a8dfaa in start_thread () at /lib64/libpthread.so.0 #10 0x7f038a67c73f in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7f02fb7fe700 (LWP 14546)): #0
[kde] [Bug 409787] New: Dialogs are too wide
https://bugs.kde.org/show_bug.cgi?id=409787 Bug ID: 409787 Summary: Dialogs are too wide Product: kde Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: sascha.gas...@gmx.de Target Milestone: --- SUMMARY Some dialogs are too wide. E.g. "KDevelop - New Project" is 1750 pixels and "Kontact - Settings" is 2823 pixel wide. And I can not reduce the size. My desktop resolution is 4k (no high-DPI). STEPS TO REPRODUCE 1. Open one of the mentioned dialogs. OBSERVED RESULT The dialog very wide. EXPECTED RESULT The dialog should not be too wide on a big desktop (e.g. 4k). Besides it should be resizable to a smaller size. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 358889] Scrollbar in left subwindow
https://bugs.kde.org/show_bug.cgi?id=358889 --- Comment #7 from Sascha Gaspar --- Sorry, I did not see the progress. But for some time this does not happen anymore. (I use an other desktop resolution but I don't think that's the cause. Now 4k instead of 2560x1600.) -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 358888] Multiple password dialogs
https://bugs.kde.org/show_bug.cgi?id=35 --- Comment #5 from Sascha Gaspar --- Sorry, I did not see the progress. But now, in Plasma 5.16.2 it is fixed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409634] Color theme name translations
https://bugs.kde.org/show_bug.cgi?id=409634 --- Comment #1 from Sascha Gaspar --- Created attachment 121404 --> https://bugs.kde.org/attachment.cgi?id=121404=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409634] New: Color theme name translations
https://bugs.kde.org/show_bug.cgi?id=409634 Bug ID: 409634 Summary: Color theme name translations Product: systemsettings Version: 5.16.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_desktoptheme Assignee: plasma-b...@kde.org Reporter: sascha.gas...@gmx.de Target Milestone: --- SUMMARY In the German translation of the GUI I get an error message in the color theme settings dialog: "Das Farbschema "Breeze-Dunkel" ist nicht installiert. Es wird stattdessen das Standardschema installiert." This means "The color sceme "Breeze-Dark" is not installed." I think, this may be a problem with the translation. I think breeze-dark is installed. See also the attached screenshot. I think you know what I mean. STEPS TO REPRODUCE Not sure: 1. Use german UI. 2. Select theme "Breeze-Dark" 3. Go to color settings OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSuSE Tumbleweed KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 407685] New: Tries to use http proxy for imap
https://bugs.kde.org/show_bug.cgi?id=407685 Bug ID: 407685 Summary: Tries to use http proxy for imap Product: kmail2 Version: 5.11.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: sascha.gas...@gmx.de Target Milestone: --- SUMMARY Kmail/Kontact uses the http proxy from the system settings for IMAP (and probably POP/SMTP). STEPS TO REPRODUCE 1. Configure a proxy in the system settings 2. Try to receive mails OBSERVED RESULT Kmail shows the state "offline" EXPECTED RESULT Kmail should receive new mails from the server. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSuSE Tumbleweed / Plasma 5 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.57.0 Qt Version: 5.0.13.1 ADDITIONAL INFORMATION I think the proxy should not be used because a http/https/ftp proxy (Squid in my case) can not handle IMAP/POP/SMTP. And I set only http, https and ftp proxy, no socks and no other protocol. Besides I added the IMAP server in the no-proxy settings and it is ignored. It seems that Kmail does not use the environment but the Plasma settings. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 405499] New: Content area does not change when clicking on tree entries
https://bugs.kde.org/show_bug.cgi?id=405499 Bug ID: 405499 Summary: Content area does not change when clicking on tree entries Product: kinfocenter Version: 5.15.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: hubn...@gmail.com Reporter: sascha.gas...@gmx.de Target Milestone: --- SUMMARY The right side (main content area) does not change when I click on a tree entry. When I select an entry and hit enter, the according content is shown. STEPS TO REPRODUCE 1. Open kinfocenter 2. Klick on an entry of the tree (e.g. X-Server) OBSERVED RESULT The right side does not change. EXPECTED RESULT The right side should show the X-Server informations. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Plasmashell 5.15.2 (also in 5.15.1) (available in About System) KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION I tried it only with Wayland. Distribution: OpenSUSE Tumbleweed -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 390151] Crash on exit [wl_proxy_destroy, wl_map_insert_at]
https://bugs.kde.org/show_bug.cgi?id=390151 Sascha Gaspar changed: What|Removed |Added CC||sascha.gas...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 387101] New: Copy files with higher I/O niceness than
https://bugs.kde.org/show_bug.cgi?id=387101 Bug ID: 387101 Summary: Copy files with higher I/O niceness than 0 Product: dolphin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sascha.gas...@gmx.de CC: elvis.angelac...@kde.org Target Milestone: --- It would be nice if Dophin copies files with a higher I/O niceness than 0. May be the default should be 6 or 7? It would also be nice if the user can configure this and change it on running copy operations. I would like to have this feature because when I copy big files, other programs stutter. When I change the io-niceness then in Konsole, they work much better. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 348194] kactivitymanager sometimes crashes on logout
https://bugs.kde.org/show_bug.cgi?id=348194 Sascha Gaspar <sascha.gas...@gmx.de> changed: What|Removed |Added CC||sascha.gas...@gmx.de --- Comment #22 from Sascha Gaspar <sascha.gas...@gmx.de> --- On my PC it crashes too. Here are some infos from coredumpctl and dmesg: PID: 1867 (kactivitymanage) UID: 1000 (sascha) GID: 1000 (sascha) Signal: 11 (SEGV) Timestamp: Mo 2016-01-25 21:19:07 CET (6 days ago) Command Line: /usr/bin/kactivitymanagerd start-daemon Executable: /usr/bin/kactivitymanagerd Control Group: /user.slice/user-1000.slice/session-c1.scope Unit: session-c1.scope Slice: user-1000.slice Session: c1 Owner UID: 1000 (sascha) Boot ID: a507d51b25dd4730a8cae8b8419567c0 Machine ID: bc95e938d3394a5f904bd1055d2c1ca2 Hostname: homeserver.sg78.de Message: Process 1867 (kactivitymanage) of user 1000 dumped core. Stack trace of thread 1867: #0 0x7fd644086291 _ZN12QSqlDatabase5closeEv (libQt5Sql.so.5) #1 0x7fd6440877f9 _ZN12QSqlDatabaseD1Ev (libQt5Sql.so.5) #2 0x7fd64408982d n/a (libQt5Sql.so.5) #3 0x7fd65cce5299 _ZN9QHashData11free_helperEPFvPNS_4NodeEE (libQt5Core.so.5) #4 0x7fd644085f63 n/a (libQt5Sql.so.5) #5 0x7fd65c4ebf88 __run_exit_handlers (libc.so.6) #6 0x7fd65c4ebfd5 exit (libc.so.6) #7 0x7fd652e15e4e _ZN14QXcbConnection16processXcbEventsEv (libQt5XcbQpa.so.5) #8 0x7fd65ce921e1 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5) #9 0x7fd65d70d9ac _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5) #10 0x7fd65d712e86 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5) #11 0x7fd65ce62bab _ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent (libQt5Core.so.5) #12 0x7fd65ce64fa6 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5) #13 0x7fd65ceb6ac2 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #14 0x7fd652e7821d n/a (libQt5XcbQpa.so.5) #15 0x7fd65ce6057a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #16 0x7fd65ce6853c _ZN16QCoreApplication4execEv (libQt5Core.so.5) #17 0x00410aa4 main (kactivitymanagerd) #18 0x7fd65c4d6610 __libc_start_main (libc.so.6) #19 0x00410c79 _start (kactivitymanagerd) Stack trace of thread 1884: #0 0x7fd65c597e23 __select (libc.so.6) #1 0x7fd65ceb4c1f _Z14qt_safe_selectiP6fd_setS0_S0_PK8timespec (libQt5Core.so.5) #2 0x7fd65ceb66f7 _ZN27QEventDispatcherUNIXPrivate8doSelectE6QFlagsIN10QEventLoop17ProcessEventsFlagEEP8timespec (libQt5Core.so.5) #3 0x7fd65ceb6bfe _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x7fd65ce6057a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x7fd65cc7cbe4 _ZN7QThread4execEv (libQt5Core.so.5) #6 0x00412e0a _ZZ12runInQThreadI8FeaturesEPT_vEN6Thread3runEv (kactivitymanagerd) #7 0x7fd65cc81b8e n/a (libQt5Core.so.5) #8 0x7fd65b5ef4a4 start_thread (libpthread.so.0) #9 0x7fd65c59f13d __clone (libc.so.6) Stack trace of thread 1883: #0 0x7fd65c597e23 __select (libc.so.6) #1 0x7fd65ceb4c1f _Z14qt_safe_selectiP6fd_setS0_S0_PK8timespec (libQt5Core.so.5) #2 0x7fd65ceb66f7 _ZN27QEventDispatcherUNIXPrivate8doSelectE6QFlagsIN10QEventLoop17ProcessEventsFlagEEP8timespec (libQt5Core.so.5) #3 0x7fd65ceb6bfe _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x7fd65ce6057a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x7fd65cc7cbe4 _ZN7QThread4execEv (libQt5Core.so.5) #6 0x00412dda _ZZ12runInQThreadI10ActivitiesEPT_vEN6Thread3runEv (kactivitymanagerd) #7 0x7fd65cc81b8e n/a (libQt5Core.so.5) #8 0x7fd65b5ef4a4 start_thread (libpthread.so.0) #9 0x7fd65c59f13d __clone (libc.so.6) Stack trace of thread 1881: #0 0x7fd65c597e23 __select (libc.so.6)
[kontact] [Bug 358888] Multible password dialogs
https://bugs.kde.org/show_bug.cgi?id=35 --- Comment #1 from Sascha Gaspar <sascha.gas...@gmx.de> --- The behavior seems to have changed a little bit in the last versions. There are much windows but Kontact does not loose the mail server passwords anymore. Or I have done something differently. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 358888] New: Multible password dialogs
https://bugs.kde.org/show_bug.cgi?id=35 Bug ID: 35 Summary: Multible password dialogs Product: kontact Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: sascha.gas...@gmx.de After startup the password window goes in a timeout when no password is typed in. Then the wallet is not opened and kontact loses the passwords for the mail servers. Kontact should wait for the mail server password prompt until the opening of the wallet is cancelled by the user. (Why isn't version 5.1.1 of Kontact selecable in the bug tracker?) Reproducible: Always Steps to Reproduce: 1. Start the PC 2. Login into Klasma 5 Kontact 3. Starts automatically on my PC, if that's not the case on yours, start Kontact 4. Don't type in the wallet password Actual Results: There is a windows from the KDE Wallet Service with a retry and a cancel button and a Password promt window for the mail server password. Expected Results: Kontact should show only one password window, either from the wallet opening or for the mail server password After the mail server password dialog pops up, kontact does not use the password from the wallet anymore although the wallet is opened afer the window pops up -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 358889] New: Scrollbar in left subwindow
https://bugs.kde.org/show_bug.cgi?id=358889 Bug ID: 358889 Summary: Scrollbar in left subwindow Product: kontact Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: sascha.gas...@gmx.de After startup there is a horizontal scrollbar in the leftmost subwindow with the integrated programs. After some resizing of the Kontact window the scrollbar disappears. Reproducible: Always Steps to Reproduce: 1. Start Kontact Actual Results: There is a horizontal scroll bar at the bottom of the left subwindow with kmail and contacts and so on in it. Expected Results: The scroll bar should not be there. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 358889] Scrollbar in left subwindow
https://bugs.kde.org/show_bug.cgi?id=358889 --- Comment #2 from Sascha Gaspar <sascha.gas...@gmx.de> --- Created attachment 96961 --> https://bugs.kde.org/attachment.cgi?id=96961=edit Screenshot of the scroll bar -- You are receiving this mail because: You are watching all bug changes.
