[kwin] [Bug 372057] Crash when changing settings on VirtualBox VM, only if compositing is enabled
https://bugs.kde.org/show_bug.cgi?id=372057 ras...@gmail.com changed: What|Removed |Added Platform|Other |Archlinux Packages Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372057] New: Crash when changing settings on VirtualBox VM, only if compositing is enabled
https://bugs.kde.org/show_bug.cgi?id=372057 Bug ID: 372057 Summary: Crash when changing settings on VirtualBox VM, only if compositing is enabled Product: kwin Version: 5.8.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: ras...@gmail.com Target Milestone: --- If compositing is enabled, I can consistently cause Kwin to crash by opening the settings menu for any virtual machine in VirtualBox, changing a setting, and clicking 'OK'. I've tried with several settings (toggle 3D accel, toggle EFI, change monitor count, etc.), it doesn't appear to matter which one is changed. No crash occurs when compositing is disabled. -- You are receiving this mail because: You are watching all bug changes.
[syndication] [Bug 372006] [Patch] Support feed deltas
https://bugs.kde.org/show_bug.cgi?id=372006 --- Comment #3 from Laurent Montel --- So what is the improvment in akregator ? What was the bug in akregator ? -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 372024] kinit5 crash at logout
https://bugs.kde.org/show_bug.cgi?id=372024 --- Comment #4 from RJ --- (In reply to Rajeesh K V from comment #3) > (In reply to Christoph Feck from comment #2) > > Ah wait, it is the touchpad kded module. You probably have an Wayland setup, > > but the touchpad module uses the XLib backend? Reassigning. > > Upon logout XlibBackend destructor causes XDisplayCleanup::cleanup() to > trigger which simply calls XCloseDisplay() (in X11 library) to close the > connection. > But lower in the stack X11 gets _XIOError. I'm not sure why. > > Like Christoph asked, are you in [X]Wayland session? Definitely not, for now. It was ordinary X11 session. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 372056] New: Choqok does not remember window position
https://bugs.kde.org/show_bug.cgi?id=372056 Bug ID: 372056 Summary: Choqok does not remember window position Product: choqok Version: Git Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mehrdad.mom...@gmail.com Reporter: a.fetto...@gmail.com CC: scarp...@kde.org Target Milestone: --- Last year I switched from KDE 4 to KDE 5 in that process I decided to upgrade as many of my qt apps to qt5. Among those apps was choqok, so I decided to the latest git version. A small bug that has been present since the switch is that choqok does not anymore remember its position on the desktop when launching it for the first time. It always starts up in the upper left corner if there are no other windows present on the desktop. One can then move around and place it somewhere else. But when you minimize to tray and then reopen it, then it has moved again. In my case it shifts down a few centimeter everytime from the original position I've set. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 369627] [Frameworks] unexpected background color
https://bugs.kde.org/show_bug.cgi?id=369627 --- Comment #13 from ras...@gmail.com --- About the unexpected color change: does this mean the bug is from QPalette? I don't understand how that's related to my KDE color theme. About Okular's background color, this is a separate issue, so I made a feature request here: https://bugs.kde.org/show_bug.cgi?id=372055 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 372055] New: Add option to change the background color
https://bugs.kde.org/show_bug.cgi?id=372055 Bug ID: 372055 Summary: Add option to change the background color Product: okular Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: ras...@gmail.com Target Milestone: --- Gwenview's settings menu has a simple slider to select a shade of gray for the background color. This would be a nice feature to have in Okular. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372037] Right clicking background in desktop grid causes glitching
https://bugs.kde.org/show_bug.cgi?id=372037 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 372042] Klipper applet do not propose QR barcode anymore
https://bugs.kde.org/show_bug.cgi?id=372042 Martin Gräßlin changed: What|Removed |Added Version|5.8.3 |unspecified Assignee|mgraess...@kde.org |neon-b...@kde.org Component|plasma-widget |Packages User Edition CC||j...@jriddell.org, ||mgraess...@kde.org, ||neon-b...@kde.org, ||sit...@kde.org Product|klipper |neon --- Comment #1 from Martin Gräßlin --- Seems to be a missing build dependency. Reassigning -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371537] Temporary freeze when showing multiple tray notifications
https://bugs.kde.org/show_bug.cgi?id=371537 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #14 from Martin Gräßlin --- In case it happens again, please reopen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372039] window position on screen after opening
https://bugs.kde.org/show_bug.cgi?id=372039 --- Comment #2 from Martin Gräßlin --- Please also provide the output of xwininfo and xprop of an affected window. If it happens the next time you can move the window by holding "alt" and left click anywhere on the window. Alternatively the shortcut Alt+F3 opens the operations menu which also allows to trigger the move. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 372054] KDE screen saver not working when VirtualBox guest is running.
https://bugs.kde.org/show_bug.cgi?id=372054 Mark Foley changed: What|Removed |Added CC||mfo...@novatec-inc.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 372054] New: KDE screen saver not working when VirtualBox guest is running.
https://bugs.kde.org/show_bug.cgi?id=372054 Bug ID: 372054 Summary: KDE screen saver not working when VirtualBox guest is running. Product: kde Version: 4.14.1 Platform: Slackware Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mfo...@novatec-inc.com Target Milestone: --- I have KDE 4.14.21 on Slackware 64 14.2. I have the KDE screen locker set to start in 15 minutes and require login after 1 minute [more]. I have the power management settings set to turn off screen after 30 minutes and suspend session after 20 minutes and lock screen. This all works fine except when I'm running a VirtualBox Windows 7 VM guest. Then the screen saver NEVER kicks in as long as the VM is running in the foreground. If another window is on top of the VM (e.g. Thunderbird, Firefox), or if the VM window is minimized, the screen saver does engage. This is a bit of a security risk as the desktop is left accessible if unattended. A shot-in-the-dark suggestion from the VirtualBox forum suggested there might be some setting in KDE defining how the screen saver works in regards to programs, e.g. playing a video. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 372024] kinit5 crash at logout
https://bugs.kde.org/show_bug.cgi?id=372024 Rajeesh K V changed: What|Removed |Added CC||rajeeshknamb...@gmail.com --- Comment #3 from Rajeesh K V --- (In reply to Christoph Feck from comment #2) > Ah wait, it is the touchpad kded module. You probably have an Wayland setup, > but the touchpad module uses the XLib backend? Reassigning. Upon logout XlibBackend destructor causes XDisplayCleanup::cleanup() to trigger which simply calls XCloseDisplay() (in X11 library) to close the connection. But lower in the stack X11 gets _XIOError. I'm not sure why. Like Christoph asked, are you in [X]Wayland session? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 158468] No way to change the time of single recurring event in edit dialog
https://bugs.kde.org/show_bug.cgi?id=158468 abyss changed: What|Removed |Added CC||abhinav.s.deshpande@gmail.c ||om --- Comment #4 from abyss --- (In reply to Denis Kurz from comment #3) > This bug has only been reported for versions before 4.14, which have been > unsupported for at least two years now. Can anyone tell if this bug still > present? > > If noone confirms this bug for a Framework-based version of korganizer > (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets > closed in about three months. I can confirm that this bug exists for my current set-up: Korganizer Version: 5.3.0 (QtWebEngine) Using: KDE Frameworks 5.27.0 Qt 5.7.0 (built against 5.7.0) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372053] New: [new color selector] lag and weird rendering of color wheel for Filter > Color > Color to Alpha
https://bugs.kde.org/show_bug.cgi?id=372053 Bug ID: 372053 Summary: [new color selector] lag and weird rendering of color wheel for Filter > Color > Color to Alpha Product: krita Version: 3.1 Beta Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Filters Assignee: krita-bugs-n...@kde.org Reporter: i...@davidrevoy.com Target Milestone: --- Created attachment 102023 --> https://bugs.kde.org/attachment.cgi?id=102023&action=edit [screenshot of the bug] Hi, maybe a bug introduced by new color-selector: ## To reproduce: - Open a basic sRGB document - Call the filter "Color to Alpha" ( Filter > Color > Color to Alpha ) ## Result: - Filter is really slow to open - The color-selector has a weird visual aspect (screenshot in attachement) - Drag-n-drop of the color cursor almost freeze computer - Crazy value possible ( with pick-color: R=6, G=6, B=6 ) ## Expected: - Color Selector follow the document's colorspace - Quick launch as it was before -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 371652] K3B Version 2.0.2 - in Left GUI-window is no root- or home-folder visible. Only optical drives are displayed
https://bugs.kde.org/show_bug.cgi?id=371652 --- Comment #5 from Leslie Zhai --- > But i think there is no need to install a higher version. > > K3B Version 2.0.2 usualy shows fine the HOME- and ROOT-folder, > like its displayed on the other two user-accounts. > > It's just broken on that one Main-user-account. > > So i only need advise how to fix it. > > Greetings > Loki Sorry that I am only maintaining K3b for KF5 but kdelibs4 unmaintained, I am tring to release k3b-2.10.0 https://mail.kde.org/pipermail/release-team/2016-November/009794.html if it is OK, you will easy-to-install deb package ;-) Regards, Leslie Zhai -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 371643] Kscreen display configuration is lost on reboot
https://bugs.kde.org/show_bug.cgi?id=371643 patrickrif...@yandex.com changed: What|Removed |Added Version|5.8.2 |5.8.3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 370430] Dolphin samba read-write issue on top folder share
https://bugs.kde.org/show_bug.cgi?id=370430
--- Comment #3 from Jón Frímann ---
I can confirm this bug in KDE 5.8.3.
It continues to happen in FreeBSD 10.3 with Samba 4.4.5. There was one
difference now, before I connected to Windows XP machine I connected to FreeBSD
machine and then I was able to create new folders at top folder levels
(samba:\\{computer}\folder\), after I connected to the Windows XP machine that
was no longer possible when I reconnected to the FreeBSD machine. There are no
error messages that I can show, since none appear in dmesg.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 372052] New: 打开应用程序菜单时，Plasma发生崩溃
https://bugs.kde.org/show_bug.cgi?id=372052 Bug ID: 372052 Summary: 打开应用程序菜单时，Plasma发生崩溃 Product: plasmashell Version: 5.8.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: hr5...@163.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.3) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.8.6-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: 当我打开应用程序菜单浏览菜单中的应用程序时，Plasma崩溃了，在此之前我删除了~/.local/share下的所有.directory文件。 The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4899faa800 (LWP 2307))] Thread 9 (Thread 0x7f47c4689700 (LWP 6507)): #0 0x7f4893dca2e9 in QMutex::unlock() () at /usr/lib/libQt5Core.so.5 #1 0x7f4894000eb1 in () at /usr/lib/libQt5Core.so.5 #2 0x7f488e9a6c89 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #3 0x7f488e9a76ab in () at /usr/lib/libglib-2.0.so.0 #4 0x7f488e9a789c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f489400172b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f4893fab23a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f4893dce0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f48971312d5 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f4893dd2d78 in () at /usr/lib/libQt5Core.so.5 #10 0x7f4892ee2454 in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f48936e87df in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f47d62e6700 (LWP 2447)): #0 0x7f48936df48d in poll () at /usr/lib/libc.so.6 #1 0x7f488e9a7786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f488e9a789c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f489400172b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f4893fab23a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f4893dce0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f47d88120a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x7f4893dd2d78 in () at /usr/lib/libQt5Core.so.5 #8 0x7f4892ee2454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f48936e87df in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f47e23cc700 (LWP 2445)): #0 0x7f48936df48d in poll () at /usr/lib/libc.so.6 #1 0x7f488e9a7786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f488e9a789c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f489400172b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f4893fab23a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f4893dce0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f4897cd0856 in () at /usr/lib/libQt5Quick.so.5 #7 0x7f4893dd2d78 in () at /usr/lib/libQt5Core.so.5 #8 0x7f4892ee2454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f48936e87df in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f486fbdd700 (LWP 2429)): #0 0x7f4892ee810f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f4899760ac4 in () at /usr/lib/libQt5Script.so.5 #2 0x7f4899760b09 in () at /usr/lib/libQt5Script.so.5 #3 0x7f4892ee2454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f48936e87df in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f487998a700 (LWP 2426)): #0 0x7f48936df48d in poll () at /usr/lib/libc.so.6 #1 0x7f488e9a7786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f488e9a789c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f489400172b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f4893fab23a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f4893dce0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f48971312d5 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f4893dd2d78 in () at /usr/lib/libQt5Core.so.5 #8 0x7f4892ee2454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f48936e87df in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f487b7c8700 (LWP 2376)): #0 0x7f48936f502f in __libc_enable_asynccancel () at /usr/lib/libc.so.6 #1 0x7f48936df482 in poll () at /usr/lib/libc.so.6 #2 0x7f488e9a7786 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f488e9a789c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f489400172b in QEventDispatcherGlib:
[kactivitymanagerd] [Bug 348194] kactivitymanager sometimes crashes on logout
https://bugs.kde.org/show_bug.cgi?id=348194 Kamil Kuduk changed: What|Removed |Added CC||kamil.ku...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 371965] git master: path to kdenlive file appended to original clip path on reloading clip
https://bugs.kde.org/show_bug.cgi?id=371965 --- Comment #6 from lukefromdc --- Created attachment 102022 --> https://bugs.kde.org/attachment.cgi?id=102022&action=edit Kdenlive file after first fix, clip reloaded This file was saved after reloading a clip, part of the path to that clip has been stripped and the clip must be found again to load the file. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 371965] git master: path to kdenlive file appended to original clip path on reloading clip
https://bugs.kde.org/show_bug.cgi?id=371965 --- Comment #5 from lukefromdc --- Created attachment 102021 --> https://bugs.kde.org/attachment.cgi?id=102021&action=edit Kdenlive file after first fix, clip not reloaded This is a valid file on my desktop and my system and opens fine because no clips have been reloaded -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 371965] git master: path to kdenlive file appended to original clip path on reloading clip
https://bugs.kde.org/show_bug.cgi?id=371965 --- Comment #4 from lukefromdc --- I made sure that "custom project folder" was unchecked, still got problems if any clip had been reloaded (and ONLY if a clip had been reloaded). If no clips are reloaded the projects open fine. Attaching two kdenlive project files: one before and one after reloading a clip. In the first file (clip not reloaded) the clip path is /home/luke/VIDEO/ZZ_Scratch/TEST/FILE0008.MOV In the second file (clip reloaded prior to save) the path comes up as VIDEO/ZZ_Scratch/TEST/FILE0008.MOV Meaning we now have a different problem. Instead of appending the path to the project file to the path (as before) it is now stripping part of the path to the clip. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 370430] Dolphin samba read-write issue on top folder share
https://bugs.kde.org/show_bug.cgi?id=370430 Martin Unzner changed: What|Removed |Added CC||marti...@posteo.de --- Comment #2 from Martin Unzner --- I can confirm this issue, and also the fact that it only occurs within KDE Plasma's KIO / Dolphin. I have that problem with a Synology DiskStation. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 372051] New: Applet turn up/down unavailable device.
https://bugs.kde.org/show_bug.cgi?id=372051 Bug ID: 372051 Summary: Applet turn up/down unavailable device. Product: plasma-pa Version: 5.7.5 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: alan.wary...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Audio volume applet does not detect when one of two output devices is unavailable/disconnected i.e Bluetooth and it do not change back default output to the only available device. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 371460] ANDs get converted to ORs when editing the filter
https://bugs.kde.org/show_bug.cgi?id=371460 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED Version|2.8-git |2.8.0 --- Comment #3 from Christoph Feck --- Thanks for the update. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 372024] kinit5 crash at logout
https://bugs.kde.org/show_bug.cgi?id=372024 Christoph Feck changed: What|Removed |Added Component|general |daemon Product|frameworks-kinit|Touchpad-KCM Assignee|fa...@kde.org |rajeeshknamb...@gmail.com --- Comment #2 from Christoph Feck --- Ah wait, it is the touchpad kded module. You probably have an Wayland setup, but the touchpad module uses the XLib backend? Reassigning. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 371916] execution tree xtree concept
https://bugs.kde.org/show_bug.cgi?id=371916 --- Comment #9 from Ivo Raisr --- As for the documentation, the concept is explained very well. Thank you for this! I found just few typos: When set to none, no memory execution - tree is be produced. + tree is produced. When set to allocs, the memory execution - tree gives the current number of allocated bytes and current number of + tree gives the current number of allocated bytes and the current number of allocated blocks. - bytes and blocks, the total number of freed bypes and + bytes and blocks, the total number of freed bytes and - an heap usage xtree graphical representation produced by + a heap usage xtree graphical representation produced by -curB current number of bytes allocated. The +curB current number of Bytes allocated. The -curBk current number of blocks allocated, +curBk current number of Blocks allocated, -An xtree file in a Callgrind Format contains a single callgraph, +An xtree file in the Callgrind Format contains a single callgraph, -An xtree file in a Massif Format contains one detailed tree +An xtree file in the Massif Format contains one detailed tree - visualiser are more versatile that the Massif Format + visualisers are more versatile than the Massif Format I also wonder if you can add a paragraph or two describing how to apply xtree analysis when profiling large programs, if possible? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 372024] kinit5 crash at logout
https://bugs.kde.org/show_bug.cgi?id=372024 --- Comment #1 from Christoph Feck --- Your crashes are really curious. Are you using some unconventional X11 setup? Here, XCloseDisplay causes an X IO Error. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 312020] Stack notifications above keep above, dock windows
https://bugs.kde.org/show_bug.cgi?id=312020 --- Comment #11 from sparhawk --- I can confirm the fix. I don't use yakuake any more, but notifications are now above terminator, which is set to "Keep Above Others". Cheers. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372050] New: No scroll in the window of hidden tray entries
https://bugs.kde.org/show_bug.cgi?id=372050 Bug ID: 372050 Summary: No scroll in the window of hidden tray entries Product: plasmashell Version: 5.8.2 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: nuor...@gmail.com Target Milestone: 1.0 The hidden tray entries (title "Status and Notifications") doesn't react to scroll over its elements, although it is a scrollable view and shows a scroollbar. This happens with both mouse and touchpad. The scrollbar works correctly if dragged. Reproduce: -start lots of programs with tray entries -select those entries to be hidden -press the small upwards triangle to trigger the hidden entries window -move cursor over entries and scroll. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 371916] execution tree xtree concept
https://bugs.kde.org/show_bug.cgi?id=371916 Ivo Raisr changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #8 from Ivo Raisr --- Thank you, Philippe, for answering my questions. I have an additional one and then some docs stuff below. >> 4. Functions in this header file use a mixture of camelCase and >> all_lower_case which is inconsistent and disturbs reader's eyes. Can you do >> something with it? > Humph, that is a very valuable comment, but I am not sure what style > to use. Alright. But you can unify the function names so their names are consistent among themselves. Consider this random selection: VG_(newXT)() VG_(xt_filter_maybe_below_main)() VG_(xt_offset_main_or_below_main)() VG_(init_XtAllocs)() VG_(XtMemoryFull_init)() VG_(XtMemoryFull_resizeInPlace)() VG_(XtMemory_report)() VG_(snapshotXT)() VG_(subFromXT)() VG_(n_ips_sel)() VG_(XtPrint_callgrind)() VG_(XtClose_massif)() Sometimes the function name follows pattern: "XTthing_operation", sometimes "operationXT" and sometimes something completely different. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372049] New: Crash upon startup
https://bugs.kde.org/show_bug.cgi?id=372049 Bug ID: 372049 Summary: Crash upon startup Product: kdevelop Version: 4.7.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: bo...@turboprinz.de Target Milestone: --- Application: kdevelop (4.7.3) KDE Platform Version: 4.14.16 Qt Version: 4.8.7 Operating System: Linux 4.4.0-45-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Kdevelop was automatically starting with a previous session together with system startup -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f459fba3900 (LWP 2339))] Thread 5 (Thread 0x7f44e2a8d700 (LWP 2849)): #0 0x7f459c293b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f459630939c in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f44dc003710, timeout=, context=0x7f44dc0009a0) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:4135 #2 0x7f459630939c in g_main_context_iterate (context=context@entry=0x7f44dc0009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3835 #3 0x7f45963094ac in g_main_context_iteration (context=0x7f44dc0009a0, may_block=1) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901 #4 0x7f459ca9f2ce in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7f459ca6d18f in QEventLoop::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f459ca6d4f5 in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f459c95c549 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7f459c95ee3c in () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f459878670a in start_thread (arg=0x7f44e2a8d700) at pthread_create.c:333 #10 0x7f459c29f82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f44f7fff700 (LWP 2829)): #0 0x7f459c293b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f459630939c in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f44f0002de0, timeout=, context=0x7f44f9a0) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:4135 #2 0x7f459630939c in g_main_context_iterate (context=context@entry=0x7f44f9a0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3835 #3 0x7f45963094ac in g_main_context_iteration (context=0x7f44f9a0, may_block=1) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901 #4 0x7f459ca9f2ce in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7f459ca6d18f in QEventLoop::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f459ca6d4f5 in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f459c95c549 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7f459c95ee3c in () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f459878670a in start_thread (arg=0x7f44f7fff700) at pthread_create.c:333 #10 0x7f459c29f82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f44fda3a700 (LWP 2827)): #0 0x7f459878c759 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f459c95f384 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f459b24cca6 in () at /usr/lib/libkdevplatformlanguage.so.8 #3 0x7f459c95ee3c in () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f459878670a in start_thread (arg=0x7f44fda3a700) at pthread_create.c:333 #5 0x7f459c29f82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f457f040700 (LWP 2494)): #0 0x7f459878c3b0 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f4599e7be1a in () at /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x7f4599e7be49 in () at /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x7f459878670a in start_thread (arg=0x7f457f040700) at pthread_create.c:333 #4 0x7f459c29f82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f459fba3900 (LWP 2339)): [KCrash Handler] #6 0x7f459b29e790 in KDevelop::ParsingEnvironmentFile::indexedTopContext() const () at /usr/lib/libkdevplatformlanguage.so.8 #7 0x7f459b29e909 in KDevelop::ParsingEnvironme
[Akonadi] [Bug 372048] It's a huge Dbus based crashbug
https://bugs.kde.org/show_bug.cgi?id=372048 --- Comment #2 from link3...@gmail.com --- The error that says it's Dbus related comes from kmail. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371537] Temporary freeze when showing multiple tray notifications
https://bugs.kde.org/show_bug.cgi?id=371537 --- Comment #13 from Alex Dănilă --- After upgrading Debian to latest Testing (new kernel, KDE and Qt stuff) I don't see this anymore. Also, doing ssh precisely during those 5 seconds of freeze looks pretty difficult. Should this reproduce, I would need an easier method to debug. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 372048] It's a huge Dbus based crashbug
https://bugs.kde.org/show_bug.cgi?id=372048 link3...@gmail.com changed: What|Removed |Added Attachment #102020|Sorry this is the real |Error report description|error report. | -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 372048] It's a huge Dbus based crashbug
https://bugs.kde.org/show_bug.cgi?id=372048 link3...@gmail.com changed: What|Removed |Added Attachment #102019|This is the file. |Self-test-report description|| -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 372048] It's a huge Dbus based crashbug
https://bugs.kde.org/show_bug.cgi?id=372048 --- Comment #1 from link3...@gmail.com --- Created attachment 102020 --> https://bugs.kde.org/attachment.cgi?id=102020&action=edit Sorry this is the real error report. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 372048] New: It's a huge Dbus based crashbug
https://bugs.kde.org/show_bug.cgi?id=372048 Bug ID: 372048 Summary: It's a huge Dbus based crashbug Product: Akonadi Version: 1.12.1 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: link3...@gmail.com Target Milestone: --- Created attachment 102019 --> https://bugs.kde.org/attachment.cgi?id=102019&action=edit This is the file. Here is the error log. The system won't start at all. This is from a linux mint 17.3 install with all the most resent updates installed. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 372045] KStars Lite (Android) doesn't remember my geolocation
https://bugs.kde.org/show_bug.cgi?id=372045 Jasem Mutlaq changed: What|Removed |Added Assignee|mutla...@ikarustech.com |afedosk...@gmail.com Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 369627] [Frameworks] unexpected background color
https://bugs.kde.org/show_bug.cgi?id=369627 Christoph Feck changed: What|Removed |Added CC||cf...@kde.org --- Comment #12 from Christoph Feck --- This is 'QPalette::Dark', which was also traditionally used as the (darker) background next to white pages in KOffice, Calligra, and also for MDI window areas. If you used the view color, you would get a glowing white as the background with standard (bright) color schemes, and therefore have no contrast to the pages. Unfortuately KColorScheme has no suitable configurable color for those background areas. Except suggesting to make the color configurable I have no idea how to compute a suitable color derived from the other colors configured by the user. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372047] Switch from DK4 to DK5 fails: collection path contains %2F instead of /
https://bugs.kde.org/show_bug.cgi?id=372047 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Migration fails: collection |Switch from DK4 to DK5 |path contains %2F instead |fails: collection path |of /|contains %2F instead of / -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372047] Migration fails: collection path contains %2F instead of /
https://bugs.kde.org/show_bug.cgi?id=372047 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|Database-Migration |Database-Setup --- Comment #1 from caulier.gil...@gmail.com --- Must be fixed with next digiKam 5.3.0. Please test and report with preview of 5.3.0 AppImage bundle for Linux : https://drive.google.com/open?id=0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 368732] More options for ID generation: volume number, first page
https://bugs.kde.org/show_bug.cgi?id=368732 Thomas Fischer changed: What|Removed |Added Resolution|--- |FIXED Latest Commit|1b347eb534b97bb9f4ed97e67bb |http://commits.kde.org/kbib |183ea911006d9 |tex/a98a91cb2a30c4a90dfae82 ||4ac0093d2f2b53170 Status|ASSIGNED|RESOLVED --- Comment #5 from Thomas Fischer --- Git commit a98a91cb2a30c4a90dfae824ac0093d2f2b53170 by Thomas Fischer. Committed on 03/11/2016 at 22:07. Pushed by thomasfischer into branch 'master'. Adding volume and page number to id suggestions Adding volume number and first page number to the set of available fields in id suggestions (next to title, authors, and year). M +68 -2src/gui/preferences/settingsidsuggestionseditor.cpp M +20 -1src/processing/idsuggestions.cpp http://commits.kde.org/kbibtex/a98a91cb2a30c4a90dfae824ac0093d2f2b53170 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372047] New: Migration fails: collection path contains %2F instead of /
https://bugs.kde.org/show_bug.cgi?id=372047 Bug ID: 372047 Summary: Migration fails: collection path contains %2F instead of / Product: digikam Version: 5.2.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Database-Migration Assignee: digikam-de...@kde.org Reporter: war...@gmx.de Target Milestone: --- I’m a user of Digikam 4.14 and trying out a freshly built 5.2.0 on my Gentoo system with Plasma 5.8.3, frameworks 5.26.0. After going through the conversion wizard, I see the root entry of the collection I am trying to migrate in the album tree, but after a short moment it vanishes and I see a progress popup at 100 %. The tag tree is still there. The timeline also shows how many images I have for a given month. But this one is cleared once I closed and reopened Digikam. I found out that in Digikam’s Settings→Collections I see the collection that I tried to migrate, but its path is written as "%2Fhome%2Ffrank%2Fbilder". So I delete that, add a new collection with the proper path, click OK and then the collection is correctly imported. Quickly glancing over it, all tags and so on seem to be there. After a while of processing, the timeline is also populated again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369125] Brushstroke offset compared to actual cursor
https://bugs.kde.org/show_bug.cgi?id=369125 --- Comment #3 from Boudewijn Rempt --- Thanks for checking again! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372039] window position on screen after opening
https://bugs.kde.org/show_bug.cgi?id=372039 Christoph Feck changed: What|Removed |Added Product|kde |kwin Component|general |general Assignee|unassigned-b...@kde.org |kwin-bugs-n...@kde.org --- Comment #1 from Christoph Feck --- Please provide the output of 'qdbus org.kde.KWin /KWin supportInformation' -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 --- Comment #9 from fl...@mailoo.org --- I was going to seize the occasion to ask around if time limit was activated (it's not for me), but given x's account, this is not what's triggering the bug. Owncloud seems a common denominator though isn't it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 --- Comment #8 from x --- 5.8.2, Tumbleweed, three OC calendars with 90 day old events limits, crashes like a train. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372043] Massive leak on on calendar plugin
https://bugs.kde.org/show_bug.cgi?id=372043 x changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from x --- *** This bug has been marked as a duplicate of bug 367541 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 x changed: What|Removed |Added CC||ro...@yopmail.fr --- Comment #7 from x --- *** Bug 372043 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 367994] KbibTex crash while loading Zotero library
https://bugs.kde.org/show_bug.cgi?id=367994 Thomas Fischer changed: What|Removed |Added Status|ASSIGNED|NEEDSINFO Resolution|--- |WORKSFORME --- Comment #2 from Thomas Fischer --- (In reply to Thomas Fischer from comment #1) > Can you please test the following commit and let me know if the bug is fixed? > The commit is not yet in the official KBibTeX Git repository but rather in > my private clone. It changes the memory management in the Zotero module and > as such may fix the issue. > > http://commits.kde.org/clones/kbibtex/thomasfischer/kbibtex/ > 74aef1c4203477eb6d49166d07b3667576218b8f Any news on this issue? Otherwise I would apply this patch to the main code and close this bug report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360059] Inconsistent and too large font used for time in digital clock plasmoid
https://bugs.kde.org/show_bug.cgi?id=360059 x changed: What|Removed |Added CC||ro...@yopmail.fr --- Comment #9 from x --- What comment 8 says and illustrates with a screenshot: the date font size is too big (and so is the time's, btw). Would it somehow be possible to have an option to select not just the font face, but also the font size for the time, and separately, for the date? Reason why you want them to be different: most frequently the user looks at the time, and if that is the shorter string, then it would make sense to allow it to take more space by increasing its font size relative to the date, which is only glanced at occasionally. On the other hand, some users may prefer to have a long time (with seconds) and only a short date, or no date at all. In this case, they may also prefer a smaller font size in order to save screen space (or bigger font size, if they have eyesight trouble). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372046] New: plasma5 show tiny icons in HiDPI screens
https://bugs.kde.org/show_bug.cgi?id=372046 Bug ID: 372046 Summary: plasma5 show tiny icons in HiDPI screens Product: plasmashell Version: 5.8.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: gh...@mageia.org CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 102018 --> https://bugs.kde.org/attachment.cgi?id=102018&action=edit don't force disabling automatic scaling When plasma5 runs in a HiDPI screen (e.g. a 4k screen with 3820x2160 pixels of resolution), and the screen DPI is set at the proper values in X11 (e.g. using DisplaySize in xorg.conf or forcing the -dpi argument in either xrandr or Xorg executable), the icons aren't scaled proportionally but remains super-tiny, and thus almost unreadable. The same happens to widgets. The higher is the resolution, the smaller and unbalanced are the icons. For instance for a 4k monitor at 15.6" you'll have near to 282 dpi, which is almost 3 times the typical average DPI choosen at 96x96. The result is shown in the screenshots here https://bugs.mageia.org/attachment.cgi?id=8587. As you can see (the image is scaled for convenience) the icons of the Plasma's "System Settings" are almost unreadable, while instead the text scales proportionally. Apparently plasma is able to scale everything proportionally to DPI without the need of extra tweaking, or playing with env var or xrdb entries, but in this case it fails. The problems seems in the line: QT_AUTO_SCREEN_SCALE_FACTOR=0 of the script /usr/bin/startkde, which forces QT_AUTO_SCREEN_SCALE_FACTOR to 0, and thus "disables the automatic scaling based on the pixel density of the monitor for QT applications". IMHO this shouldn't be forced in the startup script, but should be left to system decide whether to apply or not, because if a user decide to force the QT_AUTO_SCREEN_SCALE_FACTOR=1 somewhere in startup scripts, those entries will be overridden by the startkde override. Removing it, would fix the problem, and Plasma will have the right behaviour, i.e. scale the icons, the widgets and the text, proportionally when requested, as you can see here: https://bugs.mageia.org/attachment.cgi?id=8586, I attach the fix. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 372045] New: KStars Lite (Android) doesn't remember my geolocation
https://bugs.kde.org/show_bug.cgi?id=372045 Bug ID: 372045 Summary: KStars Lite (Android) doesn't remember my geolocation Product: kstars Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: aa...@kde.org Target Milestone: --- Each time i start KStars Lite and i go to the geo location "window" it thinks i'm in Greenwich instead of the place i last set it with the "Set From GPS" button. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368468] digiKam hanging at start up with a collection that has >100000 sub folders
https://bugs.kde.org/show_bug.cgi?id=368468 --- Comment #8 from caulier.gil...@gmail.com --- Lars, Can you review last commits from Maik using current 5.3.0 AppImage bundle for Linux ? https://drive.google.com/open?id=0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 Jarom Jackson changed: What|Removed |Added CC||argentu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 367495] Geolocation editor and reverse geocoding segmentation fault
https://bugs.kde.org/show_bug.cgi?id=367495 caulier.gil...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||5.3.0 Resolution|--- |FIXED --- Comment #1 from caulier.gil...@gmail.com --- This problem is not reproducible with 5.3.0 AppImage bundle. https://drive.google.com/open?id=0BzeiVr-byqt5Y0tIRWVWelRJenM I close this file now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372044] New: Add indication of holiday region
https://bugs.kde.org/show_bug.cgi?id=372044 Bug ID: 372044 Summary: Add indication of holiday region Product: plasmashell Version: 5.8.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Calendar Assignee: plasma-b...@kde.org Reporter: ro...@yopmail.fr Target Milestone: 1.0 It's good to see that the feature in bug #92471 (which I'm not sure why is still open) has been finally re-implemented on Plasma 5. For those of us who have multiple holiday regions selected though, it would be very helpful if it could follow the behaviour KDE4 and give some indication of which holiday region/set each holiday pertains to, especially as it may not always be obvious from the language. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 371593] Sort valuelist combo
https://bugs.kde.org/show_bug.cgi?id=371593 --- Comment #5 from Thomas Fischer --- (In reply to Juergen Spitzmueller from comment #3) > Created attachment 101765 [details] > Updated patch that considers two more combo boxes Thank you for the patch! I applied it both to 0.6, 0.7, and master (not pushed yet). I made minor adjustments and some reformatting. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 Sven Brauch changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #9 from Sven Brauch --- Heh, yes, the trace shows what happens. The "missing include" problem assistant looks through all the files in your include paths recursively, and apparently across the network file system that takes too long. Not sure how to solve that right now -- but at least we know what the problem is. Thanks! I'll set status to confirmed since this is certainly an issue which can be reproduced and fixed. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366104] digikam5 "hangs' @ 100%CPU at exit
https://bugs.kde.org/show_bug.cgi?id=366104 caulier.gil...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||5.3.0 Resolution|--- |FIXED --- Comment #5 from caulier.gil...@gmail.com --- The original problem from this file is not reproducible with digiKam 5.3.0 Linux AppImage bundle. https://drive.google.com/open?id=0BzeiVr-byqt5Y0tIRWVWelRJenM I close this file now. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 --- Comment #8 from Lukas Jirkovsky --- I hope I sent interrupt at the right time... #0 0x74cc4c9b in __getdents64 () at /usr/lib/libc.so.6 #1 0x74cc4a10 in readdir_r () at /usr/lib/libc.so.6 #2 0x75556773 in () at /usr/lib/libQt5Core.so.5 #3 0x754dcc8c in () at /usr/lib/libQt5Core.so.5 #4 0x754dd4dd in () at /usr/lib/libQt5Core.so.5 #5 0x754ddd5c in QDirIterator::QDirIterator(QString const&, QStringList const&, QFlags, QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x754d6dcc in QDir::entryList(QStringList const&, QFlags, QFlags) const () at /usr/lib/libQt5Core.so.5 #7 0x7fffbdb12bf5 in (anonymous namespace)::scanIncludePaths(QString const&, QDir const&, int) (identifier=..., dir=..., maxDepth=maxDepth@entry=2) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/clang/duchain/unknowndeclarationproblem.cpp:95 #8 0x7fffbdb12fbc in (anonymous namespace)::scanIncludePaths(QString const&, QDir const&, int) (identifier=..., dir=..., maxDepth=2, maxDepth@entry=3) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/clang/duchain/unknowndeclarationproblem.cpp:105 #9 0x7fffbdb16ae3 in (anonymous namespace)::scanIncludePaths (includes=..., identifier=...) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/clang/duchain/unknowndeclarationproblem.cpp:118 #10 0x7fffbdb16ae3 in (anonymous namespace)::includeFiles (file=..., declarations=..., identifier=...) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/clang/duchain/unknowndeclarationproblem.cpp:390 #11 0x7fffbdb16ae3 in (anonymous namespace)::fixUnknownDeclaration(KDevelop::QualifiedIdentifier const&, KDevelop::Path const&, KDevelop::DocumentRange const&) (identifier=..., file=..., docrange=...) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/clang/duchain/unknowndeclarationproblem.cpp:466 #12 0x7fffbdb172b6 in UnknownDeclarationProblem::solutionAssistant() const (this=0x7fff8d2e60f0) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/clang/duchain/unknowndeclarationproblem.cpp:520 #13 0x72e9a6f7 in KDevelop::ProblemNavigationContext::html(bool) (this=0x2601e40, shorten=) at /home/stativ/aurbuild/kdevplatform-git/src/kdevplatform/language/duchain/navigation/problemnavigationcontext.cpp:172 #14 0x72e9fc16 in KDevelop::AbstractNavigationWidget::update() (this=this@entry=0x2821c50) at /home/stativ/aurbuild/kdevplatform-git/src/kdevplatform/language/duchain/navigation/abstractnavigationwidget.cpp:148 #15 0x72ea0800 in KDevelop::AbstractNavigationWidget::setContext(QExplicitlySharedDataPointer, int) (this=this@entry=0x2821c50, context=..., initBrows=initBrows@entry=400) at /home/stativ/aurbuild/kdevplatform-git/src/kdevplatform/language/duchain/navigation/abstractnavigationwidget.cpp:116 #16 0x7fffc22c04ba in ContextBrowserPlugin::navigationWidgetForPosition(KTextEditor::View*, KTextEditor::Cursor) (this=this@entry=0x118bef0, view=view@entry=0xe91640, position=...) at /home/stativ/aurbuild/kdevplatform-git/src/kdevplatform/plugins/contextbrowser/contextbrowser.cpp:539 #17 0x7fffc22c20b2 in ContextBrowserPlugin::showToolTip(KTextEditor::View*, KTextEditor::Cursor) (this=0x118bef0, view=0xe91640, position=...) at /home/stativ/aurbuild/kdevplatform-git/src/kdevplatform/plugins/contextbrowser/contextbrowser.cpp:585 #18 0x7fffc22c3e4f in ContextBrowserHintProvider::textHint(KTextEditor::View*, KTextEditor::Cursor const&) (this=0x118c068, view=, cursor=...) at /home/stativ/aurbuild/kdevplatform-git/src/kdevplatform/plugins/contextbrowser/contextbrowser.cpp:407 #19 0x71a4ffbf in () at /usr/lib/libKF5TextEditor.so.5 #20 0x71b518a5 in () at /usr/lib/libKF5TextEditor.so.5 #21 0x755e9659 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #22 0x755f66d8 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib/libQt5Core.so.5 #23 0x755ea473 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #24 0x7629de0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #25 0x762a5581 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #26 0x755bdde0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #27 0x756116ae in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #28 0x75611bd1 in () at /usr/lib/libQt5Core.so.5 #29 0x7fffec611587 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #30 0x7fffec6117f0 in () at /usr/lib/libglib-2.0.so.0 #31 0x7fffec61189c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #32 0x7561270f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #33 0x755bc23a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #34 0x7
[plasmashell] [Bug 371488] Persistent Notifications removed with swipe come back later
https://bugs.kde.org/show_bug.cgi?id=371488 --- Comment #2 from JanKusanagi --- Verified to be fixed in Mageia's 5.8.3. Thanks!! =) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372043] New: Massive leak on on calendar plugin
https://bugs.kde.org/show_bug.cgi?id=372043 Bug ID: 372043 Summary: Massive leak on on calendar plugin Product: plasmashell Version: 5.8.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Calendar Assignee: plasma-b...@kde.org Reporter: ro...@yopmail.fr Target Milestone: 1.0 If I go to the digital clock settings > Calendar, and tick on the PIM Events Plugin box, first, plasma freezes for a while (e.g., while I write this), then it crashes. When restarting it, if I try to display the calendar by clicking on the digital clock widget, it eats up all 16 Gb of memory in about 20 seconds, then crashes again. I suspect this is not how it is supposed to work. The PIM events in question are from three ownCloud calendars, which work fine on Kontact and elsewhere. Note: I see bug #293354 but in my case it's plasmashell eating up all the memory, not korgac. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 369003] editor crash
https://bugs.kde.org/show_bug.cgi?id=369003 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||5.3.0 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from caulier.gil...@gmail.com --- This problem is not reproducible with 5.3.0 AppImage bundle. https://drive.google.com/open?id=0BzeiVr-byqt5Y0tIRWVWelRJenM I close this file now. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 --- Comment #7 from Lukas Jirkovsky --- I just got an idea, though I may be completely wrong. Is it possible that it's related to the Clang Fix-its? They don't show when navigating using keyboard. I'll try to get backtrace. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369125] Brushstroke offset compared to actual cursor
https://bugs.kde.org/show_bug.cgi?id=369125 Pierre changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Pierre --- Hi :) It no longer happens. Tested with 5b6b187b36bdce977072ce9cb8df02db1a03424a / 3.0.92 but I can't tell you what commit exactly fixed it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371576] AppIndicator GTK apps fail to find icons in custom GTK icon theme folder and crash
https://bugs.kde.org/show_bug.cgi?id=371576 --- Comment #5 from André Brait --- Full >>>path<<< to the icon file, sorry for the typo. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 371593] Sort valuelist combo
https://bugs.kde.org/show_bug.cgi?id=371593 Thomas Fischer changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kbib ||tex/1397efc1bb858b34b4bed95 ||f19cf5084a66b27e8 Resolution|--- |FIXED --- Comment #4 from Thomas Fischer --- Git commit 1397efc1bb858b34b4bed95f19cf5084a66b27e8 by Thomas Fischer, on behalf of Juergen Spitzmueller. Committed on 03/11/2016 at 21:45. Pushed by thomasfischer into branch 'kbibtex/0.6'. Sorting field and entry types alphabetically Sorting lists of field and entry types as used in comboboxs locale-aware alphabetically. The change affects the following places: - Element widget, more specifically the combobox where the type of an entry can be selected: article, book, ... - The filter bar that allows, among others, filter the main list view by entries of type article, book, ... - The value list which can list and count occurrences of existing authors, titles, journals. The combobox to select which field type to assemble a list for is now sorted. Signed-off-by: Thomas Fischer M +18 -8src/gui/element/elementwidgets.cpp M +14 -1src/gui/widgets/filterbar.cpp M +7-0src/program/docklets/valuelist.cpp http://commits.kde.org/kbibtex/1397efc1bb858b34b4bed95f19cf5084a66b27e8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371576] AppIndicator GTK apps fail to find icons in custom GTK icon theme folder and crash
https://bugs.kde.org/show_bug.cgi?id=371576 --- Comment #4 from André Brait --- (In reply to Marco Martin from comment #3) > do you have an application that can reproduce the problem that doesn't > require any particular hardware? I have modified one of mine to behave like it used to when using the default options, and also to not depend on any specific hardware: https://github.com/andrebrait/nvidia-power-indicator-fake If you change the icon option to 'color', however, it sets the full icon to the icon file and it works ok. It seems that it now appears, but no icon is displayed. I can't get the same message as the user got, but I'm on Arch Linux, so many things have changed between when this bug was reported and now. At the time, the user was running KDE Neon. Please let me know if I can be of any help. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 --- Comment #6 from Sven Brauch --- Ok, so it really seems to be I/O. Thanks for the tests! Maybe it would be useful after all to run kdevelop in gdb, interrupt it when it's hanging, and get a backtrace. I guess that's the easiest way to find the code path causing the I/O -- I can't see it from the perf data. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 --- Comment #5 from Lukas Jirkovsky --- Another bunch of tests: Test #1 The project sources are in tmpfs, includes are on the samba share => same behaviour Test #2 All sources, including includes are in tmpfs => everything's fine -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 --- Comment #4 from Lukas Jirkovsky --- There must be something different in how the reparse (if it's the reparse) is invoked. I just did few more experiments: Test #1 1. rename a variable 2. move to a previous use of the variable using arrow keys 3. in the meantime, the project is reparsed and all previous uses are now marked "Use of undeclared identifier" The whole time KDevelop is responsive. Another test 1. rename a variable 2. quickly click on a use before it gets marked as a problem KDevelop stays responsive Test #2 1. rename a variable 2. wait for the reparse to finish 3. click on a use that is now underlined The whole KDevelop UI (I didn't realize it wasn't just the editor before) freezes for about 5 seconds. In fact, any click on the problem freezes the UI. Maybe I should have emphasized that the UI freezes every time I click on a problem, even when the project is fully parsed, so the parser may not be the problem after all. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 347721] Gwenview does not show PNM images (portable-anymap)
https://bugs.kde.org/show_bug.cgi?id=347721 --- Comment #7 from Alex10336 --- Thanks for forwarding issue. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 372042] New: Klipper applet do not propose QR barcode anymore
https://bugs.kde.org/show_bug.cgi?id=372042 Bug ID: 372042 Summary: Klipper applet do not propose QR barcode anymore Product: klipper Version: 5.8.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: plasma-widget Assignee: mgraess...@kde.org Reporter: ap10...@gmail.com Target Milestone: --- Since 5.8.0, QR barcode generator vanished. --- Using version 5.8.3 Up to date of Kde Neon - User Edition. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 370352] system hangs when waking up from screen off with a blank screen with mouse pointer
https://bugs.kde.org/show_bug.cgi?id=370352 --- Comment #13 from Rajinder Yadav --- Forget what I said about disabling the screen lock, I finally got a black screen with a mouse pointer and was not able to view by desktop. Also I tired pressing my power button to try to put system into RAM suspend mode, nothing happened. The moused pointer still movable but entire screen was black. Forced to do hard reboot. Here is my info video info: 01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] Flags: bus master, fast devsel, latency 0, IRQ 27 Memory at fd00 (32-bit, non-prefetchable) [size=16M] Memory at f000 (64-bit, prefetchable) [size=128M] Memory at f800 (64-bit, prefetchable) [size=32M] I/O ports at dc00 [size=128] Expansion ROM at fea8 [disabled] [size=512K] Capabilities: Kernel driver in use: nouveau Kernel modules: nvidiafb, nouveau -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 371966] No uninitialised values reported with PGI -Mstack_arrays
https://bugs.kde.org/show_bug.cgi?id=371966
--- Comment #10 from Carl Ponder ---
Stopping at line 70 puts it right after the array-allocation but before the
array-writes are happening:
62 implicit none
63 integer, intent(in) :: N
64 integer ( kind = 4 ) i
65 integer ( kind = 4 ) :: x(1:N)
66
67 !
68 ! X = { 0, 1, 2, 3, 4, ?a, ?b, ?c, ?d, ?e }.
69 !
70 do i = 1, 5
The data-state still says initialized, even though the array contains junk
values:
(gdb) print x
$2 = (40, 0, 117993993, 0, 117993992, 0, 69349896, 0, 19, 0)
(gdb) print &x
$3 = (PTR TO -> ( integer (10))) 0xffeffed90
(gdb) monitor xb 0xffeffed90 40
00 00 00 00 00 00 00 00
0xFFEFFED90:0x280x000x000x000x000x000x000x00
00 00 00 00 00 00 00 00
0xFFEFFED98:0x090x720x080x070x000x000x000x00
00 00 00 00 00 00 00 00
0xFFEFFEDA0:0x080x720x080x070x000x000x000x00
00 00 00 00 00 00 00 00
0xFFEFFEDA8:0x080x320x220x040x000x000x000x00
00 00 00 00 00 00 00 00
0xFFEFFEDB0:0x130x000x000x000x000x000x000x00
I'm checking with the compiler guys on this.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 372035] Crash while typing PHP code
https://bugs.kde.org/show_bug.cgi?id=372035 Sven Brauch changed: What|Removed |Added Component|general |Language Support: PHP CC||m...@svenbrauch.de -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 --- Comment #3 from Sven Brauch --- Ah, sorry, I overlooked the samba part. I find the perf data hard to read ... but it does seem to spend noticeable time in I/O. Maybe it would be interesting to copy the project to local disk and see if it still hangs. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 371966] No uninitialised values reported with PGI -Mstack_arrays
https://bugs.kde.org/show_bug.cgi?id=371966 --- Comment #9 from Philippe Waroquiers --- (In reply to Carl Ponder from comment #8) > If I *don't* compile with the -Mstack_arrays, I get this at line 77 instead: > > (gdb) print x > $1 = (0, 1, 2, 3, 4, 0, 0, 0, 0, 0) > (gdb) print &x > $2 = (PTR TO -> ( integer (10))) 0x70881d0 > > (gdb) monitor xb 0x70881d0 40 > 00 00 00 00 00 00 00 00 > 0x70881D0:0x000x000x000x000x010x000x000x00 > 00 00 00 00 00 00 00 00 > 0x70881D8:0x020x000x000x000x030x000x000x00 > 00 00 00 00 ff ff ff ff > 0x70881E0:0x040x000x000x000x000x000x000x00 > ff ff ff ff ff ff ff ff > 0x70881E8:0x000x000x000x000x000x000x000x00 > ff ff ff ff ff ff ff ff > 0x70881F0:0x000x000x000x000x000x000x000x00 So, the code generated is different. You should now debug at asm instruction level, using e.g. disp /i $pc then repeat stepi xb ... till you identify which instruction is effectively initialising the array. At this point, nothing seems abnormal on valgrind side. So very probably the compiler is generating some code that initialises this memory. You should discuss with the compiler people to ask why. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] New: KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 Bug ID: 372040 Summary: KDevelop editor become unresponsive when clicking into a problem Product: kdevelop Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: l.jirkov...@gmail.com Target Milestone: --- Created attachment 102016 --> https://bugs.kde.org/attachment.cgi?id=102016&action=edit perf record output If I click on an underlined identifier, the editor becomes unresponsive for several seconds. I noticed that when I navigate to the identifier in the editor using keyboard arrows, there is no slowdown and KDevelop is perfectly resnposive the whole time. This problem happens with a work-related project that can be considered somewhat peculiar. There are about 6000 includes in ~500 subdirectories in the include path. The project itself is only a small subset of sources - the problem occurs even with a small test project that consists only of a single file that includes only few of the includes, though it becomes worse with larger projects. The sources are mounted using samba from a locally running virtual machine. Attached is a profile generated using the linux perf utility with the following command: perf record -g -p sleep 3 which I executed just before clicking on a problem in the editor. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 --- Comment #2 from Lukas Jirkovsky --- The home directory is on a SSD, so the speed is decent. Also, I forgot to mention the versions: kdevplatform 6cf05bdad48f093dcf9efad4f78d8275ce44f7a6 kdevelop cbe05bc0d8218744cc30a0e0241f8c3f25497049 clang 3.9.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 371124] Frequent crash without apparent common cause, I have the reports from drmingw
https://bugs.kde.org/show_bug.cgi?id=371124 --- Comment #21 from María --- Yes, that's my same hang on saving problem, but I always work with large files (A3, A4 300dpi) and not always happen. Sometimes everything is perfect and sometimes it happens frequently (I usually save the work pressing the icon on the toolbar) In my case I think krita crash from 3.0 (not totally sure) but the hang on saving happen only in 3.0.1.90 and 3.0.91, so now I try not to save frecuently and when krita crash I rescue the autosaved (I have reduce the autosave time :) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372041] New: "Add Folders" attempts to import parent directory AND target dir.
https://bugs.kde.org/show_bug.cgi?id=372041 Bug ID: 372041 Summary: "Add Folders" attempts to import parent directory AND target dir. Product: digikam Version: 5.2.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: Import Assignee: digikam-de...@kde.org Reporter: watershe...@gmail.com Target Milestone: --- Created attachment 102017 --> https://bugs.kde.org/attachment.cgi?id=102017&action=edit Import dialog screenshot I am working on a prototype install of digiKam on Windows to show to my company. My album collection is located in a folder on the Desktop. I placed another folder of images on the Desktop and opened DK's "Add Folders" tool under the Import menu. I navigated to the folder I wanted imported, but DK by default also selected the parent (in this case C:\Users\library\Desktop). As seen in the attachment, the Directory field says '"Desktop" "target folder"', indicating that both will be imported. In addition, if I click other folders also on the Desktop, DK selects them all, instead of just the most recent click. If I want to deselect some I can ctrl-click them, but there's no way to deselect "Desktop" unless I navigate into a subfolder and then back out. Then, when I click my target folder, it is the only one that is selected. Importing both caused a full system crash, because Desktop contains the target folder, and both are being copied into a folder that also lives on the desktop. DigiKam started trying to copy my archive into the new subfolder within the archive, over and over, creating recursive subdirectories. I did a hard reboot and used robocopy (http://superuser.com/a/1048242) to delete the new subdirectory. Now I know how to avoid this problem, but it could easily happen to others. I have a feeling the problem may be specific to the Windows version of DK. Thanks for your work on digiKam! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 Sven Brauch changed: What|Removed |Added CC||m...@svenbrauch.de --- Comment #1 from Sven Brauch --- Is your home directory on a network share? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372038] git master - Custom project folder location won't change from root directory " / " [video included]
https://bugs.kde.org/show_bug.cgi?id=372038 --- Comment #1 from Jesse --- UPDATE 1: Running from Terminal produces this when trying to change custom project folder directory QObject::connect: No such slot KdenliveDoc::slotMoveFinished(KJob *) QObject::connect: No such slot KdenliveDoc::slotMoveProgress(KJob *, unsigned long) -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 371269] No (obvious) way to end or restart a private conversation
https://bugs.kde.org/show_bug.cgi?id=371269 --- Comment #6 from Pali Rohár --- But not main window. Window in which you are writing conversation... Window where is your active OTR. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 360170] Failed with error while ripping DVD (may be encrypted DVD)
https://bugs.kde.org/show_bug.cgi?id=360170 --- Comment #16 from Matthias --- yeah, 4 years no updates, so is this a surprise..? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 372039] New: window position on screen after opening
https://bugs.kde.org/show_bug.cgi?id=372039 Bug ID: 372039 Summary: window position on screen after opening Product: kde Version: unspecified Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mikah...@gmx.de Target Milestone: --- I noticed since 2 - 3 weeks that intermittent the top area of a window, I mean the bar with the symbols to hide, maximize and close, is located outside the upper edge of the visible screen. This happens when the program / window has just been started. It is also not possible to reach this outer area with the mouse. The only possibilities are to close the program / window with the right-click on the taskbar or to grab the window with the mouse and pull it down in the visible area of the screen. The error occurs with the debian / siduction versions of amd64 and i386. Both distributions have the current dist-upgrades installed. The issue is intermittent and not reproducible. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372038] git master - Custom project folder location won't change from root directory " / " [video included]
https://bugs.kde.org/show_bug.cgi?id=372038 Jesse changed: What|Removed |Added URL||https://youtu.be/BbBVQIgEYG ||0 CC||jesse.dub...@gmail.com Severity|normal |major -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372038] New: git master - Custom project folder location won't change from root directory " / " [video included]
https://bugs.kde.org/show_bug.cgi?id=372038 Bug ID: 372038 Summary: git master - Custom project folder location won't change from root directory " / " [video included] Product: kdenlive Version: git-master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: jesse.dub...@gmail.com Target Milestone: --- See video link in URL field for example. Project folder for proxy clips, thumbnails and render preview files won't change from / directory on older projects (created about a week ago). Steps to reproduce: 1. Open project 2. Go do top menu > Project > Project Settings 3. With "Custom Project Folder" enabled, click on the folder icon and change the folder to any other destination (kdenlive folder in home, Dropbox folder, etc.) 4. Click OK Actual results: Nothing changes. Going back into Project Settings folder shows it's back to root / Expected results: for the current custom project folder to change. Bug discovered while using Kdenlive 16.11.70 git master build from ppa:kdenlive/kdenlive-master, Ubuntu 16.10 w/ Unity 7.5.0 desktop environment, KDE Frameworks 5.26.0, Qt 5.6.1. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 358984] Saving changes inode number of hard linked files
https://bugs.kde.org/show_bug.cgi?id=358984 Thomas Fischer changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Latest Commit|5884726b8fd4e218b800a47b1be |http://commits.kde.org/kbib |9fb78a4e9d538 |tex/b72743cd7532e167751f0d2 ||788c8509301ae5515 Resolution|WAITINGFORINFO |FIXED --- Comment #3 from Thomas Fischer --- Git commit b72743cd7532e167751f0d2788c8509301ae5515 by Thomas Fischer. Committed on 03/11/2016 at 20:25. Pushed by thomasfischer into branch 'kbibtex/0.7'. Refactoring writing files This patch addresses issues when writing bibliography files, as it gets apparent when writing a file with multiple hard links. The changes introduced with this commit include: - When writing to local files, no temporary file is used. Instead, the target file gets directly overwritten. If the local filename is a symbolic link, the real file the symbolic link points to will get overwritten. Backup files' names will be based on the symbolic links' names, not the real files' names. For remote files, a local temporary file is used to write data to before uploading this temporary file to its target location. - In case of errors, a message box may get shown. If the bibliography exporter added text to an error log, a special message box listing those error messages will be shown. M +73 -45 src/parts/part.cpp http://commits.kde.org/kbibtex/b72743cd7532e167751f0d2788c8509301ae5515 -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 371269] No (obvious) way to end or restart a private conversation
https://bugs.kde.org/show_bug.cgi?id=371269 --- Comment #5 from Tristan Miller --- OK, I have attached a screenshot. The Settings->Configure Toolbars dialog does not list any OTR-related actions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371704] LNF Scripting contextmenu config not always works
https://bugs.kde.org/show_bug.cgi?id=371704 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/plas ||ma-workspace/b9760e852042fb ||113caef8ad547967b98cfdd32a --- Comment #5 from David Edmundson --- Git commit b9760e852042fb113caef8ad547967b98cfdd32a by David Edmundson. Committed on 03/11/2016 at 20:24. Pushed by davidedmundson into branch 'Plasma/5.8'. Introduce new pre-layout script hook Summary: layout.js used to be run before any containments were added. This was broken in a697d291 which creates desktop containments for that activity first. However, some scripts rely on being able to alter global configuration before any containments are loaded. In order to allow the same functionality we need to provide a new hook for whatever these scripts may need to do. Test Plan: Not done yet. Reviewers: #plasma, mart Reviewed By: mart Subscribers: apol, mart, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D3220 M +25 -1shell/shellcorona.cpp http://commits.kde.org/plasma-workspace/b9760e852042fb113caef8ad547967b98cfdd32a -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 371269] No (obvious) way to end or restart a private conversation
https://bugs.kde.org/show_bug.cgi?id=371269 --- Comment #4 from Tristan Miller --- Created attachment 102015 --> https://bugs.kde.org/attachment.cgi?id=102015&action=edit Screenshot of Kopete 1.10.1 showing no Tools menu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372037] New: Right clicking background in desktop grid causes glitching
https://bugs.kde.org/show_bug.cgi?id=372037 Bug ID: 372037 Summary: Right clicking background in desktop grid causes glitching Product: kwin Version: 5.8.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: pbs3...@googlemail.com Target Milestone: --- Created attachment 102014 --> https://bugs.kde.org/attachment.cgi?id=102014&action=edit Screenshot of glitching Steps to reproduce: • Activate the desktop grid. • Right-click on any part of a desktop not covered by a window. What goes wrong: • For every desktop except the one that was right-clicked, the desktop background is presented like just another window. • Floating x-buttons randomly appear on some of the desktops. • See the attached screenshot. • Kwin becomes extremely laggy until the desktop grid is closed. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 371269] No (obvious) way to end or restart a private conversation
https://bugs.kde.org/show_bug.cgi?id=371269 --- Comment #3 from Pali Rohár --- Looks very strange. Please provide screenshot, I really cannot believe that there is no Conversation or Format or Tools menu... Also via Settings you should be able to configure toolbars and add here OTR icon (if you do not have it already). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 372036] New: Missing GCompris translations
https://bugs.kde.org/show_bug.cgi?id=372036 Bug ID: 372036 Summary: Missing GCompris translations Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: alvare...@kde.org CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- I've install gcompris-qt, but no translations files are installed. -- You are receiving this mail because: You are watching all bug changes.
