[kmail2] [Bug 396074] New: kmail does not remember folder list columns setting
https://bugs.kde.org/show_bug.cgi?id=396074 Bug ID: 396074 Summary: kmail does not remember folder list columns setting Product: kmail2 Version: 5.7.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: b...@valdyas.org Target Milestone: --- Every time I start kmail, it defaults back to the separate columns settings for unread/total/size. Kmail should remember that setting. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 388261] App icons should respect active icon theme
https://bugs.kde.org/show_bug.cgi?id=388261 --- Comment #22 from PK --- Created attachment 113696 --> https://bugs.kde.org/attachment.cgi?id=113696&action=edit discover uses stange icon for kolourpaint Discover now respects my installed and preferred icon theme! Great! Only, for the appliction KolourPaint discover chooses an icon that is not in my preferred theme. I did "locate kolourpaint.svg" and I found the icon that Discover uses in the folder /usr/share/icons/hycolor. So I renamed that folder, deleted the cache, rebooted and still discover uses this icon. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 395916] Playing a video in a web browser does not inhibit lock screen
https://bugs.kde.org/show_bug.cgi?id=395916 Kai Uwe Broulik changed: What|Removed |Added Product|plasmashell |Falkon Target Milestone|1.0 |--- Assignee|plasma-b...@kde.org |now...@gmail.com CC||k...@privat.broulik.de Component|generic-wayland |extensions Version|5.13.2 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396005] Breeze Dark widgets do not honour color scheme
https://bugs.kde.org/show_bug.cgi?id=396005 Kai Uwe Broulik changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- That's by design. There's "Breeze" which follows the color schemes, "Breeze Light" which is always light and "Breeze Dark" which is always dark. Use "Breeze" and set a dark color scheme. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396011] Dragging icons doesn't work most of the time
https://bugs.kde.org/show_bug.cgi?id=396011 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #2 from Kai Uwe Broulik --- Looks like a Qt bug and affects all places using Qml and drag and drop, e.g. dragging a file from Dolphin to the wallpaper dialog also shows the same erratic changing between accepted and denied cursor -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 388082] ktp-text-ui does not scroll automatically
https://bugs.kde.org/show_bug.cgi?id=388082 Krzysztof Nowicki changed: What|Removed |Added CC||kri...@op.pl --- Comment #9 from Krzysztof Nowicki --- Same here on KDE Apps 17.12.3 and Qt 5.11.0 (Gentoo). For me this started to appear after upgrading Qt from 5.9 to 5.11. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396059] Slideshow Wallpaper cause FPS drops in OpenGL applications
https://bugs.kde.org/show_bug.cgi?id=396059 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de Component|Desktop Containment |Image Wallpaper Assignee|se...@kde.org |notm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395618] Text glitching when moving file or folder on desktop w/ font rendering on subpixel hinting RGB and moderate
https://bugs.kde.org/show_bug.cgi?id=395618 --- Comment #4 from GreenBarbers --- (In reply to Nate Graham from comment #3) > GreenBarbers, what distro and what Qt versions are you using? If you;re able > to upgrade, could you confirm whether or not it happens with Plasma 5.13 or > Qt 5.10 or Qt 5.11? Hello Nate, I've just updated my system and the bug it's still persistent Currently using: -KDE Plasma 5.13.2 -Qt 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 376340] QtCurve style configure dialog crashes
https://bugs.kde.org/show_bug.cgi?id=376340 Antonio Rojas changed: What|Removed |Added CC||szuru.b...@hotmail.com --- Comment #32 from Antonio Rojas --- *** Bug 396073 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396073] System Settings crashes on launching QtCurve config
https://bugs.kde.org/show_bug.cgi?id=396073 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 376340 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395875] ImageEditor window is blank when opened a second time
https://bugs.kde.org/show_bug.cgi?id=395875 --- Comment #21 from Maik Qualmann --- There actually seems to be a problem with Qt-5.11. Other programs will also lose Menubar, Tollbar or Statusbar, such as KMail or VirtualBox. I was able to reproduce this again with the digiKam main window, when processes are still running in the background and the window was closed. https://bugreports.qt.io/browse/QTBUG-66800 https://bugreports.qt.io/browse/QTBUG-67426 Maik -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 395651] CMakeLists.txt MOZILLA_DIR hard coded /lib/mozilla
https://bugs.kde.org/show_bug.cgi?id=395651 --- Comment #11 from Chris --- (In reply to Fabian Vogt from comment #10) > It's not possible to do it in a way which works everywhere. Why is that? My suggestion make virtually every aspect of this variable user configurable except for the 'mozzila' part. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 396043] Percentage sign is doubled when language is set to Polish
https://bugs.kde.org/show_bug.cgi?id=396043 Burkhard Lueck changed: What|Removed |Added Version|5.13.2 |unspecified Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 Product|ksysguard |i18n Assignee|ksysguard-b...@kde.org |kdei18n-pl-uw...@lists.sour ||ceforge.net Component|ksysguard |pl CC||lu...@hube-lueck.de --- Comment #1 from Burkhard Lueck --- This is a wrong translation in locale pl: l10n-kf5/pl/messages/kde-workspace/ksysguard.po:209:msgid "CPU: %1%" l10n-kf5/pl/messages/kde-workspace/ksysguard.po-210-msgstr "Procesor: %1%%" -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 395947] Using pam_kwallet5.so breaks pam_mkhomedir.so
https://bugs.kde.org/show_bug.cgi?id=395947 Fabian Vogt changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #5 from Fabian Vogt --- It's not fixed - that commit is not in 5.12.x. @aacid: Any reason in particular it was only submitted for 5.13? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 396035] Error Object below the minimum elevation line
https://bugs.kde.org/show_bug.cgi?id=396035 Jasem Mutlaq changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 396072] Guiding timing out
https://bugs.kde.org/show_bug.cgi?id=396072 --- Comment #1 from Jasem Mutlaq --- It's issues with your mount. What mount are you using? Enable INDI+Guide logging in Ekos and then attach the log. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 396058] Final line in an account may not be real balance
https://bugs.kde.org/show_bug.cgi?id=396058 --- Comment #1 from Stephane MANKOWSKI --- Hi, Your operation view is sorted by date + onather column. This is why you have this strange behavior. Click on the column 'balance' to set the sort on date only, so compliant with balances. Regards. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [radeonsi/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 --- Comment #2 from Shmerl --- (In reply to Martin Flöser from comment #1) > Please try to get a backtrace from KWin. What is a good way to attach debugger to it before it crashes? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [radeonsi/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 Martin Flöser changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Martin Flöser --- Please try to get a backtrace from KWin. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 344802] disInstr(arm): unhandled instruction: 0xEC510F1E
https://bugs.kde.org/show_bug.cgi?id=344802 Austin English changed: What|Removed |Added CC||austinengl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 344802] disInstr(arm): unhandled instruction: 0xEC510F1E
https://bugs.kde.org/show_bug.cgi?id=344802 John Reiser changed: What|Removed |Added Attachment #101694|0 |1 is obsolete|| --- Comment #17 from John Reiser --- Created attachment 113695 --> https://bugs.kde.org/attachment.cgi?id=113695&action=edit patch to read timer tick registers on arm32, arm64 native for both arm32 and arm64 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395995] Notifications Messed up?
https://bugs.kde.org/show_bug.cgi?id=395995 --- Comment #3 from wolfyrion --- Two screenshots with 4 monitors and notifications messed https://i.imgur.com/mYNIcIl.jpg https://i.imgur.com/Lso3AAx.jpg -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 346619] MTP IOSlave should use f_bsize for block size
https://bugs.kde.org/show_bug.cgi?id=346619 Nate Graham changed: What|Removed |Added Severity|minor |wishlist Version|4.14.1 |5.47.0 Product|kio |frameworks-kio Summary|dolphin uses small blocks |MTP IOSlave should use |(4096 bytes) for|f_bsize for block size |copying/moving operations | Component|file|general CC||kdelibs-b...@kde.org --- Comment #3 from Nate Graham --- Thanks for the update! So the slowness of not respecting f_bsize manifested when you used Dolphin to move or copy a file (via copy-paste or drag-and-drop) to a local mount for an MTP device? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396073] New: System Settings crashes on launching QtCurve config
https://bugs.kde.org/show_bug.cgi?id=396073 Bug ID: 396073 Summary: System Settings crashes on launching QtCurve config Product: systemsettings Version: 5.13.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: szuru.b...@hotmail.com Target Milestone: --- Application: systemsettings5 (5.13.2) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.3-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Changed Widget style in Application Style settings to QtCurve. The package I have is qtcurve-kde. It happens on several independent PCs. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe50847c840 (LWP 9349))] Thread 6 (Thread 0x7fe4d8c51700 (LWP 9356)): #0 0x7fe503aa4ea9 in poll () from /usr/lib/libc.so.6 #1 0x7fe4fcd2a523 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fe4fcd2a63e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fe5043c1054 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fe50436c94c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fe5041b5a99 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fe501ead9c9 in ?? () from /usr/lib/libQt5Qml.so.5 #7 0x7fe5041bfb45 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7fe4ff38c075 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fe503aaf53f in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7fe4e0ba8700 (LWP 9355)): #0 0x7fe503aa4ea9 in poll () from /usr/lib/libc.so.6 #1 0x7fe4fcd2a523 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fe4fcd2a63e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fe5043c1054 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fe50436c94c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fe5041b5a99 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fe501ead9c9 in ?? () from /usr/lib/libQt5Qml.so.5 #7 0x7fe5041bfb45 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7fe4ff38c075 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fe503aaf53f in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7fe4e3ebe700 (LWP 9353)): #0 0x7fe4ff391ffc in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fe4e8dbe124 in ?? () from /usr/lib/dri/i965_dri.so #2 0x7fe4e8dbde18 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7fe4ff38c075 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fe503aaf53f in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7fe4eba0a700 (LWP 9352)): #0 0x7fe503aa0934 in read () from /usr/lib/libc.so.6 #1 0x7fe4fcd6fed1 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fe4fcd29ff8 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7fe4fcd2a4c6 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7fe4fcd2a63e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7fe5043c1054 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7fe50436c94c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7fe5041b5a99 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x7fe504811976 in ?? () from /usr/lib/libQt5DBus.so.5 #9 0x7fe5041bfb45 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7fe4ff38c075 in start_thread () from /usr/lib/libpthread.so.0 #11 0x7fe503aaf53f in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7fe4f4d53700 (LWP 9351)): #0 0x7fe503aa4ea9 in poll () from /usr/lib/libc.so.6 #1 0x7fe4fef50180 in ?? () from /usr/lib/libxcb.so.1 #2 0x7fe4fef51e4b in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7fe4f74d722a in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7fe5041bfb45 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fe4ff38c075 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fe503aaf53f in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7fe50847c840 (LWP 9349)): [KCrash Handler] #6 0x7fe5039ed86b in raise () from /usr/lib/libc.so.6 #7 0x7fe5039d840e in abort () from /usr/lib/libc.so.6 #8 0x7fe503dfc44a in __gnu_cxx::__verbose_terminate_handler () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/vterminate.cc:95 #9 0x7fe503e029d6 in __cxxabiv1::__terminate(void (*)()) () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:47 #10 0x7fe503e02a13 in std::terminate () at /build/gcc/src/gcc/libstdc++-
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 --- Comment #21 from Brennan Kinney --- (In reply to Nate Graham from comment #20) > Thanks for the additional information, Brennan. However, as previously > noted, high memory usage of the sort described by you and others in this > ticket is not considered a bug because: > 1. it's only done when there's actually unused memory available > 2. Okular should give it up when the system is under memory pressure > 3. you can change the memory caching aggressiveness in the settings if this > sort of thing unnerves you > > If you're seeing that any of the above conditions are not working properly, > please file a new bug report to track that issue. Thanks! Nate, it's not just caching, there is an obvious leak/growth, a 90kb PDF of 4 pages, 30MB on open, steadily rising memory usage by scrolling repeatedly through the pages up/down. This growth only stops once the scrolling does, and will resume again by scrolling. The cache is not being used, memory is just being allocated for the content again, and again, instead of reused or freed(until the mentioned memory pressure). I could continue that process for the same file and bring the memory usage up for the single document from the 60MB I got it to 1GB or 10GB without issue from the looks of it. That's not good behaviour, even if it is freed at a later point, the application shouldn't balloon memory like that pointlessly. If others think that is appropriate, it's a bit of a worry. Don't claim it as working as intended when it's clearly poor memory handling. It's ok to admit that this behaviour is happening and that it is not correct, but not see any value or importance in investing time to correct it, just don't pretend that it's allocating hundreds to thousands of MB in memory for small documents from scrolling pages when that growth is constant and does not stop, Okular is not using that memory in it's entirerity, it's not an optimization, it's a bug. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 396067] Update Button Absent
https://bugs.kde.org/show_bug.cgi?id=396067 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- Does the issue disappear if you resize the window at all in any direction? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396059] Slideshow Wallpaper cause FPS drops in OpenGL applications
https://bugs.kde.org/show_bug.cgi?id=396059 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 396054] "Konsole" name on tab label should be user choice.
https://bugs.kde.org/show_bug.cgi?id=396054 Nate Graham changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- It is a user choice: 1. The tab title is determined by your profile and can be adjusted using Settings > Edit Current Profile > Tabs 2. Right-click on the tab and choose "Rename Tab..." For future reference, see https://community.kde.org/Get_Involved/Bug_Reporting#Step_1:_Make_sure_it.27s_a_real_bug -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 396039] Password is displayed in plain text on one screen, but shown as dots (asterisks, whatever) on second screen
https://bugs.kde.org/show_bug.cgi?id=396039 Nate Graham changed: What|Removed |Added CC||n...@kde.org Component|general |breeze-theme --- Comment #2 from Nate Graham --- Yikes, that's bad. FWIW, SDDM is the login manager; kscreenlocker is the lock screen. So you're using KDE Plasma 5.12? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 396042] Imported photo Date Modified value has +9 hour offset
https://bugs.kde.org/show_bug.cgi?id=396042 Nate Graham changed: What|Removed |Added Version|18.04.2 |5.47.0 Product|dolphin |frameworks-kio Assignee|dolphin-bugs-n...@kde.org |fa...@kde.org CC||kdelibs-b...@kde.org, ||n...@kde.org Component|panels: information |general Summary|Imported photo Modified |Imported photo Date |Date has +9 hour offset |Modified value has +9 hour ||offset --- Comment #1 from Nate Graham --- Thanks, this information all comes from KIO; sending it there. By any chance, is your timezone UTC+9? If so, that's probably the source of the +9 hour offset. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 344802] disInstr(arm): unhandled instruction: 0xEC510F1E
https://bugs.kde.org/show_bug.cgi?id=344802
--- Comment #16 from John Reiser ---
(In reply to Matt Cowell from comment #13)
> Created attachment 101694 [details]
> Add decode for CNTVCT, CNTPCT, and CNTFRQ
Today the patch now lives at https://bugsfiles.kde.org/attachment.cgi?id=101694
and does apply, with offsets:
$ patch -p1 <344802-101694.patch
patching file VEX/priv/guest_arm_defs.h
Hunk #1 succeeded at 350 (offset 112 lines).
patching file VEX/priv/guest_arm_helpers.c
Hunk #1 succeeded at 1445 (offset 258 lines).
patching file VEX/priv/guest_arm_toIR.c
Hunk #1 succeeded at 18755 (offset 1500 lines).
Hunk #2 succeeded at 23277 (offset 1548 lines).
However the patch does not compile on arm64(aarch64):
priv/guest_arm_helpers.c: In function ‘arm_dirtyhelper_MRRS_CNTVCT’:
priv/guest_arm_helpers.c:1458:4: error: invalid 'asm': invalid operand prefix
'%Q'
__asm__ __volatile__("mrrc p15, 1, %Q0, %R0, c14" : "=r"(w));
^~~
priv/guest_arm_helpers.c:1458:4: error: invalid 'asm': incompatible floating
point / vector register operand for '%R'
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 396062] Show Virtual keyboard and keyboard layout indicator on the login screen
https://bugs.kde.org/show_bug.cgi?id=396062 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 396006] Can't attach tabs unless single process mode is used
https://bugs.kde.org/show_bug.cgi?id=396006 --- Comment #3 from Nate Graham --- Attaching/detaching tabs works for me with both single and multi process mode with Konsole from git master--including when I restart after changing the setting. :) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 396071] plasma5 screen management going wrong
https://bugs.kde.org/show_bug.cgi?id=396071 bugreporte...@gmail.com changed: What|Removed |Added CC||bugreporte...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 396072] New: Guiding timing out
https://bugs.kde.org/show_bug.cgi?id=396072 Bug ID: 396072 Summary: Guiding timing out Product: kstars Version: 2.9.6 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: nloo...@gmail.com Target Milestone: --- While trying out the guiding module, if i press "Guide" it gives me the following message: 2018-07-02T03:25:35 GUIDE_RA: Scope cannot reach the start point after 35 iterations. Possible mount or backlash problems... 2018-07-02T03:22:56 RA drifting reverse... 2018-07-02T03:22:25 RA drifting forward... 2018-07-02T03:22:25 Calibration started. Guiding does not seem to start. What does this error mean and how do i fix it? -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 396070] ksplashqml core dumps after recent update
https://bugs.kde.org/show_bug.cgi?id=396070 bugreporte...@gmail.com changed: What|Removed |Added CC||bugreporte...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 396071] New: plasma5 screen management going wrong
https://bugs.kde.org/show_bug.cgi?id=396071 Bug ID: 396071 Summary: plasma5 screen management going wrong Product: KScreen Version: 5.13.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: se...@kde.org Reporter: bugreporte...@gmail.com Target Milestone: --- With the most recent update of KDE, screen management is acting up. I have a desktop with 3 monitors. Expected behavior: If no hardware has changed, I should be able to log into KDE and the layout of everything remains as it was when I last logged out. The arrangement of the 3 monitors in particular should be the same (left, middle, right). Actual behavior: Each time I log in, the arrangement of the 3 monitors has changed. For example, the middle monitor becomes the left monitor. The desktop wallpapers get mixed up, and sometimes the panel placement gets mixed up too. In more detail, here are some things I have observed: 1. I get a popup asking me about laptop display options. I'm on a desktop, not a laptop. Furthermore, the options presented are confusing. None the selections I have picked have actually worked, and neither has doing nothing. I do not want this dialog every time I log in when my attached screens have not changed. More importantly, I do not want my settings lost on each login. 2. As stated, the arrangement of my screens has changed (e.g., the screen that should be in the middle is arranged on the left or right, etc.) 3. the primary display may have changed too. Other settings may be lost or changed too, such as the locations and settings of my panels. That appears to be a consequence of the screen arrangement being screwed up. As far as I can tell, this started with plasmashell 5.13.2. This computer, running the same hardware with Arch and KDE has worked correctly for the last 2 years until this recent update. Here are my versions: Linux 4.17.3-1-ARCH #1 SMP PREEMPT Tue Jun 26 04:42:36 UTC 2018 x86_64 GNU/Linux plasmashell 5.13.2 dolphin 18.04.2 kate 18.04.2 QMake version 3.1 Using Qt version 5.11.1 in /usr/lib My monitors are: left: DELL U3415W Expected Geometry: 3440x1440+0+0 middle: ELL U3415W Expected Geometry: 3440x1440+3440+0 right: Acer K272HUL Expected Geometry: 2560x1440+6880+0 I am in touch with a friend running KDe on a laptop with 2 external monitors and they are experiencing what sounds like the same issue. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 396035] Error Object below the minimum elevation line
https://bugs.kde.org/show_bug.cgi?id=396035 --- Comment #2 from Niels Looije --- You were right, the date on the autostar was wrong. Setting the right date and time fixed this problem -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 396006] Can't attach tabs unless single process mode is used
https://bugs.kde.org/show_bug.cgi?id=396006 --- Comment #2 from Christoph Feck --- Nate, if this works for you, you probably have not restarted Konsole :) To transfer a tab between separate processes, I guess Konsole has to be completely redesigned. Similar to recent work in Web browsers to use separate processes for each tab. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 396070] New: ksplashqml core dumps after recent update
https://bugs.kde.org/show_bug.cgi?id=396070 Bug ID: 396070 Summary: ksplashqml core dumps after recent update Product: ksplash Version: 5.13.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bugreporte...@gmail.com Target Milestone: --- I"m seeing this stack trace in the journal after each login starting a few days ago. I'm running Arch Linux KDE with an nvidia GPU. Jul 01 20:37:03 systemd-coredump[1490]: Process 1421 (ksplashqml) of user 1000 dumped core. Stack trace of thread 1430: #0 0x7f230f06086b raise (libc.so.6) #1 0x7f230f04b40e abort (libc.so.6) #2 0x7f230f0a28b8 __libc_message (libc.so.6) #3 0x7f230f0a8d4a malloc_printerr (libc.so.6) #4 0x7f230f0aa7e4 _int_free (libc.so.6) #5 0x7f23102e2153 n/a (libQt5Gui.so.5) #6 0x7f23102e0fc5 n/a (libQt5Gui.so.5) #7 0x7f23102b19fb n/a (libQt5Gui.so.5) #8 0x7f23102b209e _ZN20QOpenGLShaderProgram4linkEv (libQt5Gui.so.5) #9 0x7f231110b596 _ZN23QSGDefaultRenderContext13compileShaderEP17QSGMaterialShaderP11QSGMaterialPKcS5_ (libQ> #10 0x7f23110d8c96 n/a (libQt5Quick.so.5) #11 0x7f23110d96b1 _ZN16QSGBatchRenderer8Renderer17renderMergedBatchEPKNS_5BatchE (libQt5Quick.so.5) #12 0x7f23110daa66 _ZN16QSGBatchRenderer8Renderer13renderBatchesEv (libQt5Quick.so.5) #13 0x7f23110e0103 _ZN16QSGBatchRenderer8Renderer6renderEv (libQt5Quick.so.5) #14 0x7f23110d04ee _ZN11QSGRenderer11renderSceneERK11QSGBindable (libQt5Quick.so.5) #15 0x7f23110d09bc _ZN11QSGRenderer11renderSceneEj (libQt5Quick.so.5) #16 0x7f231110b030 _ZN23QSGDefaultRenderContext15renderNextFrameEP11QSGRendererj (libQt5Quick.so.5) #17 0x7f231116edb5 _ZN19QQuickWindowPrivate16renderSceneGraphERK5QSize (libQt5Quick.so.5) #18 0x7f2338a0 n/a (libQt5Quick.so.5) #19 0x7f237658 n/a (libQt5Quick.so.5) #20 0x7f230f832b45 n/a (libQt5Core.so.5) #21 0x7f230bb83075 start_thread (libpthread.so.0) #22 0x7f230f12253f __clone (libc.so.6) Stack trace of thread 1443: #0 0x7f230f11d0f9 syscall (libc.so.6) #1 0x7f22fe96df00 n/a (libGLX_nvidia.so.0) #2 0x7f22fe9473ba n/a (libGLX_nvidia.so.0) #3 0x7f2307bd987c glXGetProcAddress (libGLX.so.0) #4 0x7f22ff05f4bd n/a (libqxcb-glx-integration.so) #5 0x7f23102a1b5d _ZN23QOpenGLExtensionMatcherC1Ev (libQt5Gui.so.5) #6 0x7f23102a49fd n/a (libQt5Gui.so.5) #7 0x7f23102a62f5 _ZNK16QOpenGLFunctions16hasOpenGLFeatureENS_13OpenGLFeatureE (libQt5Gui.so.5) #8 0x7f23110e95e4 _ZN30QSGOpaqueTextureMaterialShader11updateStateERKN17QSGMaterialShader11RenderStateEP11QS> #9 0x7f23110d9784 _ZN16QSGBatchRenderer8Renderer17renderMergedBatchEPKNS_5BatchE (libQt5Quick.so.5) #10 0x7f23110daa66 _ZN16QSGBatchRenderer8Renderer13renderBatchesEv (libQt5Quick.so.5) #11 0x7f23110e0103 _ZN16QSGBatchRenderer8Renderer6renderEv (libQt5Quick.so.5) #12 0x7f23110d04ee _ZN11QSGRenderer11renderSceneERK11QSGBindable (libQt5Quick.so.5) #13 0x7f23110d09bc _ZN11QSGRenderer11renderSceneEj (libQt5Quick.so.5) #14 0x7f231110b030 _ZN23QSGDefaultRenderContext15renderNextFrameEP11QSGRendererj (libQt5Quick.so.5) #15 0x7f231116edb5 _ZN19QQuickWindowPrivate16renderSceneGraphERK5QSize (libQt5Quick.so.5) #16 0x7f2338a0 n/a (libQt5Quick.so.5) #17 0x7f237658 n/a (libQt5Quick.so.5) #18 0x7f230f832b45 n/a (libQt5Core.so.5) #19 0x7f230bb83075 start_thread (libpthread.so.0) #20 0x7f230f12253f __clone (libc.so.6) Stack trace of thread 1446: #0 0x7f230f12f83b __lll_lock_wait_private (libc.so.6) #1 0x7f230f0aa8d6 _int_free (libc.so.6) #2 0x7f23110d8da0 n/a (libQt5Quick.so.5) #3 0x7f23110d96b1 _ZN16QSGBatchRenderer8Renderer17renderMergedBatchEPKNS_5BatchE (libQt5Quick.so.5) #4 0x7f23110daa66 _ZN16QSGBatchRenderer8Renderer13renderBatchesEv (libQt5Quick.so.5) #5 0x7f23110e0103 _ZN16QSGBatchRenderer8Renderer6renderEv (libQt5Quick.so.5) #6 0x7f23110d04ee _ZN11QSGRenderer11renderSceneERK11QSGBindable (libQt5Quick.so.5) #7 0x7f23110d09bc _ZN11QSGRenderer11renderSceneEj (libQt5Quick.so.5) #8 0x7f231110b030 _ZN23QSGDefaultRenderContext15renderNextFrameEP11QSGRendererj (libQt5Quick.so.5) #9 0x7f231116edb5 _ZN19QQuickWindowPrivate16renderSceneGraphERK5QSize (libQt5Quick.so.5) #10 0x7f2338a0 n/a (libQt5Quick.so.5) #11 0x7f237658 n/a (libQt5Quick.so.5) #12 0x7f230f832b45 n/a (libQt5Core.so.5) #13 0x7f230bb83075 start_thread (libpthread.so.0) #14 0x7f230f12253f __clone (libc.so.6) Stack trace of thread 1423: #0 0x7f230f117ea9 __poll (libc.so.6) #1 0x7f230994d523 n/a (libglib-2.0.so.0) #2 0x7f230994d63e g_main_context_iteration (libglib-2.0.so.0) #3 0x7f230fa34039 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop
[akregator] [Bug 394738] Akregator doesn't save hidden columns in feed list after updating to Qt 5.11
https://bugs.kde.org/show_bug.cgi?id=394738 Christoph Feck changed: What|Removed |Added Resolution|--- |UPSTREAM Status|CONFIRMED |RESOLVED --- Comment #6 from Christoph Feck --- Since there are no changes im Akregator, let's assume it was a Qt regression. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 396061] [GitStable][Nvidia-384] ksmserver crashes after proprietary nvidia driver is turned on/driver is changed in NVIDIA X Sever Settings.
https://bugs.kde.org/show_bug.cgi?id=396061 Christoph Feck changed: What|Removed |Added Flags|Backport-, Brainstorm-, | |corner_case-, | |Translation_missing-, | |Usability+ | Status|CONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #3 from Christoph Feck --- Please don't: - confirm your own bugs, unless you investigated the root of the issue, - set flags that you don't know what they do If this issue is still reproducible after a reboot, please ask for help in a forum of your distribution to find a suitable NVIDIA driver for your kernel. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 395515] lua proramms: breaking long strings by \z results in uglifying following text ( all red and underelined as if a syntax error )
https://bugs.kde.org/show_bug.cgi?id=395515 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395995] Notifications Messed up?
https://bugs.kde.org/show_bug.cgi?id=395995 Nate Graham changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Nate Graham --- Please get back to us with the information that David requested. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 Nate Graham changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 Nate Graham changed: What|Removed |Added Resolution|FIXED |INVALID -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #20 from Nate Graham --- Thanks for the additional information, Brennan. However, as previously noted, high memory usage of the sort described by you and others in this ticket is not considered a bug because: 1. it's only done when there's actually unused memory available 2. Okular should give it up when the system is under memory pressure 3. you can change the memory caching aggressiveness in the settings if this sort of thing unnerves you If you're seeing that any of the above conditions are not working properly, please file a new bug report to track that issue. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395618] Text glitching when moving file or folder on desktop w/ font rendering on subpixel hinting RGB and moderate
https://bugs.kde.org/show_bug.cgi?id=395618 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #3 from Nate Graham --- GreenBarbers, what distro and what Qt versions are you using? If you;re able to upgrade, could you confirm whether or not it happens with Plasma 5.13 or Qt 5.10 or Qt 5.11? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 396019] Folding layer 1 not possible when layer 2 yet folded
https://bugs.kde.org/show_bug.cgi?id=396019 Nate Graham changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||n...@kde.org --- Comment #1 from Nate Graham --- Missing the attachment? -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 396017] Load display no longer available
https://bugs.kde.org/show_bug.cgi?id=396017 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED --- Comment #1 from Nate Graham --- KDE 4 has not been supported since October of 2015. I recommend upgrading your distro so that you get KDE Plasma 5. :) -- You are receiving this mail because: You are watching all bug changes.
[kxkb] [Bug 396013] Keyboard layout limit of 8 is too low
https://bugs.kde.org/show_bug.cgi?id=396013 Nate Graham changed: What|Removed |Added CC||h...@kde.org, n...@kde.org --- Comment #1 from Nate Graham --- Makes sense to me. Eike, is this something that will be resolved with your GSoC student's work? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396011] Dragging icons doesn't work most of the time
https://bugs.kde.org/show_bug.cgi?id=396011 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #1 from Nate Graham --- Not able to reproduce with git master on Neon. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396008] Dolphin does not remember the scroll position when maximize/unmaximize the window
https://bugs.kde.org/show_bug.cgi?id=396008 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Component|general |view-engine: general CC||n...@kde.org Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 396006] Can't attach tabs unless single process mode is used
https://bugs.kde.org/show_bug.cgi?id=396006 Nate Graham changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- Works for me without using single process mode. Can you verify that switching that setting (and only that setting) on and off triggers and fixes the bug? -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 396027] start fails due to "Config Error: Unable to open file /usr/local/bin/kf5-frameworks-build-include which was included from line 44"
https://bugs.kde.org/show_bug.cgi?id=396027 --- Comment #1 from Michael Pyne --- I get the impression that kdesrc-build is trying to refer to a base configuration file that is normally present within the kdesrc-build source directory. If so the fix would likely be to have kdesrc-build-setup to use the same separate path for where the installed data would go, aside from $PREFIX/bin. Would it be possible to attach the kdesrc-buildrc (or .kdesrc-buildrc) that was generated by kdesrc-build-setup? Also are you running kdesrc-build as root, or as an unprivileged user? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 396006] Can't attach tabs unless single process mode is used
https://bugs.kde.org/show_bug.cgi?id=396006 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396005] Breeze Dark widgets do not honour color scheme
https://bugs.kde.org/show_bug.cgi?id=396005 Nate Graham changed: What|Removed |Added Product|Breeze |plasmashell Target Milestone|--- |1.0 Assignee|plasma-b...@kde.org |visual-des...@kde.org CC||n...@kde.org, ||plasma-b...@kde.org Component|general |Theme - Breeze -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 396069] New: plasma-discover Crash on Startup
https://bugs.kde.org/show_bug.cgi?id=396069 Bug ID: 396069 Summary: plasma-discover Crash on Startup Product: Discover Version: 5.13.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: tste...@protonmail.com Target Milestone: --- Application: plasma-discover (5.13.2) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.3-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I just installed packagekit-qt5 and flatpak, and now whenever I start discover it crashes. Discover launches fine without either package (but is obviously useless since no packages are found), and works fine with just flatpak. If just package-qt5 is installed it crashes (though there is already a bug report filed for this). As a side note, I am running Obarun which is based on Arch, and build flatpak from source. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6dbd421780 (LWP 5835))] Thread 23 (Thread 0x7f6d3b56b700 (LWP 9225)): #0 0x7f6db898bea9 in poll () at /usr/lib/libc.so.6 #1 0x7f6db30c6523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6db30c663e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6d89e22d7f in () at /usr/lib/libostree-1.so.1 #4 0x7f6db30eea2a in () at /usr/lib/libglib-2.0.so.0 #5 0x7f6db5075075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f6db899653f in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7f6d5effd700 (LWP 9222)): #0 0x7f6db898bea9 in poll () at /usr/lib/libc.so.6 #1 0x7f6db30c6523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6db30c663e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6d89e22d7f in () at /usr/lib/libostree-1.so.1 #4 0x7f6db30eea2a in () at /usr/lib/libglib-2.0.so.0 #5 0x7f6db5075075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f6db899653f in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7f6d70d40700 (LWP 9221)): #0 0x7f6db898bea9 in poll () at /usr/lib/libc.so.6 #1 0x7f6db30c6523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6db30c663e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6d89e22d7f in () at /usr/lib/libostree-1.so.1 #4 0x7f6db30eea2a in () at /usr/lib/libglib-2.0.so.0 #5 0x7f6db5075075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f6db899653f in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7f6d5d7fa700 (LWP 9166)): #0 0x7f6db89910f9 in syscall () at /usr/lib/libc.so.6 #1 0x7f6db310d52d in g_cond_wait_until () at /usr/lib/libglib-2.0.so.0 #2 0x7f6db3098903 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f6db30ef436 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f6db30eea2a in () at /usr/lib/libglib-2.0.so.0 #5 0x7f6db5075075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f6db899653f in clone () at /usr/lib/libc.so.6 Thread 19 (Thread 0x7f6d3bd6c700 (LWP 9164)): #0 0x7f6db89910f9 in syscall () at /usr/lib/libc.so.6 #1 0x7f6db310d52d in g_cond_wait_until () at /usr/lib/libglib-2.0.so.0 #2 0x7f6db3098903 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f6db30ef436 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f6db30eea2a in () at /usr/lib/libglib-2.0.so.0 #5 0x7f6db5075075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f6db899653f in clone () at /usr/lib/libc.so.6 Thread 18 (Thread 0x7f6d733d3700 (LWP 9163)): #0 0x7f6db89910f9 in syscall () at /usr/lib/libc.so.6 #1 0x7f6db310d52d in g_cond_wait_until () at /usr/lib/libglib-2.0.so.0 #2 0x7f6db3098903 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f6db30ef436 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f6db30eea2a in () at /usr/lib/libglib-2.0.so.0 #5 0x7f6db5075075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f6db899653f in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7f6d3a569700 (LWP 9162)): #0 0x7f6db89910f9 in syscall () at /usr/lib/libc.so.6 #1 0x7f6db310d52d in g_cond_wait_until () at /usr/lib/libglib-2.0.so.0 #2 0x7f6db3098903 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f6db30ef436 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f6db30eea2a in () at /usr/lib/libglib-2.0.so.0 #5 0x7f6db5075075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f6db899653f in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f6d5dffb700 (LWP 9160)): #0 0x7f6db898bea9 in poll () at /usr/lib/libc.so.6 #1 0x7f6db30c6523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6db30
[kdevelop] [Bug 374068] There is no user / password management for git
https://bugs.kde.org/show_bug.cgi?id=374068 boospy changed: What|Removed |Added CC||li...@osit.cc --- Comment #1 from boospy --- Is this fixed? If i would like to push, that is not possible, not asking for user and password. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 396068] New: Make qml-module-qt-labs-platform a build dependency
https://bugs.kde.org/show_bug.cgi?id=396068 Bug ID: 396068 Summary: Make qml-module-qt-labs-platform a build dependency Product: elisa Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: n...@kde.org Target Milestone: --- If you build Elisa from source but don't have qml-module-qt-labs-platform installed from something else, Elisa won't launch: $ elisa [...] QQmlApplicationEngine failed to load component qrc:/qml/ElisaMainWindow.qml:259 Type ContentView unavailable qrc:/qml/ContentView.qml:427 Type MediaPlayListView unavailable qrc:/qml/MediaPlayListView.qml:26 module "Qt.labs.platform" is not installed Now technically it's a runtime dependency and not a build dependency, but it would be nice if this dependency were expressed in CMakeLists.txt so that build-from-source users would get all the requisite dependencies. Or if that's not the right way to express runtime dependencies for build-from-source users... it would be nice if whatever right way to do it may be got done. :) -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 395947] Using pam_kwallet5.so breaks pam_mkhomedir.so
https://bugs.kde.org/show_bug.cgi?id=395947 Bernard Gray changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 395947] Using pam_kwallet5.so breaks pam_mkhomedir.so
https://bugs.kde.org/show_bug.cgi?id=395947 --- Comment #4 from Bernard Gray --- (In reply to Fabian Vogt from comment #3) > This should be fixed in pam_kwallet 5.13.0 - not sure why it wasn't added to > Plasma/5.12. > > Can you build pam_kwallet with > https://cgit.kde.org/kwallet-pam.git/commit/ > ?id=06760eed821f5383d03dc83a9a077a377ba39541 to confirm that it's fixed or > try pam_kwallet 5.13.x? Should be relatively easy, pam_kwallet has no > dependencies on other parts of Plasma. Hi Fabian, Thanks for this tidbit - I did give it a test last week with this patch, and it has resolved the issue. My apologies for the slow reply! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393723] Kwin master with bad blur effect on secondary monitor ( works perfectly on primary )
https://bugs.kde.org/show_bug.cgi?id=393723 Kamil Piwowarski <9luty1...@gmail.com> changed: What|Removed |Added CC||9luty1...@gmail.com --- Comment #14 from Kamil Piwowarski <9luty1...@gmail.com> --- *** Bug 396055 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396055] Multiscreen Wayland: Blur effect broken
https://bugs.kde.org/show_bug.cgi?id=396055 Kamil Piwowarski <9luty1...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #14 from Kamil Piwowarski <9luty1...@gmail.com> --- I am so stupid ;/ Sorry for wasting your time. Everything is ok. Some months ago I've testing multiscreen setup and I've created backup of `/usr/lib64/libkwin4_effect_builtins.so.1` --> `/usr/lib64/libkwin4_effect_builtins.so.1.bak`. When testing I've changed symlink from `/usr/lib64/libkwin4_effect_builtins.so.1.0.0` to point `/usr/lib64/libkwin4_effect_builtins.so.1.bak`. During updates symlinks didn't changed. So I was using old file libkwin4_effect_builtins.so and that was a problem. *** This bug has been marked as a duplicate of bug 393723 *** -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 395627] CMAKE_{PREFIX,MODULE}_PATH not set at all
https://bugs.kde.org/show_bug.cgi?id=395627 Michael Pyne changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kde ||src-build/7f92da7b307c784de ||ec804f65137b10733e6a88e Resolution|--- |FIXED Version Fixed In||18.08 --- Comment #4 from Michael Pyne --- Git commit 7f92da7b307c784deec804f65137b10733e6a88e by Michael Pyne. Committed on 01/07/2018 at 23:15. Pushed by mpyne into branch 'master'. Don't double-set CMAKE_PREFIX_PATH if set by user. This fixes bug 395627, where the error is actually that we set CMAKE_PREFIX_PATH twice if qtdir is set to a non-system path and the user is also setting CMAKE_PREFIX_PATH. Unfortunately the second value overrides the first (the one the user set). Also added a test for this, which fails before the fix and passes afterwards. The full test suite (all 5...) pass. FIXED-IN:18.08 M +5-2modules/ksb/BuildSystem/KDE4.pm A +78 -0t/bug-395627-keep-cmake-prefix.t A +26 -0t/data/bug-395627/kdesrc-buildrc https://commits.kde.org/kdesrc-build/7f92da7b307c784deec804f65137b10733e6a88e -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 396067] Update Button Absent
https://bugs.kde.org/show_bug.cgi?id=396067 David Brown changed: What|Removed |Added CC||djv...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 396067] New: Update Button Absent
https://bugs.kde.org/show_bug.cgi?id=396067 Bug ID: 396067 Summary: Update Button Absent Product: Discover Version: 5.13.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: djv...@hotmail.com Target Milestone: --- Created attachment 113694 --> https://bugs.kde.org/attachment.cgi?id=113694&action=edit Update activity missing update button, garbled text in upper right corner. See screenshot. The "Update" or "Update All" button is missing from the update activity and there is some non-clickable mangled text in the upper right corner. This problem persists using a variety of themes and application style settings, and does not change whether the window is maximized or floating. I saw a previous bug report where this problem occurred only when more than one update was selected, but it doesn't seem to make any difference in my case. I only tag this as a "major" bug because it completely prevents me from installing any updates through Discover. I haven't done it yet, but I expect the only workaround will be to uninstall and then reinstall to get the updated packages. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 394738] Akregator doesn't save hidden columns in feed list after updating to Qt 5.11
https://bugs.kde.org/show_bug.cgi?id=394738 --- Comment #5 from wincak --- Looks fixed here too now with KDE Plasma 5.13.2, Qt 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 395988] KMainWindow saves invalid window/widget state under Qt 5.11.1
https://bugs.kde.org/show_bug.cgi?id=395988 --- Comment #10 from Max --- (In reply to Max from comment #0) I apologize i wrote something wrong here: > Above commit changed things so window close event gets handled by child > widgets sooner... widgets get destroyed (and hidden) before > QApplication::saveStateRequest triggers KMainWindow::saveState(). > KMainWindow::saveMainWindowSettings() then calls > QStatusBar/QMenuBar::isHidden() (which will return true) and updates rc file. Widgets get destroyed (and hidden) before KMainWindow::saveMainWindowSettings() gets triggered. Also it doesn't get trigerred by QApplication::saveStateRequest in this case. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 395988] KMainWindow saves invalid window/widget state under Qt 5.11.1
https://bugs.kde.org/show_bug.cgi?id=395988 --- Comment #9 from Max --- Created attachment 113693 --> https://bugs.kde.org/attachment.cgi?id=113693&action=edit Simple app to reproduce the problem - Corrected Corrected the example app, statusbar, menubar and toolbar also break. SetupGUI() was supposed to be called after setting up all widgets, since that one restores settings from rc file. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 395939] Ark keeps destination path open after extraction, preventing removable storage unmount
https://bugs.kde.org/show_bug.cgi?id=395939 Elvis Angelaccio changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||18.07.80 Resolution|--- |FIXED Latest Commit||https://commits.kde.org/ark ||/36d6287503ad9d0879f97709cf ||fee60fdc24a651 --- Comment #1 from Elvis Angelaccio --- Git commit dbe7eba74931af83c7fef47e75422dc00d5ab567 by Elvis Angelaccio. Committed on 01/07/2018 at 21:49. Pushed by elvisangelaccio into branch 'master'. Add checks for expected working dir in the extraction tests After an extraction ends, the current working directory should be the same we started from. Otherwise Ark might prevent unmounting of removable devices. M +11 -0autotests/app/batchextracttest.cpp M +11 -0autotests/kerfuffle/extracttest.cpp https://commits.kde.org/ark/dbe7eba74931af83c7fef47e75422dc00d5ab567 --- Comment #2 from Elvis Angelaccio --- Git commit 478d2d71f861f51ca561282727bd876cfc622370 by Elvis Angelaccio. Committed on 01/07/2018 at 21:50. Pushed by elvisangelaccio into branch 'master'. libarchive: restore old working directory after extraction Otherwise Ark might prevent unmounting of removable devices. To simplify the logic in `extractFiles()`, we move the `QDir::setCurrent()` call as far as possible (which is before the huge while loop). M +21 -4plugins/libarchive/libarchiveplugin.cpp M +4-0plugins/libarchive/libarchiveplugin.h https://commits.kde.org/ark/478d2d71f861f51ca561282727bd876cfc622370 --- Comment #3 from Elvis Angelaccio --- Git commit 36d6287503ad9d0879f97709cffee60fdc24a651 by Elvis Angelaccio. Committed on 01/07/2018 at 22:14. Pushed by elvisangelaccio into branch 'master'. cliinterface: restore old working directory after extraction Otherwise Ark might prevent unmounting of removable devices. To fix this issue we only need to save the current working dir before the very first `QDir::setCurrent()` call in `extractFiles()`, and also to restore it at the end of every extraction. However, since `m_oldWorkingDir` is used also by copy and move jobs, we can't touch it from extract jobs, otherwise we'll break `movetest`. As workaround, we can use a new variable that will be used only by extract jobs. FIXED-IN: 18.07.80 M +17 -4kerfuffle/cliinterface.cpp M +3-1kerfuffle/cliinterface.h https://commits.kde.org/ark/36d6287503ad9d0879f97709cffee60fdc24a651 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 395939] Ark keeps destination path open after extraction, preventing removable storage unmount
https://bugs.kde.org/show_bug.cgi?id=395939 Elvis Angelaccio changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||18.07.80 Resolution|--- |FIXED Latest Commit||https://commits.kde.org/ark ||/36d6287503ad9d0879f97709cf ||fee60fdc24a651 --- Comment #1 from Elvis Angelaccio --- Git commit dbe7eba74931af83c7fef47e75422dc00d5ab567 by Elvis Angelaccio. Committed on 01/07/2018 at 21:49. Pushed by elvisangelaccio into branch 'master'. Add checks for expected working dir in the extraction tests After an extraction ends, the current working directory should be the same we started from. Otherwise Ark might prevent unmounting of removable devices. M +11 -0autotests/app/batchextracttest.cpp M +11 -0autotests/kerfuffle/extracttest.cpp https://commits.kde.org/ark/dbe7eba74931af83c7fef47e75422dc00d5ab567 --- Comment #2 from Elvis Angelaccio --- Git commit 478d2d71f861f51ca561282727bd876cfc622370 by Elvis Angelaccio. Committed on 01/07/2018 at 21:50. Pushed by elvisangelaccio into branch 'master'. libarchive: restore old working directory after extraction Otherwise Ark might prevent unmounting of removable devices. To simplify the logic in `extractFiles()`, we move the `QDir::setCurrent()` call as far as possible (which is before the huge while loop). M +21 -4plugins/libarchive/libarchiveplugin.cpp M +4-0plugins/libarchive/libarchiveplugin.h https://commits.kde.org/ark/478d2d71f861f51ca561282727bd876cfc622370 --- Comment #3 from Elvis Angelaccio --- Git commit 36d6287503ad9d0879f97709cffee60fdc24a651 by Elvis Angelaccio. Committed on 01/07/2018 at 22:14. Pushed by elvisangelaccio into branch 'master'. cliinterface: restore old working directory after extraction Otherwise Ark might prevent unmounting of removable devices. To fix this issue we only need to save the current working dir before the very first `QDir::setCurrent()` call in `extractFiles()`, and also to restore it at the end of every extraction. However, since `m_oldWorkingDir` is used also by copy and move jobs, we can't touch it from extract jobs, otherwise we'll break `movetest`. As workaround, we can use a new variable that will be used only by extract jobs. FIXED-IN: 18.07.80 M +17 -4kerfuffle/cliinterface.cpp M +3-1kerfuffle/cliinterface.h https://commits.kde.org/ark/36d6287503ad9d0879f97709cffee60fdc24a651 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 395939] Ark keeps destination path open after extraction, preventing removable storage unmount
https://bugs.kde.org/show_bug.cgi?id=395939 Elvis Angelaccio changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||18.07.80 Resolution|--- |FIXED Latest Commit||https://commits.kde.org/ark ||/36d6287503ad9d0879f97709cf ||fee60fdc24a651 --- Comment #1 from Elvis Angelaccio --- Git commit dbe7eba74931af83c7fef47e75422dc00d5ab567 by Elvis Angelaccio. Committed on 01/07/2018 at 21:49. Pushed by elvisangelaccio into branch 'master'. Add checks for expected working dir in the extraction tests After an extraction ends, the current working directory should be the same we started from. Otherwise Ark might prevent unmounting of removable devices. M +11 -0autotests/app/batchextracttest.cpp M +11 -0autotests/kerfuffle/extracttest.cpp https://commits.kde.org/ark/dbe7eba74931af83c7fef47e75422dc00d5ab567 --- Comment #2 from Elvis Angelaccio --- Git commit 478d2d71f861f51ca561282727bd876cfc622370 by Elvis Angelaccio. Committed on 01/07/2018 at 21:50. Pushed by elvisangelaccio into branch 'master'. libarchive: restore old working directory after extraction Otherwise Ark might prevent unmounting of removable devices. To simplify the logic in `extractFiles()`, we move the `QDir::setCurrent()` call as far as possible (which is before the huge while loop). M +21 -4plugins/libarchive/libarchiveplugin.cpp M +4-0plugins/libarchive/libarchiveplugin.h https://commits.kde.org/ark/478d2d71f861f51ca561282727bd876cfc622370 --- Comment #3 from Elvis Angelaccio --- Git commit 36d6287503ad9d0879f97709cffee60fdc24a651 by Elvis Angelaccio. Committed on 01/07/2018 at 22:14. Pushed by elvisangelaccio into branch 'master'. cliinterface: restore old working directory after extraction Otherwise Ark might prevent unmounting of removable devices. To fix this issue we only need to save the current working dir before the very first `QDir::setCurrent()` call in `extractFiles()`, and also to restore it at the end of every extraction. However, since `m_oldWorkingDir` is used also by copy and move jobs, we can't touch it from extract jobs, otherwise we'll break `movetest`. As workaround, we can use a new variable that will be used only by extract jobs. FIXED-IN: 18.07.80 M +17 -4kerfuffle/cliinterface.cpp M +3-1kerfuffle/cliinterface.h https://commits.kde.org/ark/36d6287503ad9d0879f97709cffee60fdc24a651 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396055] Multiscreen Wayland: Blur effect broken
https://bugs.kde.org/show_bug.cgi?id=396055 --- Comment #13 from Vlad Zagorodniy --- Created attachment 113692 --> https://bugs.kde.org/attachment.cgi?id=113692&action=edit Demo to my previous comment -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396055] Multiscreen Wayland: Blur effect broken
https://bugs.kde.org/show_bug.cgi?id=396055 Vlad Zagorodniy changed: What|Removed |Added Flags||Wayland+, X11- --- Comment #12 from Vlad Zagorodniy --- I think this bug is caused by const int yTranslate = effects->virtualScreenSize().height() - screen.height() - screen.y(); it essentially "pulls" screen content down. Still, I'm not sure why this bug is not reproducible when launching windowed kwin_wayland. Interesting. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] New: Wayland session is coring right after login [radeonsi/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 Bug ID: 396066 Summary: Wayland session is coring right after login [radeonsi/DisplayPort] Product: kwin Version: 5.13.1 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: shm...@mykolab.com Target Milestone: --- I just tried to use Wayland session with KDE Plasma 5.13.1 and it's coring right after login and falling back to sddm. That's what I see in dmesg: [ 176.359816] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:956 [ 176.814144] QThread[2620]: segfault at f ip 7f30f30b0e60 sp 7f30e506e4f0 error 4 in libwayland-client.so.0.3.0[7f30f30a9000+d000] Is it a Mesa problem of something with KWin? Current Debian testing x86_64, Plasma 5.13.1 pulled from unstable. GPU: AMD Vega 56, connected over DisplayPort. OpenGL renderer string: Radeon RX Vega (VEGA10, DRM 3.25.0, 4.17.0-trunk-amd64, LLVM 6.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.1.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395549] Some effects not doing anything but shows a status bar that stays forever rolling.
https://bugs.kde.org/show_bug.cgi?id=395549 --- Comment #8 from eugeneyale --- (In reply to Rafael from comment #7) > I switched from "American English" to "Español de españa" and tried "Ruido" > (Noise) again, with same results. No changes. Noise failed also for me in English or in French -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395549] Some effects not doing anything but shows a status bar that stays forever rolling.
https://bugs.kde.org/show_bug.cgi?id=395549 --- Comment #7 from Rafael --- I switched from "American English" to "Español de españa" and tried "Ruido" (Noise) again, with same results. No changes. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395549] Some effects not doing anything but shows a status bar that stays forever rolling.
https://bugs.kde.org/show_bug.cgi?id=395549 --- Comment #6 from eugeneyale --- (In reply to Vincent PINON from comment #5) > Hello, > Could you test the effects changing the Application language ? > (either from command "LANG=C kdenlive", or from "Help / Switch Application > Language"). > As Windows archive doesn't handle language very well yet, maybe it saves in > this case. I have already tried to change from french to English without any success But i tried again just now and I found that, when I search effect "Chroma" in French, it found 1 result : "divers"/"chromakey" (this effect fail) When I tried in English, it found 2 results "misc"/"chromakey" and this effect fail but also "alpha manipulation"/"Chroma key" (with space) and this effect is OK So I tried again in French, and the correct name of effect is "manipulation alpha"/couleur clé" and it works The effect "misc"/"chromakey" is failed even if a change the language -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396055] Multiscreen Wayland: Blur effect broken
https://bugs.kde.org/show_bug.cgi?id=396055 --- Comment #11 from Kamil Piwowarski <9luty1...@gmail.com> --- Created attachment 113691 --> https://bugs.kde.org/attachment.cgi?id=113691&action=edit aligned to the left Only bottom monitor is ok -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396065] New: Brush tools,vector tools, or any drawing tools won't work
https://bugs.kde.org/show_bug.cgi?id=396065 Bug ID: 396065 Summary: Brush tools,vector tools, or any drawing tools won't work Product: krita Version: 4.1.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tool/Assistants Assignee: krita-bugs-n...@kde.org Reporter: deeisabe...@gmail.com Target Milestone: --- I'll try using drawing tools, and though it says it's working on my layer, the lines or strokes wont show up on the screen; whether I use my tablet or not. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 379154] effect chroma key works the wrong way
https://bugs.kde.org/show_bug.cgi?id=379154 Vincent PINON changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396055] Multiscreen Wayland: Blur effect broken
https://bugs.kde.org/show_bug.cgi?id=396055 --- Comment #10 from Kamil Piwowarski <9luty1...@gmail.com> --- Created attachment 113690 --> https://bugs.kde.org/attachment.cgi?id=113690&action=edit wayland - vertically aligned to the top Another bug - on vertically stacked screens (aligned to the top). See screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395549] Some effects not doing anything but shows a status bar that stays forever rolling.
https://bugs.kde.org/show_bug.cgi?id=395549 --- Comment #5 from Vincent PINON --- Hello, Could you test the effects changing the Application language ? (either from command "LANG=C kdenlive", or from "Help / Switch Application Language"). As Windows archive doesn't handle language very well yet, maybe it saves in this case. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395865] Green Colour clip is only white
https://bugs.kde.org/show_bug.cgi?id=395865 Vincent PINON changed: What|Removed |Added Resolution|--- |UPSTREAM Status|CONFIRMED |RESOLVED --- Comment #7 from Vincent PINON --- The problem is in MLT 6.8.0, patched 5 days after release. Debian switched to a git snapshot (http://metadata.ftp-master.debian.org/changelogs/main/m/mlt/mlt_6.8.0+git20180605-1_changelog), ask your MLT packager to pick the patches... Hopefully MLT will release a bugfix soon? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388591] Rename malfunction
https://bugs.kde.org/show_bug.cgi?id=388591 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Version Fixed In|5.8.0 |6.0.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396041] Wrong rendering tab icons
https://bugs.kde.org/show_bug.cgi?id=396041 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388591] Rename malfunction
https://bugs.kde.org/show_bug.cgi?id=388591 --- Comment #4 from Maik Qualmann --- Git commit ef6a81ef2c63b31827a769f764f831716e70406d by Maik Qualmann. Committed on 01/07/2018 at 19:52. Pushed by mqualmann into branch 'master'. we do not need album refresh, initialize a re-sorting fixes the problem for everyone FIXED-IN: 6.0.0 M +1-0core/app/items/digikamimageview.cpp M +1-0core/app/views/tableview/tableview.cpp https://commits.kde.org/digikam/ef6a81ef2c63b31827a769f764f831716e70406d -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395477] regression: folder view widget in panel = file list popup is too tiny
https://bugs.kde.org/show_bug.cgi?id=395477 Emil Sedgh changed: What|Removed |Added CC||emilse...@kde.org --- Comment #11 from Emil Sedgh --- Can confirm on 5.13.1 on Debian. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396064] New: Restore defaults button resets to the previous saved setting and not the actual default settings
https://bugs.kde.org/show_bug.cgi?id=396064 Bug ID: 396064 Summary: Restore defaults button resets to the previous saved setting and not the actual default settings Product: krita Version: 4.1.0 beta Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: antti.s...@gmail.com Target Milestone: --- Video visualization: https://youtu.be/Z5ODitlqHU0 Steps to reproduce: Open settings Select 'Canvas Input Settings' Open 'Show Popup Palette' (I haven't tested any other setting) Add a shortcut and save Go back to that setting and Restore Defaults Delete the new binding and try Restore Defaults again Expected behavior: Only Right button should be left in the binding Actual behavior: The last saved setting gets restored Build & Platform: krita 4.2.0-pre-alpha Xubuntu 17.10 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396055] Multiscreen Wayland: Blur effect broken
https://bugs.kde.org/show_bug.cgi?id=396055 --- Comment #9 from Kamil Piwowarski <9luty1...@gmail.com> --- Created attachment 113689 --> https://bugs.kde.org/attachment.cgi?id=113689&action=edit kwin_wayland without plasma I was doing some testing and experiments and when I run kwin_wayland remotely by ssh `XDG_SESSION_ID=c2 QT_QPA_PLATFORM=wayland kwin_wayland --libinput --exit-with-session=konsole` it almost works as expected. Almost, because you can see "lines" between screens. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 396061] [GitStable][Nvidia-384] ksmserver crashes after proprietary nvidia driver is turned on/driver is changed in NVIDIA X Sever Settings.
https://bugs.kde.org/show_bug.cgi?id=396061 Jakub Strzelecki changed: What|Removed |Added Flags||corner_case- -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 396061] [GitStable][Nvidia-384] ksmserver crashes after proprietary nvidia driver is turned on/driver is changed in NVIDIA X Sever Settings.
https://bugs.kde.org/show_bug.cgi?id=396061 Jakub Strzelecki changed: What|Removed |Added CC||kuba...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 396061] [GitStable][Nvidia-384] ksmserver crashes after proprietary nvidia driver is turned on/driver is changed in NVIDIA X Sever Settings.
https://bugs.kde.org/show_bug.cgi?id=396061 Jakub Strzelecki changed: What|Removed |Added Flags||Backport-, Brainstorm-, ||Translation_missing-, ||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396063] New: Crash on boot
https://bugs.kde.org/show_bug.cgi?id=396063 Bug ID: 396063 Summary: Crash on boot Product: plasmashell Version: 5.13.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: k...@craigm.info CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.13.2) Qt Version: 5.11.0 Frameworks Version: 5.47.0 Operating System: Linux 4.13.0-45-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: - What I was doing when the application crashed: Booted computer with auto login. Once boot completed (and thus I was logged in looking at my desktop) there was a crash indicator. This might be related to another issue I have where boot often mostly compleates (shows my desktop pixture at least) then goes to black screens with just a mouse (I assume in that case the shell crashed but didn't restart). I think these issues might be caused by moving the mouse (perhaps hovering over something) at a particular time during boot. Booting usally seems to work if I leave it alone until its done. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7fc507e05940 (LWP 1520))] Thread 15 (Thread 0x7fc40164d700 (LWP 2244)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc5016225cb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x60ed620) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=this@entry=0x612a608, mutex=mutex@entry=0x612a600, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fc50569cafd in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x612a5f8) at scenegraph/qsgthreadedrenderloop.cpp:245 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x612a580) at scenegraph/qsgthreadedrenderloop.cpp:709 #5 0x7fc50569cf81 in QSGRenderThread::run (this=0x612a580) at scenegraph/qsgthreadedrenderloop.cpp:738 #6 0x7fc501621727 in QThreadPrivate::start (arg=0x612a580) at thread/qthread_unix.cpp:367 #7 0x7fc5004aa6ba in start_thread (arg=0x7fc40164d700) at pthread_create.c:333 #8 0x7fc500f2241d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7fc408972700 (LWP 2243)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc5016225cb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x5f33210) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=this@entry=0x5fa6db8, mutex=mutex@entry=0x5fa6db0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fc50569cafd in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x5fa6da8) at scenegraph/qsgthreadedrenderloop.cpp:245 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x5fa6d30) at scenegraph/qsgthreadedrenderloop.cpp:709 #5 0x7fc50569cf81 in QSGRenderThread::run (this=0x5fa6d30) at scenegraph/qsgthreadedrenderloop.cpp:738 #6 0x7fc501621727 in QThreadPrivate::start (arg=0x5fa6d30) at thread/qthread_unix.cpp:367 #7 0x7fc5004aa6ba in start_thread (arg=0x7fc408972700) at pthread_create.c:333 #8 0x7fc500f2241d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7fc40937a700 (LWP 2242)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc5016225cb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x3b9bec0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=this@entry=0x5150818, mutex=mutex@entry=0x5150810, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fc50569cafd in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x5150808) at scenegraph/qsgthreadedrenderloop.cpp:245 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x5150790) at scenegraph/qsgthreadedrenderloop.cpp:709 #5 0x7fc50569cf81 in QSGRenderThread::run (this=0x5150790) at scenegraph/qsgthreadedrenderloop.cpp:738 #6 0x7fc501621727 in QThreadPrivate::start (arg=0x5150790) at thread/qthread_unix.cpp:367 #7 0x7fc5004aa6ba in start_thread (arg=0x7fc40937a700) at pthread_create.c:333 #8 0x7fc500f2241d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7fc409f82700 (LWP 2234)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc5016225cb in QWaitConditionPrivate::
[kde] [Bug 395691] kdeinit crash at logon
https://bugs.kde.org/show_bug.cgi?id=395691 --- Comment #3 from Shmuel (Seymour J.) Metz --- (In reply to Ben Creasy from comment #1) > It doesn't seem like this provides enough information to debug. Was there a > stack trace? > > Is this an entirely default install? If so, did you try filing this with > openSUSE Tumbleweed? If so, can you link to that discussion? This was a normal install of Tumbledweed, followed by multiple runs of Yast and zipper dup. I've added the debug repository and installed the debug packages, so if it happens again I should get a good trace. I have not opened an incident with Novell, but can do so if you want me to. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396062] New: Show Virtual keyboard and keyboard layout indicator on the login screen
https://bugs.kde.org/show_bug.cgi?id=396062 Bug ID: 396062 Summary: Show Virtual keyboard and keyboard layout indicator on the login screen Product: plasmashell Version: 5.13.2 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mof...@tm2mail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Currently virtual keyboard and keyboard layout indicator are shown on the lock screen, but not on the login screen. I find it a bit inconsistent, it would be great to show these buttons/indicators on the login screen too. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 396061] [GitStable][Nvidia-384] ksmserver crashes after proprietary nvidia driver is turned on/driver is changed in NVIDIA X Sever Settings.
https://bugs.kde.org/show_bug.cgi?id=396061 --- Comment #2 from Jakub Strzelecki --- Discover also affected due to this bug: https://transfer.sh/JjHCw/plasma-discover.kcrash.txt -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 396061] [GitStable][Nvidia-384] ksmserver crashes after proprietary nvidia driver is turned on/driver is changed in NVIDIA X Sever Settings.
https://bugs.kde.org/show_bug.cgi?id=396061 Jakub Strzelecki changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED Keywords||reproducible --- Comment #1 from Jakub Strzelecki --- How to reproduce: 1.Get Nvidia Optimus laptop. 2.sudo ubuntu-drivers autoinstall && reboot 3.Launch nvidia x settings. 4.Switch to Nvidia driver. 5.The driver change requires(for some reason) to logout and login ,rebooting doesn't change the driver. 6.ksmserver crashed. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 396061] [GitStable][Nvidia-384] ksmserver crashes after proprietary nvidia driver is turned on/driver is changed in NVIDIA X Sever Settings.
https://bugs.kde.org/show_bug.cgi?id=396061 Jakub Strzelecki changed: What|Removed |Added Summary|[GitStable][Nvidia-384] |[GitStable][Nvidia-384] |ksmserver crashes after |ksmserver crashes after |proprietary nvidia driver |proprietary nvidia driver |is turned on in NVIDIA X|is turned on/driver is |Sever Settings. |changed in NVIDIA X Sever ||Settings. -- You are receiving this mail because: You are watching all bug changes.
