[kasts] [Bug 443286] Insecure redirect break downlaods
https://bugs.kde.org/show_bug.cgi?id=443286 Sebastian Dicke changed: What|Removed |Added CC||sdi...@live.de --- Comment #10 from Sebastian Dicke --- Maybe there should be an option in the settings dialog to allow insecure media file downloads by default and to show a warning popup with the option to allow the insecure download for the current file (and a tip to contact the podcast provider to fix the issue, maybe with an clickable link to the the podcast homepage). -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 454694] New: Confusing handling of image sorting
https://bugs.kde.org/show_bug.cgi?id=454694 Bug ID: 454694 Summary: Confusing handling of image sorting Product: gwenview Version: 22.04.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: sdi...@live.de Target Milestone: --- SUMMARY *** When the sorting criterion „Datum“ (in the German translation, should be „Date“ in English) is selected via menu and you switch to another folder, then the images are sorted by name, but in the menu „Datum“ is selected. *** STEPS TO REPRODUCE 1. Select sorting according to date in the menu „View“ → „Sorting“ while being in the overview tab. 2. Switch to another folder. 3. View the state in the menu mentioned above and compare the date of the images in the right bar. The selected sorting variant do not matches the actual sorting variant. OBSERVED RESULT The selected sorting is only applied to the single folder which is currently active. EXPECTED RESULT The sorting should be applied to all folders viewed. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 434807] New: Misspelling when writing to fstab
https://bugs.kde.org/show_bug.cgi?id=434807 Bug ID: 434807 Summary: Misspelling when writing to fstab Product: partitionmanager Version: 20.12.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: sdi...@live.de Target Milestone: --- SUMMARY Newly added entries for Btrfs file systems are misspelled. In the entry is Btrfs as file system type annotated, which is an incorrect spelling from mounts point of view. It will mount the created file system after change the type annotation to btrfs. STEPS TO REPRODUCE 1. Create a new Btrfs filesystem 2. Open mount point edit dialog 3. Set a path 4. Press the Ok button 5. The change will be written to /etc/fstab 6. Try to mount the file system with mount -a, which will fail OBSERVED RESULT Mount will fail EXPECTED RESULT Mount should be conducted without errors SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.12 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 404713] New: Overlapping lines when mixing Roman and Asian character sets
https://bugs.kde.org/show_bug.cgi?id=404713 Bug ID: 404713 Summary: Overlapping lines when mixing Roman and Asian character sets Product: kate Version: 18.12.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: sdi...@live.de Target Milestone: --- SUMMARY Visual appearance of files with different character sets may have a reduced text readability. STEPS TO REPRODUCE 1. Open an document with Roman characters in one line and both Roman and Asian ones in the next line. (E. g. this one: https://github.com/QMatrixClient/libqmatrixclient/blob/master/mime/packages/freedesktop.org.xml). OBSERVED RESULT Some lines are overlapping, different characters crossing. EXPECTED RESULT The lines are separated vertically by a free space and all characters have their own space, do not cross. SOFTWARE/OS VERSIONS KDE Plasma Version: 15.15.1 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 394723] Package description text disappears on mouse over
https://bugs.kde.org/show_bug.cgi?id=394723 --- Comment #2 from Sebastian Dicke --- I am using Breeze dark. The described behaviours do not occur anymore since a short time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397685] New: Plasma panel hangs when audio player process is stopped
https://bugs.kde.org/show_bug.cgi?id=397685 Bug ID: 397685 Summary: Plasma panel hangs when audio player process is stopped Product: plasmashell Version: 5.13.1 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sdi...@live.de CC: plasma-b...@kde.org Target Milestone: 1.0 Steps to reproduce: 1. Play a audio file with a media player which playback can be controlled with a widget in plasma panel. 2. Send a SIGSTOP to the media player process. 3. Press playback start/stop shortcut or key. 4. Click on any place on the plasma panel. No reaction is noticeable. 5. Send a SIGCONT to the media player process previously stopped. 6. The expected reactions to the clicks on the panel occurs. The same behaviour occurs with openSUSE builds from version 5.13.4. The behaviour occurs both with VLC and dragon player. I am not sure which component is responsible for this behaviour so I chose component general as component to report the bug. -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 394723] New: Package description text disappears on mouse over
https://bugs.kde.org/show_bug.cgi?id=394723 Bug ID: 394723 Summary: Package description text disappears on mouse over Product: apper Version: 1.0.0 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dantt...@gmail.com Reporter: sdi...@live.de Target Milestone: --- Steps to reproduce: 1. Open apper 2. Select an package 3. The Package description is shown 4. Move the mouse on the description 4. The description text disappears 5. Move the mouse away 6. The text is not showed 7. Select another package 8. This package's description is shown -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 390978] New: Apper crashes just after start
https://bugs.kde.org/show_bug.cgi?id=390978 Bug ID: 390978 Summary: Apper crashes just after start Product: apper Version: 0.9.0 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dantt...@gmail.com Reporter: sdi...@live.de Target Milestone: --- Application: apper (0.9.3) Qt Version: 5.9.2 Frameworks Version: 5.42.0 Operating System: Linux 4.14.0-3-amd64 x86_64 Distribution: Debian GNU/Linux testing (buster) -- Information about the crash: I started apper with no arguments or options, the application crashes without show it main window. The problems occurred after restarting the system and reinstall the application, too. If I rund it from terminal emulator sometimes it outputs something like this: „QCommandLineParser: option not defined: "install-mime-type" QCommandLineParser: option not defined: "install-package-name" QCommandLineParser: option not defined: "install-provide-file" QCommandLineParser: option not defined: "install-catalog" QCommandLineParser: option not defined: "remove-package-by-file" kf5.kwidgetsaddons: Invalid pixmap specified. kf5.kwidgetsaddons: Invalid pixmap specified. KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = apper path = /usr/bin pid = 32159 KCrash: Arguments: /usr/bin/apper KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0” And sometimes something like this: „QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 12 and type 'Read', disabling... QSocketNotifier: Invalid socket 9 and type 'Read', disabling...” Followed by bash output „[1]+ Exit 253apper“ The crash can be reproduced every time. -- Backtrace: Application: apper (apper), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3af4ac0940 (LWP 29029))] Thread 3 (Thread 0x7f3ada234700 (LWP 29031)): #0 0x7f3aeb1f7908 in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f3aedc57230 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3aedc12c07 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3aedc130c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f3aedc1322c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f3aec09210b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3aec0372aa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3aebe5635a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f3af0756e45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f3aebe5b22d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f3ae8f7951a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #11 0x7f3aeb2063ef in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7f3adc764700 (LWP 29030)): #0 0x7f3aeb1fbe6b in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f3ae8495150 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f3ae8496ee9 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f3ade8c7029 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f3aebe5b22d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3ae8f7951a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7f3aeb2063ef in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7f3af4ac0940 (LWP 29029)): [KCrash Handler] #6 0x7f3af46e4aea in KCModuleProxy::realModule() const () from /usr/lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #7 0x557fe23849a6 in MainUi::MainUi(QWidget*) () #8 0x557fe23891b7 in Apper::showUi() () #9 0x7f3aec0688c2 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f3aecf198d4 in QGuiApplication::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #11 0x7f3aeeab34ef in QApplication::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f3aeeaad63c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f3aeeab4f04 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f3aec039258 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f3aec03b9cd in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f3aec092ac3 in ?? () from
[dolphin] [Bug 390812] New: Dolphin shortcuts interfere with the terminal panel
https://bugs.kde.org/show_bug.cgi?id=390812 Bug ID: 390812 Summary: Dolphin shortcuts interfere with the terminal panel Product: dolphin Version: 17.12.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: panels: terminal Assignee: dolphin-bugs-n...@kde.org Reporter: sdi...@live.de Target Milestone: --- Steps: 1. Define a single character shortcut (within the printable ASCII range for example) in dolphin 2. Open a terminal panel 3. Type the character defined in (1). 4. The defined action is proceeded This behavior make normal usage of the terminal panel hard. Maybe such shortcuts should not affect the terminal panel? The same behavior exists with packages from openSUSE Tumbleweed (Dolphin 17.12.2) and Debian Testing (Dolphin 17.08.3). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 379634] Fails to load PDF files from SFTP filesystem
https://bugs.kde.org/show_bug.cgi?id=379634 --- Comment #2 from Sebastian Dicke <sdi...@live.de> --- gwenview and kate each in version 16.08.3 (compiled again Qt 5.7.1). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 379634] Fails to load PDF files from SFTP filesystem
https://bugs.kde.org/show_bug.cgi?id=379634 Sebastian Dicke <sdi...@live.de> changed: What|Removed |Added Platform|Other |Debian testing -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 379634] New: Fails to load PDF files from SFTP filesystem
https://bugs.kde.org/show_bug.cgi?id=379634 Bug ID: 379634 Summary: Fails to load PDF files from SFTP filesystem Product: okular Version: 0.26.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: sdi...@live.de Target Milestone: --- Steps: 1. "Mount" SFTP filesystem via Dolphin. (Using a public key added via ssh-add previously) 2. Go into a folder on this filesystem. 3. Click on a file in dolphin Okular shows a password dialog. When dialog was closed, dolphin print a error message in this form: sftp://[…] kann nicht geöffnet werden. Der Grund lautet: The host key for the server sdicke.thatip.net has changed. This could either mean that DNS SPOOFING is happening or the IP address for the host and its host key have changed at the same time. The fingerprint for the key sent by the remote host is: […]". Another KDE application are able to open files from the same filesystem. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378672] New: Kate crashes when opening files from sshfs mounted path
https://bugs.kde.org/show_bug.cgi?id=378672 Bug ID: 378672 Summary: Kate crashes when opening files from sshfs mounted path Product: kate Version: 16.08 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: sdi...@live.de Target Milestone: --- Versions: Kate: 16.08.3 KDE Frameworks: 5.28.0 Qt: 5.7.1 Kernel: 4.9.0-2-amd64 Steps: 1. Mount a filesystem via sshfs. 2. Open a text file saved in this filesystem via dolphin. 3. Kate shows the content. 4. Kate crashes. It do not matter if the cursor get moved. File opening from the same filesystem with other applications causes no problems. The bug is reproducible, I tried the same with different files more than 10 times. This bug do not occurs with file saved on a SSD connected the the motherboard. Stacktrace: Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f14ea4a3900 (LWP 7253))] Thread 11 (Thread 0x7f14c0a2b700 (LWP 7263)): #0 0x7f14e2b5f14f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f14e60c0c6b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f14c5f55d50 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #3 0x7f14c5f59f88 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7f14c5f54ecd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7f14c5f57d99 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f14e60bfda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f14e2b59424 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f14e56d59bf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 10 (Thread 0x7f14c122c700 (LWP 7262)): #0 0x7f14e2b5f14f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f14e60c0c6b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f14c5f55d50 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #3 0x7f14c5f59f88 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7f14c5f54ecd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7f14c5f57d99 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f14e60bfda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f14e2b59424 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f14e56d59bf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 9 (Thread 0x7f14c1a2d700 (LWP 7261)): #0 0x7f14e2b5f14f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f14e60c0c6b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f14c5f55d50 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #3 0x7f14c5f59f88 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7f14c5f54ecd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7f14c5f57d99 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f14e60bfda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f14e2b59424 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f14e56d59bf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 8 (Thread 0x7f14c222e700 (LWP 7260)): #0 0x7f14e2b5f14f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f14e60c0c6b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f14c5f55d50 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #3 0x7f14c5f59f88 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7f14c5f54ecd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
[dolphin] [Bug 374228] New: Dolphing hangs if mounted sshfs server disconnected without proper unmounting
https://bugs.kde.org/show_bug.cgi?id=374228 Bug ID: 374228 Summary: Dolphing hangs if mounted sshfs server disconnected without proper unmounting Product: dolphin Version: 16.08.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sdi...@live.de Target Milestone: --- I reproduced the following behavior often: 1. Mount a sshfs filesystem in a home folders direct sub folder. 2. Open a folder contained in this filesystem. 3. Disconnect the sshfs filesystem providing server by disconnect the network interface. 4. The open dolphin window (which was opened in step 2) don not react the mouse input anymore. If I open a new dolphin window, the application in normally useable, except if I open the home folder (sub folders are not the folder in which the sshfs was mounted are not affected), no contents are showed, the progressbar in the right down corner are active. If I navigate the the folder in which the sshfs is mounted, the current window do not react the mouse inputs, too. After a few minutes all affected windows react to mouse inputs again. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 373745] Page number textfield resizing do not work properly
https://bugs.kde.org/show_bug.cgi?id=373745 --- Comment #2 from Sebastian Dicke <sdi...@live.de> --- I tried version 1.0 and there the problem obviously does not exist anymore. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 373745] Page number textfield resizing do not work properly
https://bugs.kde.org/show_bug.cgi?id=373745 Sebastian Dicke <sdi...@live.de> changed: What|Removed |Added Version|unspecified |0.26.1 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 373745] New: Page number textfield resizing do not work properly
https://bugs.kde.org/show_bug.cgi?id=373745 Bug ID: 373745 Summary: Page number textfield resizing do not work properly Product: okular Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: sdi...@live.de Target Milestone: --- I watched the following behavior often at least one year with Okular binaries from different distributions (Debian, openSUSE Tumbleweed, Antergos): Scrolling through the pages, via arrow key or via scrollbar, when the page number exceeds 9 the page number is not viewed properly anymore in the textfield, the textfield did not changed it size but the page number now need more place to be showed and so parts of the page number are not visible until window resize. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373330] New: systemsettings5 crashes after leaving application style area
https://bugs.kde.org/show_bug.cgi?id=373330 Bug ID: 373330 Summary: systemsettings5 crashes after leaving application style area Product: systemsettings Version: 5.8.2 Platform: Debian testing OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sdi...@live.de Target Milestone: --- Application: systemsettings5 (5.8.2) Qt Version: 5.7.1 Frameworks Version: 5.27.0 Operating System: Linux 4.8.0-1-amd64 x86_64 Distribution: Debian GNU/Linux testing (stretch) -- Information about the crash: - What I was doing when the application crashed: Opened the application, opened application style section, gone to window decorations tab and clicked on the back buttom. Then, in the most cases, a segmentation fault occures. The crash can be reproduced sometimes. -- Backtrace: Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa900c185c0 (LWP 19442))] Thread 4 (Thread 0x7fa8d8895700 (LWP 19448)): #0 0x7fa8fd32b56d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa8f86299f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa8f8629b0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa8fdc496fb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa8fdbf307a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa8fda150d3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa8fc39b5d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fa8fda19d88 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa8fa537464 in start_thread (arg=0x7fa8d8895700) at pthread_create.c:333 #9 0x7fa8fd3349df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7fa8e6be3700 (LWP 19445)): #0 0x7fa8fd3275dd in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa8f866dc40 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa8f86294be in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa8f8629994 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa8f8629b0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fa8fdc496fb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa8fdbf307a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa8fda150d3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa900d6b6d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7fa8fda19d88 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fa8fa537464 in start_thread (arg=0x7fa8e6be3700) at pthread_create.c:333 #11 0x7fa8fd3349df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7fa8ef685700 (LWP 19444)): #0 0x7fa8fd32b56d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa8fadb1150 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fa8fadb2ee9 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fa8f1be4b69 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fa8fda19d88 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa8fa537464 in start_thread (arg=0x7fa8ef685700) at pthread_create.c:333 #6 0x7fa8fd3349df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7fa900c185c0 (LWP 19442)): [KCrash Handler] #6 0x7fa8fc26dd85 in QV4::WeakValue::free() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fa8fc2dea82 in QV4::QObjectWrapper::destroyObject(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fa8fc174dbf in QV4::MemoryManager::sweep(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7fa8fc1761cc in QV4::MemoryManager::~MemoryManager() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7fa8fc25d69b in QV4::ExecutionEngine::~ExecutionEngine() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x7fa8fc39d086 in QV8Engine::~QV8Engine() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x7fa8fc39d1a9 in QV8Engine::~QV8Engine() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x7fa8fc1f49a6 in QJSEngine::~QJSEngine() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x7fa8fc30890d in QQmlEngine::~QQmlEngine() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #15 0x7fa8fc3089c9 in QQmlEngine::~QQmlEngine() () from
[bomber] [Bug 363573] The game could be auto paused when you click on any menu item
https://bugs.kde.org/show_bug.cgi?id=363573 Sebastian Dicke <sdi...@live.de> changed: What|Removed |Added CC||sdi...@live.de --- Comment #1 from Sebastian Dicke <sdi...@live.de> --- It would be helpful to play the game. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 372639] New: KInfocenter crashes in file indexing page
https://bugs.kde.org/show_bug.cgi?id=372639 Bug ID: 372639 Summary: KInfocenter crashes in file indexing page Product: kinfocenter Version: 5.8.2 Platform: Debian testing OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: hubn...@gmail.com Reporter: sdi...@live.de Target Milestone: --- Application: kinfocenter (5.8.2) Qt Version: 5.6.1 Frameworks Version: 5.27.0 Operating System: Linux 4.8.0-1-amd64 x86_64 Distribution: Debian GNU/Linux testing (stretch) -- Information about the crash: - What I was doing when the application crashed: Opened the file indexing page, which do not show any exept of a gray background and click with the left or right mouse key bottom on the gray area. Then the application crashes. The crash can be reproduced every time. -- Backtrace: Application: Info Center (kinfocenter), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9ad65358c0 (LWP 2536))] Thread 5 (Thread 0x7f9ab2108700 (LWP 2541)): #0 0x7f9ad36ff56d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f9ad03939f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9ad0393b0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9ad401a51b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9ad3fc219a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9ad3de7e53 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9ad2ef7a55 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f9ad3decd78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9ad0dd2464 in start_thread (arg=0x7f9ab2108700) at pthread_create.c:333 #9 0x7f9ad37089df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 4 (Thread 0x7f9ab3df9700 (LWP 2540)): #0 __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:67 #1 0x7f9ad36ff562 in poll () at ../sysdeps/unix/syscall-template.S:84 #2 0x7f9ad03939f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9ad0393b0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9ad401a51b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9ad3fc219a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9ad3de7e53 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9ad2ef7a55 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f9ad3decd78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f9ad0dd2464 in start_thread (arg=0x7f9ab3df9700) at pthread_create.c:333 #10 0x7f9ad37089df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7f9abc49a700 (LWP 2538)): #0 0x7f9ad36ff56d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f9ad03939f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9ad0393b0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9ad401a51b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9ad3fc219a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9ad3de7e53 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9ad667a525 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f9ad3decd78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9ad0dd2464 in start_thread (arg=0x7f9abc49a700) at pthread_create.c:333 #9 0x7f9ad37089df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7f9ac4cfc700 (LWP 2537)): #0 0x7f9ad36ff56d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f9acd6ea150 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f9acd6ebee9 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f9ac725aa79 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f9ad3decd78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9ad0dd2464 in start_thread (arg=0x7f9ac4cfc700) at pthread_create.c:333 #6 0x7f9ad37089df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7f9ad65358c0 (LWP 2536)): [KCrash Handler] #6 0x7f9ad49409de in QWidget::setFocus(Qt::FocusReason) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7f9ad4946daf in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f9ad4900bec in
[dolphin] [Bug 358737] New: Dolphin crashes after click on "Configure Dolphin"
https://bugs.kde.org/show_bug.cgi?id=358737
Bug ID: 358737
Summary: Dolphin crashes after click on "Configure Dolphin"
Product: dolphin
Version: 15.12.1
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: sdi...@live.de
Application: dolphin (15.12.1)
KDE Platform Version: 5.5.4
Qt Version: 5.5.1
Operating System: Linux 4.1.16-1-lts x86_64
Distribution: Antergos
Output to stderr:
KSambaShare: Could not find smb.conf!
QLayout: Cannot add a null widget to QVBoxLayout/
QLayout: Cannot add a null widget to QVBoxLayout/
initialization OK, home trash dir: "/home/sebastian/.local/share/Trash"
"Tag 'b' is not defined in message {<__kuit_internal_top__>Check this box
to allow automatic deletion o...}."
"Tag 'b' is not defined in message {<__kuit_internal_top__>Check this box
to allow automatic deletion o...}."
QLayout: Attempting to add QLayout "" to PreviewsSettingsPage "", which already
has a layout
QLayout: Cannot add a null widget to QVBoxLayout/
QLayout: Cannot add a null widget to QVBoxLayout/
initialization OK, home trash dir: "/home/sebastian/.local/share/Trash"
"Tag 'b' is not defined in message {<__kuit_internal_top__>Check this box
to allow automatic deletion o...}."
"Tag 'b' is not defined in message {<__kuit_internal_top__>Check this box
to allow automatic deletion o...}."
QLayout: Attempting to add QLayout "" to PreviewsSettingsPage "", which already
has a layout
QLayout: Cannot add a null widget to QVBoxLayout/
QLayout: Cannot add a null widget to QVBoxLayout/
initialization OK, home trash dir: "/home/sebastian/.local/share/Trash"
"Tag 'b' is not defined in message {<__kuit_internal_top__>Check this box
to allow automatic deletion o...}."
"Tag 'b' is not defined in message {<__kuit_internal_top__>Check this box
to allow automatic deletion o...}."
QLayout: Attempting to add QLayout "" to PreviewsSettingsPage "", which already
has a layout
When I was using valgrind to analyse the problem, no crash occurred.
Reproducible: Sometimes
Steps to Reproduce:
1. Left click on Control menu
2. Left click on Configure Dolphin
--
You are receiving this mail because:
You are watching all bug changes.
