[okular] [Bug 391953] New: Cannot print multiple copies of the same page onto a single page
https://bugs.kde.org/show_bug.cgi?id=391953 Bug ID: 391953 Summary: Cannot print multiple copies of the same page onto a single page Product: okular Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: siauder...@hotmail.com Target Milestone: --- Hi, today I was trying to print 2 copies of a 1 page PDF onto a single sheet of paper. However, instead it printed 2 separate pages for me with the page only occupying the top half of the page. Subsequently I tried to print multiple copies of the same page to a single PDF so that I could then use it to print the same page twice on a single sheet of paper, but no matter how many times I tried, the generated PDF only contained 1 page (i.e. it refused to print the same page twice). It is unexpected behaviour that I cannot print multiple copies of the same page in a PDF onto a single page as Acrobat on Windows allows me to do this. Also, if we print multiple copies of the same page to another PDF the new PDF should contain multiple copies of the page and not just 1 copy. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 391410] Installed list is empty if selected immediately after discover is opened
https://bugs.kde.org/show_bug.cgi?id=391410 --- Comment #6 from tguen --- Installing `packagekit-qt5` fixed the issue. (It also now integrates pacman repos, which I have been wondering how to fix.) Should this be listed as a dependency? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 251235] Flash export tool does not install.
https://bugs.kde.org/show_bug.cgi?id=251235 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Flash export plugin does|Flash export tool does not |not install.|install. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 192165] Flash export tool does not auto-rotate portrait images.
https://bugs.kde.org/show_bug.cgi?id=192165 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Flash export plugin does|Flash export tool does not |not auto-rotate portrait|auto-rotate portrait |images. |images. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 126165] meta-bug for digikam editor tool release (digikam devels only)
https://bugs.kde.org/show_bug.cgi?id=126165 caulier.gil...@gmail.com changed: What|Removed |Added Summary|meta-bug for|meta-bug for digikam editor |digikamimageplugins-0.9.0-b |tool release (digikam |eta1 release (digikam |devels only) |devels only)| -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391786] kmymoney git 5.0 crashes on exit, even if no file loaded
https://bugs.kde.org/show_bug.cgi?id=391786 --- Comment #7 from NSLW --- (In reply to Jack from comment #6) > I have now recompiled for Debug, Release, and RelWithDebInfo with both gcc > 6.4.0 and 7.3.0, and can no longer reproduce the crash, so I'm just going to > close this as invalid. (would WORKSFORME be better?) I'll reopen only if I > can consistently reproduce the crash. > > I am assuming it was either something that got updated recently, or maybe > just a build or install dir that was not as clean as I thought. I think it's not completely invalid. We see that it depends on a compilation step. If my assumption is right, KMyMoney crashes if compiled with some optimizations. It would be good to know with which ones. I hope to get optimization issues solved by fixing defects reported by https://scan.coverity.com/projects/kmymoney?tab=overview and enabling more checks during the compilation. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 391952] New: Tips - white text on white background
https://bugs.kde.org/show_bug.cgi?id=391952 Bug ID: 391952 Summary: Tips - white text on white background Product: kde Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: laryo...@mail.tomsknet.ru Target Milestone: --- Can not read tips text. The text in the tips is printed in white on a white background. Therefore, it is impossible to read. If you change the style of the KDE, the problem disappears. But when you restart the program, the problem appears again. I observe this in the programs gimp and Libre Offfice Calc. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390958] plasmashell segfaulted when using classical application menu under wayland
https://bugs.kde.org/show_bug.cgi?id=390958 --- Comment #4 from sergei.cherni...@gmail.com --- I have got only one line: Application: Plasma (plasmashell), signal: Segmentation fault Do you know how I can get missing debug symbols? Or, may be someone else can help reproduce it to get useful backtrace? I have successfully reproduced it on another machine with the same setup - kubuntu 17.10 + kubuntu backports ppa -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391863] plasmashell gets in endless loop while screen is locked
https://bugs.kde.org/show_bug.cgi?id=391863 --- Comment #2 from A. Wilcox (awilfox) --- I said Plasma 5.12.2; that includes all the KDE Plasma packages. KF 5.43.0. Qt 5.9.3. Kernel 4.14.19. Mesa 17.3.1. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391778] FreeRDP second Full-Screen Monitor is hidden
https://bugs.kde.org/show_bug.cgi?id=391778 --- Comment #13 from Martin Flöser --- Thanks for the debug output. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391902] [r600g] kwin not starts with OpenGL ES on RV730
https://bugs.kde.org/show_bug.cgi?id=391902 --- Comment #4 from Martin Flöser --- (In reply to Eugene from comment #3) > I meant OpenGL ES would be better. Why? You have a desktop GPU, why would you want to use goes. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 Alexander Zhigalin changed: What|Removed |Added CC||alexan...@zhigalin.tk --- Comment #10 from Alexander Zhigalin --- (In reply to Christoph Feck from comment #8) > Revert from comment 7 is not a revert from the patch in comment #2. > > Unfortunately phabricator keeps the repository for a commit as a private > secret, so I cannot even comment on the relation between those commits. > > Anyway, if you are still affected with 5.7.0, then the commit from comment > #2 was not effective to resolve the issue. Yes it is. There was 2 patches, D8843 and D8844. The D8843 was reverted by https://phabricator.kde.org/R490:90c1d9af3e47c1591aab96cbc742b1c6d9367426 -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 382647] sendImages plugin is in Tools rather than Export category, so it doesn't show up in Gwenview's Share button that displays all the Export plugins
https://bugs.kde.org/show_bug.cgi?id=382647 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Product|digikam |kipiplugins Component|Export-Flash|general -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 288465] spelling-error in flashexport tool Unkown Unknown
https://bugs.kde.org/show_bug.cgi?id=288465 caulier.gil...@gmail.com changed: What|Removed |Added Summary|spelling-error-in-binary|spelling-error in |usr/lib/kde4/kipiplugin_fla |flashexport tool Unkown |shexport.so Unkown Unknown |Unknown -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 141389] Unpredictable image ordering in gallery.xml
https://bugs.kde.org/show_bug.cgi?id=141389 caulier.gil...@gmail.com changed: What|Removed |Added Product|kipiplugins |digikam Component|general |Export-Flash Version|0.1.6 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 118637] Flash export to simpleviewer format
https://bugs.kde.org/show_bug.cgi?id=118637 caulier.gil...@gmail.com changed: What|Removed |Added Product|kipiplugins |digikam Component|general |Export-Flash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 251235] Flash export plugin does not install.
https://bugs.kde.org/show_bug.cgi?id=251235 caulier.gil...@gmail.com changed: What|Removed |Added Product|kipiplugins |digikam Component|general |Export-Flash Version|1.4.0 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 171794] display keywords by flash export
https://bugs.kde.org/show_bug.cgi?id=171794 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Export-Flash Version|0.2.0 |unspecified Product|kipiplugins |digikam -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 232339] wrong flash export url (for SimpleViewer)
https://bugs.kde.org/show_bug.cgi?id=232339 caulier.gil...@gmail.com changed: What|Removed |Added Product|kipiplugins |digikam Component|general |Export-Flash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 288465] spelling-error-in-binary usr/lib/kde4/kipiplugin_flashexport.so Unkown Unknown
https://bugs.kde.org/show_bug.cgi?id=288465 caulier.gil...@gmail.com changed: What|Removed |Added Product|kipiplugins |digikam Component|general |Export-Flash Version|2.3.0 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 150393] SimpleView export - XML file is corrupted if exif comment contains a "<"
https://bugs.kde.org/show_bug.cgi?id=150393 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Export-Flash Product|kipiplugins |digikam -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 226296] flash export, unable to install simple viewer
https://bugs.kde.org/show_bug.cgi?id=226296 caulier.gil...@gmail.com changed: What|Removed |Added Version|1.1.0 |unspecified Component|general |Export-Flash Product|kipiplugins |digikam -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 168927] Add support for PostcardViewer, AutoViewer and TiltViewer
https://bugs.kde.org/show_bug.cgi?id=168927 caulier.gil...@gmail.com changed: What|Removed |Added Product|kipiplugins |digikam Component|general |Export-Flash Version|0.2.0 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 134298] simple viewer export: save settings / keep settings missing!
https://bugs.kde.org/show_bug.cgi?id=134298 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Export-Flash Product|kipiplugins |digikam -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 225401] Cannot export to Flash
https://bugs.kde.org/show_bug.cgi?id=225401 caulier.gil...@gmail.com changed: What|Removed |Added Version|1.1.0 |unspecified Component|general |Export-Flash Product|kipiplugins |digikam -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 279515] FlashExport's FirstRunDialog doesn't install simpleviewer's archive
https://bugs.kde.org/show_bug.cgi?id=279515 caulier.gil...@gmail.com changed: What|Removed |Added Version|2.1.0 |unspecified Component|general |Export-Flash Product|kipiplugins |digikam -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 134774] exported simpleviewer gallery fails to load images due to wrong xml file name.
https://bugs.kde.org/show_bug.cgi?id=134774 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Export-Flash Product|kipiplugins |digikam -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 277480] Export Flash dose not work
https://bugs.kde.org/show_bug.cgi?id=277480 caulier.gil...@gmail.com changed: What|Removed |Added Product|kipiplugins |digikam Component|general |Export-Flash Version|1.8.0 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 192165] Flash export plugin does not auto-rotate portrait images.
https://bugs.kde.org/show_bug.cgi?id=192165 caulier.gil...@gmail.com changed: What|Removed |Added Product|kipiplugins |digikam Component|general |Export-Flash Version|0.3.0 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 134299] simple viewer export: read orientation of image from EXIF
https://bugs.kde.org/show_bug.cgi?id=134299 caulier.gil...@gmail.com changed: What|Removed |Added Product|kipiplugins |digikam Component|general |Export-Flash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382647] sendImages plugin is in Tools rather than Export category, so it doesn't show up in Gwenview's Share button that displays all the Export plugins
https://bugs.kde.org/show_bug.cgi?id=382647 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Export-Flash Product|kipiplugins |digikam -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 305517] Segfaults after choosing Export - Export to Flash
https://bugs.kde.org/show_bug.cgi?id=305517 caulier.gil...@gmail.com changed: What|Removed |Added Version|2.5.0 |unspecified Component|general |Export-Flash Product|kipiplugins |digikam -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391951] New: plasmashell crash after 2018-03-15 update
https://bugs.kde.org/show_bug.cgi?id=391951 Bug ID: 391951 Summary: plasmashell crash after 2018-03-15 update Product: plasmashell Version: 5.12.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bna...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.3) Qt Version: 5.9.3 Frameworks Version: 5.44.0 Operating System: Linux 4.13.0-37-generic x86_64 Distribution: KDE neon LTS User Edition 5.12 -- Information about the crash: - Unusual behavior I noticed: plasmashell crash after 2018-03-15 update The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6a4365e900 (LWP 6518))] Thread 14 (Thread 0x7f695a1b1700 (LWP 6534)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6a3d42265b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f6a41195ebd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7f6a411967b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f6a3d421709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a3c2c86ba in start_thread (arg=0x7f695a1b1700) at pthread_create.c:333 #6 0x7f6a3cd3041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7f695adfd700 (LWP 6533)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6a3d42265b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f6a41195ebd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7f6a411967b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f6a3d421709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a3c2c86ba in start_thread (arg=0x7f695adfd700) at pthread_create.c:333 #6 0x7f6a3cd3041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7f695b7fe700 (LWP 6532)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6a3d42265b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f6a41195ebd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7f6a411967b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f6a3d421709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a3c2c86ba in start_thread (arg=0x7f695b7fe700) at pthread_create.c:333 #6 0x7f6a3cd3041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7f695bfff700 (LWP 6531)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6a3d42265b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f6a41195ebd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7f6a411967b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f6a3d421709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a3c2c86ba in start_thread (arg=0x7f695bfff700) at pthread_create.c:333 #6 0x7f6a3cd3041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7f6963e3d700 (LWP 6529)): #0 0x7f6a3cd2474d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f6a37b1338c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a37b1349c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a3d64b6cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6a3d5f3e2a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a3d41c8f4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f696631b517 in KCupsConnection::run() () from /usr/lib/x86_64-linux-gnu/libkcupslib.so #7 0x7f6a3d421709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6a3c2c86ba in start_thread (arg=0x7f6963e3d700) at pthread_create.c:333 #9 0x7f6a3cd3041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f697d02a700 (LWP 6526)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6a3d42265b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f6a
[choqok] [Bug 251164] Copy shortcut does not work
https://bugs.kde.org/show_bug.cgi?id=251164 Braxton Salyer changed: What|Removed |Added CC||braxtonsal...@gmail.com --- Comment #6 from Braxton Salyer --- I think this may currently be a design decision from the choqok team until the app gets ported to kirigami, as it clearly used to rely on kde4libs and simply has the relevant code commented out. That said, for some reason, this segfaults for me when I build from source BEFORE I make any changes, but I have come up with a possible? fix for this particular thing if someone else wants to try it out: in cmakelists.txt insert at line 60 KF5::ConfigGui in /libchoqok/ui/textbrowser.cpp insert at line 37 #include replace line 122 w/ copy->setShortcut( KStandardShortcut::copy().at(0) ); replace line 133 w/ selectAll->setShortcut( KStandardShortcut::selectAll().at(0) ); -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 385766] KTorrent crashed after exit from menu File->Quit and running App again.
https://bugs.kde.org/show_bug.cgi?id=385766 --- Comment #5 from gose...@gmail.com --- Created attachment 111456 --> https://bugs.kde.org/attachment.cgi?id=111456&action=edit New crash information added by DrKonqi ktorrent (5.1.0) using Qt 5.10.1 - What I was doing when the application crashed: Closing KTorrent with Ctrl-Q crashed the app after a few seconds. I'm on ArchLinux but I compiled KTorrent from sources with "-DCMAKE_BUILD_TYPE=RelWithDebInfo" to get a better trace. -- Backtrace (Reduced): #6 0x7f8ff91d2bcd in QVariant::QVariant(QString const&) () from /usr/lib/libQt5Core.so.5 #7 0x5605e65aa04d in kt::ViewModel::Item::data (this=0x5605e6c8a650, col=) at /home/german/kde/ktorrent/trunk/src/ktorrent-5.1.0/ktorrent/view/viewmodel.cpp:255 #8 0x5605e65abf7d in kt::ViewModel::data (this=, index=..., role=) at /home/german/kde/ktorrent/trunk/src/ktorrent-5.1.0/ktorrent/view/viewmodel.cpp:648 #9 0x7f8ffa18d941 in QStyledItemDelegate::initStyleOption(QStyleOptionViewItem*, QModelIndex const&) const () from /usr/lib/libQt5Widgets.so.5 #10 0x7f8ffa18ce17 in QStyledItemDelegate::sizeHint(QStyleOptionViewItem const&, QModelIndex const&) const () from /usr/lib/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 385766] KTorrent crashed after exit from menu File->Quit and running App again.
https://bugs.kde.org/show_bug.cgi?id=385766 gose...@gmail.com changed: What|Removed |Added CC||gose...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391950] New: KDE Settings standard hotkeys crashed on close
https://bugs.kde.org/show_bug.cgi?id=391950 Bug ID: 391950 Summary: KDE Settings standard hotkeys crashed on close Product: systemsettings Version: 5.10.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: grosser.meister.mo...@gmx.net Target Milestone: --- Application: systemsettings5 (5.10.5) Qt Version: 5.9.4 Frameworks Version: 5.42.0 Operating System: Linux 4.15.7-200.fc26.x86_64 x86_64 Distribution: "Fedora release 26 (Twenty Six)" -- Information about the crash: - What I was doing when the application crashed: I searched for a standard hotkey (then clicked around the other hotkey menues and clicked back to the still filtered standard hotkeys) and then closed the settings window. Then it crashed. -- Backtrace: Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc8f83b2300 (LWP 9017))] Thread 2 (Thread 0x7fc8e607e700 (LWP 9020)): #0 0x7fc901af2a5d in poll () at /lib64/libc.so.6 #1 0x7fc8faa5b579 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fc8faa5b68c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fc90291ad8b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fc9028c8aaa in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fc9027199aa in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fc903066659 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7fc90271dec2 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7fc8feb5c36d in start_thread () at /lib64/libpthread.so.0 #9 0x7fc901afeb4f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fc8f83b2300 (LWP 9017)): [KCrash Handler] #6 0x0031 in () #7 0x7fc8d7f6dfde in ProvidersModel::~ProvidersModel() () at /usr/lib64/qt5/plugins/kf5/urifilters/kurisearchfilter.so #8 0x7fc8d7f6e049 in ProvidersModel::~ProvidersModel() () at /usr/lib64/qt5/plugins/kf5/urifilters/kurisearchfilter.so #9 0x7fc9028f8e08 in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #10 0x7fc903e44594 in QWidget::~QWidget() () at /lib64/libQt5Widgets.so.5 #11 0x7fc9054e1cd1 in KCModule::~KCModule() () at /lib64/libKF5ConfigWidgets.so.5 #12 0x7fc8d7f7d707 in FilterOptions::~FilterOptions() () at /usr/lib64/qt5/plugins/kf5/urifilters/kurisearchfilter.so #13 0x7fc8d8397c4e in KURIFilterModule::~KURIFilterModule() () at /usr/lib64/qt5/plugins/kcm_webshortcuts.so #14 0x7fc8d8397c99 in KURIFilterModule::~KURIFilterModule() () at /usr/lib64/qt5/plugins/kcm_webshortcuts.so #15 0x7fc906432954 in KCModuleProxy::deleteClient() () at /lib64/libKF5KCMUtils.so.5 #16 0x7fc9064329ff in KCModuleProxy::~KCModuleProxy() () at /lib64/libKF5KCMUtils.so.5 #17 0x7fc906432bc9 in KCModuleProxy::~KCModuleProxy() () at /lib64/libKF5KCMUtils.so.5 #18 0x7fc9028f8e08 in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #19 0x7fc903e44594 in QWidget::~QWidget() () at /lib64/libQt5Widgets.so.5 #20 0x7fc903e447c9 in QWidget::~QWidget() () at /lib64/libQt5Widgets.so.5 #21 0x7fc9028f8e08 in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #22 0x7fc903e44594 in QWidget::~QWidget() () at /lib64/libQt5Widgets.so.5 #23 0x7fc903f9ed79 in QScrollArea::~QScrollArea() () at /lib64/libQt5Widgets.so.5 #24 0x7fc9028f8e08 in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #25 0x7fc903e44594 in QWidget::~QWidget() () at /lib64/libQt5Widgets.so.5 #26 0x7fc9043f64bd in KPageStackedWidget::~KPageStackedWidget() () at /lib64/libKF5WidgetsAddons.so.5 #27 0x7fc9028f8e08 in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #28 0x7fc903e44594 in QWidget::~QWidget() () at /lib64/libQt5Widgets.so.5 #29 0x7fc9043fa2b9 in KPageWidget::~KPageWidget() () at /lib64/libKF5WidgetsAddons.so.5 #30 0x7fc9028f8e08 in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #31 0x7fc903e44594 in QWidget::~QWidget() () at /lib64/libQt5Widgets.so.5 #32 0x7fc90666b909 in ModuleView::~ModuleView() () at /lib64/libsystemsettingsview.so.3 #33 0x7fc9028f8e08 in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #34 0x7fc903e44594 in QWidget::~QWidget() () at /lib64/libQt5Widgets.so.5 #35 0x7fc903fb4619 in QStackedWidget::~QStackedWidget() () at /lib64/libQt5Widgets.so.5 #36 0x7fc9028f8e08 in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #37 0x7fc903e44594 in QWidget::~QWidget() () at /lib64/libQt5Widgets.so.5 #38 0x7fc903fb4619 in QStackedWidget::~QStackedWidget() () at /lib64/libQt5Widgets.so.5
[kdenlive] [Bug 389624] Automatic scene split does not work in newer versions
https://bugs.kde.org/show_bug.cgi?id=389624 liamgl...@gmail.com changed: What|Removed |Added CC||liamgl...@gmail.com --- Comment #2 from liamgl...@gmail.com --- I can confirm that is not working on 17.12.3. I've tried with a lot of different files. It seems it's processing something (based on the progress bar and 50% of CPU usage) and, in the end, I get nothing. I tried all combinations of adding markers, cutting and save result with and without the clip in the timeline and same null result. -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 386256] Speed up loading of large data files
https://bugs.kde.org/show_bug.cgi?id=386256 --- Comment #4 from Milian Wolff --- commit 4edc10044f2743e067b0387d04518b94afd602e1 Author: Milian Wolff Date: Fri Mar 16 19:47:19 2018 +0100 Optionally use zstd for compression of heaptrack data files Zstandard is much faster compared to gzip, drastically improving both record and analysis performance of heaptrack in turn. Since Zstandard support is missing from upstream boost as of yet, this patch is introducing a copy of the zstd boost iostream code written by Reimar Döffinger and published at: https://github.com/rdoeffinger/iostreams/tree/zstd Many thanks to Reimar for enabling Zstandard support in heaptrack! Below are some performance numbers for compression and decompression of heaptrack data. The dramatic reduction in compression time significantly reduces the overhead imposed by heaptrack on your system while recording data. And the time saved while decompressing the data speeds up the analysis steps later on. Performance for compression of 224MB of raw heaptrack data: gzip: Performance counter stats for 'gzip -kf heaptrack.kmail.15607' (5 runs): 4869,759387 task-clock:u (msec) #0,996 CPUs utilized ( +- 0,70% ) 0 context-switches:u#0,000 K/sec 0 cpu-migrations:u #0,000 K/sec 112 page-faults:u #0,023 K/sec ( +- 0,52% ) 14.986.414.840 cycles:u #3,077 GHz ( +- 0,62% ) 21.816.226.253 instructions:u#1,46 insn per cycle ( +- 0,00% ) 4.022.016.531 branches:u# 825,917 M/sec ( +- 0,00% ) 157.529.308 branch-misses:u #3,92% of all branches ( +- 0,07% ) 4,890694017 seconds time elapsed ( +- 0,60% ) The size of the gzip compressed data file is 15807235 bytes. zstd: Performance counter stats for 'zstd -kf heaptrack.kmail.15607' (5 runs): 577,288680 task-clock:u (msec) #0,995 CPUs utilized ( +- 0,49% ) 0 context-switches:u#0,000 K/sec 0 cpu-migrations:u #0,000 K/sec 634 page-faults:u #0,001 M/sec ( +- 0,08% ) 1.626.811.592 cycles:u #2,818 GHz ( +- 0,37% ) 2.750.788.523 instructions:u#1,69 insn per cycle ( +- 0,00% ) 312.504.536 branches:u# 541,331 M/sec ( +- 0,00% ) 10.858.277 branch-misses:u #3,47% of all branches ( +- 0,08% ) 0,580079819 seconds time elapsed ( +- 0,67% ) The size of the zstd compressed data file is 16188988 bytes. Performance for parsing the data files with heaptrack_print, which requires two decompression passes: gzip: Performance counter stats for 'heaptrack_print heaptrack.kmail.15607.gz' (5 runs): 6180,813184 task-clock:u (msec) #0,998 CPUs utilized ( +- 0,76% ) 0 context-switches:u#0,000 K/sec 0 cpu-migrations:u #0,000 K/sec 20.111 page-faults:u #0,003 M/sec ( +- 0,00% ) 19.138.095.427 cycles:u #3,096 GHz ( +- 0,66% ) 36.417.197.208 instructions:u#1,90 insn per cycle ( +- 0,00% ) 7.683.651.885 branches:u# 1243,146 M/sec ( +- 0,00% ) 153.959.798 branch-misses:u #2,00% of all branches ( +- 1,24% ) 6,194282999 seconds time elapsed ( +- 0,71% ) zstd: Performance counter stats for 'heaptrack_print heaptrack.kmail.15607.zst' (5 runs): 4496,786684 task-clock:u (msec) #0,999 CPUs utilized ( +- 0,43% ) 0 context-switches:u#0,000 K/sec 0 cpu-migrations:u #0,000 K/sec 24.304 page-faults:u #0,005 M/sec ( +- 0,00% ) 13.944.273.234 cycles:u #3,101 GHz ( +- 0,40% ) 33.232.471.804 instructions:u#2,38 insn per cycle ( +- 0,00% ) 6.912.954.404 branches:u# 1537,310 M/sec ( +- 0,00% )
[Heaptrack] [Bug 386256] Speed up loading of large data files
https://bugs.kde.org/show_bug.cgi?id=386256 --- Comment #2 from Milian Wolff --- Git commit a189ad4d2aa09e7afcd47987bdc75537dd22d5d3 by Milian Wolff. Committed on 16/03/2018 at 23:51. Pushed by mwolff into branch 'master'. Optimize: only map trace indices for allocation infos Previously, we used to run the binary search to map a trace index to an allocation object on every (de)allocation. These events are occurring extremely often, of course - usually orders of magnitudes more often than the allocation info events. Now, we only map the trace index to an allocation when a new allocation info is parsed. This way, we don't need to run the slow binary search and can access the allocation object directly through the mapped index in the allocation index. For a large data file (~13GB uncompressed) the results are quite impressive: Before this patch, heaptrack_print took ca. 3min to parse the zstd compressed data. With this patch applied, we are down to 2min6s! Before: Performance counter stats for 'heaptrack_print heaptrack.Application.19285.zst': 178798,164042 task-clock:u (msec) #0,998 CPUs utilized 0 context-switches:u#0,000 K/sec 0 cpu-migrations:u #0,000 K/sec 30.570 page-faults:u #0,171 K/sec 551.902.999.436 cycles:u #3,087 GHz 1.540.185.452.300 instructions:u#2,79 insn per cycle 332.833.340.539 branches:u# 1861,503 M/sec 1.350.342.839 branch-misses:u #0,41% of all branches 179,193276255 seconds time elapsed After: Performance counter stats for 'heaptrack_print heaptrack.Application.19285.zst': 125579,754384 task-clock:u (msec) #0,999 CPUs utilized 0 context-switches:u#0,000 K/sec 0 cpu-migrations:u #0,000 K/sec 33.982 page-faults:u #0,271 K/sec 393.084.840.177 cycles:u #3,130 GHz 1.127.147.336.034 instructions:u#2,87 insn per cycle 238.225.815.121 branches:u# 1897,008 M/sec 998.456.200 branch-misses:u #0,42% of all branches 125,663808724 seconds time elapsed M +20 -10 src/analyze/accumulatedtracedata.cpp M +8-2src/analyze/accumulatedtracedata.h M +2-1src/analyze/gui/parser.cpp https://commits.kde.org/heaptrack/a189ad4d2aa09e7afcd47987bdc75537dd22d5d3 --- Comment #3 from Milian Wolff --- Git commit ef4a460cc69310618ec72cbaf284501bd19a6133 by Milian Wolff. Committed on 16/03/2018 at 23:50. Pushed by mwolff into branch 'master'. Optimize AccumulatedTraceData::findAllocation Instead of sorting the vector of Allocation objects which are 48byte large, introduce a separate sorted vector of pairs of TraceIndex and and AllocationIndex, both just 4 byte large. Lookup and insertion in the middle of this much smaller container is considerably faster, improving the heaptrack_print analysis time by ~10% in one of my larger test files (from ~3minutes down to 2min40s). M +20 -11 src/analyze/accumulatedtracedata.cpp M +3-0src/analyze/accumulatedtracedata.h M +5-0src/analyze/allocationdata.h https://commits.kde.org/heaptrack/ef4a460cc69310618ec72cbaf284501bd19a6133 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 391949] New: crash sys.monitor
https://bugs.kde.org/show_bug.cgi?id=391949 Bug ID: 391949 Summary: crash sys.monitor Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ger.sulta...@yandex.ru Target Milestone: --- Application: kdeinit5 (5.8.7) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.14.20-desktop-1.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: - What I was doing when the application crashed: - i was closed application after working long time Application: Системный монитор (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fef656c2800 (LWP 31616))] Thread 2 (Thread 0x7fef49118700 (LWP 31618)): #0 0x7fef63c78877 in read () at /lib64/libc.so.6 #1 0x7fef5f8d6073 in () at /usr/lib64/nvidia-current/tls/libnvidia-tls.so.384.111 #2 0x7fef608b8690 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #3 0x7fef6087479e in g_main_context_check () at /lib64/libglib-2.0.so.0 #4 0x7fef60874c38 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #5 0x7fef60874d9c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #6 0x7fef64207e2b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7fef641b349a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #8 0x7fef63fed3bc in QThread::exec() () at /lib64/libQt5Core.so.5 #9 0x7fef655e4635 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #10 0x7fef63ff1ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #11 0x7fef615c166d in start_thread () at /lib64/libpthread.so.0 #12 0x7fef63c88e0d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fef656c2800 (LWP 31616)): [KCrash Handler] #6 0x7fef64bc7bc0 in free_reply_list () at /lib64/libxcb.so.1 #7 0x7fef64bc98ec in _xcb_map_delete () at /lib64/libxcb.so.1 #8 0x7fef64bc81fd in _xcb_in_destroy () at /lib64/libxcb.so.1 #9 0x7fef64bc6535 in xcb_disconnect () at /lib64/libxcb.so.1 #10 0x7fef64dffc47 in XCloseDisplay () at /lib64/libX11.so.6 #11 0x7fef4dcd2ccf in QXcbConnection::~QXcbConnection() () at /lib64/libQt5XcbQpa.so.5 #12 0x7fef4dcd3049 in QXcbConnection::~QXcbConnection() () at /lib64/libQt5XcbQpa.so.5 #13 0x7fef4dcd47c6 in QXcbIntegration::~QXcbIntegration() () at /lib64/libQt5XcbQpa.so.5 #14 0x7fef4dcd48c9 in QXcbIntegration::~QXcbIntegration() () at /lib64/libQt5XcbQpa.so.5 #15 0x7fef644ee8a7 in QGuiApplicationPrivate::~QGuiApplicationPrivate() () at /lib64/libQt5Gui.so.5 #16 0x7fef62a68f69 in QApplicationPrivate::~QApplicationPrivate() () at /lib64/libQt5Widgets.so.5 #17 0x7fef641e798c in QObject::~QObject() () at /lib64/libQt5Core.so.5 #18 0x7fef641b6fd4 in QCoreApplication::~QCoreApplication() () at /lib64/libQt5Core.so.5 #19 0x7fef62a6a904 in QApplication::~QApplication() () at /lib64/libQt5Widgets.so.5 #20 0x7fef5a7e8a7f in kdemain () at /usr/lib64/libkdeinit5_ksysguard.so #21 0x0040818f in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) () #22 0x00409437 in handle_launcher_request(int, char const*) [clone .isra.26] () #23 0x00409bd6 in handle_requests(int) () #24 0x00404dd3 in main () -- Backtrace: Application: Системный монитор (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fef656c2800 (LWP 31616))] Thread 2 (Thread 0x7fef49118700 (LWP 31618)): #0 0x7fef63c78877 in read () at /lib64/libc.so.6 #1 0x7fef5f8d6073 in () at /usr/lib64/nvidia-current/tls/libnvidia-tls.so.384.111 #2 0x7fef608b8690 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #3 0x7fef6087479e in g_main_context_check () at /lib64/libglib-2.0.so.0 #4 0x7fef60874c38 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #5 0x7fef60874d9c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #6 0x7fef64207e2b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7fef641b349a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #8 0x7fef63fed3bc in QThread::exec() () at /lib64/libQt5Core.so.5 #9 0x7fef655e4635 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #10 0x7fef63ff1ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #11 0x7fef615c166d in start_thread () at /lib64/libpthread.so.0 #12 0x7fef63c88e0d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fef656c2800 (LWP 31616)): [KCrash Handler] #6 0x7fef64bc7bc0 in free_reply_list () at /lib64/libxcb.so.1 #7
[kded-appmenu] [Bug 391813] App menu window decoration has an excessively long delay before opening submenus on mouse hover
https://bugs.kde.org/show_bug.cgi?id=391813 --- Comment #8 from ghavami...@hotmail.com --- Yes it's same in doplhin menu system. -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 391813] App menu window decoration has an excessively long delay before opening submenus on mouse hover
https://bugs.kde.org/show_bug.cgi?id=391813 --- Comment #7 from David Edmundson --- Can you confirm it's the same with dolphin context menus so I can recategorise this more appropriately? -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 391813] App menu window decoration has an excessively long delay before opening submenus on mouse hover
https://bugs.kde.org/show_bug.cgi?id=391813 --- Comment #6 from ghavami...@hotmail.com --- I see you're point, accidentally opening sub-menus, though if you look at it another way, which is my experience via launcher menu, it's fine to have them open sequentially immediately and very responsively, until you reach your desired sub-menu and if you drift off that somehow, it is as immediately corrected, by virtue of it being immediately responsive, as the mistake was made initially, by realigning to your desired sub-menu; if this were a recurrent problem it may be more to do with the geometry of the menu being easy to drift off of; the alternative solution of a delay means the compromise of a delay in opening the desired sub-menu choice and so invites an arguably unnecessary click to open it, if you are impatient like myself, and can't wait for the hover to open it, which isn't a bad way of doing things, but less economical and fluid. personally, without fluidity and a hotkey to open and display the menu prior to my cursor reaching the sub-menus, I'd not use the global menu, when I can have them ever present to directly access on the traditional menu bar, the only purpose of the global menu is aesthetic otherwise and to provide slightly more screen space but not for a compromise in workflow -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391905] No way to delete Look & Feel themes
https://bugs.kde.org/show_bug.cgi?id=391905 --- Comment #1 from ozorio.silva.n...@gmail.com --- Comment on attachment 111426 --> https://bugs.kde.org/attachment.cgi?id=111426 Not an exclusion option layout theme I downloaded the arc dark theme and adapta, but I can not remove them. standard themes should not be removed this I agree only the default theme could not be removed, but themes installed via download should have the removal option -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384031] Monitor Scaling / HiDPI support breaks font Anti-Aliasing
https://bugs.kde.org/show_bug.cgi?id=384031 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pla ||sma-framework/a21bc11fe1165 ||1f6d211489ebfc8435cef877194 --- Comment #19 from Nate Graham --- Git commit a21bc11fe11651f6d211489ebfc8435cef877194 by Nathaniel Graham. Committed on 16/03/2018 at 22:26. Pushed by ngraham into branch 'master'. Fix text scaling with non-integer scale factors when PLASMA_USE_QT_SCALING=1 is set Summary: When `PLASMA_USE_QT_SCALING=1` is set, Plasma uses native Qt scaling. This works fine for integer scale factors, and fixes a lot of bugs (see [[https://bugs.kde.org/show_bug.cgi?id=356446|Bug 356446]]) but it introduces a new one: with non-integer scale factors, text becomes blurry and pixellated because of a bug in `Text.NativeRendering`: https://bugreports.qt.io/browse/QTBUG-67007 QQC2-desktop-style forces the use of `Text.QtRendering` rendering for non-integer scale factors, successfully working around the problem. But PlasmaComponents QML objects don't implement the same workaround, so we see the issue in Plasma. This patch fixes that, and gets us one step closer to being able to use Qt scaling in Plasmashell. There is no effect when `PLASMA_USE_QT_SCALING=1` is not being used. FIXED-IN 5.13 Related: bug 391691, bug 386216, bug 391695, bug 391694, bug 385547, bug 391692, bug 356446 Test Plan: Before: `PLASMA_USE_QT_SCALING=1` set, 1.2 scale factor: Plasma text looks awful: {F5749797} After: `PLASMA_USE_QT_SCALING=1` set, 1.2 scale factor: Plasma text looks amazing! {F5749798} Note that we still get sub-pixel anti-aliasing and good kerning. There appear to be no layout regressions. Without both `PLASMA_USE_QT_SCALING=1` and a non-integer scale factor set, there is no visual change compared to the status quo. Reviewers: #plasma, davidedmundson Reviewed By: #plasma, davidedmundson Subscribers: mart, broulik, #frameworks Tags: #frameworks Differential Revision: https://phabricator.kde.org/D11244 M +4-2examples/applets/testtheme/contents/ui/FontGizmo.qml M +5-1src/declarativeimports/plasmacomponents/qml/Label.qml M +5-1 src/declarativeimports/plasmacomponents/qml/private/DualStateButton.qml M +4-0src/declarativeimports/plasmacomponents3/ComboBox.qml M +5-1src/declarativeimports/plasmacomponents3/Label.qml M +5-1src/declarativeimports/plasmacomponents3/TextArea.qml M +5-1src/declarativeimports/plasmacomponents3/TextField.qml M +5-0src/declarativeimports/plasmastyle/ComboBoxStyle.qml M +4-1src/declarativeimports/plasmastyle/SpinBoxStyle.qml M +4-1src/declarativeimports/plasmastyle/TextAreaStyle.qml M +4-1src/declarativeimports/plasmastyle/TextFieldStyle.qml https://commits.kde.org/plasma-framework/a21bc11fe11651f6d211489ebfc8435cef877194 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356446] plasmashell does not respect QT_DEVICE_PIXEL_RATIO
https://bugs.kde.org/show_bug.cgi?id=356446 --- Comment #31 from Nate Graham --- Git commit a21bc11fe11651f6d211489ebfc8435cef877194 by Nathaniel Graham. Committed on 16/03/2018 at 22:26. Pushed by ngraham into branch 'master'. Fix text scaling with non-integer scale factors when PLASMA_USE_QT_SCALING=1 is set Summary: When `PLASMA_USE_QT_SCALING=1` is set, Plasma uses native Qt scaling. This works fine for integer scale factors, and fixes a lot of bugs (see [[https://bugs.kde.org/show_bug.cgi?id=356446|Bug 356446]]) but it introduces a new one: with non-integer scale factors, text becomes blurry and pixellated because of a bug in `Text.NativeRendering`: https://bugreports.qt.io/browse/QTBUG-67007 QQC2-desktop-style forces the use of `Text.QtRendering` rendering for non-integer scale factors, successfully working around the problem. But PlasmaComponents QML objects don't implement the same workaround, so we see the issue in Plasma. This patch fixes that, and gets us one step closer to being able to use Qt scaling in Plasmashell. There is no effect when `PLASMA_USE_QT_SCALING=1` is not being used. FIXED-IN 5.13 Related: bug 391691, bug 384031, bug 386216, bug 391695, bug 391694, bug 385547, bug 391692 Test Plan: Before: `PLASMA_USE_QT_SCALING=1` set, 1.2 scale factor: Plasma text looks awful: {F5749797} After: `PLASMA_USE_QT_SCALING=1` set, 1.2 scale factor: Plasma text looks amazing! {F5749798} Note that we still get sub-pixel anti-aliasing and good kerning. There appear to be no layout regressions. Without both `PLASMA_USE_QT_SCALING=1` and a non-integer scale factor set, there is no visual change compared to the status quo. Reviewers: #plasma, davidedmundson Reviewed By: #plasma, davidedmundson Subscribers: mart, broulik, #frameworks Tags: #frameworks Differential Revision: https://phabricator.kde.org/D11244 M +4-2examples/applets/testtheme/contents/ui/FontGizmo.qml M +5-1src/declarativeimports/plasmacomponents/qml/Label.qml M +5-1 src/declarativeimports/plasmacomponents/qml/private/DualStateButton.qml M +4-0src/declarativeimports/plasmacomponents3/ComboBox.qml M +5-1src/declarativeimports/plasmacomponents3/Label.qml M +5-1src/declarativeimports/plasmacomponents3/TextArea.qml M +5-1src/declarativeimports/plasmacomponents3/TextField.qml M +5-0src/declarativeimports/plasmastyle/ComboBoxStyle.qml M +4-1src/declarativeimports/plasmastyle/SpinBoxStyle.qml M +4-1src/declarativeimports/plasmastyle/TextAreaStyle.qml M +4-1src/declarativeimports/plasmastyle/TextFieldStyle.qml https://commits.kde.org/plasma-framework/a21bc11fe11651f6d211489ebfc8435cef877194 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391695] Workspace Theme/Desktop Theme KCM: use of QtQuickControls1 and/or PlasmaComponents labels causes blurry pixellated text with non-integer scale factors
https://bugs.kde.org/show_bug.cgi?id=391695 --- Comment #4 from Nate Graham --- Git commit a21bc11fe11651f6d211489ebfc8435cef877194 by Nathaniel Graham. Committed on 16/03/2018 at 22:26. Pushed by ngraham into branch 'master'. Fix text scaling with non-integer scale factors when PLASMA_USE_QT_SCALING=1 is set Summary: When `PLASMA_USE_QT_SCALING=1` is set, Plasma uses native Qt scaling. This works fine for integer scale factors, and fixes a lot of bugs (see [[https://bugs.kde.org/show_bug.cgi?id=356446|Bug 356446]]) but it introduces a new one: with non-integer scale factors, text becomes blurry and pixellated because of a bug in `Text.NativeRendering`: https://bugreports.qt.io/browse/QTBUG-67007 QQC2-desktop-style forces the use of `Text.QtRendering` rendering for non-integer scale factors, successfully working around the problem. But PlasmaComponents QML objects don't implement the same workaround, so we see the issue in Plasma. This patch fixes that, and gets us one step closer to being able to use Qt scaling in Plasmashell. There is no effect when `PLASMA_USE_QT_SCALING=1` is not being used. FIXED-IN 5.13 Related: bug 391691, bug 384031, bug 386216, bug 391694, bug 385547, bug 391692, bug 356446 Test Plan: Before: `PLASMA_USE_QT_SCALING=1` set, 1.2 scale factor: Plasma text looks awful: {F5749797} After: `PLASMA_USE_QT_SCALING=1` set, 1.2 scale factor: Plasma text looks amazing! {F5749798} Note that we still get sub-pixel anti-aliasing and good kerning. There appear to be no layout regressions. Without both `PLASMA_USE_QT_SCALING=1` and a non-integer scale factor set, there is no visual change compared to the status quo. Reviewers: #plasma, davidedmundson Reviewed By: #plasma, davidedmundson Subscribers: mart, broulik, #frameworks Tags: #frameworks Differential Revision: https://phabricator.kde.org/D11244 M +4-2examples/applets/testtheme/contents/ui/FontGizmo.qml M +5-1src/declarativeimports/plasmacomponents/qml/Label.qml M +5-1 src/declarativeimports/plasmacomponents/qml/private/DualStateButton.qml M +4-0src/declarativeimports/plasmacomponents3/ComboBox.qml M +5-1src/declarativeimports/plasmacomponents3/Label.qml M +5-1src/declarativeimports/plasmacomponents3/TextArea.qml M +5-1src/declarativeimports/plasmacomponents3/TextField.qml M +5-0src/declarativeimports/plasmastyle/ComboBoxStyle.qml M +4-1src/declarativeimports/plasmastyle/SpinBoxStyle.qml M +4-1src/declarativeimports/plasmastyle/TextAreaStyle.qml M +4-1src/declarativeimports/plasmastyle/TextFieldStyle.qml https://commits.kde.org/plasma-framework/a21bc11fe11651f6d211489ebfc8435cef877194 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 391692] Multimedia/Audio Volume KCM: use of QtQuickControls1 and/or PlasmaComponents labels causes blurry pixellated text with non-integer scale factors
https://bugs.kde.org/show_bug.cgi?id=391692 --- Comment #2 from Nate Graham --- Git commit a21bc11fe11651f6d211489ebfc8435cef877194 by Nathaniel Graham. Committed on 16/03/2018 at 22:26. Pushed by ngraham into branch 'master'. Fix text scaling with non-integer scale factors when PLASMA_USE_QT_SCALING=1 is set Summary: When `PLASMA_USE_QT_SCALING=1` is set, Plasma uses native Qt scaling. This works fine for integer scale factors, and fixes a lot of bugs (see [[https://bugs.kde.org/show_bug.cgi?id=356446|Bug 356446]]) but it introduces a new one: with non-integer scale factors, text becomes blurry and pixellated because of a bug in `Text.NativeRendering`: https://bugreports.qt.io/browse/QTBUG-67007 QQC2-desktop-style forces the use of `Text.QtRendering` rendering for non-integer scale factors, successfully working around the problem. But PlasmaComponents QML objects don't implement the same workaround, so we see the issue in Plasma. This patch fixes that, and gets us one step closer to being able to use Qt scaling in Plasmashell. There is no effect when `PLASMA_USE_QT_SCALING=1` is not being used. FIXED-IN 5.13 Related: bug 391691, bug 384031, bug 386216, bug 391695, bug 391694, bug 385547, bug 356446 Test Plan: Before: `PLASMA_USE_QT_SCALING=1` set, 1.2 scale factor: Plasma text looks awful: {F5749797} After: `PLASMA_USE_QT_SCALING=1` set, 1.2 scale factor: Plasma text looks amazing! {F5749798} Note that we still get sub-pixel anti-aliasing and good kerning. There appear to be no layout regressions. Without both `PLASMA_USE_QT_SCALING=1` and a non-integer scale factor set, there is no visual change compared to the status quo. Reviewers: #plasma, davidedmundson Reviewed By: #plasma, davidedmundson Subscribers: mart, broulik, #frameworks Tags: #frameworks Differential Revision: https://phabricator.kde.org/D11244 M +4-2examples/applets/testtheme/contents/ui/FontGizmo.qml M +5-1src/declarativeimports/plasmacomponents/qml/Label.qml M +5-1 src/declarativeimports/plasmacomponents/qml/private/DualStateButton.qml M +4-0src/declarativeimports/plasmacomponents3/ComboBox.qml M +5-1src/declarativeimports/plasmacomponents3/Label.qml M +5-1src/declarativeimports/plasmacomponents3/TextArea.qml M +5-1src/declarativeimports/plasmacomponents3/TextField.qml M +5-0src/declarativeimports/plasmastyle/ComboBoxStyle.qml M +4-1src/declarativeimports/plasmastyle/SpinBoxStyle.qml M +4-1src/declarativeimports/plasmastyle/TextAreaStyle.qml M +4-1src/declarativeimports/plasmastyle/TextFieldStyle.qml https://commits.kde.org/plasma-framework/a21bc11fe11651f6d211489ebfc8435cef877194 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391691] Logout overlay has blurry pixellated text with non-integer scale factors
https://bugs.kde.org/show_bug.cgi?id=391691 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pla ||sma-framework/a21bc11fe1165 ||1f6d211489ebfc8435cef877194 --- Comment #7 from Nate Graham --- Git commit a21bc11fe11651f6d211489ebfc8435cef877194 by Nathaniel Graham. Committed on 16/03/2018 at 22:26. Pushed by ngraham into branch 'master'. Fix text scaling with non-integer scale factors when PLASMA_USE_QT_SCALING=1 is set Summary: When `PLASMA_USE_QT_SCALING=1` is set, Plasma uses native Qt scaling. This works fine for integer scale factors, and fixes a lot of bugs (see [[https://bugs.kde.org/show_bug.cgi?id=356446|Bug 356446]]) but it introduces a new one: with non-integer scale factors, text becomes blurry and pixellated because of a bug in `Text.NativeRendering`: https://bugreports.qt.io/browse/QTBUG-67007 QQC2-desktop-style forces the use of `Text.QtRendering` rendering for non-integer scale factors, successfully working around the problem. But PlasmaComponents QML objects don't implement the same workaround, so we see the issue in Plasma. This patch fixes that, and gets us one step closer to being able to use Qt scaling in Plasmashell. There is no effect when `PLASMA_USE_QT_SCALING=1` is not being used. FIXED-IN 5.13 Related: bug 384031, bug 386216, bug 391695, bug 391694, bug 385547, bug 391692, bug 356446 Test Plan: Before: `PLASMA_USE_QT_SCALING=1` set, 1.2 scale factor: Plasma text looks awful: {F5749797} After: `PLASMA_USE_QT_SCALING=1` set, 1.2 scale factor: Plasma text looks amazing! {F5749798} Note that we still get sub-pixel anti-aliasing and good kerning. There appear to be no layout regressions. Without both `PLASMA_USE_QT_SCALING=1` and a non-integer scale factor set, there is no visual change compared to the status quo. Reviewers: #plasma, davidedmundson Reviewed By: #plasma, davidedmundson Subscribers: mart, broulik, #frameworks Tags: #frameworks Differential Revision: https://phabricator.kde.org/D11244 M +4-2examples/applets/testtheme/contents/ui/FontGizmo.qml M +5-1src/declarativeimports/plasmacomponents/qml/Label.qml M +5-1 src/declarativeimports/plasmacomponents/qml/private/DualStateButton.qml M +4-0src/declarativeimports/plasmacomponents3/ComboBox.qml M +5-1src/declarativeimports/plasmacomponents3/Label.qml M +5-1src/declarativeimports/plasmacomponents3/TextArea.qml M +5-1src/declarativeimports/plasmacomponents3/TextField.qml M +5-0src/declarativeimports/plasmastyle/ComboBoxStyle.qml M +4-1src/declarativeimports/plasmastyle/SpinBoxStyle.qml M +4-1src/declarativeimports/plasmastyle/TextAreaStyle.qml M +4-1src/declarativeimports/plasmastyle/TextFieldStyle.qml https://commits.kde.org/plasma-framework/a21bc11fe11651f6d211489ebfc8435cef877194 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 386216] Desktop Behavior/Desktop Effects KCM: use of QtQuickControls1 and/or PlasmaComponents labels causes blurry pixellated text with non-integer scale factors
https://bugs.kde.org/show_bug.cgi?id=386216 --- Comment #7 from Nate Graham --- Git commit a21bc11fe11651f6d211489ebfc8435cef877194 by Nathaniel Graham. Committed on 16/03/2018 at 22:26. Pushed by ngraham into branch 'master'. Fix text scaling with non-integer scale factors when PLASMA_USE_QT_SCALING=1 is set Summary: When `PLASMA_USE_QT_SCALING=1` is set, Plasma uses native Qt scaling. This works fine for integer scale factors, and fixes a lot of bugs (see [[https://bugs.kde.org/show_bug.cgi?id=356446|Bug 356446]]) but it introduces a new one: with non-integer scale factors, text becomes blurry and pixellated because of a bug in `Text.NativeRendering`: https://bugreports.qt.io/browse/QTBUG-67007 QQC2-desktop-style forces the use of `Text.QtRendering` rendering for non-integer scale factors, successfully working around the problem. But PlasmaComponents QML objects don't implement the same workaround, so we see the issue in Plasma. This patch fixes that, and gets us one step closer to being able to use Qt scaling in Plasmashell. There is no effect when `PLASMA_USE_QT_SCALING=1` is not being used. FIXED-IN 5.13 Related: bug 391691, bug 384031, bug 391695, bug 391694, bug 385547, bug 391692, bug 356446 Test Plan: Before: `PLASMA_USE_QT_SCALING=1` set, 1.2 scale factor: Plasma text looks awful: {F5749797} After: `PLASMA_USE_QT_SCALING=1` set, 1.2 scale factor: Plasma text looks amazing! {F5749798} Note that we still get sub-pixel anti-aliasing and good kerning. There appear to be no layout regressions. Without both `PLASMA_USE_QT_SCALING=1` and a non-integer scale factor set, there is no visual change compared to the status quo. Reviewers: #plasma, davidedmundson Reviewed By: #plasma, davidedmundson Subscribers: mart, broulik, #frameworks Tags: #frameworks Differential Revision: https://phabricator.kde.org/D11244 M +4-2examples/applets/testtheme/contents/ui/FontGizmo.qml M +5-1src/declarativeimports/plasmacomponents/qml/Label.qml M +5-1 src/declarativeimports/plasmacomponents/qml/private/DualStateButton.qml M +4-0src/declarativeimports/plasmacomponents3/ComboBox.qml M +5-1src/declarativeimports/plasmacomponents3/Label.qml M +5-1src/declarativeimports/plasmacomponents3/TextArea.qml M +5-1src/declarativeimports/plasmacomponents3/TextField.qml M +5-0src/declarativeimports/plasmastyle/ComboBoxStyle.qml M +4-1src/declarativeimports/plasmastyle/SpinBoxStyle.qml M +4-1src/declarativeimports/plasmastyle/TextAreaStyle.qml M +4-1src/declarativeimports/plasmastyle/TextFieldStyle.qml https://commits.kde.org/plasma-framework/a21bc11fe11651f6d211489ebfc8435cef877194 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385547] Workspace Theme/Look & Feel KCM: use of QtQuickControls1 and/or PlasmaComponents labels causes blurry pixellated text with non-integer scale factors
https://bugs.kde.org/show_bug.cgi?id=385547 --- Comment #12 from Nate Graham --- Git commit a21bc11fe11651f6d211489ebfc8435cef877194 by Nathaniel Graham. Committed on 16/03/2018 at 22:26. Pushed by ngraham into branch 'master'. Fix text scaling with non-integer scale factors when PLASMA_USE_QT_SCALING=1 is set Summary: When `PLASMA_USE_QT_SCALING=1` is set, Plasma uses native Qt scaling. This works fine for integer scale factors, and fixes a lot of bugs (see [[https://bugs.kde.org/show_bug.cgi?id=356446|Bug 356446]]) but it introduces a new one: with non-integer scale factors, text becomes blurry and pixellated because of a bug in `Text.NativeRendering`: https://bugreports.qt.io/browse/QTBUG-67007 QQC2-desktop-style forces the use of `Text.QtRendering` rendering for non-integer scale factors, successfully working around the problem. But PlasmaComponents QML objects don't implement the same workaround, so we see the issue in Plasma. This patch fixes that, and gets us one step closer to being able to use Qt scaling in Plasmashell. There is no effect when `PLASMA_USE_QT_SCALING=1` is not being used. FIXED-IN 5.13 Related: bug 391691, bug 384031, bug 386216, bug 391695, bug 391694, bug 391692, bug 356446 Test Plan: Before: `PLASMA_USE_QT_SCALING=1` set, 1.2 scale factor: Plasma text looks awful: {F5749797} After: `PLASMA_USE_QT_SCALING=1` set, 1.2 scale factor: Plasma text looks amazing! {F5749798} Note that we still get sub-pixel anti-aliasing and good kerning. There appear to be no layout regressions. Without both `PLASMA_USE_QT_SCALING=1` and a non-integer scale factor set, there is no visual change compared to the status quo. Reviewers: #plasma, davidedmundson Reviewed By: #plasma, davidedmundson Subscribers: mart, broulik, #frameworks Tags: #frameworks Differential Revision: https://phabricator.kde.org/D11244 M +4-2examples/applets/testtheme/contents/ui/FontGizmo.qml M +5-1src/declarativeimports/plasmacomponents/qml/Label.qml M +5-1 src/declarativeimports/plasmacomponents/qml/private/DualStateButton.qml M +4-0src/declarativeimports/plasmacomponents3/ComboBox.qml M +5-1src/declarativeimports/plasmacomponents3/Label.qml M +5-1src/declarativeimports/plasmacomponents3/TextArea.qml M +5-1src/declarativeimports/plasmacomponents3/TextField.qml M +5-0src/declarativeimports/plasmastyle/ComboBoxStyle.qml M +4-1src/declarativeimports/plasmastyle/SpinBoxStyle.qml M +4-1src/declarativeimports/plasmastyle/TextAreaStyle.qml M +4-1src/declarativeimports/plasmastyle/TextFieldStyle.qml https://commits.kde.org/plasma-framework/a21bc11fe11651f6d211489ebfc8435cef877194 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391694] Workspace Theme/Splash Screen KCM: use of QtQuickControls1 and/or PlasmaComponents labels causes blurry pixellated text with non-integer scale factors
https://bugs.kde.org/show_bug.cgi?id=391694 --- Comment #1 from Nate Graham --- Git commit a21bc11fe11651f6d211489ebfc8435cef877194 by Nathaniel Graham. Committed on 16/03/2018 at 22:26. Pushed by ngraham into branch 'master'. Fix text scaling with non-integer scale factors when PLASMA_USE_QT_SCALING=1 is set Summary: When `PLASMA_USE_QT_SCALING=1` is set, Plasma uses native Qt scaling. This works fine for integer scale factors, and fixes a lot of bugs (see [[https://bugs.kde.org/show_bug.cgi?id=356446|Bug 356446]]) but it introduces a new one: with non-integer scale factors, text becomes blurry and pixellated because of a bug in `Text.NativeRendering`: https://bugreports.qt.io/browse/QTBUG-67007 QQC2-desktop-style forces the use of `Text.QtRendering` rendering for non-integer scale factors, successfully working around the problem. But PlasmaComponents QML objects don't implement the same workaround, so we see the issue in Plasma. This patch fixes that, and gets us one step closer to being able to use Qt scaling in Plasmashell. There is no effect when `PLASMA_USE_QT_SCALING=1` is not being used. FIXED-IN 5.13 Related: bug 391691, bug 384031, bug 386216, bug 391695, bug 385547, bug 391692, bug 356446 Test Plan: Before: `PLASMA_USE_QT_SCALING=1` set, 1.2 scale factor: Plasma text looks awful: {F5749797} After: `PLASMA_USE_QT_SCALING=1` set, 1.2 scale factor: Plasma text looks amazing! {F5749798} Note that we still get sub-pixel anti-aliasing and good kerning. There appear to be no layout regressions. Without both `PLASMA_USE_QT_SCALING=1` and a non-integer scale factor set, there is no visual change compared to the status quo. Reviewers: #plasma, davidedmundson Reviewed By: #plasma, davidedmundson Subscribers: mart, broulik, #frameworks Tags: #frameworks Differential Revision: https://phabricator.kde.org/D11244 M +4-2examples/applets/testtheme/contents/ui/FontGizmo.qml M +5-1src/declarativeimports/plasmacomponents/qml/Label.qml M +5-1 src/declarativeimports/plasmacomponents/qml/private/DualStateButton.qml M +4-0src/declarativeimports/plasmacomponents3/ComboBox.qml M +5-1src/declarativeimports/plasmacomponents3/Label.qml M +5-1src/declarativeimports/plasmacomponents3/TextArea.qml M +5-1src/declarativeimports/plasmacomponents3/TextField.qml M +5-0src/declarativeimports/plasmastyle/ComboBoxStyle.qml M +4-1src/declarativeimports/plasmastyle/SpinBoxStyle.qml M +4-1src/declarativeimports/plasmastyle/TextAreaStyle.qml M +4-1src/declarativeimports/plasmastyle/TextFieldStyle.qml https://commits.kde.org/plasma-framework/a21bc11fe11651f6d211489ebfc8435cef877194 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 391948] New: krusader 2.6: Regression - preserve state of selection of files/folder after perform copying task
https://bugs.kde.org/show_bug.cgi?id=391948 Bug ID: 391948 Summary: krusader 2.6: Regression - preserve state of selection of files/folder after perform copying task Product: krusader Version: 2.6.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: m...@fork.pl Reporter: linn...@gmail.com Target Milestone: --- As in Krusader 2.0 or DoubleCMD, if select files/folders and then copy them to somewhere, the state of files/folders' selection is preserved. With this behavior, I could quickly check that if the files/folders are copied successfully. Or, If I want to move these selected files/folders (after copying), I just perform cut/paste task, without worrying what files/folders need to be selected again. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386918] F9 shortcut is default added for two commands
https://bugs.kde.org/show_bug.cgi?id=386918 --- Comment #2 from Braxton Salyer --- Created attachment 111455 --> https://bugs.kde.org/attachment.cgi?id=111455&action=edit Patch the bug by Reassigning Debug-Launch to Alt+F9 This is the second file to the patch. It updates the handbook to follow the new key shortcut. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386918] F9 shortcut is default added for two commands
https://bugs.kde.org/show_bug.cgi?id=386918 Braxton Salyer changed: What|Removed |Added Ever confirmed|0 |1 CC||braxtonsal...@gmail.com Status|UNCONFIRMED |ASSIGNED Assignee|kdevelop-bugs-n...@kde.org |braxtonsal...@gmail.com --- Comment #1 from Braxton Salyer --- Created attachment 111454 --> https://bugs.kde.org/attachment.cgi?id=111454&action=edit Patch the bug by Reassigning Debug-Launch to Alt+F9 This is the patch to the Code. I'll also submit a second file that updates the handbook accordingly -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 391947] New: Document corruption due to random pasting from clipboard
https://bugs.kde.org/show_bug.cgi?id=391947 Bug ID: 391947 Summary: Document corruption due to random pasting from clipboard Product: kate Version: 16.04 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: sharpzq4...@gmail.com Target Milestone: --- Hi there, I have twice found that a document was being "interfered with" while writing plain text in Kate. The first time, I was moving chunks around with the copy/paste function and using undo often, and had difficulty understanding why unexpected changes were occurring. I kept seeing text that I recently pasted in the wrong places, and I thought it might have had to do with Kate's undo function but this was incorrect. The second time, I knew of possible problems with the clipboard or undo functions, so I did not use them at all. I was writing a monthly list of things to do and apart from going up and down to append to different sections, I pretty much wrote the document from beginning to end. Point being, this bug happens easily, if it is not isolated to my system alone. What happens is while writing out plain text without any formatting other than hitting enter for new lines and occasionally using tab to indent, I can use the mouse to scroll back up to areas of the document which ran out of view, and the contents of my clipboard (at the time a link to a Youtube video) had appeared at one or two random places in the text. Sometimes at the end of a line and sometimes right in the middle of a word, splitting it apart. Because I had not entered in any URLs in the document, it was very easy to spot. Please note that this cannot be accidental triggering of the "Paste" function by any component of the hardware, OS or Kate. The insertions always occur in areas off-screen and never where the cursor is. As such it goes unnoticed until reviewing the document. I don't know if the insertions occur while I scroll with the mouse clicked on the scrollbar to move back up the document, or if they occur randomly while I am typing. Here is the information about my OS and Kate: $ lsb_release -a No LSB modules are available. Distributor ID: LinuxMint Description:Linux Mint 18.1 Serena Release:18.1 Codename: serena $ apt-cache policy kate kate: Installed: 4:16.04.3-0ubuntu1~ubuntu16.04~ppa63 Candidate: 4:16.04.3-0ubuntu1~ubuntu16.04~ppa63 Version table: *** 4:16.04.3-0ubuntu1~ubuntu16.04~ppa63 500 500 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 4:15.12.3-0ubuntu2 500 500 http://mirror.csclub.uwaterloo.ca/ubuntu xenial/universe amd64 Packages Help -> About Editor Component: "Kate Part Version 5.36.0" Help -> About Kate: "Kate Version 16.04.3" -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 391946] New: Default mode in 'Find in folder' is not preserved
https://bugs.kde.org/show_bug.cgi?id=391946 Bug ID: 391946 Summary: Default mode in 'Find in folder' is not preserved Product: krusader Version: 2.6.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: search Assignee: m...@fork.pl Reporter: linn...@gmail.com Target Milestone: --- 1) Settings > Configure Krusader > Panel > Search Bar > Default Mode : Search 2) Ctrl+I to Open 'Search Filter' 3) Escape search mode 4) Ctrl+F, or type something What is expected, is that in step 4, the mode of search bar would be 'Search', but instead of 'Filter' mode. I must manually to chose the 'Search' mode again (when search bar appears). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 378339] Crash in QQuickItem::isVisible() when removing characters in search text box
https://bugs.kde.org/show_bug.cgi?id=378339 Nate Graham changed: What|Removed |Added CC||reyjos...@gmail.com --- Comment #34 from Nate Graham --- *** Bug 391259 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391259] crashed after looking for power settings
https://bugs.kde.org/show_bug.cgi?id=391259 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE CC||n...@kde.org Status|UNCONFIRMED |RESOLVED --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 378339 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 378339] Crash in QQuickItem::isVisible() when removing characters in search text box
https://bugs.kde.org/show_bug.cgi?id=378339 Nate Graham changed: What|Removed |Added CC||notux...@gmail.com --- Comment #33 from Nate Graham --- *** Bug 391938 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391938] System Settings app crashed after multiple searches
https://bugs.kde.org/show_bug.cgi?id=391938 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 378339 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391942] Settings App Crashes while searching by typing in the search field
https://bugs.kde.org/show_bug.cgi?id=391942 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 378339 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 378339] Crash in QQuickItem::isVisible() when removing characters in search text box
https://bugs.kde.org/show_bug.cgi?id=378339 Nate Graham changed: What|Removed |Added CC||temp00...@gmail.com --- Comment #32 from Nate Graham --- *** Bug 391942 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 378339] Crash in QQuickItem::isVisible() when removing characters in search text box
https://bugs.kde.org/show_bug.cgi?id=378339 Nate Graham changed: What|Removed |Added CC||mark...@gmail.com --- Comment #31 from Nate Graham --- *** Bug 391841 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391841] KDE Settings Crash
https://bugs.kde.org/show_bug.cgi?id=391841 Nate Graham changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||n...@kde.org Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 378339 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391676] Settings App Crashed while searching
https://bugs.kde.org/show_bug.cgi?id=391676 Nate Graham changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||n...@kde.org Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 378339 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 378339] Crash in QQuickItem::isVisible() when removing characters in search text box
https://bugs.kde.org/show_bug.cgi?id=378339 Nate Graham changed: What|Removed |Added CC||w...@cwilgo.com --- Comment #30 from Nate Graham --- *** Bug 391676 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 369676] White lockscreen text's readability depends on background
https://bugs.kde.org/show_bug.cgi?id=369676 Michail Vourlakos changed: What|Removed |Added CC||mvourla...@gmail.com --- Comment #23 from Michail Vourlakos --- (In reply to Marco Martin from comment #19) > another version, with blur > https://www.youtube.com/watch?v=KWCZwrPXfVk Looks very good! I just want to add some ideas in case they will help a bit more with the contrast between the background and the text color used when the background isnt blurred... Latte demonstrated the following: https://www.youtube.com/watch?v=srkKkSnjG-w watch out the top panel how changes its color... The algorithm is the following: 1. For the underlying background is calculated the relative luminas only for the region of the background which is under the panel 2. That luminas value is cached so it isnt calculated again when we switch to that background 3. Based on that luminas value Latte is choosing between backgroundColor and textColor, the one that provides the greater contrast. 4. [based on another Latte part that I had to make similar design decisions] a. When a whitish color is used for the text then enabling shadows looks really good b. but when a darkish color is used for text then it is better to disable totally the shadows -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391778] FreeRDP second Full-Screen Monitor is hidden
https://bugs.kde.org/show_bug.cgi?id=391778 --- Comment #12 from Robert Cheramy --- Created attachment 111453 --> https://bugs.kde.org/attachment.cgi?id=111453&action=edit Output of kwin debug messages Here is the Output of KWIN with Debug activated (I activated everything using kdebugsettings) when starting freerdp in fullscreen mode. I also checked .xsessions-error (which is empty as I started kwin --replace from the console. There are no other messages generated ther when I start freerdp), and did not find the error "fullscreenMonitors update failed. request higher than number of screens.". -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391251] Double free or corruption when creating a new asset account.
https://bugs.kde.org/show_bug.cgi?id=391251 Jack changed: What|Removed |Added CC||ostroffjh@users.sourceforge ||.net --- Comment #10 from Jack --- Jose - Exactly which ebuild are you using? 5.0.0-r1 from the main tree, or 5.0. (git 5.0) or (git master) from the KDE overlay? If you do "ebuild /path/to/ebuild configure" the build.log should have the output from cmake, which should confirm the build type. As suggested in comment 9, it is possible that the skylake specification is causing a problem - can you try backing off to a more generic setting and see if that eliminates the crash? (For those not familiar with Gentoo linux, it is a source based distro, and an ebuild is a package definition file, with all the information necessary to download, configure, compile, and install the package - either from tarball or git.) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391937] System Settings > Input Devices no longer lists mouse
https://bugs.kde.org/show_bug.cgi?id=391937 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 391933] Unreadable application names Breeze dark
https://bugs.kde.org/show_bug.cgi?id=391933 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391786] kmymoney git 5.0 crashes on exit, even if no file loaded
https://bugs.kde.org/show_bug.cgi?id=391786 Jack changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #6 from Jack --- I have now recompiled for Debug, Release, and RelWithDebInfo with both gcc 6.4.0 and 7.3.0, and can no longer reproduce the crash, so I'm just going to close this as invalid. (would WORKSFORME be better?) I'll reopen only if I can consistently reproduce the crash. I am assuming it was either something that got updated recently, or maybe just a build or install dir that was not as clean as I thought. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 391941] Crash when flatpak installation is canceled
https://bugs.kde.org/show_bug.cgi?id=391941 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 391920] Konsole default settings (theme consistency, font size)
https://bugs.kde.org/show_bug.cgi?id=391920 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #2 from Nate Graham --- FWIW I agree that the default fixed-width font size is too small and submitting a patch to increase it has been on my to-do list for a while. I also plan to do the same with the geberal font (10pt -> 11pt), for the same reason that you identified, but I expect that will be fairly controversial... Let's use this bug to track using the Breeze theme by default. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 310733] Konsole Blows Up Randomly [Konsole::Session::closeInForceWay]
https://bugs.kde.org/show_bug.cgi?id=310733 Ahmad Samir changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||a.samir...@gmail.com Resolution|--- |UNMAINTAINED --- Comment #4 from Ahmad Samir --- KDE4/konsole is no longer maintained. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 312006] Crash while dragging a tab from one window to another Konsole window
https://bugs.kde.org/show_bug.cgi?id=312006 Ahmad Samir changed: What|Removed |Added Resolution|--- |UNMAINTAINED CC||a.samir...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from Ahmad Samir --- KDE4/konsole is no longer maintained. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384230] vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0xAB 0x68
https://bugs.kde.org/show_bug.cgi?id=384230 --- Comment #16 from Tom Hughes --- Were not actually daft you know and I did check the Intel manual multiple times. To be clear I believe this quote covers it: "The address-size override prefix (67H) allows programs to switch between 16- and 32-bit addressing. Either size can be the default; the prefix selects the non-default size. Using this prefix and/or other undefined opcodes when operands for the instruction do not reside in memory is reserved; such use may cause unpredictable behavior." In this case the only operand to the instruction is an immediate offset encoded as part of the instruction, which does not "reside in memory" and as such this use of the prefix constitutes a reserved instruction and using it may cause "unpredictable behaviour". -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 313754] Very slow repainting on remote connections
https://bugs.kde.org/show_bug.cgi?id=313754 Ahmad Samir changed: What|Removed |Added Resolution|--- |UNMAINTAINED CC||a.samir...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #3 from Ahmad Samir --- KDE4/konsole is no longer maintained; reopen if you can still reproduce this issue with a recent konsole version. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384230] vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0xAB 0x68
https://bugs.kde.org/show_bug.cgi?id=384230 Jannik Vogel changed: What|Removed |Added CC||em...@jannikvogel.de --- Comment #15 from Jannik Vogel --- (In reply to John Reiser from comment #10) > The "proper fix" is for the compiler not to generate totally wasteful code > in the first place. > > The change in valgrind correctly accommodates poor code. To me, valgrind emulation always try to be transparent to the user. So if something runs on the host CPU, it should run through valgrind too. So arguing with a compiler is not the correct thing to do here. A fix for valgrind was necessary and Toms patch gets the job done. Wether this might be necessary for other instructions too should be tested to make this patch more generic. (In reply to Tom Hughes from comment #14) > Not really - the actual bogus instruction was in ld.so which is not part of > the code generated by that compilation. Not 100% true. The code was also found in arch linux libGLdispatch and libopenal. That's at least where I was affected, but other instances probably exist too. > So you would need to isolate the relevant file in the glibc source and try > and create a minimised preprocessed test case from that then find a set of > compiler options which would cause it to generate that code sequence for the > test case. When I originally found out about this issue, I reached out to the arch linux openal package maintainer to figure out how packages are build. While the openal maintainer (heftig) did not respond, other people on arch linux IRC helped me figure out what I needed to know. Packge https://www.archlinux.org/packages/multilib/x86_64/lib32-openal/ (version 1.18.2-1), which is affected by this bug: - Was compiled using "gcc-multilib-7.2.0-1" (see arch repos) - Configured using this: https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/lib32-openal - Systemwide compile flags can be found in makepkg.conf of the devtools helper package So we at least know which compiler generates such a sequence. I've also responded in #valgrind-dev (IRC) later, when heftig responded about why this instruction exists (following is a direct quote from heftig): > the purpose is to make the call instruction a byte longer > https://sourceware.org/ml/binutils/2016-05/msg00322.html > it's the linker patching indirect -fno-plt calls (which were 6 bytes) to > direct calls (which are 5 bytes) > since you have an extra byte to fill, you either need to insert a nop (which > would be an extra instruction) or add a pointless prefix so this is likely done to not waste an additional nop cycle or to avoid getting interrupts between those instructions. It might have other implications though. So while this looks like broken code, it's actually a clever hack to make instructions longer. As a result the patch might be incomplete as this can probably done with other instructions too. --- If anybody still has doubts about this patch I'd recommend checking the x86 docs to see if that says it's an illegal instruction - if not it should be supported; if it is contact intel about it. If you want to know more about why this sequence is generated, I'd recommend to contact the people who worked on gcc 7.2.0 -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 391945] New: Wrong files size total reported on mouse hover over directory files part of the pie chart
https://bugs.kde.org/show_bug.cgi?id=391945 Bug ID: 391945 Summary: Wrong files size total reported on mouse hover over directory files part of the pie chart Product: filelight Version: 17.12.0 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: martin.sandsm...@kde.org Reporter: aalexg...@gmail.com Target Milestone: --- Created attachment 111452 --> https://bugs.kde.org/attachment.cgi?id=111452&action=edit Mouse hover overlay reports wrong files size sum Files size total in current folder on mouse hover is not correct see attachment. Here are file sizes for all directories: % find . -maxdepth 1 ! -path . -type d | xargs -d '\n' -L 1 du -bs | awk '{print $1}' 78772 745066525 3441629536 792029780 1668518203 1248460712 2410312454 1552634848 965684835 1732673045 1232779583 1880206317 2869673916 1500356354 1003583257 2281767082 2141378925 2919326790 1496157397 1509558978 512845222 2908380736 1927334107 4112794124 994318199 999466902 1133569459 1113997520 3129252241 1610099646 2086720155 4937213305 3434514949 2900469855 1265724800 827611252 1819433910 959563994 1500136989 996375050 9439992341 2656450434 755596321 745891909 5411970018 4692706751 734421645 1177324767 4871323069 4685952076 736395481 3538202754 5332514783 4698232057 1464425538 12817999061 6938637424 4695298027 1490054435 1769023174 4685746992 735448275 739878866 775971247 0 787754775 1994143744 9443144092 7610171492 734453750 1074387336 744753388 753796341 734256300 739257322 2555184414 2263464014 738891705 915617891 1585899685 1549654465 3988947153 2510556696 735580628 841332223 2739077626 3086760385 1765779470 3659959671 733550396 2270697612 2447636838 2142446034 4912217197 1767698268 2093883955 2606589712 629470919 1598160189 2924573867 1989033452 2213776012 975304059 1662186329 1356061247 1020998257 623809876 1501163032 3586698718 6532687697 4451038416 4150486684 3409729597 1077355393 2527882031 3757913434 1498388538 22602463019 1593559899 920185563 Here are file sizes for all files: % find . -maxdepth 1 ! -path . -type f | xargs -d '\n' -L 1 du -bs | awk '{print $1}' 63410 893144825 104598 945705311 77139 1177017634 875020638 112319 979205126 69554 69545 2571694139 2572383811 85519 52991 1178161631 145265 1093616024 276134947 735160320 739720192 2086496435 2465583854 125121 28568 26470 47732 50129 1474034274 42427 888638488 791250335 788964820 998817691 1948370907 4158962468 113632 92624 1236271330 1915547105 996938882 2141489921 1048588649 Same thing happens regardless of whether I open the parent folder or the folder that has the problem. The problem only exists for this specific folder. There are many files having all sorts of names with spaces, brackets, dots, dashes etc. If needed I could send the file list to a developer but I will not post it publicly. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 391944] New: konqueror crash on plasmashell start-up
https://bugs.kde.org/show_bug.cgi?id=391944 Bug ID: 391944 Summary: konqueror crash on plasmashell start-up Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: arthur.ma...@internode.on.net Target Milestone: --- Application: kdeinit5 (5.0.97) Qt Version: 5.9.2 Frameworks Version: 5.42.0 Operating System: Linux 4.16.0-rc5+ x86_64 Distribution: Debian GNU/Linux testing/unstable -- Information about the crash: even though I hadn't been running konqueror in previous session, found a crash after starting plasmashell after a reboot. The crash can be reproduced sometimes. -- Backtrace: Application: Konqueror (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0981f54780 (LWP 4242))] Thread 27 (Thread 0x7f08ecff9700 (LWP 4506)): #0 0x7f097e4fa4ec in futex_wait_cancelable (private=, expected=0, futex_word=0x55f975f9362c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f097e4fa4ec in __pthread_cond_wait_common (abstime=0x0, mutex=0x55f975f935d8, cond=0x55f975f93600) at pthread_cond_wait.c:502 #2 0x7f097e4fa4ec in __pthread_cond_wait (cond=0x55f975f93600, mutex=0x55f975f935d8) at pthread_cond_wait.c:655 #3 0x7f0929c86ba5 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f0929c87087 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f0929c87e21 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f0929c844fb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f097e4f45aa in start_thread (arg=0x7f08ecff9700) at pthread_create.c:463 #8 0x7f0980074cbf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7f08ed7fa700 (LWP 4500)): #0 0x7f0972a24165 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #1 0x7f0972a2509d in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #2 0x7f0972a25449 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #3 0x7f0972a25ccf in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #4 0x7f0972e8e338 in pa_mainloop_dispatch () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f0972e8e70e in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f0972e8e790 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7f0972e9c5f9 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #8 0x7f0972a35c58 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #9 0x7f097e4f45aa in start_thread (arg=0x7f08ed7fa700) at pthread_create.c:463 #10 0x7f0980074cbf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f08edffb700 (LWP 4499)): #0 0x7f097e4fa81a in futex_reltimed_wait_cancelable (private=, reltime=0x7f08edffa9d0, expected=0, futex_word=0x7f08edffab58) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f097e4fa81a in __pthread_cond_wait_common (abstime=0x7f08edffaa70, mutex=0x7f08edffab08, cond=0x7f08edffab30) at pthread_cond_wait.c:533 #2 0x7f097e4fa81a in __pthread_cond_timedwait (cond=0x7f08edffab30, mutex=0x7f08edffab08, abstime=0x7f08edffaa70) at pthread_cond_wait.c:667 #3 0x7f0929cb5552 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f0929c7c82e in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f0929c574bb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f0929c53d38 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f0929c7070b in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f0929c883e6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f0929c844fb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f097e4f45aa in start_thread (arg=0x7f08edffb700) at pthread_create.c:463 #11 0x7f0980074cbf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f08ee7fc700 (LWP 4498)): #0 0x7f097e4fa4ec in futex_wait_cancelable (private=, expected=0, futex_word=0x55f975f2d8b8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f097e4fa4ec in __pthread_cond_wait_common (abstime=0x0, mutex=0x55f975f2d7f8, cond=0x55f975f2d890) at pthread_cond_wait.c:502 #2 0x7f097e4fa4ec in __pthread_cond_wait (cond=0x55f975f2d890, mutex=0x55f975f2d7f8) at pthread_cond_wait.c:655 #3 0x7f092a40c8b0 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f0929c87e21 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f0929c844fb in () at /usr/lib/x86_64-l
[kwin] [Bug 391902] [r600g] kwin not starts with OpenGL ES on RV730
https://bugs.kde.org/show_bug.cgi?id=391902 --- Comment #3 from Eugene --- I meant OpenGL ES would be better. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391902] [r600g] kwin not starts with OpenGL ES on RV730
https://bugs.kde.org/show_bug.cgi?id=391902 --- Comment #2 from Eugene --- (In reply to Martin Flöser from comment #1) > Please try normal OpenGL I am now on normal OpenGL. But OpenGL would be much better. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 361742] debian/rules uses deprecated /usr/share/pkg-kde-tools/qt-kde-team/3/debian-qt-kde.mk
https://bugs.kde.org/show_bug.cgi?id=361742 Valeriy Malov changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||jazzv...@gmail.com Resolution|--- |FIXED --- Comment #1 from Valeriy Malov --- Closing this because Debian control files and rpm spec files have been removed from the repository (to avoid clashing with distribution specific build stuff and confusing maintainers) -- You are receiving this mail because: You are watching all bug changes.
[kmines] [Bug 391630] Mine count is incorrect sometimes (happened multiple times)
https://bugs.kde.org/show_bug.cgi?id=391630 Expert Multimedia changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #7 from Expert Multimedia --- Ignore previous comment and image "Issue remains in git 2018-03-30". I noticed the mines I was counting were ones with x's which means they weren't mines, but rather places I flagged mines incorrectly. The case is also the same with the first screenshot, so I'll say this bug in general is unconfirmed. If I get a screenshot that demonstrates there is a bug I'll post it. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 320061] If I open a vncserver session the kde daemon will crash, OK with the main console - pointer does not work, it shows a double horizontal arrow.
https://bugs.kde.org/show_bug.cgi?id=320061 Valeriy Malov changed: What|Removed |Added CC||jazzv...@gmail.com Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Valeriy Malov --- I'm just going to close this bug because it's very old and I can't reproduce it, neither these stack traces are relevant anymore (there's no TabletDaemon::findTabletDevice anymore, second stack trace is unrelated to wacom module) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 391920] Konsole default settings (theme consistency, font size)
https://bugs.kde.org/show_bug.cgi?id=391920 Ahmad Samir changed: What|Removed |Added Severity|normal |wishlist CC||a.samir...@gmail.com --- Comment #1 from Ahmad Samir --- The default font size is the same as the fixed font size set in kdeglobals; so you need to file a separate bug against whatever component sets the default font size in KF5. (I don't know which component ... :)). -- You are receiving this mail because: You are watching all bug changes.
[kmines] [Bug 391630] Mine count is incorrect sometimes (happened multiple times)
https://bugs.kde.org/show_bug.cgi?id=391630 --- Comment #6 from Expert Multimedia --- OK, I got it to compile but still the same issue occurs (I added an additional screenshot, where the "2" NE (up, right) from the yellow mine clicked should be a "3") #howto compile (discovered myself by trial and error): sudo apt remove kmines sudo apt install cmake extra-cmake-modules libkf5-plasma-dev libkf5iconthemes-dev libkf5plasma-dev libkf5windowsystem-dev libkf5declarative-dev libkf5xmlgui-dev libkf5activities-dev libkf5wayland-dev libkf5crash-dev libkf5newstuff-dev kdoctools-dev kde-games-core-declarative libkdegames-dev libkf5kdegames-dev mkdir build cd build cmake .. -DCMAKE_INSTALL_PREFIX=/usr/local make sudo make install -- You are receiving this mail because: You are watching all bug changes.
[kmines] [Bug 391630] Mine count is incorrect sometimes (happened multiple times)
https://bugs.kde.org/show_bug.cgi?id=391630 --- Comment #5 from Expert Multimedia --- Created attachment 111451 --> https://bugs.kde.org/attachment.cgi?id=111451&action=edit Issue remains in git 2018-03-30 The 2 NE (up, right) from the yellow mine clicked should be a 3 -- You are receiving this mail because: You are watching all bug changes.
[plasma-mycroft] [Bug 391943] New: Weather temperatures displayed as degrees k, not F
https://bugs.kde.org/show_bug.cgi?id=391943 Bug ID: 391943 Summary: Weather temperatures displayed as degrees k, not F Product: plasma-mycroft Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Plasmoid Assignee: ai...@outlook.com Reporter: bund...@gmail.com Target Milestone: --- Created attachment 111450 --> https://bugs.kde.org/attachment.cgi?id=111450&action=edit Screenshot of incorrect temperature label (Joe Strummer says, "36k is really cold".) Although I'm still getting Mycroft set up, I couldn't help noticing that the weather information shows values like "Minimum Temperature 36.72k". "K" is Kelvin, and that's really cold. -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 386256] Speed up loading of large data files
https://bugs.kde.org/show_bug.cgi?id=386256 Milian Wolff changed: What|Removed |Added Summary|Loading files using |Speed up loading of large |multiple threads to readuce |data files |load times | -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391932] Google source of stock quotes quit
https://bugs.kde.org/show_bug.cgi?id=391932 akoolw...@gmail.com changed: What|Removed |Added CC||akoolw...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391932] Google source of stock quotes quit
https://bugs.kde.org/show_bug.cgi?id=391932 --- Comment #1 from akoolw...@gmail.com --- This was the format of the request & the response: Fetching URL https://finance.google.com/finance?q=TSE:XEC... The file or folder https://finance.google.com/search?q=TSE:XEC does not exist. Unable to update price for TSE:XEC (empty quote data) -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 383127] KTorrent crash while closing
https://bugs.kde.org/show_bug.cgi?id=383127 --- Comment #16 from steffko --- Created attachment 111449 --> https://bugs.kde.org/attachment.cgi?id=111449&action=edit New crash information added by DrKonqi ktorrent (5.1.0) using Qt 5.10.0 Another backtrace. Again, the output keeps on changing. -- Backtrace (Reduced): #6 QChar::isSurrogate (this=) at ../../../include/QtCore/../../src/corelib/tools/qchar.h:460 #7 QStringIterator::next (invalidAs=65533, this=, this=) at ../../../include/QtCore/5.10.0/QtCore/private/../../../../../src/corelib/tools/qstringiterator_p.h:168 #8 QFontEngineFT::stringToCMap (this=0x55c36bb8a080, str=, len=, glyphs=0x7ffc3f858710, nglyphs=0x7ffc3f8586fc, flags=...) at freetype/qfontengine_ft.cpp:1733 #9 0x7fad2e7f76e2 in QFontEngineMulti::stringToCMap (this=0x55c36b966620, str=0x56326c978af5, len=3, glyphs=0x7ffc3f858710, nglyphs=0x7ffc3f8586fc, flags=...) at text/qfontengine.cpp:1896 #10 0x7fad2e81849c in QTextEngine::shapeText (this=this@entry=0x55c36b8bcc30, item=item@entry=13) at text/qtextengine.cpp:1050 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 386897] make word/char count a global sticky preference not a temporary menu option
https://bugs.kde.org/show_bug.cgi?id=386897 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 364216] Bugzilla bug is fixed in upstream but still affects KDE bugtracker
https://bugs.kde.org/show_bug.cgi?id=364216 Ben Cooksley changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||bcooks...@kde.org Resolution|--- |INVALID --- Comment #2 from Ben Cooksley --- At this time Upstream haven't upgraded the schema to UTF8MB4 as they mentioned, so these characters aren't supported. You might want to reopen the bug at upstream to remind them to look into this. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 391875] Setting Speeddial As Homepage Randomly Gives Empty Page
https://bugs.kde.org/show_bug.cgi?id=391875 --- Comment #8 from private2@yandex.com --- I'm also with 5.10.1... You may try with QupZilla Appimage, i've reproduced it also with it. Does the debug code will give you the needed information? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 391895] Autohide controls when in fullscreen
https://bugs.kde.org/show_bug.cgi?id=391895 --- Comment #2 from e.sukun...@yandex.com --- (In reply to Henrik Fehlauer from comment #1) Thank you Henrik for the follow-up! I checked the narrow zone seen at the bottom of the screen in fullscreen, as per your mention. I feel your idea would be a great solution to this issue and definitely better than my own proposal. -- You are receiving this mail because: You are watching all bug changes.