[kmail2] [Bug 379791] Confusing Account Wizard dialog
https://bugs.kde.org/show_bug.cgi?id=379791 Burkhard Lueck changed: What|Removed |Added CC||lu...@hube-lueck.de --- Comment #1 from Burkhard Lueck --- In kmail2 5.2.3 and kmail2 5.5.40 alpha 1 I do not have an "Add Account" button. Your version of kmail? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 360415] amd64 instructions ADCX and ADOX are not implemented in VEX
https://bugs.kde.org/show_bug.cgi?id=360415 Julian Seward changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #15 from Julian Seward --- Test cases in valgrind r16372. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 d...@newtech.fi changed: What|Removed |Added CC||d...@newtech.fi --- Comment #20 from d...@newtech.fi --- I also have this problem on a multiuser setup. At the moment there are 4 login sessions on different virtual screens. Two of the nonactive ones behave nicely, but on of them is spinning one core at 100%. This with Nvidia drivers. So the issues is NOT resolved... -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #21 from d...@newtech.fi ---
Here an extract of an strace of the bad screenlocker:
[pid 12126] futex(0x5651d612b36c, FUTEX_WAIT_PRIVATE, 459831, NULL
[pid 12251] <... restart_syscall resumed> ) = -1 ETIMEDOUT (Connection timed
out)
[pid 12251] futex(0x7f0508252f98, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 12251] clock_gettime(CLOCK_MONOTONIC, {tv_sec=1798396, tv_nsec=523409219})
= 0
[pid 12251] clock_gettime(CLOCK_MONOTONIC, {tv_sec=1798396, tv_nsec=523437825})
= 0
[pid 12251] futex(0x7f050a64,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 13051589, {tv_sec=1494750748,
tv_nsec=585611000}, 0x
[pid 12241] <... restart_syscall resumed> ) = -1 ETIMEDOUT (Connection timed
out)
[pid 12253] <... restart_syscall resumed> ) = -1 ETIMEDOUT (Connection timed
out)
[pid 12241] futex(0x5651d5c31338, FUTEX_WAKE_PRIVATE, 1
[pid 12253] futex(0x7f0504253398, FUTEX_WAKE_PRIVATE, 1
[pid 12241] <... futex resumed> ) = 0
[pid 12253] <... futex resumed> ) = 0
[pid 12241] clock_gettime(CLOCK_MONOTONIC,
[pid 12253] clock_gettime(CLOCK_MONOTONIC,
[pid 12241] <... clock_gettime resumed> {tv_sec=1798396, tv_nsec=531774677}) =
0
[pid 12253] <... clock_gettime resumed> {tv_sec=1798396, tv_nsec=531786416}) =
0
[pid 12241] clock_gettime(CLOCK_MONOTONIC,
[pid 12253] clock_gettime(CLOCK_MONOTONIC,
[pid 12241] <... clock_gettime resumed> {tv_sec=1798396, tv_nsec=531817216}) =
0
[pid 12253] <... clock_gettime resumed> {tv_sec=1798396, tv_nsec=531842134}) =
0
[pid 12241] futex(0x7f052a64,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 13714495, {tv_sec=1494750748,
tv_nsec=594006000}, 0x
[pid 12253] futex(0x7f04f8000a64,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 13712545, {tv_sec=1494750748,
tv_nsec=594021000}, 0x
[pid 12251] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)
[pid 12251] futex(0x7f0508252f98, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 12251] clock_gettime(CLOCK_MONOTONIC, {tv_sec=1798396, tv_nsec=623569800})
= 0
[pid 12251] clock_gettime(CLOCK_MONOTONIC, {tv_sec=1798396, tv_nsec=623596748})
= 0
[pid 12251] futex(0x7f050a64,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 13051591, {tv_sec=1494750748,
tv_nsec=685769000}, 0x
[pid 12241] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)
[pid 12253] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)
[pid 12241] futex(0x5651d5c31338, FUTEX_WAKE_PRIVATE, 1
[pid 12253] futex(0x7f0504253398, FUTEX_WAKE_PRIVATE, 1
[pid 12241] <... futex resumed> ) = 0
[pid 12253] <... futex resumed> ) = 0
[pid 12241] clock_gettime(CLOCK_MONOTONIC,
[pid 12253] clock_gettime(CLOCK_MONOTONIC,
[pid 12241] <... clock_gettime resumed> {tv_sec=1798396, tv_nsec=631951238}) =
0
[pid 12253] <... clock_gettime resumed> {tv_sec=1798396, tv_nsec=631957635}) =
0
[pid 12241] clock_gettime(CLOCK_MONOTONIC,
[pid 12253] clock_gettime(CLOCK_MONOTONIC,
[pid 12241] <... clock_gettime resumed> {tv_sec=1798396, tv_nsec=631981719}) =
0
[pid 12253] <... clock_gettime resumed> {tv_sec=1798396, tv_nsec=631988158}) =
0
[pid 12241] futex(0x7f052a64,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 13714497, {tv_sec=1494750748,
tv_nsec=694161000}, 0x
[pid 12253] futex(0x7f04f8000a64,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 13712547, {tv_sec=1494750748,
tv_nsec=694177000}, 0x
[pid 12251] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)
--
You are receiving this mail because:
You are watching all bug changes.
[ark] [Bug 379802] New: Renaming files or folders in root position generates a crash in Ark
https://bugs.kde.org/show_bug.cgi?id=379802 Bug ID: 379802 Summary: Renaming files or folders in root position generates a crash in Ark Product: ark Version: 17.04.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: g03f...@gmail.com CC: rthoms...@gmail.com Target Milestone: --- If I try to rename a file or a folder in root position inside a compressed file I've got always a crash. The problem doesn't occur when I try to rename a file or a folder that are in subdirectories. The crash happens with various compressed formats. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379803] New: Kwin crashed when switching screens
https://bugs.kde.org/show_bug.cgi?id=379803 Bug ID: 379803 Summary: Kwin crashed when switching screens Product: kwin Version: 5.8.6 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: essl.m...@gmail.com Target Milestone: --- Application: kwin_x11 (5.8.6) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.62-18.6-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: ctrl-alt-f1 loginctl unlock-sessions ctrl-alt-f7 Just installed the most recent updates. Screen lock stopped working. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb542aa8940 (LWP 2191))] Thread 7 (Thread 0x7fb51e5ba700 (LWP 1778573)): #0 0x7fb5424ed0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb53f6e165b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb53a99b4eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fb53a99b995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fb53f6e09e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fb5424e8744 in start_thread () at /lib64/libpthread.so.0 #6 0x7fb542226d3d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fb51d7e2700 (LWP 691752)): #0 0x7fb5424ed0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb53f6e165b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb53a99b4eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fb53a99b995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fb53f6e09e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fb5424e8744 in start_thread () at /lib64/libpthread.so.0 #6 0x7fb542226d3d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fb51700 (LWP 9189)): #0 0x7fb54221fb03 in select () at /lib64/libc.so.6 #1 0x7fb53f8ef849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb53f8f10c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7fb53f8f1527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb53f8a0fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb53f6dbf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb53f6e09e9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fb5424e8744 in start_thread () at /lib64/libpthread.so.0 #8 0x7fb542226d3d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fb51cfd1700 (LWP 2313)): #0 0x7fb5424ed0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb53e86f93b in () at /usr/lib64/libQt5Script.so.5 #2 0x7fb53e86f969 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fb5424e8744 in start_thread () at /lib64/libpthread.so.0 #4 0x7fb542226d3d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fb51f5bb700 (LWP 2278)): #0 0x7fb54221fb03 in select () at /lib64/libc.so.6 #1 0x7fb53f8ef849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb53f8f10c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7fb53f8f1527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb53f8a0fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb53f6dbf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb53a2c69c8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fb53f6e09e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fb5424e8744 in start_thread () at /lib64/libpthread.so.0 #9 0x7fb542226d3d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fb525a44700 (LWP 2228)): #0 0x7fb54221fb03 in select () at /lib64/libc.so.6 #1 0x7fb53f8ef849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb53f8f10c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7fb53f8f1527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb53f8a0fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb53f6dbf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb5394a71d5 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7fb53f6e09e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fb5424e8744 in start_thread () at /lib64/libpthread.so.0 #9 0x7fb542226d3d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0
[kdeconnect] [Bug 379804] New: Device with kde connect 1.6.2 is not visible
https://bugs.kde.org/show_bug.cgi?id=379804 Bug ID: 379804 Summary: Device with kde connect 1.6.2 is not visible Product: kdeconnect Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: g547...@rmqkr.net Target Milestone: --- I have kde connect 0.8 on kubuntu 14.04 lts, after installing android app version 1.6.2 on Android 4.4 device becomes unreachable (no ping) and cannot see other devices (refreshing device list on the phone shows no results). Downgrading to 1.6.1 resolves the issue. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 379804] Device with kde connect 1.6.2 is not reachable
https://bugs.kde.org/show_bug.cgi?id=379804 g547...@rmqkr.net changed: What|Removed |Added Summary|Device with kde connect |Device with kde connect |1.6.2 is not visible|1.6.2 is not reachable -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 379770] Scaled UI settings will prevent access to rescale UI or apply
https://bugs.kde.org/show_bug.cgi?id=379770 --- Comment #3 from Sebastian Kügler --- Hi Jey, Thanks for the report. Could you attach a screenshot showing the problem to this bug report? Thanks in advance! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 368868] disInstr(arm64): unhandled instruction 0xD53BE000
https://bugs.kde.org/show_bug.cgi?id=368868 Julian Seward changed: What|Removed |Added CC||jsew...@acm.org --- Comment #1 from Julian Seward --- pmaydell, is reading of cntfrq_el0 from user space always allowed? If so I can just implement this as a pass-through to the host. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 368868] disInstr(arm64): unhandled instruction 0xD53BE000
https://bugs.kde.org/show_bug.cgi?id=368868 --- Comment #2 from Julian Seward --- Ah, it looks like it is RO at EL0. Good. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379805] New: Kmail ne s'ouvre pas erreur Akoni
https://bugs.kde.org/show_bug.cgi?id=379805 Bug ID: 379805 Summary: Kmail ne s'ouvre pas erreur Akoni Product: kmail2 Version: 5.2.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: hcolsou...@gmail.com Target Milestone: --- Created attachment 105523 --> https://bugs.kde.org/attachment.cgi?id=105523&action=edit Copie d'écran avec info system et message erreur kamil Bonjour A l'ouverture de Kmail j'ai un message erreur "The Akoni personal information management service is not operationnel". Je n'arrive pas à le configurer, pourriez-vous m'aider? Dans l'attente d'une solution recevez mes sincères salutations. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 379806] New: ShowFoto crashes when clicking Color Effects from menu
https://bugs.kde.org/show_bug.cgi?id=379806 Bug ID: 379806 Summary: ShowFoto crashes when clicking Color Effects from menu Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: hobrob2...@hotmail.co.uk Target Milestone: --- Application: showfoto (5.2.0) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.57-18.3-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: Clicking Effects > Color Effects..., apllication immediately crashes. Appears to happen irrespective of image type being edited, have tried Olympus RAW format, .JPG, same result. The crash can be reproduced every time. -- Backtrace: Application: Showfoto (showfoto), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb4fde929c0 (LWP 7994))] Thread 13 (Thread 0x7fb4a9ef6700 (LWP 8010)): #0 0x7fb4f9599468 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb4fa3e25a8 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb4fa3de9a0 in () at /usr/lib64/libQt5Core.so.5 #3 0x7fb4fa3e19e9 in () at /usr/lib64/libQt5Core.so.5 #4 0x7fb4f9594744 in start_thread () at /lib64/libpthread.so.0 #5 0x7fb4f9ad8d3d in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7fb4ad50f700 (LWP 8009)): #0 0x7fb4f604df9e in () at /usr/lib64/libgomp.so.1 #1 0x7fb4f604b910 in () at /usr/lib64/libgomp.so.1 #2 0x7fb4f9594744 in start_thread () at /lib64/libpthread.so.0 #3 0x7fb4f9ad8d3d in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7fb4add10700 (LWP 8008)): #0 0x7fb4f604df9e in () at /usr/lib64/libgomp.so.1 #1 0x7fb4f604b910 in () at /usr/lib64/libgomp.so.1 #2 0x7fb4f9594744 in start_thread () at /lib64/libpthread.so.0 #3 0x7fb4f9ad8d3d in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7fb4ae511700 (LWP 8007)): #0 0x7fb4f604df9e in () at /usr/lib64/libgomp.so.1 #1 0x7fb4f604b910 in () at /usr/lib64/libgomp.so.1 #2 0x7fb4f9594744 in start_thread () at /lib64/libpthread.so.0 #3 0x7fb4f9ad8d3d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fb4aed12700 (LWP 8006)): #0 0x7fb4f604df9e in () at /usr/lib64/libgomp.so.1 #1 0x7fb4f604b910 in () at /usr/lib64/libgomp.so.1 #2 0x7fb4f9594744 in start_thread () at /lib64/libpthread.so.0 #3 0x7fb4f9ad8d3d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fb4af513700 (LWP 8005)): #0 0x7fb4f604df9e in () at /usr/lib64/libgomp.so.1 #1 0x7fb4f604b910 in () at /usr/lib64/libgomp.so.1 #2 0x7fb4f9594744 in start_thread () at /lib64/libpthread.so.0 #3 0x7fb4f9ad8d3d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fb4afd14700 (LWP 8004)): #0 0x7fb4f604df9e in () at /usr/lib64/libgomp.so.1 #1 0x7fb4f604b910 in () at /usr/lib64/libgomp.so.1 #2 0x7fb4f9594744 in start_thread () at /lib64/libpthread.so.0 #3 0x7fb4f9ad8d3d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fb4b0515700 (LWP 8003)): #0 0x7fb4f604df9e in () at /usr/lib64/libgomp.so.1 #1 0x7fb4f604b910 in () at /usr/lib64/libgomp.so.1 #2 0x7fb4f9594744 in start_thread () at /lib64/libpthread.so.0 #3 0x7fb4f9ad8d3d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fb4bf32a700 (LWP 8002)): #0 0x7fb4f9599468 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb4fa3e25a8 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb4fa3de9a0 in () at /usr/lib64/libQt5Core.so.5 #3 0x7fb4fa3e19e9 in () at /usr/lib64/libQt5Core.so.5 #4 0x7fb4f9594744 in start_thread () at /lib64/libpthread.so.0 #5 0x7fb4f9ad8d3d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fb4c9042700 (LWP 7997)): #0 0x7fb4f95990bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb4fa3e265b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb4fd29f3c9 in () at /usr/lib64/libdigikamcore.so.5.2.0 #3 0x7fb4fa3e19e9 in () at /usr/lib64/libQt5Core.so.5 #4 0x7fb4f9594744 in start_thread () at /lib64/libpthread.so.0 #5 0x7fb4f9ad8d3d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fb4d1dbc700 (LWP 7996)): #0 0x7fb4f9ad049d in poll () at /lib64/libc.so.6 #1 0x7fb4f0f2e314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb4f0f2e42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb4fa5f432b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb4fa5a1fdb in QEventLoop::exec(QFlags)
[kmymoney4] [Bug 378379] Segfault if a Report is deleted from reports menu whilst it is open in a tab.
https://bugs.kde.org/show_bug.cgi?id=378379 Thomas Baumgart changed: What|Removed |Added Latest Commit|https://commits.kde.org/kmy |https://commits.kde.org/kmy |money/30564ba57d2614f1410b8 |money/53879797bc19b45d8704e |7e1d4edd81e8fc35fc3 |be4dbcfa28449058f0e --- Comment #2 from Thomas Baumgart --- Git commit 53879797bc19b45d8704ebe4dbcfa28449058f0e by Thomas Baumgart. Committed on 14/05/2017 at 11:06. Pushed by tbaumgart into branch '4.8'. Close report's tab when deleting it from TOC FIXED-IN:5.0 (cherry picked from commit 30564ba57d2614f1410b87e1d4edd81e8fc35fc3) Signed-off-by: Thomas Baumgart M +8-0kmymoney/views/kreportsview.cpp https://commits.kde.org/kmymoney/53879797bc19b45d8704ebe4dbcfa28449058f0e -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 379807] New: ShowFoto crashes when clicking Color Effects from menu
https://bugs.kde.org/show_bug.cgi?id=379807 Bug ID: 379807 Summary: ShowFoto crashes when clicking Color Effects from menu Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: hobrob2...@hotmail.co.uk Target Milestone: --- Application: showfoto (5.2.0) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.57-18.3-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: Clicking Effects > Color Effects..., apllication immediately crashes. Appears to happen irrespective of image type being edited, have tried Olympus RAW format, .JPG, same result. The crash can be reproduced every time. -- Backtrace: Application: Showfoto (showfoto), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb4fde929c0 (LWP 7994))] Thread 13 (Thread 0x7fb4a9ef6700 (LWP 8010)): #0 0x7fb4f9599468 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb4fa3e25a8 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb4fa3de9a0 in () at /usr/lib64/libQt5Core.so.5 #3 0x7fb4fa3e19e9 in () at /usr/lib64/libQt5Core.so.5 #4 0x7fb4f9594744 in start_thread () at /lib64/libpthread.so.0 #5 0x7fb4f9ad8d3d in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7fb4ad50f700 (LWP 8009)): #0 0x7fb4f604df9e in () at /usr/lib64/libgomp.so.1 #1 0x7fb4f604b910 in () at /usr/lib64/libgomp.so.1 #2 0x7fb4f9594744 in start_thread () at /lib64/libpthread.so.0 #3 0x7fb4f9ad8d3d in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7fb4add10700 (LWP 8008)): #0 0x7fb4f604df9e in () at /usr/lib64/libgomp.so.1 #1 0x7fb4f604b910 in () at /usr/lib64/libgomp.so.1 #2 0x7fb4f9594744 in start_thread () at /lib64/libpthread.so.0 #3 0x7fb4f9ad8d3d in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7fb4ae511700 (LWP 8007)): #0 0x7fb4f604df9e in () at /usr/lib64/libgomp.so.1 #1 0x7fb4f604b910 in () at /usr/lib64/libgomp.so.1 #2 0x7fb4f9594744 in start_thread () at /lib64/libpthread.so.0 #3 0x7fb4f9ad8d3d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fb4aed12700 (LWP 8006)): #0 0x7fb4f604df9e in () at /usr/lib64/libgomp.so.1 #1 0x7fb4f604b910 in () at /usr/lib64/libgomp.so.1 #2 0x7fb4f9594744 in start_thread () at /lib64/libpthread.so.0 #3 0x7fb4f9ad8d3d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fb4af513700 (LWP 8005)): #0 0x7fb4f604df9e in () at /usr/lib64/libgomp.so.1 #1 0x7fb4f604b910 in () at /usr/lib64/libgomp.so.1 #2 0x7fb4f9594744 in start_thread () at /lib64/libpthread.so.0 #3 0x7fb4f9ad8d3d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fb4afd14700 (LWP 8004)): #0 0x7fb4f604df9e in () at /usr/lib64/libgomp.so.1 #1 0x7fb4f604b910 in () at /usr/lib64/libgomp.so.1 #2 0x7fb4f9594744 in start_thread () at /lib64/libpthread.so.0 #3 0x7fb4f9ad8d3d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fb4b0515700 (LWP 8003)): #0 0x7fb4f604df9e in () at /usr/lib64/libgomp.so.1 #1 0x7fb4f604b910 in () at /usr/lib64/libgomp.so.1 #2 0x7fb4f9594744 in start_thread () at /lib64/libpthread.so.0 #3 0x7fb4f9ad8d3d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fb4bf32a700 (LWP 8002)): #0 0x7fb4f9599468 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb4fa3e25a8 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb4fa3de9a0 in () at /usr/lib64/libQt5Core.so.5 #3 0x7fb4fa3e19e9 in () at /usr/lib64/libQt5Core.so.5 #4 0x7fb4f9594744 in start_thread () at /lib64/libpthread.so.0 #5 0x7fb4f9ad8d3d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fb4c9042700 (LWP 7997)): #0 0x7fb4f95990bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb4fa3e265b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb4fd29f3c9 in () at /usr/lib64/libdigikamcore.so.5.2.0 #3 0x7fb4fa3e19e9 in () at /usr/lib64/libQt5Core.so.5 #4 0x7fb4f9594744 in start_thread () at /lib64/libpthread.so.0 #5 0x7fb4f9ad8d3d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fb4d1dbc700 (LWP 7996)): #0 0x7fb4f9ad049d in poll () at /lib64/libc.so.6 #1 0x7fb4f0f2e314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb4f0f2e42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb4fa5f432b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb4fa5a1fdb in QEventLoop::exec(QFlags)
[kmymoney4] [Bug 379695] Loan to a friend. I entered the debt sum twice
https://bugs.kde.org/show_bug.cgi?id=379695 Thomas Baumgart changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Thomas Baumgart --- There is no need to enter amounts twice. It's just a matter of the right collection of accounts and understanding of the mechanics of accounting. The following steps should help you: 1.) Create an asset account called 'Loan to friend' 2.) Change the credit card payment in your savings account to a transfer into this asset account 3.) When you friend pays you back (even in multiple installations) enter a transfer transaction from the 'Loan to friend' account to the account that he transferred the money to. 4.) Once the asset is payed back, you can close the 'Loan to friend' account. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 379695] Loan to a friend. I entered the debt sum twice
https://bugs.kde.org/show_bug.cgi?id=379695 --- Comment #3 from Thomas Baumgart --- *** Bug 379696 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 379696] Make it easy to lend/borrow to/from a friend
https://bugs.kde.org/show_bug.cgi?id=379696 Thomas Baumgart changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Thomas Baumgart --- *** This bug has been marked as a duplicate of bug 379695 *** -- You are receiving this mail because: You are watching all bug changes.
[ksnapshot] [Bug 379808] New: ksnapshot captures screen with the 'save file' dialogue box
https://bugs.kde.org/show_bug.cgi?id=379808 Bug ID: 379808 Summary: ksnapshot captures screen with the 'save file' dialogue box Product: ksnapshot Version: 0.8.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: ase...@kde.org Reporter: dhirajha...@gmail.com Target Milestone: --- Created attachment 105524 --> https://bugs.kde.org/attachment.cgi?id=105524&action=edit ksnapshot saves the screen along with 'save file' dialogue box Launch ksnapshot save full screen capture open the saved image saved image contains 'save file' dialogue box every time.. even with delayed shots... see attachment... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379798] 4k resolution problem
https://bugs.kde.org/show_bug.cgi?id=379798 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Um... There's no screenshot attached, but have you tried to enable hidpi? Either use the checkbox in 3.1.3 or check https://docs.krita.org/KritaFAQ#On_Windows.2C_the_Krita_User_Interface_is_too_small_on_my_HiDPI_screen. to set an environment variable to enable it. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 379809] New: akonadiserver crashes with SIGSEGV after "akonadictl stop"
https://bugs.kde.org/show_bug.cgi?id=379809 Bug ID: 379809 Summary: akonadiserver crashes with SIGSEGV after "akonadictl stop" Product: Akonadi Version: 5.5.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: oleksa...@natalenko.name Target Milestone: --- Application: akonadiserver (5.5.1) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.11.0-pf2 x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Invoking "akonadictl stop" or logging out from KDE session triggers akonadiserver crash with SIGSEGV. This is latest Arch Linux with "akonadi" and "qt5-base" recompiled with debug info enabled. The same crash occurs with non-debug packages. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9776098c40 (LWP 26523))] Thread 15 (Thread 0x7f96f97fa700 (LWP 26629)): #0 0x7f9772971b63 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f9774578ba1 in QWaitConditionPrivate::wait_relative (this=0x7f975c09ed20, time=3) at thread/qwaitcondition_unix.cpp:133 #2 0x7f9774578bce in QWaitConditionPrivate::wait (this=0x7f975c09ed20, time=3) at thread/qwaitcondition_unix.cpp:141 #3 0x7f97745789c5 in QWaitCondition::wait (this=0x7f975c09eb60, mutex=0x7f975c003570, time=3) at thread/qwaitcondition_unix.cpp:215 #4 0x7f9774571104 in QThreadPoolThread::run (this=0x7f975c09eb50) at thread/qthreadpool.cpp:133 #5 0x7f9774577438 in QThreadPrivate::start (arg=0x7f975c09eb50) at thread/qthread_unix.cpp:368 #6 0x7f977296b2e7 in start_thread () from /usr/lib/libpthread.so.0 #7 0x7f9773c6254f in clone () from /usr/lib/libc.so.6 Thread 14 (Thread 0x7f96f9ffb700 (LWP 26628)): #0 0x7f9772971b63 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f9774578ba1 in QWaitConditionPrivate::wait_relative (this=0x7f975c09e8b0, time=3) at thread/qwaitcondition_unix.cpp:133 #2 0x7f9774578bce in QWaitConditionPrivate::wait (this=0x7f975c09e8b0, time=3) at thread/qwaitcondition_unix.cpp:141 #3 0x7f97745789c5 in QWaitCondition::wait (this=0x7f975c09e6f0, mutex=0x7f975c003570, time=3) at thread/qwaitcondition_unix.cpp:215 #4 0x7f9774571104 in QThreadPoolThread::run (this=0x7f975c09e6e0) at thread/qthreadpool.cpp:133 #5 0x7f9774577438 in QThreadPrivate::start (arg=0x7f975c09e6e0) at thread/qthread_unix.cpp:368 #6 0x7f977296b2e7 in start_thread () from /usr/lib/libpthread.so.0 #7 0x7f9773c6254f in clone () from /usr/lib/libc.so.6 Thread 13 (Thread 0x7f96fa7fc700 (LWP 26627)): #0 0x7f9772971b63 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f9774578ba1 in QWaitConditionPrivate::wait_relative (this=0x7f975c09e460, time=3) at thread/qwaitcondition_unix.cpp:133 #2 0x7f9774578bce in QWaitConditionPrivate::wait (this=0x7f975c09e460, time=3) at thread/qwaitcondition_unix.cpp:141 #3 0x7f97745789c5 in QWaitCondition::wait (this=0x7f975c09e2a0, mutex=0x7f975c003570, time=3) at thread/qwaitcondition_unix.cpp:215 #4 0x7f9774571104 in QThreadPoolThread::run (this=0x7f975c09e290) at thread/qthreadpool.cpp:133 #5 0x7f9774577438 in QThreadPrivate::start (arg=0x7f975c09e290) at thread/qthread_unix.cpp:368 #6 0x7f977296b2e7 in start_thread () from /usr/lib/libpthread.so.0 #7 0x7f9773c6254f in clone () from /usr/lib/libc.so.6 Thread 12 (Thread 0x7f96faffd700 (LWP 26626)): #0 0x7f9772971b63 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f9774578ba1 in QWaitConditionPrivate::wait_relative (this=0x7f975c09e050, time=3) at thread/qwaitcondition_unix.cpp:133 #2 0x7f9774578bce in QWaitConditionPrivate::wait (this=0x7f975c09e050, time=3) at thread/qwaitcondition_unix.cpp:141 #3 0x7f97745789c5 in QWaitCondition::wait (this=0x7f975c09de90, mutex=0x7f975c003570, time=3) at thread/qwaitcondition_unix.cpp:215 #4 0x7f9774571104 in QThreadPoolThread::run (this=0x7f975c09de80) at thread/qthreadpool.cpp:133 #5 0x7f9774577438 in QThreadPrivate::start (arg=0x7f975c09de80) at thread/qthread_unix.cpp:368 #6 0x7f977296b2e7 in start_thread () from /usr/lib/libpthread.so.0 #7 0x7f9773c6254f in clone () from /usr/lib/libc.so.6 Thread 11 (Thread 0x7f9718ff9700 (LWP 26615)): [KCrash Handler] #6 0x7f97747fe98c in QTimer::stop (this=0x0) at kernel/qtimer.cpp:239 #7 0x0042efd7 in Akonadi::Server::Connection::quit (this=0xd5b0d0
[kmail2] [Bug 379805] Kmail ne s'ouvre pas erreur Akoni
https://bugs.kde.org/show_bug.cgi?id=379805 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- Hello In french "Salut, les bugs reports se font en anglais par défaut mais comme je suis français ça va" :) Le bouton détail de donne des infos ? Est ce que tu as des erreurs en console ? Est ce que Akonadi est bien installé sur ta machine ?" I ask more info about errors. -- You are receiving this mail because: You are watching all bug changes.
[simon] [Bug 356452] Simon can't add Arabic or Hebrew words
https://bugs.kde.org/show_bug.cgi?id=356452
--- Comment #11 from Christopher Edward ---
(In reply to Mario Fux from comment #10)
> Ok now back to this bug. Christopher, I can add the word () bug get a
> sphinxtrain error as well. The one below:
>
> You wrote this:
> an error message appears:
> Kmeans_init.exe has stopped working
>
> Does this mean that "Kmeans_init.exe has stopped working" is your error
> message?
>
> Thanks for a quick feedback
> Mario
>
> /usr/bin/sphinxtrain -t default{201cb64d-4f61-49b4-9ed2-b3ddb536f6f0} setup
> Sphinxtrain path: /usr/lib/sphinxtrain
> Sphinxtrain binaries path: /usr/lib/sphinxtrain
> Setting up the database default{201cb64d-4f61-49b4-9ed2-b3ddb536f6f0}
>
> /usr/bin/sphinxtrain run
> Sphinxtrain path: /usr/lib/sphinxtrain
> Sphinxtrain binaries path: /usr/lib/sphinxtrain
> Running the training
>
> Configuration (e.g. etc/sphinx_train.cfg) not defined
> Compilation failed in require at
> /usr/lib/sphinxtrain/scripts/000.comp_feat/slave_feat.pl line 51.
> BEGIN failed--compilation aborted at
> /usr/lib/sphinxtrain/scripts/000.comp_feat/slave_feat.pl line 51.
The error message is: "Kmeans_init.exe has stopped working"
Now I retested on 0.4.1 and another error showed up, have a look:
https://youtu.be/aLSiF2y2FvQ
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 365161] Can't select which pages to print
https://bugs.kde.org/show_bug.cgi?id=365161 JMarieChosson changed: What|Removed |Added CC||jean-marie.chosson2@wanadoo ||.fr --- Comment #1 from JMarieChosson --- Hello, I'm also searching such function in Okular ! Without it, even if okular is now my new viewer by default, i often re-use evince to make "aux p'tits oignons" printing ! This function is already able to be used with EVINCE or LibreOffice, and is very convenient ! Thanks for this very good tool : okular ! And sorry for my bad use of english... Kore JMarie -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 368868] disInstr(arm64): unhandled instruction 0xD53BE000
https://bugs.kde.org/show_bug.cgi?id=368868 Julian Seward changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Julian Seward --- Fixed, vex r3368. -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 379810] New: qca compilation fails with openssl 1.1
https://bugs.kde.org/show_bug.cgi?id=379810 Bug ID: 379810 Summary: qca compilation fails with openssl 1.1 Product: qca Version: Git Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dr...@land.ru Reporter: ha...@hboeck.de CC: br...@frogmouth.net, jus...@affinix.com Target Milestone: --- Created attachment 105525 --> https://bugs.kde.org/attachment.cgi?id=105525&action=edit build failure Latest qca (both 2.1.3 and git head) fails to build with openssl 1.1. I'll attach the build failure output. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 249844] wrong memo field after duplicating and editing transaction
https://bugs.kde.org/show_bug.cgi?id=249844 Thomas Baumgart changed: What|Removed |Added Latest Commit|https://commits.kde.org/kmy |https://commits.kde.org/kmy |money/398304bcf331a322a0fe7 |money/fbd612529ed896765b82f |e475775aea887c4b565 |37c912d761aa582b8c2 --- Comment #14 from Thomas Baumgart --- Git commit fbd612529ed896765b82f37c912d761aa582b8c2 by Thomas Baumgart. Committed on 14/05/2017 at 13:16. Pushed by tbaumgart into branch '4.8'. Update memo in the other split if requested FIXED-IN:5.0 (cherry picked from commit 398304bcf331a322a0fe7e475775aea887c4b565) and adapted to work on Qt4.8 Signed-off-by: Thomas Baumgart M +7-3kmymoney/dialogs/transactioneditor.cpp https://commits.kde.org/kmymoney/fbd612529ed896765b82f37c912d761aa582b8c2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379811] New: segfault while using plasma-discover
https://bugs.kde.org/show_bug.cgi?id=379811 Bug ID: 379811 Summary: segfault while using plasma-discover Product: Discover Version: 5.9.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: rick.bel...@gmail.com Target Milestone: --- Application: plasma-discover (5.9.4) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.0-20-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: I was searching for various plasma themes. I had run it manually with plasma-discover --compact full. The crash ended with this on the screen: org.kde.knewstuff.core: Redirected to "https://download.kde.org/khotnewstuff/korganizercalenders/korganizercalenders.xml"; ... org.kde.knewstuff.core: Redirected to "https://distribute.kde.org/khotnewstuff/korganizercalenders/korganizercalenders.xml"; ... KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = plasma-discover path = /usr/bin pid = 11328 KCrash: Arguments: /usr/bin/plasma-discover --compact full KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 25 and type 'Write', disabling... QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 16 and type 'Read', disabling... QSocketNotifier: Invalid socket 13 and type 'Read', disabling... QSocketNotifier: Invalid socket 34 and type 'Read', disabling... QSocketNotifier: Invalid socket 19 and type 'Read', disabling... QSocketNotifier: Invalid socket 26 and type 'Write', disabling... QSocketNotifier: Invalid socket 32 and type 'Write', disabling... QSocketNotifier: Invalid socket 20 and type 'Read', disabling... QSocketNotifier: Invalid socket 40 and type 'Write', disabling... QSocketNotifier: Invalid socket 27 and type 'Write', disabling... The crash can be reproduced sometimes. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f712f3ee8c0 (LWP 11328))] Thread 19 (Thread 0x7f70d97fa700 (LWP 11456)): #0 0x7f712a99e18d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f7125650576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f712565068c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f712b5caf2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f712b57488a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f712b3a1fe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f712b3a6c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f71277816da in start_thread (arg=0x7f70d97fa700) at pthread_create.c:456 #8 0x7f712a9aa17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 18 (Thread 0x7f70daffd700 (LWP 11430)): #0 0x7f712f2cfe15 in __GI___tls_get_addr (ti=0x7f712b9bf660) at dl-tls.c:834 #1 0x7f712b3a5b26 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f712b5ca67a in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f712564fa6d in g_main_context_prepare () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f712565049b in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f712565068c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f712b5caf2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f712b57488a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f712b3a1fe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f712b3a6c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f71277816da in start_thread (arg=0x7f70daffd700) at pthread_create.c:456 #11 0x7f712a9aa17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 17 (Thread 0x7f70f0afa700 (LWP 11428)): #0 0x7f712a999cad in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f7125694b30 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7125650042 in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7125650514 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f712565068c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f712b5caf2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f712b57488a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/l
[kile] [Bug 379812] New: Unable to write a remote file
https://bugs.kde.org/show_bug.cgi?id=379812 Bug ID: 379812 Summary: Unable to write a remote file Product: kile Version: 2.1.3 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: user interface Assignee: michel.lud...@kdemail.net Reporter: n.ah...@tudelft.nl Target Milestone: --- When I try to write to a remote tex file in a mounted file system. I receive the following error: "The document could not be saved, as it was not possible to write to /run/user/10024/gvfs/sftp:host=officepc,user=nauman/data/mytex.tex. Check that you have write access to this file or that enough disk space is available." Obviously the disk is not full. I have also tried by giving full permissions on the file but it doesn't work. So much so it also deletes all the contents of the file when kile is closed. For a local tex file it works perfectly. I am running Ubuntu 16.04. My kile version is 2.1.3 using KDE Development Platform 4.14.16 best regards Nauman -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 379812] Unable to write a remote tex file via kile
https://bugs.kde.org/show_bug.cgi?id=379812 Nauman Ahmed changed: What|Removed |Added Summary|Unable to write a remote|Unable to write a remote |file|tex file via kile -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 374075] File does not appear in Dolphin after creation in home folder
https://bugs.kde.org/show_bug.cgi?id=374075 --- Comment #4 from Elvis Angelaccio --- (In reply to Elvis Angelaccio from comment #1) > Btw the problem is that the dir lister does not emit completed() ...because KDirWatch::self() does not emit the dirty() signal for "/home/user" and KCoreDirListerCache::slotFileDirty doesn't get called. I think the bug might be in KDirWatch, kdirwatch.cpp receives the CREATE signal for "/home/user" but for some reason does not append "/home/user" to e->m_pendingFileChanges. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 208625] Temporary files (for previewing files in the trash or remote files) aren't deleted
https://bugs.kde.org/show_bug.cgi?id=208625 --- Comment #41 from David Faure --- Git commit 78c45a1ea0e28a98f34c6d113c807f14700b22d4 by David Faure. Committed on 14/05/2017 at 13:41. Pushed by dfaure into branch 'master'. PreviewJob: clean up empty temp file when get() fails. (e.g. because it's a directory) M +13 -4src/widgets/previewjob.cpp https://commits.kde.org/kio/78c45a1ea0e28a98f34c6d113c807f14700b22d4 -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 379812] Unable to write a remote tex file via kile
https://bugs.kde.org/show_bug.cgi?id=379812 Nauman Ahmed changed: What|Removed |Added Platform|Mint (Ubuntu based) |Ubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 208625] Temporary files (for previewing files in the trash or remote files) aren't deleted
https://bugs.kde.org/show_bug.cgi?id=208625 David Faure changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kio ||/1620032772465be475ae0746af ||f63a566ef2a546 Version Fixed In||5.35 Status|CONFIRMED |RESOLVED --- Comment #42 from David Faure --- Git commit 1620032772465be475ae0746aff63a566ef2a546 by David Faure. Committed on 14/05/2017 at 13:48. Pushed by dfaure into branch 'master'. PreviewJob: skip remote directories. Too expensive to preview. For some protocols, file_copy() would end up copying the whole directory locally! FIXED-IN: 5.35 M +6-0src/widgets/previewjob.cpp https://commits.kde.org/kio/1620032772465be475ae0746aff63a566ef2a546 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379751] I18N_ARGUMENT_MISSING in Edit Metadata
https://bugs.kde.org/show_bug.cgi?id=379751 --- Comment #2 from philippe weyland --- Is the window title issue linked to the fact I'm not able to save the changes ? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379791] Confusing Account Wizard dialog
https://bugs.kde.org/show_bug.cgi?id=379791 --- Comment #2 from Martin --- Created attachment 105526 --> https://bugs.kde.org/attachment.cgi?id=105526&action=edit Screenshot I mean this dialog. There is a "Postfach erstellen" button, which is annoying. It would be better to remove this button. And in addition hide button "Finish" for this step. It makes no sense to show this disabled button here. The UI of KDE programs are sometimes overloaded. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 379813] New: Korganizer and Kaddressbook doesnt sync anymore using Webdav
https://bugs.kde.org/show_bug.cgi?id=379813 Bug ID: 379813 Summary: Korganizer and Kaddressbook doesnt sync anymore using Webdav Product: korganizer Version: 5.5.1 Platform: PCLinuxOS OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: groupware Assignee: kdepim-b...@kde.org Reporter: berndwet...@mailbox.org Target Milestone: --- Since the update to the 17.04 Version, Addressbook and Korganizer are not synced anymore. The 17.04 Update installed a new package "kdav" (17.04..). Since that time it is still possible to set up a new calendar in "DAV- Groupware Resources". After adding required user information and collecting the resources, Events are not displayed in Korganizer, and Contacts are not displayed in Kaddressbook. It you have already setup your account before the upgrade, everything is visible but it is not syncing anymore with a webdav server. I am collecting email, Contacts and Events from my provider mailbox.org. Collecting Emails is not affected. Bernd -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 353312] Image thumbnails (jpeg) missing for files bigger than 3 MB
https://bugs.kde.org/show_bug.cgi?id=353312 Alex Bikadorov changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Alex Bikadorov --- *** This bug has been marked as a duplicate of bug 329307 *** -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 329307] Can not configure built-in previewer to display .jpg files over 5 Mb
https://bugs.kde.org/show_bug.cgi?id=329307 Alex Bikadorov changed: What|Removed |Added CC||zal...@volny.cz --- Comment #1 from Alex Bikadorov --- *** Bug 353312 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 329307] Can not configure built-in previewer to display .jpg files over 5 Mb
https://bugs.kde.org/show_bug.cgi?id=329307 Alex Bikadorov changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED CC||alex.bikado...@kdemail.net --- Comment #2 from Alex Bikadorov --- Maximum file size was removed in KDE Frameworks/KIO, see https://phabricator.kde.org/D4552. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 329307] Can not configure built-in previewer to display .jpg files over 5 Mb
https://bugs.kde.org/show_bug.cgi?id=329307 Alex Bikadorov changed: What|Removed |Added CC||m...@pensaro.net --- Comment #3 from Alex Bikadorov --- *** Bug 321098 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 321098] Preview configuration
https://bugs.kde.org/show_bug.cgi?id=321098 Alex Bikadorov changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||alex.bikado...@kdemail.net Resolution|--- |DUPLICATE --- Comment #1 from Alex Bikadorov --- *** This bug has been marked as a duplicate of bug 329307 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379805] Kmail ne s'ouvre pas erreur Akoni
https://bugs.kde.org/show_bug.cgi?id=379805 --- Comment #2 from Daniel --- Bonjour Merci pour prendre un peu de temps pour me répondre. C'est justement ce que je me pose comme question. Je viens juste de faire démarrer thunderbird et ainsi j'ai pu voir le mail. Que dois-je faire pour remonter les messages d'erreur? D. Auquier je viens de commencer à installer Ubuntu*Mate après avoir lu pas mal de pages d'info je fais le grand saut vers ce nouvel univers afin d'oublier Microsoft et ses bugs de virus. Merci d'avance pour l'aide. Cordialement. AD Le 14/05/2017 à 14:32, Laurent Montel a écrit : > https://bugs.kde.org/show_bug.cgi?id=379805 > > Laurent Montel changed: > > What|Removed |Added > > CC||mon...@kde.org > > --- Comment #1 from Laurent Montel --- > Hello > In french "Salut, les bugs reports se font en anglais par défaut mais comme je > suis français ça va" :) > Le bouton détail de donne des infos ? > Est ce que tu as des erreurs en console ? Est ce que Akonadi est bien installé > sur ta machine ?" > > I ask more info about errors. > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379751] I18N_ARGUMENT_MISSING in Edit Metadata
https://bugs.kde.org/show_bug.cgi?id=379751 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #3 from caulier.gil...@gmail.com --- no. It's just a translation format problem... -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 356785] kwallet4 still asks for password although pam-kwallet should open both kwallet4 and kwallet5
https://bugs.kde.org/show_bug.cgi?id=356785 Geert Janssens changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Geert Janssens --- Now that most of the applications I use have switched to kf5, I no longer have a use case to test this. And since no other users have confirmed this, I'll just close this bug again. I'm hesitating on the resolution reason as none really fit the bill. I'll choose "Unmaintained". If that's a wrong choice, feel free to correct it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 356791] KDE Applications won't show contents of nfs mount (automount)
https://bugs.kde.org/show_bug.cgi?id=356791 Geert Janssens changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #6 from Geert Janssens --- I have resolved this issue by exporting directories outside of the /home directory on the server. It seems like there is some security feature interfering with exporting directories under /home. I never was able to figure out whether this is something in nfs or selinux or whatever. So works for me now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379814] New: Black Screen on Resuming from Suspend to RAM with Nvidia Proprietary Driver
https://bugs.kde.org/show_bug.cgi?id=379814 Bug ID: 379814 Summary: Black Screen on Resuming from Suspend to RAM with Nvidia Proprietary Driver Product: kwin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: jonespanic...@gmail.com Target Milestone: --- I get a black screen on resuming from suspend to RAM. This happens every single time, but only when using Nvidia proprietary driver. Cannot go to tty with Ctrl-Alt-Fn keys. Nothing works. Just black screen. Not even mouse pointer. I am not sure if this is to be fixed by Nvidia guys or KDE. -Linux Mint 18.1 KDE version, Nvidia 930MX graphics, driver used Nvidia 375/378/381. OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce 930MX/PCIe/SSE2 OpenGL version string: 3.1.0 NVIDIA 381.22 OpenGL shading language version string: 1.40 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 381.22 GPU class: Unknown OpenGL version: 3.1 GLSL version: 1.40 X server version: 1.18.4 Linux kernel version: 4.4 Requires strict binding:no GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no I'm fed up of this issue, I can give you any diagnostic info needed, just let me know what is needed... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379805] Kmail ne s'ouvre pas erreur Akoni
https://bugs.kde.org/show_bug.cgi?id=379805 --- Comment #3 from Daniel --- Ré BonjourLe bouton "Détail" ne réagit pas j'ai oublié de le mentionner dans ma réponse.Cordialement D. AUQUIER Envoyé depuis mon appareil Samsung Message d'origine De : Laurent Montel Date : 2017/05/14 14:32 (GMT+01:00) À : hcolsou...@gmail.com Objet : [kmail2] [Bug 379805] Kmail ne s'ouvre pas erreur Akoni https://bugs.kde.org/show_bug.cgi?id=379805 Laurent Montel changed: What |Removed |Added CC| |mon...@kde.org --- Comment #1 from Laurent Montel --- Hello In french "Salut, les bugs reports se font en anglais par défaut mais comme je suis français ça va" :) Le bouton détail de donne des infos ? Est ce que tu as des erreurs en console ? Est ce que Akonadi est bien installé sur ta machine ?" I ask more info about errors. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 371503] disInstr(arm64): unhandled instruction 0xF89F0000 (prfum)
https://bugs.kde.org/show_bug.cgi?id=371503 Julian Seward changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Julian Seward --- Fixed, vex r3369. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379791] Confusing Account Wizard dialog
https://bugs.kde.org/show_bug.cgi?id=379791 Burkhard Lueck changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #3 from Burkhard Lueck --- You did not provide your version of KMail (kmail -v). Anyway master and stable version have a different dialog, therefore your report is invalid -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 379815] New: random crash when changing system audio volume with media keys
https://bugs.kde.org/show_bug.cgi?id=379815 Bug ID: 379815 Summary: random crash when changing system audio volume with media keys Product: okular Version: 1.1.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: keziolio...@gmail.com Target Milestone: --- Okular crashed randomly when increasing the volume with the keyboard media keys, I was not able to reproduce Arch linux with kde-unstable, okular 1.1.1, everything is up to date mag 14 16:24:05 desktop systemd-coredump[9116]: Process 15413 (okular) of user 1000 dumped core. Stack trace of thread 15413: #0 0x7f879a206a10 raise (libc.so.6) #1 0x7f879a20813a abort (libc.so.6) #2 0x7f87856a7212 pa_fdsem_post (libpulsecommon-10.0.so) #3 0x7f87856bf2ea pa_srbchannel_write (libpulsecommon-10.0.so) #4 0x7f87856bd4fd n/a (libpulsecommon-10.0.so) #5 0x7f87856be668 n/a (libpulsecommon-10.0.so) #6 0x7f87856be989 n/a (libpulsecommon-10.0.so) #7 0x7f87856bf20a n/a (libpulsecommon-10.0.so) #8 0x7f8785b07f36 n/a (libpulse-mainloop-glib.so.0) #9 0x7f87950097b7 g_main_context_dispatch (libglib-2.0.so.0) #10 0x7f8795009a20 n/a (libglib-2.0.so.0) #11 0x7f8795009acc g_main_context_iteration (libglib-2.0.so.0) #12 0x7f879abdc07f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #13 0x7f879ab858ca _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #14 0x7f879ab8de14 _ZN16QCoreApplication4execEv (libQt5Core.so.5) #15 0x0040b97d n/a (okular) #16 0x7f879a1f3511 __libc_start_main (libc.so.6) #17 0x0040d24a _start (okular) Stack trace of thread 15415: #0 0x7f879a2b567d poll (libc.so.6) #1 0x7f87950099b6 n/a (libglib-2.0.so.0) #2 0x7f8795009acc g_main_context_iteration (libglib-2.0.so.0) #3 0x7f879abdc07f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x7f879ab858ca _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x7f879a9a7a73 _ZN7QThread4execEv (libQt5Core.so.5) #6 0x7f879aff1125 n/a (libQt5DBus.so.5) #7 0x7f879a9ac6d8 n/a (libQt5Core.so.5) #8 0x7f8796f512e7 start_thread (libpthread.so.0) #9 0x7f879a2bf54f __clone (libc.so.6) Stack trace of thread 15418: #0 0x7f8796f57756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x7f87796070cb n/a (radeonsi_dri.so) #2 0x7f8779606df7 n/a (radeonsi_dri.so) #3 0x7f8796f512e7 start_thread (libpthread.so.0) #4 0x7f879a2bf54f __clone (libc.so.6) Stack trace of thread 15414: #0 0x7f879a2b567d poll (libc.so.6) #1 0x7f8797d048e0 n/a (libxcb.so.1) #2 0x7f8797d06679 xcb_wait_for_event (libxcb.so.1) #3 0x7f878f642239 n/a (libQt5XcbQpa.so.5) #4 0x7f879a9ac6d8 n/a (libQt5Core.so.5) #5 0x7f8796f512e7 start_thread (libpthread.so.0) #6 0x7f879a2bf54f __clone (libc.so.6) Stack trace of thread 15416: #0 0x7f8796f57756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x7f87796070cb n/a (radeonsi_dri.so) #2 0x7f8779606df7 n/a (radeonsi_dri.so) #3 0x7f8796f512e7 start_thread (libpthread.so.0) #4 0x7f879a2bf54f __clone (libc.so.6) Stack trace of thread 15419: #0 0x7f8796f57756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x7f87796070cb n/a (radeonsi_dri.so) #2 0x7f8779606df7 n/a (radeonsi_dri.so) #3 0x7f8796f512e7 start_thread (libpthread.so.0) #4 0x7f879a2bf54f __clone (libc.so.6) Stack trace of thread 15417: #0 0x7f8796f57756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x7f87796070cb n/a (radeonsi_dri.so) #2 0x7f8779606df7 n/a (radeonsi_dri.so) #3 0x7f8796f512e7 start_thread (libpthread.so.0) #4 0x7f879a2bf54f __clone (libc.so.6) Stack trace of thread 15420: #0 0x7f8796f57756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x7f87796070cb n/a (radeonsi_dri.so) #2 0x7f8779606df7 n/a (radeonsi_dri.so) #3 0x7f8796f512e7 start_thread (libpthread.so.0) #4 0x7f879a2bf54f __clone (libc.so.6) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379816] New: Cannot edit IMAP resources after upgrade to 5.5.0
https://bugs.kde.org/show_bug.cgi?id=379816 Bug ID: 379816 Summary: Cannot edit IMAP resources after upgrade to 5.5.0 Product: kmail2 Version: 5.5.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: guoyunhebr...@gmail.com Target Milestone: --- I have two Gmail accounts in KMail. After upgrading to 5.5.0 today, I was asked to provide Google account passwords. I did. After that, I found that I cannot edit IMAP resources in KMail Settings. When I click the modify button, it said "the resource is broken" and IMAP status is "cannot start". -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 379817] New: Behaviour change: JPEG image preview scaled to widget size
https://bugs.kde.org/show_bug.cgi?id=379817 Bug ID: 379817 Summary: Behaviour change: JPEG image preview scaled to widget size Product: kio-extras Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: default Assignee: plasma-de...@kde.org Reporter: alex.bikado...@kdemail.net Target Milestone: --- Created attachment 105528 --> https://bugs.kde.org/attachment.cgi?id=105528&action=edit Dolphin JPEG image preview Preview images in KImageFilePreview for JPEG files are always scaled to the widget size - no matter how how small the jpeg is. PNGs are not scaled. Dolphin and Krusader are affected. See screenshot. I tracked it down to thumbnail/jpegcreator and its maybe caused by https://git.reviewboard.kde.org/r/129851/ Version: KDE Frameworks 5.33.0 kio-extras 17.04.0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 379818] New: Kate, Kwrite seems to not apply acls rules
https://bugs.kde.org/show_bug.cgi?id=379818 Bug ID: 379818 Summary: Kate, Kwrite seems to not apply acls rules Product: kate Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: jcd...@free.fr Target Milestone: --- Created attachment 105529 --> https://bugs.kde.org/attachment.cgi?id=105529&action=edit screenshots of acl command and other. Initial conditions : - OS : Leap 42.2 - Kernel : 4.4.62-18.6-default - x86_64 - File system : ext4 and xfs UUID=857c3295-5944-4593-82e2-bb90dede4312 / ext4 noatime,acl,user_xattr 1 1 UUID=6173a3df-4407-427c-b01a-c2d664471fc8 /data3_dwnld_pub xfs defaults 1 2 - ACL : 2.2.52-8.55 - KDE : Frameworks 5.26.0 - Qt 5.6.1 (built against 5.6.1) - KATE : Version 16.08.2 Goal : In folders defined as "PUBLIC" for users in group "publicuser', any users can do anythings but cannot delete objects they do not own. 1st Step : Creation of initial group, user and folders Create group publicuser Create user publicuser (no login user), user_test1, user_test2 Add publicuser, user_test1, user_test2 to group publicuser Create a new folder : mkdir -p /d_pub_folder chown publicuser:publicuser /d_pub_folder Create sub-folder for each regular user mkdir -p /d_pub_folder/user_test1 chown user_test1:publicuser /d_pub_folder/user_test1 mkdir -p /d_pub_folder/user_test2 chown user_test2:publicuser /d_pub_folder/user_test2 Set properties on new folders chmod -R 770 /d_pub_folder chmod -R g+s /d_pub_folder chmod -R +t /d_pub_folder Set ACL on new folders #set user to rwx, group to ---, group publicuser to rwx,other to --- setfacl -R -m u::rwx,g::---,g:publicuser:rwx,o:--- /d_pub_folder #set default : user to rwx, group to ---, group publicuser to rwx,other to --- setfacl -R -d -m u::rwx,g::---,g:publicuser:rwx,o:--- /d_pub_folder 2nd Step : Files creation Create new files owned by each user in their respective folder su to user_test1 echo "Create by user_test1 in user_test1's folder" > /d_pub_folder/user_test1/testfile_1.txt su to user_test2 echo "Create by user_test2 in user_test2's folder" > /d_pub_folder/user_test2/testfile_2.txt Create new files own by user_test2 in user_test2's folder echo "Create by user_test2 in user_test1's folder" > /d_pub_folder/user_test1/testfile_4.txt 3rd Step : ACL Check from a "public" folder /d_pub_folder/ 1°) OK : any user can create a file in it's own folder 2°) OK : any user can create a file in folder owned by others 3°) OK : any user can modify a file they owned in folder owned by others 4°) OK : any user cannot delete a file they do not owned any where 5°) OK : any user can modify a file they do not owned using vi in a terminal emulator (Konsole) What does not work USING KATE or KWRITE 6°) FAILED : any user cannot modify a file they do not owned. Write is denied Any help is welcome. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 379818] Kate, Kwrite seems to not apply acls rules
https://bugs.kde.org/show_bug.cgi?id=379818 jcdole changed: What|Removed |Added Platform|Other |openSUSE RPMs Severity|normal |grave Version|unspecified |16.08 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379819] New: [Wayland] QT UI element overflow in systemsettings Display section
https://bugs.kde.org/show_bug.cgi?id=379819 Bug ID: 379819 Summary: [Wayland] QT UI element overflow in systemsettings Display section Product: kwin Version: 5.9.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: rajdeepna...@gmail.com Target Milestone: --- Created attachment 105530 --> https://bugs.kde.org/attachment.cgi?id=105530&action=edit Overflown UI in systemsettings Display tab Steps to reproduce: 1. Go to systemsettings -> Display and Monitor -> Displays 2. Resize the window to the smallest size possible 3. Scroll down. The Display layout section will overflow outside the application window, as seen in attached screenshot. Also, moving the window around causes a trail of overflown UI to appear, which I could not capture in a screenshot. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 338908] KISS feed sync (brainstorming)
https://bugs.kde.org/show_bug.cgi?id=338908 James Cain changed: What|Removed |Added CC||dequ...@mykolab.com --- Comment #1 from James Cain --- I agree that akregator needs a syncing-service, but I'd rather see it built-in. In other words, not using a 3rd party service. It would just need a back-end and a front-end, similar to how Quassel handles syncing for IRC. The back-end could be on a user's main PC, a server on the LAN, a Kodi or Plex plugin, reside within OwnCloud, or via a hosted service like Digital Ocean or maybe a service that KDE could provide. I could see potentially many great enterprise uses for this as well, such as syncing Intranet news and information within a company or school, etc. If anyone thinks this may have merit, I could spin-off a separate bug report. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 379820] New: KDE File chooser items shown in multiple lines when sort isn't set to 'by name'
https://bugs.kde.org/show_bug.cgi?id=379820 Bug ID: 379820 Summary: KDE File chooser items shown in multiple lines when sort isn't set to 'by name' Product: kde Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: pmarget...@gmail.com Target Milestone: --- Created attachment 105531 --> https://bugs.kde.org/attachment.cgi?id=105531&action=edit Sorting is set do 'by date' and 'descending' is enabled. Folder names are chopped up into multiple lines. KDE File chooser (open or save as dialogues) items shown in multiple lines when sort isn't set to 'by name'. Using sort 'by type', 'by date', 'by size' results in content being chopped up into multiple rows. Icon size must be set to something other than smallest to reproduce this bug. More details and a discussion on this bug can be found here: https://forum.manjaro.org/t/kde-open-save-dialogue-bug-item-names-multi-lined/23706 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 321863] Krusader crasher during synchronization of directory with tons of sub-dirs
https://bugs.kde.org/show_bug.cgi?id=321863 Alex Bikadorov changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Alex Bikadorov --- Was the "Compare by content" setting checked? If so, does it crash when unchecked? (I know this is an old report.) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 379548] IMAP resource crashes on configure operation
https://bugs.kde.org/show_bug.cgi?id=379548 Luca Giambonini changed: What|Removed |Added CC||luc...@bluewin.ch --- Comment #7 from Luca Giambonini --- Created attachment 105532 --> https://bugs.kde.org/attachment.cgi?id=105532&action=edit journalctl crash log with debug symbols backstrace journal -f with debug symbols -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 379820] KDE File chooser items names shown in multiple lines when sort isn't set to 'by name'
https://bugs.kde.org/show_bug.cgi?id=379820 pmarget...@gmail.com changed: What|Removed |Added Summary|KDE File chooser items |KDE File chooser items |shown in multiple lines |names shown in multiple |when sort isn't set to 'by |lines when sort isn't set |name' |to 'by name' -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 202414] allow to hide status bar and toolbar
https://bugs.kde.org/show_bug.cgi?id=202414 --- Comment #20 from Valerio Pilo --- I've submitted https://phabricator.kde.org/D5854 (to fix the statusbar persistence) and https://phabricator.kde.org/D5855 (to add the toolbar menu entry). I've used standard KDE Actions, so they will end up in the Settings menu like in all other apps. Perhaps we should move the Sidebar menu entry there as well, for the sake of consistency. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 203119] keyboard shortcuts: user defined shortcuts are vanishing (are auto deleted)
https://bugs.kde.org/show_bug.cgi?id=203119 kranthi changed: What|Removed |Added CC||kranthi.t2...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 379448] There is no information
https://bugs.kde.org/show_bug.cgi?id=379448 --- Comment #20 from Cristian Aravena Romero --- == New packages for ubuntu [0]zesty & ubuntu [0]artful == [0] https://bugs.launchpad.net/bugs/1689641 [1] https://bugs.launchpad.net/bugs/1690595 "Good idea, it doesn't hurt to be ahead of the game for once... The packages for artful have been build and published. Cheers, Rok" -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 379548] IMAP resource crashes on configure operation
https://bugs.kde.org/show_bug.cgi?id=379548 Sebastian Kuhne changed: What|Removed |Added CC||sebastiankuhne1@googlemail. ||com --- Comment #8 from Sebastian Kuhne --- I am on openSUSE Tumbleweed (latest update), with KDE applications 17.04. I am facing the same issue. Once generated an IMAP resource in KDE's Kontact it can't be configured properly. The same happens using aconadiconsole (Agents --> IMAP resource --> Configure --> Configure Natively) - no window opens for configuration. The IMAP resource; however, is a standard Google mail account. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 379820] KDE File chooser items names shown in multiple lines when sort isn't set to 'by name'
https://bugs.kde.org/show_bug.cgi?id=379820 DeMus changed: What|Removed |Added CC||jan.muss...@gmail.com --- Comment #1 from DeMus --- Same thing as what pmarget...@gmail.com writes happens to me in my Manjaro 17.01 KDE. Only when the sort key is set to "name" things are okay, if not file and folder names are chopped after second character. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 379820] KDE File chooser items names shown in multiple lines when sort isn't set to 'by name'
https://bugs.kde.org/show_bug.cgi?id=379820 --- Comment #2 from DeMus --- P.s. KDE Plasma 5.9.5 KDE Frameworks 5.33.0 Qt version 5.8.0 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 379770] Scaled UI settings will prevent access to rescale UI or apply
https://bugs.kde.org/show_bug.cgi?id=379770 --- Comment #4 from jey.and@gmail.com --- Created attachment 105533 --> https://bugs.kde.org/attachment.cgi?id=105533&action=edit Screenshot of display cut-off -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379790] MDI SubWindows are frozen (non-responsive) with Breeze and Oxygen
https://bugs.kde.org/show_bug.cgi?id=379790 --- Comment #3 from Tim E. Real --- Created attachment 105534 --> https://bugs.kde.org/attachment.cgi?id=105534&action=edit Frozen MDI test UI file 1 Open in Qt5Designer or Creator. The MDI sub windows are frozen in Breeze or Oxygen. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 379548] IMAP resource crashes on configure operation
https://bugs.kde.org/show_bug.cgi?id=379548 --- Comment #9 from Luca Giambonini --- For me is fixed with: https://cgit.kde.org/kdepim-runtime.git/patch/?id=e8b131fe179f474af9de12f1289ea70cd99e90e4 -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 379821] New: Exponent button (x*10y) only works with numbers entered immediately previously
https://bugs.kde.org/show_bug.cgi?id=379821 Bug ID: 379821 Summary: Exponent button (x*10y) only works with numbers entered immediately previously Product: kcalc Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: ete...@alum.rit.edu Reporter: kde-bugzi...@jonathancottrill.net Target Milestone: --- KCalc version 17.04.0, with KDE Frameworks 5.32.0 and Qt 5.7.1. If you enter a number with the keyboard or application buttons, the Exponent (x*10y) button works appropriately; example: 1. Enter 2 in KCalc 2. Press x*10y button 3. Observer 2e0 in display However, if the current number was not entered immediately previously, it is "lost" (treated as zero). Issue #1: Pasted value 1. Copy single character 2 to clipboard 2. Paste into KCalc 3. Press x*10y button 4. Observe result is 0e0, *NOT* 2e0, as expected Issue #2: Result of prior calculation (perhaps arguable, as other calculators treat this case in different ways) 1. Add 1 and 1 2. Observe result is 2 3. Press x*10y button 4. Observe result is 0e0, *NOT* 2e0, as expected -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 379821] Exponent button (x*10y) only works with numbers entered immediately previously
https://bugs.kde.org/show_bug.cgi?id=379821 Jonathan Cottrill changed: What|Removed |Added CC||kde-bugzilla@jonathancottri ||ll.net -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 379822] New: Multimedia icon confusing for new users
https://bugs.kde.org/show_bug.cgi?id=379822 Bug ID: 379822 Summary: Multimedia icon confusing for new users Product: systemsettings Version: 5.9.5 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ber...@codewiz.org Target Milestone: --- Warning, UX bug. Feel free to close as WONTFIX if you disagree. I recently observed a new KDE user browse through the main Systemsettings window in search for the sound configuration KCM. This user missed the Multimedia icon because: 1) "This icon looks like a monitor, but I wanted to configure sound so I was looking for a speaker" 2) No mental association between Sound / Audio the abstract concept of Multimedia 3) Multimedia appears way down in the window Here are some (personal) ideas to give better cues to the user: 1) Split the Sound kcm and promote it to a top-level entry in the systemsettings main window 2) Change the Multimedia icon to look more distinct from a display, possibly including a speaker logo (either alone, or besides a film, a "play button" or a clapperboard). 3) Rename Multimedia to "Sound and Video" 4) Move the Hardware group up, at least before Network and possibly also before Personalization -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366451] "display scaling" on hidpi screen results in poor font quality
https://bugs.kde.org/show_bug.cgi?id=366451 Jan Chren (rindeal) changed: What|Removed |Added CC||dev.rindeal+bugs.kde.org@gm ||ail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379790] MDI SubWindows are frozen (non-responsive) with Breeze and Oxygen
https://bugs.kde.org/show_bug.cgi?id=379790 --- Comment #4 from Tim E. Real --- Wow. I never tried saving/re-opening a test-case UI file before. This fresh suse installation is on Breeze by default. So the attached UI file's MDI sub windows are frozen even without previewing the form. They are frozen right in the Qt5Designer editor ! Qt Version 5.7.1 As mentioned, also observed on KUbuntu 6.0.4 LTS, worse it happens even without setting any stylesheet on the QMDIArea. (The supplied UI file has a stylesheet set on the QMDIArea.) Also observed on another, older PC running same KUbuntu 6.0.4 LTS. Others in our group have also reported the problem. Only commonality I can think of, at least in my setup, is the Nouveau nVidia drivers. But I think I tried an ATI card at one point. Everything is fine if the attached UI file is opened in Qt4Designer! Indeed, our Qt app was fine in Qt4 (and Qt3, Qt2, Qt1, he he.) Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366451] "display scaling" on hidpi screen results in poor font quality
https://bugs.kde.org/show_bug.cgi?id=366451 --- Comment #17 from Jan Chren (rindeal) --- Created attachment 105535 --> https://bugs.kde.org/attachment.cgi?id=105535&action=edit logout overlay; scaling=1.5 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 355410] Scroll speed of QML scroll area is too slow with the xf86-input-libinput driver
https://bugs.kde.org/show_bug.cgi?id=355410 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379314] Crash when restoring activity
https://bugs.kde.org/show_bug.cgi?id=379314 --- Comment #2 from Jaime Torres --- Created attachment 105536 --> https://bugs.kde.org/attachment.cgi?id=105536&action=edit New crash information added by DrKonqi dolphin (17.04.0) using Qt 5.7.1 - What I was doing when the application crashed: Just logged in and restoring the previous session. -- Backtrace (Reduced): #6 DolphinViewContainer::setActive (this=0x0, active=active@entry=true) at /usr/src/debug/dolphin-17.04.0/src/dolphinviewcontainer.cpp:208 #7 0x7f1c48bd2b72 in DolphinTabPage::restoreState (this=0x2daced0, state=...) at /usr/src/debug/dolphin-17.04.0/src/dolphintabpage.cpp:239 #8 0x7f1c48bd4b35 in DolphinTabWidget::readProperties (this=0x268abd0, group=...) at /usr/src/debug/dolphin-17.04.0/src/dolphintabwidget.cpp:90 #9 0x7f1c461224a0 in KMainWindow::readPropertiesInternal(KConfig*, int) () from /usr/lib64/libKF5XmlGui.so.5 #10 0x7f1c46122502 in KMainWindow::restore(int, bool) () from /usr/lib64/libKF5XmlGui.so.5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379314] Crash when restoring activity
https://bugs.kde.org/show_bug.cgi?id=379314 Jaime Torres changed: What|Removed |Added CC||jtam...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379790] MDI SubWindows are frozen (non-responsive) with Breeze and Oxygen
https://bugs.kde.org/show_bug.cgi?id=379790 --- Comment #5 from Tim E. Real --- Wow! When the attached UI file is opened, it is not only the MDI sub windows that are affected - it is the ENTIRE QMainWindow containing the QMDIArea. In fact, I am unable to even move the window around in Qt5Designer ! I can place items on the form, but I cannot select anything afterwards. The rest of Qt5Designer is OK, of course. -- You are receiving this mail because: You are watching all bug changes.
[ktouchpadenabler] [Bug 379785] palm rejection
https://bugs.kde.org/show_bug.cgi?id=379785 Albert Astals Cid changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Albert Astals Cid --- only think that ktouchpadenabler is listen to the touchpad enable key on your laptop and enable/disable it. Anything else is out of scope. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 379823] New: Message to cut and delete when opening image
https://bugs.kde.org/show_bug.cgi?id=379823 Bug ID: 379823 Summary: Message to cut and delete when opening image Product: gwenview Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: caynannu...@gmail.com CC: myr...@kde.org Target Milestone: --- After updating my system LinuxMint 18.1 x64 KDE: 4.14.22, kde4-config: 1.0,kde4-config: 1.0 Every time I click on an image a message appears saying "there is a command to both cut and delete the image", when I ignore the message nothing happens to the file. -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 379810] qca compilation fails with openssl 1.1
https://bugs.kde.org/show_bug.cgi?id=379810 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu --- Comment #1 from Rex Dieter --- That's ok, Qt5 itself doesn't support openssl 1.1 yet either, which is an important prerequisite. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 379824] New: Crash after closing settings
https://bugs.kde.org/show_bug.cgi?id=379824 Bug ID: 379824 Summary: Crash after closing settings Product: systemsettings Version: 5.9.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: barnaba...@gmail.com Target Milestone: --- Application: systemsettings5 (5.9.5) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.10.15-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: I just closed the system settings after turning desktop compositing on - Unusual behavior I noticed: Logging in fresh after installing the latest updates, Kwin crashed, disabling compositing. After enabling it back and closing the settings app, this crash happened. -- Backtrace: Application: Rendszerbeállítások (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa78784b500 (LWP 1933))] Thread 3 (Thread 0x7fa758bc8700 (LWP 1984)): #0 0x7fa77d6ac1c9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7fa77d66699b in () at /usr/lib/libglib-2.0.so.0 #2 0x7fa77d666acc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fa783e9d09b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fa783e468ca in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fa783c68a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fa781f65025 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fa783c6d6d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7fa77f5ae2e7 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fa78358054f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fa76c1f0700 (LWP 1936)): #0 0x7fa78357667d in poll () at /usr/lib/libc.so.6 #1 0x7fa77d6669b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fa77d666acc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fa783e9d09b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fa783e468ca in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fa783c68a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fa7847b4125 in () at /usr/lib/libQt5DBus.so.5 #7 0x7fa783c6d6d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7fa77f5ae2e7 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fa78358054f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fa78784b500 (LWP 1933)): [KCrash Handler] #6 0x09841400 in () #7 0x7fa76f06eba6 in () at /usr/lib/libKF5Notifications.so.5 #8 0x7fa76f06ec39 in () at /usr/lib/libKF5Notifications.so.5 #9 0x7fa783e72441 in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #10 0x7fa783e7bd9f in QObject::~QObject() () at /usr/lib/libQt5Core.so.5 #11 0x7fa76f040ea9 in () at /usr/lib/libKF5Notifications.so.5 #12 0x7fa7834ca6c0 in __run_exit_handlers () at /usr/lib/libc.so.6 #13 0x7fa7834ca71a in () at /usr/lib/libc.so.6 #14 0x7fa7834b4518 in __libc_start_main () at /usr/lib/libc.so.6 #15 0x0040c33a in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379825] New: Conversion of DNG files to DNG with metadata loss - maybe add warning
https://bugs.kde.org/show_bug.cgi?id=379825 Bug ID: 379825 Summary: Conversion of DNG files to DNG with metadata loss - maybe add warning Product: digikam Version: 5.5.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Import Assignee: digikam-de...@kde.org Reporter: vas...@gmx.net Target Milestone: --- I own a Pentax camera which is capable of producing DNG-Files. Unfortunately i had left the "convert raw files to dng"-option enabled when importing which converted all my DNG files to DNG files but deleting Makernotes in the process so that all the new DNGs now have missing lens information. I think a warning when trying to convert from DNG to DNG would be a good idea (maybe mentioning the possible loss of metadata) as this took me quite some time to track down (at first i thought that the camera did no longer encode the lens used, then i realised that the information was there in the jpeg files but not the dng ones and finally i realised that i had left the conversion option enabled). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379825] Conversion of DNG files to DNG with metadata loss - maybe add warning
https://bugs.kde.org/show_bug.cgi?id=379825 vas...@gmx.net changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379826] New: Plasma Crash after closing firefox window - segmentation fault
https://bugs.kde.org/show_bug.cgi?id=379826 Bug ID: 379826 Summary: Plasma Crash after closing firefox window - segmentation fault Product: plasmashell Version: 5.9.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: tho...@elsensohn.ch CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.5) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.10.13-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I tried to close ocular window and closed the firefox window. Then I tried to close the other window but was already crashed. Restored after some seconds. - Unusual behavior I noticed: The menubar was wrong. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f300d93f800 (LWP 721))] Thread 19 (Thread 0x7eeef7fff700 (LWP 7132)): #0 0x7f30065a2756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f30076e858b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f30076e14d3 in QSemaphore::acquire(int) () at /usr/lib/libQt5Core.so.5 #3 0x7eeefd65c37c in () at /usr/lib/qt/plugins/texttospeech/libqttexttospeech_flite.so #4 0x7f30076e76d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f300659c2e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f3006ffa54f in clone () at /usr/lib/libc.so.6 Thread 18 (Thread 0x7f2f14e12700 (LWP 1976)): #0 0x7f3007914f21 in QTimerInfoList::repairTimersIfNeeded() () at /usr/lib/libQt5Core.so.5 #1 0x7f3007914fb3 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #2 0x7f300791666e in () at /usr/lib/libQt5Core.so.5 #3 0x7f3001dc6e8d in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #4 0x7f3001dc78db in () at /usr/lib/libglib-2.0.so.0 #5 0x7f3001dc7acc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #6 0x7f300791709b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f30078c08ca in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #8 0x7f30076e2a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #9 0x7f300a81b025 in () at /usr/lib/libQt5Qml.so.5 #10 0x7f30076e76d8 in () at /usr/lib/libQt5Core.so.5 #11 0x7f300659c2e7 in start_thread () at /usr/lib/libpthread.so.0 #12 0x7f3006ffa54f in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7f2f164b1700 (LWP 1295)): #0 0x7f3001dc6d38 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #1 0x7f3001dc78db in () at /usr/lib/libglib-2.0.so.0 #2 0x7f3001dc7acc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f300791709b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f30078c08ca in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f30076e2a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f30076e76d8 in () at /usr/lib/libQt5Core.so.5 #7 0x7f300659c2e7 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f3006ffa54f in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f2f16ffd700 (LWP 1225)): #0 0x7f30065a2756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f30076e858b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f2f4f0d81d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f2f4f0dc9d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f2f4f0d7263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f2f4f0dca32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f2f4f0d7263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f2f4f0dca32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f2f4f0d7263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f2f4f0da249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f30076e76d8 in () at /usr/lib/libQt5Core.so.5 #11 0x7f300659c2e7 in start_thread () at /usr/lib/libpthread.so.0 #12 0x7f3006ffa54f in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f2f177fe700 (LWP 1224)): #0 0x7f30065a2756 in pthread_cond_wait@@GLIBC_2.3.2 () at
[kdeconnect] [Bug 368438] KDE Connect does not communicate while running in background on phone
https://bugs.kde.org/show_bug.cgi?id=368438 --- Comment #18 from Theresa --- I can confirm that the problem is fixed with Android 7.x Alas my phone (Oneplus One) only has Android 6. Is there any chance of fixing this also for Android 6 devices? -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 376344] cant write to smb shares which has write access
https://bugs.kde.org/show_bug.cgi?id=376344 Sergey changed: What|Removed |Added CC||rion...@gmail.com --- Comment #22 from Sergey --- Just faced the same bug, but workaround from @tempel.julian does not work well. I finally have write access to my Windows share (requires auth) but if I create with dolphin a subdirectory I can't open it. It requires authentication again but this time the same login/password do not work anymore. Another glitch. If I don't use *:* for auth but just smb://host/share and login via popup dialog, then I create a subdirctory in cifs mounted directory for the same share, I can open the new subdirectory with Dolphin, but again no write access inside. But if I write a few files from console (the same mounted cifs) to the subdirectory I magically obtain the write access from Dolphin. I also tested with "mount cifs" and it works in all circumstances where dolphin fails. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378700] There is gap on the right of every invoked tray icon
https://bugs.kde.org/show_bug.cgi?id=378700 n...@mail.ticket-please.ga changed: What|Removed |Added CC||n...@mail.ticket-please.ga --- Comment #2 from n...@mail.ticket-please.ga --- bump! just booted with neon dev unstable which is going with KF 5.35 and gap is still there. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379827] New: Dolphin crashed moving files to a NTFS partition
https://bugs.kde.org/show_bug.cgi?id=379827 Bug ID: 379827 Summary: Dolphin crashed moving files to a NTFS partition Product: dolphin Version: 17.04.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ivan.rinco...@gmail.com Target Milestone: --- Application: dolphin (17.04.0) Qt Version: 5.7.1 Frameworks Version: 5.33.0 Operating System: Linux 4.8.0-51-generic x86_64 Distribution: KDE neon User Edition 5.9 -- Information about the crash: - What I was doing when the application crashed: File in /home/user (Ext4) > move to > /media/user/folder (NTFS) with Dolphin > access denied to /home/file.ex message > Retry > The file /home/user//file.ex does not exist message > Cancel > Crash NTFS partition parameters in fstab: UUID=DCDA0B17DA0AED98 /media/ivan/Acer ntfsdefaults,umask=007,gid=46 0 0 The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f91d4a568c0 (LWP 31556))] Thread 4 (Thread 0x7f91c2d3e700 (LWP 31562)): #0 0x7f91e7757b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f91dc4bf38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f91dc4bf49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f91e24e775b in QEventDispatcherGlib::processEvents (this=0x7f91bc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f91e24920ba in QEventLoop::exec (this=this@entry=0x7f91c2d3dd00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f91e22c1f64 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7f91e22c6b48 in QThreadPrivate::start (arg=0x28f0fd0) at thread/qthread_unix.cpp:368 #7 0x7f91de7c86ba in start_thread (arg=0x7f91c2d3e700) at pthread_create.c:333 #8 0x7f91e776382d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f91cbfff700 (LWP 31560)): #0 __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:65 #1 0x7f91e7757b52 in poll () at ../sysdeps/unix/syscall-template.S:84 #2 0x7f91dc4bf38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f91dc4bf49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f91e24e775b in QEventDispatcherGlib::processEvents (this=0x7f91c40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f91e24920ba in QEventLoop::exec (this=this@entry=0x7f91cbffecd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f91e22c1f64 in QThread::exec (this=) at thread/qthread.cpp:507 #7 0x7f91e7e47735 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f91e22c6b48 in QThreadPrivate::start (arg=0x7f91e7ebbd60) at thread/qthread_unix.cpp:368 #9 0x7f91de7c86ba in start_thread (arg=0x7f91cbfff700) at pthread_create.c:333 #10 0x7f91e776382d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f91d1ecb700 (LWP 31559)): #0 0x7f91e7757b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f91db7c0c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f91db7c28d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f91d4423d79 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f91e22c6b48 in QThreadPrivate::start (arg=0x23649a0) at thread/qthread_unix.cpp:368 #5 0x7f91de7c86ba in start_thread (arg=0x7f91d1ecb700) at pthread_create.c:333 #6 0x7f91e776382d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f91d4a568c0 (LWP 31556)): [KCrash Handler] #6 0x7f91e24c5fee in QObjectPrivate::setParent_helper (this=0x18fb9e1, o=o@entry=0x0) at kernel/qobject.cpp:1978 #7 0x7f91e24c6b79 in QObject::setParent (this=, parent=parent@entry=0x0) at kernel/qobject.cpp:1957 #8 0x7f91e378aa32 in KCompositeJob::removeSubjob (this=, job=0x2c28930) at /workspace/build/src/lib/jobs/kcompositejob.cpp:71 #9 0x7f91e57f26f4 in KIO::CopyJobPrivate::slotResultErrorCopyingFiles (this=this@entry=0x2c02b50, job=job@entry=0x2c28930) at /workspace/build/src/core/copyjob.cpp:1445 #10 0x7f91e57f2d84 in KIO::CopyJobPrivate::slotResultCopyingFiles (this=this@entry=0x2c02b50, job=job@entry=0x2c28930) at /workspace/build/src/core/copyjob.cpp:1313 #11 0x7f91e57f4d57 in KIO::CopyJob::slotResult (this=0x2c092f0, job=0x2c28930) at /workspace/build/src/core/copyjob.cpp:2114 #12 0x7f91e24bee89 in QMetaObject::activate (sender=sender@entry=0x2c28930, signalOffset=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff25f37b80) at k
[kdeconnect] [Bug 368438] KDE Connect does not communicate while running in background on phone
https://bugs.kde.org/show_bug.cgi?id=368438 --- Comment #19 from Matt Whitlock --- (In reply to Theresa from comment #18) > Alas my phone (Oneplus One) only has Android 6. FYI, LineageOS 14.1 (Android 7.1) is available for the OnePlus One. LineageOS is the successor to CyanogenOS (which, if I'm not mistaken, is what the OnePlus One runs out of the box). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379803] Kwin crashed when switching screens
https://bugs.kde.org/show_bug.cgi?id=379803 --- Comment #1 from Martin Flöser --- NVIDIA graphics? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378698] Icons became too large
https://bugs.kde.org/show_bug.cgi?id=378698 n...@mail.ticket-please.ga changed: What|Removed |Added CC||n...@mail.ticket-please.ga --- Comment #9 from n...@mail.ticket-please.ga --- Created attachment 105537 --> https://bugs.kde.org/attachment.cgi?id=105537&action=edit screen There is also too big icon for gwenview -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 344326] Buffer objects (VBO, FBO) need remapping after suspend/vt switch with NVIDIA
https://bugs.kde.org/show_bug.cgi?id=344326 Martin Flöser changed: What|Removed |Added CC||jonespanic...@gmail.com --- Comment #160 from Martin Flöser --- *** Bug 379814 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379814] Black Screen on Resuming from Suspend to RAM with Nvidia Proprietary Driver
https://bugs.kde.org/show_bug.cgi?id=379814 Martin Flöser changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Flöser --- *** This bug has been marked as a duplicate of bug 344326 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378698] Icons became too large
https://bugs.kde.org/show_bug.cgi?id=378698 --- Comment #10 from n...@mail.ticket-please.ga --- Created attachment 105538 --> https://bugs.kde.org/attachment.cgi?id=105538&action=edit screen2 and for flash device before clicking for actions -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379819] [Wayland] QT UI element overflow in systemsettings Display section
https://bugs.kde.org/show_bug.cgi?id=379819 Martin Flöser changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Flöser --- *** This bug has been marked as a duplicate of bug 365864 *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365864] Display layout preview renders off-window in Display Configuration using Wayland
https://bugs.kde.org/show_bug.cgi?id=365864 Martin Flöser changed: What|Removed |Added CC||rajdeepna...@gmail.com --- Comment #14 from Martin Flöser --- *** Bug 379819 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378698] Icons became too large
https://bugs.kde.org/show_bug.cgi?id=378698 --- Comment #11 from n...@mail.ticket-please.ga --- and that goddamn gap on the right discribed in https://bugs.kde.org/show_bug.cgi?id=378700 (seems that devs ignoring that bug) -- You are receiving this mail because: You are watching all bug changes.
