[valgrind] [Bug 357673] New: crash if I try to run valgrind with a binary link with libcurl
https://bugs.kde.org/show_bug.cgi?id=357673 Bug ID: 357673 Summary: crash if I try to run valgrind with a binary link with libcurl Product: valgrind Version: 3.10.0 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: lambertarthu...@gmail.com Hi, I have almost the same bug found here : https://bugzilla.redhat.com/show_bug.cgi?id=810992 When I link my software with libcurl (which uses openssl), valgrind is not able to run correctly : # valgrind ./test ==4659== Memcheck, a memory error detector ==4659== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==4659== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info ==4659== Command: ./nyx_core_dev ==4659== ==4659== Invalid read of size 4 ==4659==at 0x4005404: _dl_get_ready_to_run (in /lib/ld-uClibc-1.0.5.so) ==4659== Address 0x7dbb96f4 is on thread 1's stack ==4659== 20 bytes below stack pointer ==4659== IR SANITY CHECK FAILURE IRSB { t0:V128 t1:V128 t2:V128 t3:I32 IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp -- IMark(0x4B0EEC8, 4, 0) -- PUT(64) = 0x4B0EECC:I32 PUT(68) = 0x4B127B8:I32 -- IMark(0x4B127B8, 4, 0) -- t0 = GET:V128(128) t1 = GET:V128(128) PUT(128) = t2 PUT(68) = 0x4B127BC:I32 -- IMark(0x4B127BC, 4, 0) -- t3 = GET:I32(64) PUT(68) = t3 PUT(68) = GET:I32(68); exit-Return } IN STATEMENT: PUT(128) = t2 ERROR = IRTemp use before def in IRExpr vex: the `impossible' happened: sanityCheckFail: exiting due to bad IR vex storage: T total 28036856 bytes allocated vex storage: P total 0 bytes allocated valgrind: the 'impossible' happened: LibVEX called failure_exit(). host stacktrace: ==4659==at 0x3805E89C: ??? (in /usr/lib/valgrind/memcheck-arm-linux) sched status: running_tid=1 Thread 1: status = VgTs_Runnable ==4659==at 0x4B0EEC8: OPENSSL_cpuid_setup (in /usr/lib/libcrypto.so.1.0.0) Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if it happened in m_mallocfree.c. If that doesn't help, please report this bug to: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what OS and version you are using. Thanks. Valgrind version : 3.10.1 The bug was fixed in valgrind 3.8.X in the previous bug. arch : ARM platform : custom embedded system built with buildroot Thanks, Arthur. Reproducible: Always Steps to Reproduce: 1. build a binary link with libcurl with openssl support using buildroot 2. run valgrind on this binary 3. Actual Results: # valgrind ./test ==4659== Memcheck, a memory error detector ==4659== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==4659== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info ==4659== Command: ./nyx_core_dev ==4659== ==4659== Invalid read of size 4 ==4659==at 0x4005404: _dl_get_ready_to_run (in /lib/ld-uClibc-1.0.5.so) ==4659== Address 0x7dbb96f4 is on thread 1's stack ==4659== 20 bytes below stack pointer ==4659== IR SANITY CHECK FAILURE IRSB { t0:V128 t1:V128 t2:V128 t3:I32 IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp IR-NoOp -- IMark(0x4B0EEC8, 4, 0) -- PUT(64) = 0x4B0EECC:I32 PUT(68) = 0x4B127B8:I32 -- IMark(0x4B127B8, 4, 0) -- t0 = GET:V128(128) t1 = GET:V128(128) PUT(128) = t2 PUT(68) = 0x4B127BC:I32 -- IMark(0x4B127BC, 4, 0) -- t3 = GET:I32(64) PUT(68) = t3 PUT(68) = GET:I32(68); exit-Return } IN STATEMENT: PUT(128) = t2 ERROR = IRTemp use before def in IRExpr vex: the `impossible' happened: sanityCheckFail: exiting due to bad IR vex storage: T total 28036856 bytes allocated vex storage: P total 0 bytes allocated valgrind: the 'impossible' happened: LibVEX called failure_exit(). host stacktrace: ==4659==at 0x3805E89C: ??? (in /usr/lib/valgrind/memcheck-arm-linux) sched status: running_tid=1 Thread 1: status = VgTs_Runnable ==4659==at 0x4B0EEC8: OPENSSL_cpuid_setup (in /usr/lib/libcrypto.so.1.0.0) Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if
[kexi] [Bug 357655] Misaligned comboboxes for foreign keys on big tables (Kexi 2.9.8)
https://bugs.kde.org/show_bug.cgi?id=357655 Jarosław Staniekchanged: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #5 from Jarosław Staniek --- Confirmed, will be fixed today for 2.9.11. The offset is equal to the scroll offset, so it's enough to have number of records that do not fit in the view, scroll slightly and the glitch can be reproduced. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 357677] New: Option to display brief headers
https://bugs.kde.org/show_bug.cgi?id=357677 Bug ID: 357677 Summary: Option to display brief headers Product: trojita Version: git Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: luke-jr+kdeb...@utopios.org KMail has (had?) an option to display only Subject/From/To lines in the preview pane. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357666] Composite/overlay icons not visible in timeline tracks (Kdenlive-git 15.13.0.r6866.e43f3d4-1)
https://bugs.kde.org/show_bug.cgi?id=357666 --- Comment #5 from Jesse--- Not just the icon - I should have been more specific - but the buttons themselves are missing. I'm going to assume it was my building or compiling via pacmanXG that was the issue. I might have a bit more to learn about Antergos/Arch. :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 312834] closing split view closes the currently focused view instead of the inactive
https://bugs.kde.org/show_bug.cgi?id=312834 --- Comment #22 from Ettore Atalan--- (In reply to andydecleyre from comment #20) > Even if you don't change the default behavior, > even if you don't enable changing the behavior in the settings, > even if you don't add another keyboard shortcut for the more intuitive > behavior (closing the pane _not_ being actively used), You'd better use another file manager due to the lack of willingness to consider user needs. It's more a KDE problem than a technical problem, anyway. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 312834] closing split view closes the currently focused view instead of the inactive
https://bugs.kde.org/show_bug.cgi?id=312834 andydecle...@gmail.com changed: What|Removed |Added CC||andydecle...@gmail.com --- Comment #20 from andydecle...@gmail.com --- Even if you don't change the default behavior, even if you don't enable changing the behavior in the settings, even if you don't add another keyboard shortcut for the more intuitive behavior (closing the pane _not_ being actively used), please just add another button in the Configure Toolbars dialog (that a user would have to seek out or stumble upon) that opens a second pane but _doesn't_ activate it, and closes the _inactive_ pane if two are already open. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 357655] Misaligned combo boxes for tabular view on bigger tables
https://bugs.kde.org/show_bug.cgi?id=357655 --- Comment #6 from Jarosław Staniek--- Created attachment 96513 --> https://bugs.kde.org/attachment.cgi?id=96513=edit Both vertical and horizontal misalignment Please note the horizontal misalignment: the combo box is moved to right when if horizontal scrollbar is at any non-zero position. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 357676] HTML-only email rendered as plain text
https://bugs.kde.org/show_bug.cgi?id=357676 --- Comment #1 from Luke-Jr--- Created attachment 96517 --> https://bugs.kde.org/attachment.cgi?id=96517=edit Raw email -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 357676] New: HTML-only email rendered as plain text
https://bugs.kde.org/show_bug.cgi?id=357676 Bug ID: 357676 Summary: HTML-only email rendered as plain text Product: trojita Version: git Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: luke-jr+kdeb...@utopios.org Message has the header Content-Type: text/html; charset="iso-8859-1" But the HTML is displayed as plain text, not rendered as HTML. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 357682] New: Combo box popups for tabular view not always fit in the current screen
https://bugs.kde.org/show_bug.cgi?id=357682 Bug ID: 357682 Summary: Combo box popups for tabular view not always fit in the current screen Product: kexi Version: 2.9.11 Platform: Compiled Sources OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tables Assignee: kexi-b...@kde.org Reporter: stan...@kde.org CC: a...@piggz.co.uk, in...@fables.co.za, kdeu...@sauron.cf, stan...@kde.org Combo boxes for tabular view not always fit in the current screen. Reproducible: Always Steps to Reproduce: 1. Use table e.g. table B from this bug https://bugs.kde.org/show_bug.cgi?id=357655 2. Open the combo box popup for cell that's on the very bottom of the maximized window or on the very right. Actual Results: If the combo box popup is tall or wide enough, it is partially displayed outside of the screen. Expected Results: The combo box popup is shifted up or/and left so it can fit on the current screen. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 357682] Combo box popups for tabular view not always fit in the current screen
https://bugs.kde.org/show_bug.cgi?id=357682 Jarosław Staniekchanged: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Assignee|kexi-b...@kde.org |stan...@kde.org Target Milestone|--- |2.9.11 Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 355398] Crash if I rescale video on render :(
https://bugs.kde.org/show_bug.cgi?id=355398 --- Comment #13 from Paul Konecny--- Created attachment 96519 --> https://bugs.kde.org/attachment.cgi?id=96519=edit Backtrace with whole pipeline rebuilt I recompiled the whole pipeline (movit mlt and kdenlive) And now get a segfault again when clicking on the timeline... log attached. I'm not sure if this is the culprit: I take the Arch PKGBUILD (the one from which the distro package is built) and add debugging and --enable-opengl to get movit working. I just noticed that Arch devs use this additional parameter: --avformat-swscale I'll comment that out and try it again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 352191] Cursor / Brush disappeared!
https://bugs.kde.org/show_bug.cgi?id=352191 --- Comment #7 from Heather--- Updating my drivers seems to have helped for the time being; if the bug resurfaces I will e sure to report it. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 355398] Crash if I rescale video on render :(
https://bugs.kde.org/show_bug.cgi?id=355398 --- Comment #14 from Paul Konecny--- Without --avformat-swscale I'm back to the black screen without a segfault but there are still a ton of messages like these (and the render aborts immediately) GL error 502 at /home/paul/rebuild/4/src/kdenlive/src/monitor/glwidget.cpp : 406 [filter avcolor_space] Invalid format glsl [filter avcolor_space] Invalid format glsl_texture GL error 502 at /home/paul/rebuild/4/src/kdenlive/src/monitor/glwidget.cpp : 406 [filter avcolor_space] Invalid format glsl [filter avcolor_space] Invalid format glsl [filter avcolor_space] Invalid format glsl_texture GL error 502 at /home/paul/rebuild/4/src/kdenlive/src/monitor/glwidget.cpp : 406 [filter avcolor_space] Invalid format glsl [filter avcolor_space] Invalid format glsl [filter avcolor_space] Invalid format glsl_texture GL error 502 at /home/paul/rebuild/4/src/kdenlive/src/monitor/glwidget.cpp : 406 [filter avcolor_space] Invalid format glsl [filter avcolor_space] Invalid format glsl [filter avcolor_space] Invalid format glsl_texture GL error 502 at /home/paul/rebuild/4/src/kdenlive/src/monitor/glwidget.cpp : 406 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 355398] Crash if I rescale video on render :(
https://bugs.kde.org/show_bug.cgi?id=355398 --- Comment #15 from Paul Konecny--- Created attachment 96520 --> https://bugs.kde.org/attachment.cgi?id=96520=edit Project file with the issues Almost forgot the project file. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 355398] Crash if I rescale video on render :(
https://bugs.kde.org/show_bug.cgi?id=355398 --- Comment #9 from Paul Konecny--- Created attachment 96515 --> https://bugs.kde.org/attachment.cgi?id=96515=edit Backtrace movit git i965 with fix Unfortunately i still get the segfault. I looked up of which package /usr/lib/libswscale.so.3 is a part of. Seems to be ffmpeg. I'll recompile that with debug and will report back. This is with movit git. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 357679] New: Not enough shortcut key options
https://bugs.kde.org/show_bug.cgi?id=357679 Bug ID: 357679 Summary: Not enough shortcut key options Product: trojita Version: git Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: luke-jr+kdeb...@utopios.org I like to use left/right to navigate between previous/next (read or unread) messages, and Esc to close popup windows. These don't seem to be available for configuring. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 357681] New: KMail crashed when trying to drag-select list of recent addresses in Settings dialog
https://bugs.kde.org/show_bug.cgi?id=357681 Bug ID: 357681 Summary: KMail crashed when trying to drag-select list of recent addresses in Settings dialog Product: kmail2 Version: 4.14.1 Platform: Debian stable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: zne...@gmail.com Application: kmail (4.14.1) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.16.0-4-amd64 x86_64 Distribution: Debian GNU/Linux 8.2 (jessie) -- Information about the crash: - What I was doing when the application crashed: >From a composer window, selected Settings -> Configure KMail... Clicked on Composer section. In there, clicked on Edit Recent Addresses. Only a few entries were there. From an empty part of the list field, I tried to drag-select the list of entries. No select box was shown, but before I could even let off of the mouse button, the whole application crashed. I re-tested without involving a composer window; just opened KMail settings from the main window. Same thing - although it took a few extra drag-select attemtps before it finally crashed. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f32d0ef6800 (LWP 18096))] Thread 5 (Thread 0x7f32a7a7e700 (LWP 18111)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f32c251706f in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f32c25170a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f32cba230a4 in start_thread (arg=0x7f32a7a7e700) at pthread_create.c:309 #4 0x7f32ce16e04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7f3266290700 (LWP 18112)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f32c2239973 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f32c25467f6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f32cba230a4 in start_thread (arg=0x7f3266290700) at pthread_create.c:309 #4 0x7f32ce16e04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f326564e700 (LWP 18113)): #0 0x7f32ce16550d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f32c5e4eee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f32c5e4effc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f32ceb07d37 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f32cead7271 in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7f32cead75d5 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f32ce9cbe99 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f32ce9ce70f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7f32cba230a4 in start_thread (arg=0x7f326564e700) at pthread_create.c:309 #9 0x7f32ce16e04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f325f173700 (LWP 18115)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f32b90cedea in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x7f32b90cee19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x7f32cba230a4 in start_thread (arg=0x7f325f173700) at pthread_create.c:309 #4 0x7f32ce16e04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f32d0ef6800 (LWP 18096)): [KCrash Handler] #6 0x7f32c7cd07c9 in KPIM::RecentAddressDialog::updateButtonState() () from /usr/lib/libkdepim.so.4 #7 0x7f32ceaed71c in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7f32ceaed71c in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f32cf586a27 in QItemSelectionModel::selectionChanged(QItemSelection const&, QItemSelection const&) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #10 0x7f32cf58c34e in QItemSelectionModel::emitSelectionChanged(QItemSelection const&, QItemSelection const&) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #11 0x7f32cf58cbdb in QItemSelectionModel::select(QItemSelection const&, QFlags) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #12 0x7f32cf559cad in QListView::setSelection(QRect const&, QFlags) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #13
[kexi] [Bug 357655] Misaligned combo boxes for tabular view on bigger tables
https://bugs.kde.org/show_bug.cgi?id=357655 Jarosław Staniekchanged: What|Removed |Added Assignee|kexi-b...@kde.org |stan...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 357655] Misaligned combo boxes for tabular view on bigger tables
https://bugs.kde.org/show_bug.cgi?id=357655 Jarosław Staniekchanged: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 357655] Misaligned combo boxes for tabular view on bigger tables
https://bugs.kde.org/show_bug.cgi?id=357655 Jarosław Staniekchanged: What|Removed |Added Component|General |Tables -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 357655] Misaligned combo boxes for tabular view on bigger tables
https://bugs.kde.org/show_bug.cgi?id=357655 Jarosław Staniekchanged: What|Removed |Added Summary|Misaligned comboboxes for |Misaligned combo boxes for |foreign keys on big tables |tabular view on bigger |(Kexi 2.9.8)|tables -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 347022] Unable to setup wacom tablet - widget missing
https://bugs.kde.org/show_bug.cgi?id=347022 Valorie Zimmermanchanged: What|Removed |Added CC||valorie.zimmer...@gmail.com --- Comment #16 from Valorie Zimmerman --- Hello Jörg Ehrichs, You say that you are no longer actively maintaining this valuable bit of KDE software. How about writing up a small description and posting it on the Mission forum? That is one of the reasons we set it up; to post "maintainer wanted" notices along with other jobs that need doing. https://forum.kde.org/viewforum.php?f=291=b238ab88922632d2d40e7c929449cc71 Valorie -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 357655] Misaligned combo boxes for tabular view on bigger tables
https://bugs.kde.org/show_bug.cgi?id=357655 Jarosław Staniekchanged: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/call ||igra/c293db532569a80e389f20 ||61f96b719b4448ebdc Version Fixed In||2.9.11 Status|ASSIGNED|RESOLVED --- Comment #8 from Jarosław Staniek --- Git commit c293db532569a80e389f2061f96b719b4448ebdc by Jaroslaw Staniek. Committed on 08/01/2016 at 00:12. Pushed by staniek into branch 'calligra/2.9'. Kexi: Fix alignment of table view combo boxes when rows or columns are scrolled FIXED-IN:2.9.11 M +9-1kexi/widget/tableview/kexicomboboxbase.cpp http://commits.kde.org/calligra/c293db532569a80e389f2061f96b719b4448ebdc -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 357634] Cover Art does not update while playing
https://bugs.kde.org/show_bug.cgi?id=357634 --- Comment #3 from sederic--- I selected "Write covers to file, maximum size: Huge 1600px" and covers are searched automatically, but I don't know where I can find this setting. And I know that a cover was found, because it appears in the playlist... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 355310] Setting Custom Icon for Places Entry Impossible Due to Forced Window Focus
https://bugs.kde.org/show_bug.cgi?id=355310 --- Comment #5 from andydecle...@gmail.com --- Thank you Gunnar Grim! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 312834] closing split view closes the currently focused view instead of the inactive
https://bugs.kde.org/show_bug.cgi?id=312834 --- Comment #21 from andydecle...@gmail.com --- OK, rereading this three year long discussion, I think I understand that the reason my last comment's reiterations of previous suggestions have not been acted on is: "Currently, the action's name switches between 'Split' and 'Close'. What short, meaningful name could a new action get to avoid confusion?" So, let's brainstorm: Split | Close Other Split | Crop Single | Dual Split | Close [Left | Right] Split | Maximize Split | Fill Split | Grow Split | Widen Split | Only Split | Focus Split | Focalize Wane | Wax Split | Expand Split | Swell I think "Split | Swell" is my favorite so far. The words are pleasantly symmetrical. My next choices are probably Grow, Fill, Expand. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 357678] New: Hide MIME type tab bar when only one option exists
https://bugs.kde.org/show_bug.cgi?id=357678 Bug ID: 357678 Summary: Hide MIME type tab bar when only one option exists Product: trojita Version: git Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: luke-jr+kdeb...@utopios.org A tab bar with only "Plaintext" and doubling the margins (one above and one below) wastes a lot of screen space. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 355398] Crash if I rescale video on render :(
https://bugs.kde.org/show_bug.cgi?id=355398 --- Comment #16 from Paul Konecny--- Created attachment 96521 --> https://bugs.kde.org/attachment.cgi?id=96521=edit New project file I created a new project file. This renders correctly even with scaling but the monitor stays black. Normal dissolves and a GPU blur effect are added. --- After reopening the monitor is back... I don't get what's happening. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 355398] Crash if I rescale video on render :(
https://bugs.kde.org/show_bug.cgi?id=355398 --- Comment #17 from Paul Konecny--- This is the output from the last try [filter avcolor_space] Invalid format glsl [filter avcolor_space] Invalid format glsl_texture [Thread 0x7fff737fe700 (LWP 21964) exited] [Thread 0x7fff70ff9700 (LWP 21969) exited] [Thread 0x7fff717fa700 (LWP 21968) exited] [Thread 0x7fff6bfff700 (LWP 21970) exited] [Thread 0x7fff727fc700 (LWP 21966) exited] [Thread 0x7fff71ffb700 (LWP 21967) exited] [Thread 0x7fff72ffd700 (LWP 21965) exited] Skipped method "slotGotProgressInfo" : Type not registered with QtDBus in parameter list: MessageType Skipped method "slotTimelineClipSelected" : Pointers are not supported: ClipItem* Skipped method "slotTimelineClipSelected" : Pointers are not supported: ClipItem* Unsupported return type 65 QPixmap in method "grab" Unsupported return type 65 QPixmap in method "grab" [Thread 0x7fff6b7fe700 (LWP 21971) exited] [Thread 0x7fff9700 (LWP 21940) exited] QXcbConnection: XCB error: 8 (BadMatch), sequence: 36216, resource id: 106954955, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 36242, resource id: 106954955, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 36267, resource id: 106954955, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 40404, resource id: 106954955, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 40430, resource id: 106954955, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 40458, resource id: 106954955, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 40530, resource id: 106954955, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 40591, resource id: 106954955, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 40652, resource id: 106954955, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 40719, resource id: 106954955, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 40786, resource id: 106954955, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 40847, resource id: 106954955, major code: 130 (Unknown), minor code: 3 [Thread 0x7fffa55ec700 (LWP 21848) exited] [Thread 0x7fffb51b2700 (LWP 21845) exited] [filter avcolor_space] Invalid format glsl [filter avcolor_space] Invalid format glsl [Thread 0x7fffa7ffe700 (LWP 21847) exited] [filter avcolor_space] Invalid format glsl [filter avcolor_space] Invalid format glsl [filter avcolor_space] Invalid format glsl_texture [Thread 0x7fffa5ded700 (LWP 21846) exited] QCoreApplication::postEvent: Unexpected null receiver [Thread 0x7fff73fff700 (LWP 21955) exited] [Thread 0x7fff80ff8700 (LWP 21956) exited] [Thread 0x7fff817f9700 (LWP 21957) exited] [Thread 0x7fff81ffa700 (LWP 21958) exited] [Thread 0x7fff827fb700 (LWP 21959) exited] [Thread 0x7fffb7fff700 (LWP 21747) exited] [Thread 0x7fffbec36700 (LWP 21745) exited] [Thread 0x7fffbfc57700 (LWP 21744) exited] [Thread 0x7fff9f7fe700 (LWP 21941) exited] [Thread 0x7fff948c6700 (LWP 21942) exited] [Thread 0x7fff837fd700 (LWP 21944) exited] [Thread 0x7fff83ffe700 (LWP 21943) exited] [Thread 0x7fff82ffc700 (LWP 21945) exited] [Thread 0x7fffa4deb700 (LWP 21764) exited] [Thread 0x7fff9d087700 (LWP 21765) exited] [Thread 0x7fff9c886700 (LWP 21766) exited] [Thread 0x7fff978c9700 (LWP 21767) exited] [Thread 0x7fff970c8700 (LWP 21768) exited] [Thread 0x7fffe3075700 (LWP 21740) exited] [Thread 0x7fffc5283700 (LWP 21741) exited] [Thread 0x77e3f800 (LWP 21739) exited] [Inferior 1 (process 21739) exited normally] (gdb) run Starting program: /usr/bin/kdenlive [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0x7fffe3075700 (LWP 22039)] [New Thread 0x7fffc5283700 (LWP 22040)] [New Thread 0x7fffbfc57700 (LWP 22043)] [New Thread 0x7fffbec36700 (LWP 22044)] Removing cache at "/home/paul/.cache/kdenlive-thumbs.kcache" [New Thread 0x7fffb7fff700 (LWP 22047)] QCoreApplication::postEvent: Unexpected null receiver Removing cache at "/home/paul/.cache/kdenlive-thumbs.kcache" // / processing file open // / processing file open: validate Opening a document with version 0.91 / 0.91 // / processing file validate ok *** FOUND GUIDES: 0 ** QXcbConnection: XCB error: 8 (BadMatch), sequence: 25733, resource id: 49259, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 25753, resource id: 49259, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 25852, resource id: 49259, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch),
[kexi] [Bug 357655] Misaligned combo boxes for tabular view on bigger tables
https://bugs.kde.org/show_bug.cgi?id=357655 --- Comment #7 from Jarosław Staniek--- Created attachment 96514 --> https://bugs.kde.org/attachment.cgi?id=96514=edit Test file with 1000 records as described -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 355398] Crash if I rescale video on render :(
https://bugs.kde.org/show_bug.cgi?id=355398 --- Comment #8 from Jean-Baptiste Mardelle--- Git commit 164988fd80c90bce637208b547d496a14fc7b004 by Jean-Baptiste Mardelle. Committed on 07/01/2016 at 23:09. Pushed by mardelle into branch 'Applications/15.12'. Try to fix render resize crash with Movit M +1-1src/dialogs/renderwidget.cpp http://commits.kde.org/kdenlive/164988fd80c90bce637208b547d496a14fc7b004 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 357674] New: kdenlive crashes
https://bugs.kde.org/show_bug.cgi?id=357674 Bug ID: 357674 Summary: kdenlive crashes Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: gtlinux...@gmail.com Application: kdenlive (15.12.0) (Compiled from sources) Qt Version: 5.5.1 Operating System: Linux 4.3.0-gentoo x86_64 Distribution: "NAME=Gentoo" -- Information about the crash: - What I was doing when the application crashed: It crashes at first start, immediately after closing of the wizard The crash can be reproduced every time. -- Backtrace: Application: Kdenlive (kdenlive), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fad05ea47c0 (LWP 11822))] Thread 5 (Thread 0x7fad038b6700 (LWP 11832)): #0 0x7fad1260a2bd in poll () from /lib64/libc.so.6 #1 0x7fad0db56b2a in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fad0db58b9f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fad05822879 in QXcbEventReader::run (this=0x563508cce510) at qxcbconnection.cpp:1229 #4 0x7fad13028f9c in QThreadPrivate::start (arg=0x563508cce510) at thread/qthread_unix.cpp:331 #5 0x7fad115a04cc in start_thread () from /lib64/libpthread.so.0 #6 0x7fad12613d9d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7face9d0b700 (LWP 11906)): #0 0x7ffe03efb939 in ?? () #1 0x7ffe03efbb3a in clock_gettime () #2 0x7fad12621260 in clock_gettime () from /lib64/libc.so.6 #3 0x7fad130e7629 in qt_clock_gettime (ts=0x7face9d0aa90, clock=) at tools/qelapsedtimer_unix.cpp:105 #4 do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:156 #5 qt_gettime () at tools/qelapsedtimer_unix.cpp:165 #6 0x7fad1327a59f in QTimerInfoList::updateCurrentTime (this=this@entry=0x7face4002ed0) at kernel/qtimerinfo_unix.cpp:84 #7 0x7fad1327aa88 in QTimerInfoList::timerWait (this=0x7face4002ed0, tm=...) at kernel/qtimerinfo_unix.cpp:381 #8 0x7fad1327c095 in timerSourcePrepareHelper (src=, timeout=0x7face9d0abb4) at kernel/qeventdispatcher_glib.cpp:127 #9 0x7fad1327c1bd in timerSourcePrepare (source=, timeout=) at kernel/qeventdispatcher_glib.cpp:160 #10 0x7fad0e42a7c0 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #11 0x7fad0e42b1b9 in ?? () from /usr/lib64/libglib-2.0.so.0 #12 0x7fad0e42b401 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #13 0x7fad1327c5bb in QEventDispatcherGlib::processEvents (this=0x7face40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #14 0x7fad13217853 in QEventLoop::exec (this=this@entry=0x7face9d0adb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #15 0x7fad13022624 in QThread::exec (this=this@entry=0x5635096d1ec0) at thread/qthread.cpp:503 #16 0x7fad11204468 in QQmlThreadPrivate::run (this=0x5635096d1ec0) at qml/ftw/qqmlthread.cpp:141 #17 0x7fad13028f9c in QThreadPrivate::start (arg=0x5635096d1ec0) at thread/qthread_unix.cpp:331 #18 0x7fad115a04cc in start_thread () from /lib64/libpthread.so.0 #19 0x7fad12613d9d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7face8c3a700 (LWP 11942)): #0 0x7fad12605f2d in read () from /lib64/libc.so.6 #1 0x7fad0e47eeb1 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fad0e42ad54 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fad0e42b233 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fad0e42b401 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fad1327c5bb in QEventDispatcherGlib::processEvents (this=0x7facdc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7fad13217853 in QEventLoop::exec (this=this@entry=0x7face8c39db0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7fad13022624 in QThread::exec (this=this@entry=0x56350a73f080) at thread/qthread.cpp:503 #8 0x7fad11204468 in QQmlThreadPrivate::run (this=0x56350a73f080) at qml/ftw/qqmlthread.cpp:141 #9 0x7fad13028f9c in QThreadPrivate::start (arg=0x56350a73f080) at thread/qthread_unix.cpp:331 #10 0x7fad115a04cc in start_thread () from /lib64/libpthread.so.0 #11 0x7fad12613d9d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7face26ce700 (LWP 21995)): [KCrash Handler] #6 0x7fad125547cc in raise () from /lib64/libc.so.6 #7 0x7fad12555db1 in abort () from /lib64/libc.so.6 #8 0x7fad13012016 in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1578 #9 QMessageLogger::fatal (this=this@entry=0x7face26cd400, msg=msg@entry=0x7fad132e1d88 "ASSERT failure in %s: \"%s\", file %s, line %d") at global/qlogging.cpp:781 #10 0x7fad1300bf06 in qt_assert_x (where=where@entry=0x7fad132ede12 "QCoreApplication::sendEvent", what=,
[kdenlive] [Bug 355398] Crash if I rescale video on render :(
https://bugs.kde.org/show_bug.cgi?id=355398 --- Comment #10 from Paul Konecny--- Created attachment 96516 --> https://bugs.kde.org/attachment.cgi?id=96516=edit Backtrace movit 1.2.0 i965 with fix With the official movit version 1.2.0 i get a segfault in libc.so.6 Guess I'll recompile some more stuff... -- You are receiving this mail because: You are watching all bug changes.
[kbruch] [Bug 357675] New: Options for "Answer:" and "Operations:" should be radio buttons
https://bugs.kde.org/show_bug.cgi?id=357675 Bug ID: 357675 Summary: Options for "Answer:" and "Operations:" should be radio buttons Product: kbruch Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: seb@hpfsc.de Reporter: aspotas...@gmail.com CC: tiagoporang...@gmail.com "Answer" (Mixed number / Reduced form) and "Operations" (+, -, /, *) are mutual exclusive options and thus need to be done as radio buttons instead of check boxes. They are currently checkboxes. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 357680] New: Option to hide deleted-but-not-purged messages
https://bugs.kde.org/show_bug.cgi?id=357680 Bug ID: 357680 Summary: Option to hide deleted-but-not-purged messages Product: trojita Version: git Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: luke-jr+kdeb...@utopios.org There's a way to hide read messages, but not deleted ones? Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 355398] Crash if I rescale video on render :(
https://bugs.kde.org/show_bug.cgi?id=355398 --- Comment #11 from Paul Konecny--- Created attachment 96518 --> https://bugs.kde.org/attachment.cgi?id=96518=edit Backtrace movit 1.2.0 i965 with fix ffmpeg and glibc Okay this is the backtrace for movit 1.2.0 with glibc ffmpeg movit-1.2.0 mlt and kdenlive all with debugging symbols. On the console I also get this message [swscaler @ 0x7fff98b50700] Warning: data is not aligned! This can lead to a speedloss kdenlive: padding_effect.cpp:132: virtual void movit::PaddingEffect::inform_input_size(unsigned int, unsigned int, unsigned int): Assertion `input_num == 0' failed. - I just tried it with movit-git and I don't get the immediate crash but the monitor stays black and when I try to render something the rendering aborts immediately This is the output of the render window: Rendering of /home/paul/Unbenannt12.mp4 crashed medium: [ ref=1, _mlt_properties_load=medium, __mlt_properties_load=medium ] Movit system requirements: Needs at least GLSL version 1.30 (has version 1,0) [consumer qglsl] OpenGL Shading Language rendering is not supported on this machine. [filter avcolor_space] Invalid format glsl [filter avcolor_space] Invalid format glsl In the terminal there are many messages like this: GL error 502 at /home/paul/rebuild/4/src/kdenlive/src/monitor/glwidget.cpp : 406 [filter avcolor_space] Invalid format glsl It seems the OpenGL context (or whatever it is called) is detected with 1.0 instead of the minimum 1.3 This is the glxinfo output for my cards: Intel HD4400 DRI_PRIME=0 glxinfo | grep "OpenGL" OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.1.0 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 11.1.0 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.1.0 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: AMD Radeon HD8750M DRI_PRIME=1 glxinfo | grep "OpenGL" OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD OLAND (DRM 2.43.0, LLVM 3.7.0) OpenGL core profile version string: 4.1 (Core Profile) Mesa 11.1.0 OpenGL core profile shading language version string: 4.10 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 11.1.0 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.1.0 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: They are capable of 3.3 and 4.1 respectively so this shouldn't be the problem. Hope this helps you J-B! Cheers! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 355398] Crash if I rescale video on render :(
https://bugs.kde.org/show_bug.cgi?id=355398 --- Comment #12 from Jean-Baptiste Mardelle--- I think there might be several issues here. First this error: Movit system requirements: Needs at least GLSL version 1.30 (has version 1,0) [consumer qglsl] If you updated movit, you probably need to recompile MLT. Be sure to do a "make distclean" in MLT's source repository to start a clean compilation. libswscale is not supposed to be called when using movit. can you send me or attach here the project file ? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 357525] plasma-nm crash confirming credentials to openconnect VPN
https://bugs.kde.org/show_bug.cgi?id=357525 René Krellchanged: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #3 from René Krell --- I'm already on Plasma 5.5.2 and cannot reproduce this any longer. Apparently there is nothing else to do here, marking this resolved. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 356956] Open with Dolphin does not set focus to mounted device
https://bugs.kde.org/show_bug.cgi?id=356956 --- Comment #1 from Axel Braun--- Actually, on a fresh install (no upgrade as in my case), it workes for an inserted USB stick, but not for a CD-ROM. Can this be a timinig issue? Dolphin is called while the mount is not fully processed? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 357621] Screen cannot be turned on after it has been set to "energy saving" (goes off)
https://bugs.kde.org/show_bug.cgi?id=357621 --- Comment #2 from Simone Gaiarin--- Yes, it doesn't turn on when the backlight is off. It seems to happen when it has been off for a while. If I've tried to replicate it I've waited some seconds after the backlight has gone off and then I moved the mouse, and it did turn on. While when I leave it there longer it doesn't turn on. How can I better debug this behavior? -- 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 #2 from Mario Fux--- Thanks Christopher and Edward for this bug report and confirmation. I hope to confirm it myself in the next week or two and then fix it for a final release of the Qt4 based version of Simon somewhen in Q1/Q2 2016. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357642] New: Calendar no longer highlights holidays like Bank Holidays, Christmas, New Year
https://bugs.kde.org/show_bug.cgi?id=357642 Bug ID: 357642 Summary: Calendar no longer highlights holidays like Bank Holidays, Christmas, New Year Product: plasmashell Version: 5.5.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Calendar Assignee: mklape...@kde.org Reporter: vkr...@yahoo.com CC: plasma-b...@kde.org This is a regression. In KDE 4.14, the calendar popup wrapped each bank holiday in a thin red line. In 5.5.2 this useful feature is gone. Reproducible: Always Steps to Reproduce: 1. Click on the digital clock in the panel. Pop up calendar appears. 2. Scroll to January or December. 3. Actual Results: Public holidays (Jan 1st, etc) are indistingushable from normal days. Expected Results: Public holidays (Jan 1st, etc) are highlighted and are easily identified. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357644] New: Plasma crashed affter delete new standart panel
https://bugs.kde.org/show_bug.cgi?id=357644 Bug ID: 357644 Summary: Plasma crashed affter delete new standart panel Product: plasmashell Version: 5.4.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: v_bol...@mail.ru CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.2) Qt Version: 5.4.2 Operating System: Linux 4.2.0-22-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: add new panel changed setting work room by "Settings Folder" run VirtualBox -> start guest system->(one time) in kubuntu delete new panel Crashed -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa2835aa800 (LWP 1178))] Thread 9 (Thread 0x7fa26ead1700 (LWP 1182)): #0 0x7fa27dd528dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fa281d99bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fa281d9b74f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fa270e1ba39 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so #4 0x7fa27e4452be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa27d5346aa in start_thread (arg=0x7fa26ead1700) at pthread_create.c:333 #6 0x7fa27dd5deed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7fa267fff700 (LWP 1185)): #0 0x7fa27dd528dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fa27aaff1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa27aaff2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa27e67c29b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa27e62275a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa27e4403d4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa280c68f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fa27e4452be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa27d5346aa in start_thread (arg=0x7fa267fff700) at pthread_create.c:333 #9 0x7fa27dd5deed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7fa25e0db700 (LWP 1190)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fa265a9a4da in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #2 0x7fa265a99c17 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #3 0x7fa27d5346aa in start_thread (arg=0x7fa25e0db700) at pthread_create.c:333 #4 0x7fa27dd5deed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7fa259cec700 (LWP 1200)): #0 0x7fa27ab43869 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fa27aafe2c4 in g_main_context_release () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa27aaff1a6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa27aaff2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa27e67c29b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa27e62275a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa27e4403d4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa280c68f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fa27e4452be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fa27d5346aa in start_thread (arg=0x7fa259cec700) at pthread_create.c:333 #10 0x7fa27dd5deed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7fa253484700 (LWP 1212)): #0 0x7fa27dd4e49d in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fa27ab424e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa27aafecd4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa27aaff190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa27aaff2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fa27e67c29b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa27e62275a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa27e4403d4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa280c68f85 in ?? () from
[kwin] [Bug 357643] Double-click on title bar does nothing.
https://bugs.kde.org/show_bug.cgi?id=357643 --- Comment #3 from Thomas Lübking--- Might affect dolphin5 as well? run "kcmshell5 mouse", alter the relevant settings on the 2nd tab to something sane (but alter them), apply, see what happens. Run dolphin, open the settings dialog - according to the dupe that was enough to trigger this *shrug* -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357500] setting the minimum panel size below the maximum panel size causes the panel to flicker between it's minimum and maximum size
https://bugs.kde.org/show_bug.cgi?id=357500 34cm8565becib9nos...@mailinator.com changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from 34cm8565becib9nos...@mailinator.com --- (In reply to David Edmundson from comment #2) > I can't reproduce this. > > It's possible a change I made in the upcoming Plasma 5.5.3 will fix this. > Could you be sure to retest when you get that. This bug is resolved as of Plasma 5.5.3. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 357615] C file parsed as a C++ file
https://bugs.kde.org/show_bug.cgi?id=357615 --- Comment #8 from Pedro Ferreira--- (In reply to Sergey Kalinichev from comment #7) > Yes, we can definitely parse .c as plain C. But then again it solves nothing > IMO, as people will come back complaining that headers are not parsed as > plain C, but sources are. So, I don't know... True, but .h files are parsed as part of #include directives. Arguably, the clang parser shouldn't be called to parse those files independently. Without wanting to sound demeaning, other IDE's don't have this problem. How did they solve it? Setting the project settings won't work on the very common setting where a project has both C and C++ files (and potentially other languages). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 357615] C file parsed as a C++ file
https://bugs.kde.org/show_bug.cgi?id=357615 --- Comment #9 from Sergey Kalinichev--- > but .h files are parsed as part of #include directives. When compiling yes, but inside IDE not necessarily (e.g. you can add a header file and work on it, and #include it later on). > Without wanting to sound demeaning, other IDE's don't have this problem. How > did they solve it? I hardly doubt any other IDE performs such in-depth analysis as Clang does, so most likely "other IDE's" are simply not smart enough to correctly parse your test case. > Setting the project settings won't work on the very common setting where a > project has both C and C++ files (and potentially other languages). Like I've already mentioned you can select language type per file basis. -- You are receiving this mail because: You are watching all bug changes.
[simon] [Bug 331252] Confusing wording (shadow vocabulary, shadow lexicon, shadow dictionary) in GUI + Dokumentation
https://bugs.kde.org/show_bug.cgi?id=331252 Mario Fuxchanged: What|Removed |Added CC||kde...@unormal.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357450] Double click on the titlebar is not a standalone event
https://bugs.kde.org/show_bug.cgi?id=357450 Vadym Krevschanged: What|Removed |Added CC||vkr...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 354597] incorrect date/time for FTP files
https://bugs.kde.org/show_bug.cgi?id=354597 Wolfgang Bauerchanged: What|Removed |Added CC||wba...@tmo.at --- Comment #8 from Wolfgang Bauer --- I had a look at this, the problem is that the year is calculated wrong in kio_ftp. Proposed fix: https://git.reviewboard.kde.org/r/126659/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 345473] Double click on titlebar to maximize suddenly stops working
https://bugs.kde.org/show_bug.cgi?id=345473 Thomas Lübkingchanged: What|Removed |Added CC||vkr...@yahoo.com --- Comment #38 from Thomas Lübking --- *** Bug 357643 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[simon] [Bug 338159] process of synchronizing the active base model hangs at 20%
https://bugs.kde.org/show_bug.cgi?id=338159 Mario Fuxchanged: What|Removed |Added CC||kde...@unormal.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357643] Double-click on title bar does nothing.
https://bugs.kde.org/show_bug.cgi?id=357643 --- Comment #4 from Vadym Krevs--- ok, ran "kcmshell mouse". Double click interval was set to 400msec. Increased to 800msec, clicked Apply. Now double-clicking on titlebars does the expected thing. Set double click interval back to 400msec, clicked Apply. Double-clicking on titlebars still does the expected thing. Win! Ran dolphin5, opened the settings dialog, closed, exited dolphin5 - no effect on double click behavior - still works. -- You are receiving this mail because: You are watching all bug changes.
[simon] [Bug 349949] crashes immediately upon opening
https://bugs.kde.org/show_bug.cgi?id=349949 Mario Fuxchanged: What|Removed |Added CC||kde...@unormal.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356841] Plasma-nm applet does not show connection speed
https://bugs.kde.org/show_bug.cgi?id=356841 Jan Grulichchanged: What|Removed |Added Target Milestone|--- |1.0 Component|applet |DataEngines Assignee|jgrul...@redhat.com |plasma-b...@kde.org Product|plasma-nm |plasmashell -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357652] Notification popup don't appear if panel is in "Auto Hide" or "Windows Can Cover" mode
https://bugs.kde.org/show_bug.cgi?id=357652 Rog131changed: What|Removed |Added CC||samrog...@hotmail.com --- Comment #1 from Rog131 --- At here, the notification is shown very briefly: When capturing the screen with the ffmpeg & framerate 30 the notification is shown only in one frame. Notification is shown at the left top corner Full: http://i.imgur.com/CKuUWMe.jpg Partial: http://i.imgur.com/7MHFjSU.png Should be at the left low corner - Auto Hide disabled: http://i.imgur.com/UERw0Dd.png -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 357648] New: [kde4] ---- activity managers crashed when copying multiple files from my hard drive to my external ahrd drive
https://bugs.kde.org/show_bug.cgi?id=357648 Bug ID: 357648 Summary: [kde4] activity managers crashed when copying multiple files from my hard drive to my external ahrd drive Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: simonandr...@gmail.com Application: kactivitymanagerd (3.0) KDE Platform Version: 4.14.13 Qt Version: 4.8.6 Operating System: Linux 3.19.0-43-generic x86_64 Distribution: Ubuntu 14.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: Hello! i was copying several times several files from my hard drive to my external hard drive and somewhere in between dr. konqi appeared :) i use kubuntu trusty with kubuntu-ppa backports (trusty) enabled nice day Simon :) The crash can be reproduced sometimes. -- Backtrace: Application: Upravljalnik dejavnosti za KDE (kactivitymanagerd), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbcfac597c0 (LWP 2425))] Thread 7 (Thread 0x7fbce9ad5700 (LWP 2427)): #0 __GI___pthread_mutex_lock (mutex=0x7fbce4000a60) at ../nptl/pthread_mutex_lock.c:70 #1 0x7fbcf55f7981 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fbcf55b5f99 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbcf55b60ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fbcf99d07be in QEventDispatcherGlib::processEvents (this=0x7fbce40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #5 0x7fbcf99a20af in QEventLoop::processEvents (this=this@entry=0x7fbce9ad4e10, flags=...) at kernel/qeventloop.cpp:149 #6 0x7fbcf99a23a5 in QEventLoop::exec (this=this@entry=0x7fbce9ad4e10, flags=...) at kernel/qeventloop.cpp:204 #7 0x7fbcf989ec5f in QThread::exec (this=) at thread/qthread.cpp:537 #8 0x0040a06a in ?? () #9 0x7fbcf98a132f in QThreadPrivate::start (arg=0xbfa3b0) at thread/qthread_unix.cpp:349 #10 0x7fbcf7901182 in start_thread (arg=0x7fbce9ad5700) at pthread_create.c:312 #11 0x7fbcf85a447d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 6 (Thread 0x7fbce92d4700 (LWP 2435)): #0 0x7fbcf859712d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fbcf55b5fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fbcf55b60ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbcf99d07be in QEventDispatcherGlib::processEvents (this=0x7fbcdc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #4 0x7fbcf99a20af in QEventLoop::processEvents (this=this@entry=0x7fbce92d3e10, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fbcf99a23a5 in QEventLoop::exec (this=this@entry=0x7fbce92d3e10, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fbcf989ec5f in QThread::exec (this=) at thread/qthread.cpp:537 #7 0x0040a09a in ?? () #8 0x7fbcf98a132f in QThreadPrivate::start (arg=0xd755d0) at thread/qthread_unix.cpp:349 #9 0x7fbcf7901182 in start_thread (arg=0x7fbce92d4700) at pthread_create.c:312 #10 0x7fbcf85a447d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 5 (Thread 0x7fbce8ad3700 (LWP 2436)): #0 __pthread_mutex_unlock_usercnt (decr=1, mutex=0x7fbcea60) at pthread_mutex_unlock.c:69 #1 __GI___pthread_mutex_unlock (mutex=0x7fbcea60) at pthread_mutex_unlock.c:310 #2 0x7fbcf55f79b1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbcf55b5e9d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fbcf55b60ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fbcf99d07be in QEventDispatcherGlib::processEvents (this=0x7fbce8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #6 0x7fbcf99a20af in QEventLoop::processEvents (this=this@entry=0x7fbce8ad2e10, flags=...) at kernel/qeventloop.cpp:149 #7 0x7fbcf99a23a5 in QEventLoop::exec (this=this@entry=0x7fbce8ad2e10, flags=...) at kernel/qeventloop.cpp:204 #8 0x7fbcf989ec5f in QThread::exec (this=) at thread/qthread.cpp:537 #9 0x0040a0ca in ?? () #10 0x7fbcf98a132f in QThreadPrivate::start (arg=0xd85d50) at thread/qthread_unix.cpp:349 #11 0x7fbcf7901182 in start_thread (arg=0x7fbce8ad3700) at pthread_create.c:312 #12 0x7fbcf85a447d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7fbcdad84700 (LWP 2439)): #0 0x7fbcf55f761a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fbcf55f7979 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fbcf55b5699 in
[kwin] [Bug 357654] New: kwin crach
https://bugs.kde.org/show_bug.cgi?id=357654 Bug ID: 357654 Summary: kwin crach Product: kwin Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: pmanou...@gmail.com Application: kwin_x11 (5.5.2) Qt Version: 5.5.1 Operating System: Linux 4.1.13-5-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I connected to qremotecontrol and started Kaffeine in order to watch DVB-T television. I am not sure why this happens to my pc. I have also another bug that is plasma related. Maybe the fglrx driver is the problem, but I am not willing to uninstall it, since I need it for the OpenCL GPU programming, and the Blender app is also using it. I occasionally work with those two (OpenCL & Blender). -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f80d8dc4800 (LWP 2731))] Thread 6 (Thread 0x7f80ba697700 (LWP 2764)): #0 0x7f80d874c2b3 in select () at /lib64/libc.so.6 #1 0x7f80d6581179 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f80d6582af5 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f80d6582f3b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f80d652bd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f80d634d61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f80d0855df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f80d635232f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f80d7d820a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f80d875304d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f80a893e700 (LWP 2803)): #0 0x7f80d7d8605f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f80d52d786b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f80d52d7899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f80d7d820a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f80d875304d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f80a9940700 (LWP 2836)): #0 0x7f80d8724ded in nanosleep () at /lib64/libc.so.6 #1 0x7f80d874c9d4 in usleep () at /lib64/libc.so.6 #2 0x7f80275639d0 in () at /usr/lib64/dri/fglrx_dri.so #3 0x7f8026c32512 in () at /usr/lib64/dri/fglrx_dri.so #4 0x7f8026c32565 in () at /usr/lib64/dri/fglrx_dri.so #5 0x7f80d7d820a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f80d875304d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f80bb3a7700 (LWP 2947)): #0 0x7f80d874c2b3 in select () at /lib64/libc.so.6 #1 0x7f80d6581179 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f80d6582af5 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f80d6582f3b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f80d652bd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f80d634d61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f80d0855df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f80d635232f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f80d7d820a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f80d875304d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f80a913f700 (LWP 4629)): #0 0x7f80d7d8605f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f80d635334b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f80d0f4725b in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f80d0f476f3 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f80d635232f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f80d7d820a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f80d875304d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f80d8dc4800 (LWP 2731)): [KCrash Handler] #6 0x7f80d071a28f in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f80d071a6f0 in QV4::ExecutionEngine::toVariant(QV4::Value const&, int, bool) () at /usr/lib64/libQt5Qml.so.5 #8 0x7f80d07d8aca in QQmlPropertyPrivate::writeBinding(QObject*, QQmlPropertyData const&, QQmlContextData*, QQmlJavaScriptExpression*, QV4::Value const&, bool, QFlags) () at /usr/lib64/libQt5Qml.so.5 #9 0x7f80d0842823 in QQmlBinding::update(QFlags) () at /usr/lib64/libQt5Qml.so.5 #10 0x7f80d084c54a in () at /usr/lib64/libQt5Qml.so.5 #11 0x7f80d07dae2b in QQmlComponentPrivate::complete(QQmlEnginePrivate*,
[kexi] [Bug 357655] Misaligned comboboxes for foreign keys on big tables (Kexi 2.9.8)
https://bugs.kde.org/show_bug.cgi?id=357655 --- Comment #1 from Arseniy--- Created attachment 96504 --> https://bugs.kde.org/attachment.cgi?id=96504=edit Screenshot of incorrect UI behaviour Document is scrolled down by 2 rows. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 354597] incorrect date/time for FTP files
https://bugs.kde.org/show_bug.cgi?id=354597 Wolfgang Bauerchanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Version Fixed In||5.19.0 Latest Commit||http://commits.kde.org/kio/ ||68af1d7e89b7fed136d4cc62b76 ||c1c6ded2d94eb --- Comment #9 from Wolfgang Bauer --- Git commit 68af1d7e89b7fed136d4cc62b76c1c6ded2d94eb by Wolfgang Bauer. Committed on 07/01/2016 at 12:38. Pushed by wbauer into branch 'master'. [kio_ftp] fix display of file/directory modification time/date - QDate() treats the year literally (i.e. 90 is really year 90, not 1990), so subtracting 1900 is wrong. - Use QDate::currentDate() instead of QDateTime::currentDateTime(), we only need the current date anyway - Initialize day, month, and year to the current date instead of 0. In the case when no year is mentioned in the server's reply (the year is implicit), it wasn't set to the current year at all, so the result was either 0 or -1. FIXED-IN: 5.19.0 REVIEW: 126659 M +8-10 src/ioslaves/ftp/ftp.cpp http://commits.kde.org/kio/68af1d7e89b7fed136d4cc62b76c1c6ded2d94eb -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 357649] New: Light text on light background in device notifier
https://bugs.kde.org/show_bug.cgi?id=357649 Bug ID: 357649 Summary: Light text on light background in device notifier Product: Breeze Version: 5.5.2 Platform: openSUSE RPMs URL: https://i.imgur.com/YSEd538.jpg OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: tom.war...@kolabnow.com See the screenshot: The text "Open with file manager" is hard to read because there is not enough contrast between text and background. I looked into the pop-ups of the other tray items, but this seems to be the only place where text of this color appears. Reproducible: Always Steps to Reproduce: 1. Plug in a device 2. Open device notifier pop-up Actual Results: Text describing the device action is hard to read Expected Results: Text describing the device action is easy to read -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 357647] Journal shows HTML source instead of rendered rich text in entry list and print preview
https://bugs.kde.org/show_bug.cgi?id=357647 --- Comment #4 from Christian Kalkhoff--- Created attachment 96502 --> https://bugs.kde.org/attachment.cgi?id=96502=edit Screenshot: HTML source in the output -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 357630] crash when exiting with parser running [KDevelop::BackgroundParser::~BackgroundParser]
https://bugs.kde.org/show_bug.cgi?id=357630 --- Comment #5 from Milian Wolff--- please use valgrind to find out whats going on instead of guessing. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 356841] Plasma-nm applet does not show connection speed
https://bugs.kde.org/show_bug.cgi?id=356841 --- Comment #5 from Paulo Fidalgo--- (In reply to Jan Grulich from comment #4) > Could you please try to add "Network Monitor" applet to your desktop to > check whether this one is working? We use same dataengine for getting > information so I would like to be sure that the problem is in plasma-nm, > altough I haven't changed anything related to our traffic monitor recently. So the problem is on data engine, because Network monitor always stays in 0/0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357652] New: Notification popup don't appear if panel is in "Auto Hide" or "Windows Can Cover" mode
https://bugs.kde.org/show_bug.cgi?id=357652 Bug ID: 357652 Summary: Notification popup don't appear if panel is in "Auto Hide" or "Windows Can Cover" mode Product: plasmashell Version: 5.5.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Notifications Assignee: mklape...@kde.org Reporter: raghavendr.ra...@gmail.com CC: plasma-b...@kde.org After the 5.5.3 update the notification Popups stopped appearing, If the panel is in "Auto Hide" or "Windows Can Cover" mode the notification popup don't appear, the only way to bring them back is to switch panel to "Always Visible" mode and back again to these modes. This needs to be done in every restart. Reproducible: Always Steps to Reproduce: 1.Switch panel to Windows can cover mode 2.restart 3.test notifications Actual Results: notification popup don't appear Expected Results: notification popups should appear regardless of the panel view mode Another user also experienced this, you can take a look at the discussion on kde forum here -> https://forum.kde.org/viewtopic.php?f=289=130420 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357652] Notification popup don't appear if panel is in "Auto Hide" or "Windows Can Cover" mode
https://bugs.kde.org/show_bug.cgi?id=357652 --- Comment #2 from Raghavendra kamath--- yes , on closer look, as Rog131 said they appear very briefly sometimes -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356723] Incomplete window updates after updating to Plasma 5.5.0
https://bugs.kde.org/show_bug.cgi?id=356723 Wilhelm Wijkanderchanged: What|Removed |Added CC||li...@0x5e.se -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 357684] New: kfiledialog's getsavefilename defaults to no overwrite confirmation, unlike qfiledialog
https://bugs.kde.org/show_bug.cgi?id=357684 Bug ID: 357684 Summary: kfiledialog's getsavefilename defaults to no overwrite confirmation, unlike qfiledialog Product: kdialog Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: br...@frogmouth.net Reporter: anntzer@gmail.com QFileDialog's getSaveFileName defaults to asking the user for confirmation when an existing file is selected (as it will likely be overwritten)... except when it delegates to the KDE5's native dialog, which defaults to no confirmation asked. Reproducible: Always Steps to Reproduce: 1. check that `kfiledialog --getsavefilename .` or `python -c 'from PyQt5.QtWidgets import *; app = QApplication([]); QFileDialog.getSaveFileName()'` don't ask the user for confirmation when an existing file is selected. 2. check that `python -c 'from PyQt5.QtWidgets import *; app = QApplication([]); QFileDialog.getSaveFileName(options=QFileDialog.DontUseNativeDialog)'` DOES prompt the user for confirmation in such a case. Actual Results: (see above) Expected Results: KFileDialog should prompt for confirmation when the user selects a file for overwriting. I believe that under KDE4, confirmation was on by default. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 357650] Power Management Window won't go away
https://bugs.kde.org/show_bug.cgi?id=357650 --- Comment #2 from Jim Hessin--- I am using Kubuntu 14.04 (LTS) - and whatever comes with that I'm not sure how to tell. On Thu, Jan 7, 2016 at 7:01 AM, Sebastian Kügler via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=357650 > > Sebastian Kügler changed: > >What|Removed |Added > > > CC||se...@kde.org > > --- Comment #1 from Sebastian Kügler --- > This seems to happen in a really old version, which may not receive fixes > anymore. Could you please specify the version of Plasma you're running? > > Your best bet is to upgrade, however, this is almost for sure fixed in > Plasma > 5. > > -- > You are receiving this mail because: > You reported the bug. > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 357655] Misaligned comboboxes for foreign keys on big tables (Kexi 2.9.8)
https://bugs.kde.org/show_bug.cgi?id=357655 Jarosław Staniekchanged: What|Removed |Added Version|unspecified |2.9.8 Target Milestone|--- |2.9.11 --- Comment #4 from Jarosław Staniek --- Thanks a lot, noted. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357654] kwin crach
https://bugs.kde.org/show_bug.cgi?id=357654 Thomas Lübkingchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Thomas Lübking --- *** This bug has been marked as a duplicate of bug 352259 *** -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 357610] audio volume gets reset to 100%
https://bugs.kde.org/show_bug.cgi?id=357610 Harald Sitterchanged: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Harald Sitter --- Phonon does not change the volume on its own, it only does so when instructed to by another application. You'll need to find out what happens at the time or rather which application is doing things when the volume changes and then file a bug against that application. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-frameworkintegration] [Bug 356840] Crash in KDEPlatformFileDialogHelper::KDEPlatformFileDialogHelper
https://bugs.kde.org/show_bug.cgi?id=356840 --- Comment #10 from EMR_Kde--- (In reply to Jason Elwell from comment #9) > Kate has become because I cannot open any files. I have turned off all > compositing, and the issue remains. Yeah, I am running Kate out of another desktop environment and it's weird... it stays up in the background, doesn't start when you want it to, freezes randomly. I've gone back to VIM :-\ In this case, I set my desktop to "Folder view" then as I was changing my desktop wallpaper. I clicked on "select file". Plasmashell crashed. Then something else crashed in the background, while I was writing the bug report!! Don't know, don't care, I am not using KDE5 for now. I just logged in to check it out, and see how stable it was/would be. I guess my question was answered. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #4 from AnAkkk--- No problem :) Thanks for the reply I am on ArchLinux, I had 5.5.2, and I just upgraded to 5.5.3 a few minutes ago. I'm guessing you might mean this: https://bugs.kde.org/show_bug.cgi?id=353974 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357652] Notification popup don't appear if panel is in "Auto Hide" or "Windows Can Cover" mode
https://bugs.kde.org/show_bug.cgi?id=357652 Martin Klapetekchanged: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Martin Klapetek --- Thanks for the report Are you able to test patches/run version from git? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357652] Notification popup don't appear if panel is in "Auto Hide" or "Windows Can Cover" mode
https://bugs.kde.org/show_bug.cgi?id=357652 Martin Klapetekchanged: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 --- Comment #4 from Martin Klapetek --- Actually now I can reproduce it. Investigating. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-frameworkintegration] [Bug 356840] Crash in KDEPlatformFileDialogHelper::KDEPlatformFileDialogHelper
https://bugs.kde.org/show_bug.cgi?id=356840 --- Comment #9 from Jason Elwell--- Please let me know what I can do to troubleshoot this. I am a humble sysadmin, but given enough instruction, I should be able to provide what is requited. Kate has become because I cannot open any files. I have turned off all compositing, and the issue remains. Please help me help fix this. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357659] New: 15.13: Bézier curve UI broken: looses settings, second handle of bottom-left point non-accessible
https://bugs.kde.org/show_bug.cgi?id=357659 Bug ID: 357659 Summary: 15.13: Bézier curve UI broken: looses settings, second handle of bottom-left point non-accessible Product: kdenlive Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: wegwerf-1-...@gmx.de The user interface for the Bézier curve effect is broken in several ways: 1. Initially (and whenever returning to this effect) the top-right and bottom-left points are accessible, but the helper pointers are outside the effect's UI window. 2. When leaving the effect by selecting something else and on return all settings for the effect are lost. As soon as the user tries to edit the Bézier curve, all settings are reset. 3. Albeit the background coloring is enabled by default, only a black background in the effect's graph UI is shown. Toggling twice makes the color background appear, albeit always the first one. Changing the channel to work on does not change the UI coloring. Note: I'm using locale DE_de, where the fraction separator is "," instead of ".". Reproducible: Always Steps to Reproduce: 1. Create Kdenlive project. 2. Add any clip to it. 3. Add Bézier Curve effect. 4. Try to change the handles. 5. Try to change the channel. Actual Results: 1. Handles are outside the UI graph region and thus inaccessible using the mouse. 2. UI graph background color is missing or does not change accordingly to channel selected. 3. Settings are lost when leaving the effect and later returning to it. Expected Results: 1. Initial all four handles should be accessible from the UI using the mouse. 2. UI should show colored background according to channel selected. 3. Settings must not be lost when leaving the effect and later returning to it. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 357658] Ark-15.12.0: default actions for clicking files: easy misconception of settings dialog
https://bugs.kde.org/show_bug.cgi?id=357658 --- Comment #3 from Till Schäfer--- The English translation for AGB (german) is "general terms and conditions" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 352259] segfault in QV4::ExecutionEngine::toVariant()
https://bugs.kde.org/show_bug.cgi?id=352259 Thomas Lübkingchanged: What|Removed |Added CC||pmanou...@gmail.com --- Comment #13 from Thomas Lübking --- *** Bug 357654 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-frameworkintegration] [Bug 356840] Crash in KDEPlatformFileDialogHelper::KDEPlatformFileDialogHelper
https://bugs.kde.org/show_bug.cgi?id=356840 EMR_Kdechanged: What|Removed |Added CC||emre...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348156] Add a feature to unredirect all fullscreen windows except some selected
https://bugs.kde.org/show_bug.cgi?id=348156 --- Comment #20 from Thomas Lübking--- (In reply to jeremy9856 from comment #19) > to use like a checkbox to activate the "gamemode" and a simple field to > enter the windows that should not disable the compositing. The checkbox is already there (this is how scripts are triggered) Please understand that everybody wants "his" feature to activate by sheer will, but we lack a brain interface. > It need some work but it worth it I think and it's a lot easier than the > Martin suggestion too. > http://blog.martin-graesslin.com/blog/2015/12/gaming-on-linux-move-to-next- > generation/ Sorry, I don't follow. It is *exactly* what's described in the "X11 workaround" section (and the rest is irrelevant to the topic) - the only question is "who activates the block" and *obviously* the ideal solution would be the client in question would just say "make me uncomposited". In a less than ideal world it's really a matter of scenario. I assume that for the vast majority of users only blocking some specific clients is the ideal solution. Only if you use your box predominantly to play resource intense games you require a blacklist approach to this (since it's obviously suddenly the more convenient way) -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 357658] Ark-15.12.0: Preview action does not respect external preview setting
https://bugs.kde.org/show_bug.cgi?id=357658 --- Comment #1 from Elvis Angelaccio--- (In reply to Till Schäfer from comment #0) > When configuring ark to use an external preview application instead of the > internal one, this works well while clicking the file. However, when using > the preview action the internal preview is always used, regardless of the > settings. Hi Till, this is the expected behavior. The preview action and the open-file action are two different things. The "Preview" button on the toolbar is always going to trigger the preview action. What you are looking for is the "Open File" action, which is currently not displayed by default on the toolbar (but it's available in the context menu when you right-click a file). You can add this action also to the toolbar: go to the "Settings" menu, then click on "Configure Toolbars...". Now choose the toolbar from the drop-down menu. At this point you should see the "Open File" action from the available ones. You should be able to move it on the right, under the "Current actions" list. (Note that the menu's names above may differ on your system, if you have Ark localized in your language). Let me know you have problems doing so. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-frameworkintegration] [Bug 356840] Crash in KDEPlatformFileDialogHelper::KDEPlatformFileDialogHelper
https://bugs.kde.org/show_bug.cgi?id=356840 --- Comment #12 from Jason Elwell--- sudo dnf -y upgrade qt5* kf5* --enablerepo updates-testing --refresh qt5-qtbase.x86_645.5.1-11.fc23@updates-testing qt5-qtbase-common.noarch 5.5.1-11.fc23@updates-testing qt5-qtbase-gui.x86_645.5.1-11.fc23@updates-testing No more immediate crashes! Thanks!!! -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 353463] RFE: Make use of iio-sensor-proxy
https://bugs.kde.org/show_bug.cgi?id=353463 Viniloxchanged: What|Removed |Added CC||vini...@vinilox.eu -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 357658] Ark-15.12.0: default actions for clicking files: easy misconception of settings dialog
https://bugs.kde.org/show_bug.cgi?id=357658 Till Schäferchanged: What|Removed |Added Summary|Ark-15.12.0: Preview action |Ark-15.12.0: default |does not respect external |actions for clicking files: |preview setting |easy misconception of ||settings dialog Severity|normal |minor -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356723] Incomplete window updates after updating to Plasma 5.5.0
https://bugs.kde.org/show_bug.cgi?id=356723 Jason Tibbittschanged: What|Removed |Added CC||ti...@math.uh.edu -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357683] New: Frozen at startup
https://bugs.kde.org/show_bug.cgi?id=357683 Bug ID: 357683 Summary: Frozen at startup Product: dolphin Version: 15.08.2 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: dvilla...@gmail.com Dolphin application suddenly froze. Then I terminated and restarted it, and it was frozen from the start. I even tried restarting my computer, and Dolphin will start frozen. I got more information when I started it from the command line, and also using GDB as per this site https://community.kde.org/Dolphin/FAQ/Freeze I get this message: KSambaShare: Could not find smb.conf! Reproducible: Always Steps to Reproduce: 1. Just start Dolphin. 2. Nothing else. Actual Results: Dolphin freezes at startup. >From terminal, I get: KSambaShare: Could not find smb.conf! Expected Results: Dolphin starts and I navigate my files and folders as usual. Thank you for your help. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357685] New: Plasma crash on boot
https://bugs.kde.org/show_bug.cgi?id=357685 Bug ID: 357685 Summary: Plasma crash on boot Product: plasmashell Version: 5.5.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: j...@mingan.name CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.0) Qt Version: 5.5.1 Operating System: Linux 4.2.8-200.fc22.x86_64 x86_64 Distribution: "Fedora release 22 (Twenty Two)" -- Information about the crash: Just booted the computer. Importantly, the notebook display shows the KDE loading logo and then goes dark. External monitor is working. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f907389c900 (LWP 2350))] Thread 7 (Thread 0x7f9053c39700 (LWP 2357)): #0 0x7f906b2162fd in poll () at /lib64/libc.so.6 #1 0x7f90716c4182 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f90716c5c77 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f9055bbbda9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f906be233ce in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f906a55d555 in start_thread () at /lib64/libpthread.so.0 #6 0x7f906b221b9d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f90511f1700 (LWP 2386)): #0 0x7f906b2162fd in poll () at /lib64/libc.so.6 #1 0x7f90667c4dbc in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f90667c4ecc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f906c05af0b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f906c001f0a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f906be1e424 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f907015eb45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7f906be233ce in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f906a55d555 in start_thread () at /lib64/libpthread.so.0 #9 0x7f906b221b9d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f9043fff700 (LWP 2395)): #0 0x7f90667c1ec0 in g_source_iter_clear () at /lib64/libglib-2.0.so.0 #1 0x7f90667c43d8 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #2 0x7f90667c4ceb in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f90667c4ecc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f906c05af0b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f906c001f0a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f906be1e424 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f907015eb45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #8 0x7f906be233ce in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f906a55d555 in start_thread () at /lib64/libpthread.so.0 #10 0x7f906b221b9d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f90429b1700 (LWP 2396)): #0 0x7f906b2162fd in poll () at /lib64/libc.so.6 #1 0x7f90667c4dbc in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f90667c4ecc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f906c05af0b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f906c001f0a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f906be1e424 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f907015eb45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7f906be233ce in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f906a55d555 in start_thread () at /lib64/libpthread.so.0 #9 0x7f906b221b9d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f9041084700 (LWP 2397)): #0 0x7f906a562540 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9072fb4514 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7f9072fb4559 in () at /lib64/libQt5Script.so.5 #3 0x7f906a55d555 in start_thread () at /lib64/libpthread.so.0 #4 0x7f906b221b9d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f903a3bc700 (LWP 2587)): #0 0x7f906b2162fd in poll () at /lib64/libc.so.6 #1 0x7f90667c4dbc in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f90667c4ecc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f906c05af0b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f906c001f0a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f906be1e424 in QThread::exec() () at
[dolphin] [Bug 357686] New: Divider on folder panel
https://bugs.kde.org/show_bug.cgi?id=357686 Bug ID: 357686 Summary: Divider on folder panel Product: dolphin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: guoyunhebr...@gmail.com Hope here will be a way to add dividers between bookmarks on folder panel, just like Firefox book mark menu. It makes long bookmark list clear. Thanks! Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 357678] Hide MIME type tab bar when only one option exists
https://bugs.kde.org/show_bug.cgi?id=357678 Jan Kundrátchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Jan Kundrát --- This is by design, to show the MIME structure of the message. While I agree that it's probably useless for a regular user, it's a nice toy, IMHO. It would also be too much work to change this "elegantly" without introducing other kludges. The margins are taken from your system's settings (Qt's settings and its style and its settings, to be specific). Maybe there's an option to tweak these for your entire system? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357669] shading and unshading a window makes it lose height
https://bugs.kde.org/show_bug.cgi?id=357669 --- Comment #2 from Marc Haber--- Gee, that was fast! Thanks, and appreciation! -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 357676] HTML-only email rendered as plain text
https://bugs.kde.org/show_bug.cgi?id=357676 --- Comment #2 from Jan Kundrát--- Please attach the data that your IMAP server returns in the BODYSTRUCTURE for this message. Here's how to do it: 1) Activate logging into an on-disk file (IMAP -> Debugging -> Log into ...). 2) Create a new mailbox just for this new e-mail. 3) Copy this message into that mailbox. 4) Open that mailbox. 5) Attach the log. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 357649] Light text on light background in device notifier
https://bugs.kde.org/show_bug.cgi?id=357649 Tom Warnkechanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Tom Warnke --- Already fixed according to https://www.reddit.com/r/kde/comments/3zujna/light_text_on_light_background_in_device_notifier/cypv740 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357687] New: Icons-Only Task Manager has button shapes
https://bugs.kde.org/show_bug.cgi?id=357687 Bug ID: 357687 Summary: Icons-Only Task Manager has button shapes Product: plasmashell Version: master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons-only Task Manager Assignee: h...@kde.org Reporter: myst...@gmail.com CC: plasma-b...@kde.org I've recently updated to a git pull of KDE from a week ago, but never exited my plasma session and restarted. Upon restart, my nice looking task manager now has button shapes. This is supposed to be an 'icons only' task manager; and you've provided no option to 'remove button outline' so I believe this to be a categorical bug. I had previously used the regular task manager, which after a certain point of open windows, started to look like this. I dislike the button outline. In the history of making plasma5 youve removed a lot of the setting options of kde4's respective task managers. I am unhappy with this removal, because I cannot get my panel to look proper anymore, after quite a long time of using kde4 and being very happy with the "no button shape, no background color, with indicators" style. I would like it back. Reproducible: Always Steps to Reproduce: 1. Want icons Only Actual Results: Get Buttons Instead. Expected Results: Icons, no outline, no button shape, just icons that I can click on. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 357677] Option to display brief headers
https://bugs.kde.org/show_bug.cgi?id=357677 --- Comment #1 from Jan Kundrát--- > KMail has (had?) an option to display only Subject/From/To > lines in the preview pane. What exactly would you like to have? If it's about the headers displayed in the part of screen which shows one e-mail and you would like to get rid of Date, Tags etc, then I don't think this will happen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351851] Hard Disk Space Usage plasmoid graphical glitch
https://bugs.kde.org/show_bug.cgi?id=351851 Marian Kyralchanged: What|Removed |Added CC||mky...@email.cz -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 357670] KMail 15.12.0: Composer auto-completion fails on first try
https://bugs.kde.org/show_bug.cgi?id=357670 Laurent Montelchanged: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- I confirm it (I saw it from some weeks/months) I couldn't success to understand why it doesn't work. I continue to investigate -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 Chris Gaddchanged: What|Removed |Added CC||gadd...@email.com -- You are receiving this mail because: You are watching all bug changes.