[kwin] [Bug 399375] Default Window Actions Modifier Key is ALT and it breaks Krita's ALT modifier
https://bugs.kde.org/show_bug.cgi?id=399375 --- Comment #17 from Martin Flöser --- I just did some research: the first window manager (twm) already uses the pattern of modifier+click to move a window (see for example: https://www.oreilly.com/library/view/x-window-system/9780937175149/Chapter03.html#ch3-06 ). According to it's documentation it uses the meta modifier. I'm not sure what is really meant by this as today's keyboards don't have a meta key. The best I found is: https://en.m.wikipedia.org/wiki/Meta_key Most likely that transferred to alt as keyboards in the beginning 90ies neither had a meta nor a Windows key. In old X speak windows is not the meta key, but super or hyper. I did this research out of personal interest as I didn't know why KWin has that binding. Now we see it is as old as X11 window managers which means it predates the digital painting industry. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397726] Error on install
https://bugs.kde.org/show_bug.cgi?id=397726 --- Comment #21 from n...@nickme.com --- I confirm, it's magically fixed in one of the recent builds. No error on install, no error on run. It did reset all my preferences and setup however. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399375] Default Window Actions Modifier Key is ALT and it breaks Krita's ALT modifier
https://bugs.kde.org/show_bug.cgi?id=399375 --- Comment #16 from Martin Flöser --- Guys, I don't care about industry standards. I can show 10 different industry standards. The only thing you present here is "my industry standard is more important than all other users". That's not a position from where we can start. It's not about who got the shortcut first or for whom it is more important. It's about how can we both use it. The behavior in KWin is also an industry standard- an X11 Standard, an Unix Standard. David already mentioned openbox, I throw in fluxbox (http://fluxbox.org/help/man-fluxbox.php) as an example for an even older window manager. Also Compiz (http://wiki.compiz.org/CommonKeyboardShortcuts) uses it and has also a shortcut for meta+lmb defined. The thing is: we are both right, it is our industry standard and we have both the right and the need for it. Asking you to change won't work, asking us to change won't work. So can we please stop the absolute position about KWin being wrong and has to change? Good, thank you! We are not going to worsen the user experience for the needs of a subgroup of users. You are not the only group of users demanding that their field is more important than all others. We cannot suite all and still have a good product. The problem is not that we use Alt. The problem is that modifier clicks can not be taken by the application. We can work on that but it'll require Krita to change code. If you are not willing to adapt Krita than we can stop the discussion. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395179] Global menu getting outside of screen
https://bugs.kde.org/show_bug.cgi?id=395179 --- Comment #5 from Sebastian Krzyszkowiak --- Forgot to mention: I'm using version 5.13.90 right now, but it was already happening for at least a few releases. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395179] Global menu getting outside of screen
https://bugs.kde.org/show_bug.cgi?id=395179 --- Comment #4 from Sebastian Krzyszkowiak --- I can confirm on X11. Also, the same issue happens with long menus and nested submenus even when the button is on the left side. Hiding the submenu and making it reappear causes it to show up correctly next time. I've attached a video showing the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395179] Global menu getting outside of screen
https://bugs.kde.org/show_bug.cgi?id=395179 Sebastian Krzyszkowiak changed: What|Removed |Added CC||d...@dosowisko.net --- Comment #3 from Sebastian Krzyszkowiak --- Created attachment 115436 --> https://bugs.kde.org/attachment.cgi?id=115436=edit Global menu going off the screen with long menus. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399430] New: Dolphin: Places: Regression: Move items up/down not working properly
https://bugs.kde.org/show_bug.cgi?id=399430 Bug ID: 399430 Summary: Dolphin: Places: Regression: Move items up/down not working properly Product: dolphin Version: 18.08.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: places Assignee: dolphin-bugs-n...@kde.org Reporter: dev...@t-online.de Target Milestone: --- SUMMARY When I try to to move folders down/up in places (drag) it gets reset or nothing happens. STEPS TO REPRODUCE 1. Add folder to places by right click a folder and select "Add to places". 2. Try to move them down/up by drag 3. OBSERVED RESULT Either nothing happens/or moved to the false position; not there where a "blue line/bar" is shown. EXPECTED RESULT Moving Folders in "Places" up/down to the right position. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.0 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION Using KDE Neon git stable. Dolphin: 18.08.2 https://i.imgur.com/AHpZYVz.png -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 399429] New: Okular should pull duplex option from printer driver defaults
https://bugs.kde.org/show_bug.cgi?id=399429 Bug ID: 399429 Summary: Okular should pull duplex option from printer driver defaults Product: okular Version: 1.5.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: sb56...@gmail.com Target Milestone: --- Hi there, I print a lot of PDF documents, sometimes I print duplex and sometimes I print single-sided. I have multiple printer configurations set up in CUPS with the duplex setting enable or disabled according to the task. Okular requires me to manually set the duplexing option. I feel that it should use the printer's defined default for duplexing. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 399428] New: Marble crashes on trying to download OpenStreetMap data
https://bugs.kde.org/show_bug.cgi?id=399428 Bug ID: 399428 Summary: Marble crashes on trying to download OpenStreetMap data Product: marble Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: nat...@degruchy.org Target Milestone: --- Application: marble (2.2.20 (2.3 development version)) Qt Version: 5.11.2 Frameworks Version: 5.50.0 Operating System: Linux 4.18.12-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Trying to download the OSM data for my area using the Marble tool. -- Backtrace: Application: Marble Virtual Globe (marble), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f449b9c9880 (LWP 13265))] Thread 15 (Thread 0x7f44331ff700 (LWP 15062)): #0 0x7f44a3866ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f44a78255fd in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f44a781d024 in () at /usr/lib/libQt5Core.so.5 #3 0x7f44a7824f65 in () at /usr/lib/libQt5Core.so.5 #4 0x7f44a3860a9d in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f44a74eda43 in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f4430c8a700 (LWP 15060)): #0 0x7f44a2c2b69b in () at /usr/lib/libglib-2.0.so.0 #1 0x7f44a2c2b872 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #2 0x7f44a2c2ce86 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f44a2c2cfce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f44a7a25fe4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f44a79d18cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f44a781aeb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f44a7824f65 in () at /usr/lib/libQt5Core.so.5 #8 0x7f44a3860a9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f44a74eda43 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7f44414e1700 (LWP 15039)): #0 0x7f44a3866ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f44a78255fd in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f44a781d024 in () at /usr/lib/libQt5Core.so.5 #3 0x7f44a7824f65 in () at /usr/lib/libQt5Core.so.5 #4 0x7f44a3860a9d in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f44a74eda43 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f441700 (LWP 15017)): #0 0x7f44a74e2bb1 in poll () at /usr/lib/libc.so.6 #1 0x7f44a2c2cee0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f44a2c2cfce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f44a7a25fe4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f44a79d18cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f44a781aeb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f44a93c9ed1 in () at /usr/lib/libmarblewidget-qt5.so.28 #7 0x7f44a7824f65 in () at /usr/lib/libQt5Core.so.5 #8 0x7f44a3860a9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f44a74eda43 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f443148b700 (LWP 14001)): #0 0x7f44a2bdb3a9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f44a2c2c608 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f44a2c2ce06 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f44a2c2cfce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f44a7a25fe4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f44a79d18cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f44a781aeb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f44a7824f65 in () at /usr/lib/libQt5Core.so.5 #8 0x7f44a3860a9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f44a74eda43 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f443248d700 (LWP 13571)): #0 0x7f44a3866afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f44a7685cd1 in __gthread_cond_wait (__mutex=, __cond=) at /build/gcc/src/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu/bits/gthr-default.h:864 #2 0x7f44a7685cd1 in std::condition_variable::wait(std::unique_lock&) (this=, __lock=...) at /build/gcc/src/gcc/libstdc++-v3/src/c++11/condition_variable.cc:53 #3 0x7f44a501a7cf in WTF::ParkingLot::parkConditionally(void const*, std::function, std::function, std::chrono::time_point > >) () at
[Breeze] [Bug 399307] Variant of drive-harddisk that indicates "I'm the disk for the operating system/the root partition"
https://bugs.kde.org/show_bug.cgi?id=399307 --- Comment #3 from Nate Graham --- And the root disk icon should be named `drive-harddisk-root`. An icon for a home directory volume should be named `drive-harddisk-home`. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399375] Default Window Actions Modifier Key is ALT and it breaks Krita's ALT modifier
https://bugs.kde.org/show_bug.cgi?id=399375 --- Comment #15 from Tyson Tan --- There are things I would like to clarify: 1) THIS IS NOT FOR KRITA I reported this bug, not because we are trying to push change for Krita's sake. I and David Revoy here are sharing the common sense of how Modifier keys operates on OS/DE in general. Our sincere intention here is to help you to improve the user experience for KDE Plasma. 2) THE COMMON SENSE We consider this to be a problem on kwin's side. Because what kwin has been doing is NOT COMMON SENSE. The COMMON SENSE and INDUSTRY STANDARD, as David Revoy mentioned: Ctrl/Shift/Alt should be reserved only for applications. This has been implemented since the dawn of of GUI and kwin is the one at odd here. kwin's taking away of the ALT key for window action goes against everything we have been using with a GUI. Only Plasma is doing it differently, and this is not what a sane people expect from a good desktop experience. 3) WHY SHOULDN'T KRITA CHANGE, BUT KWIN kwin's reservation of ALT for window actions is hitting every application outside of KDE, and not limited to applications outside of KDE. Those being hit are those adopted the INDUSTRIAL STANDARD and COMMON-SENSE. The more powerful they are, the harder they are hit. The applications we used for examples include Krita, GIMP, Inkscape, Blender. These are the NAMECARDS of the whole FOSS world. It delivers a clear message when they ONLY have problems under KDE Plasma, and the said problems CRIPPLES their CORE functionalities. If Krita should be the one to change, then EVERY application that adopt to this COMMON SENSE, this industry standard of modifier key arrangement should add rules specifically made for kwin. kwin is a special case in the grand scheme of things, not Krita, not GIMP/Inkscape/Blender/etc. And as a result, Krita shouldn't change, neither should GIMP, Inkscape nor Blener, etc. 4) THE SHORTTERM SOLUTION YOU PROPOSED I understand your proposal. I'm not a programmer so I don't know even what you mentioned is doable. But for now, let's assume it can be implemented. Then what? You have quieted one loudest scream that's closest to you. But what about everything else? Is this shortterm solution (implemented by Krita, although it is really a kwin issue) going to give you a false sense of security? What about those disgruntled users who can't reach you because they don't know what and where to report? While the status quo goes on, I wonder why people are so reluctant to adopt KDE Plasma as their daily DE. Missing ALT for whatever productivity applications they are using must be one of them. 5) WE CARE ABOUT KDE When a certain application has KDE Plasma specific compatibility issues like this, and by any luck it was reported to those projects as a bug, they will be for certain marked as UPSTREAM or NOT-OUR-BUG. Those information are rarely being relayed to you. We care because we are involved in KDE and we don't want to stand there watching it goes down a path that turns people away. 6) JUST DROP WINDOW ACTION SHORTCUTS BY DEFAULT Why do we even need to use ALT as a shortcut to move our window? Is it this important? Can't we just click on the titlebar and drag it around? It doesn't make any sense! My shortterm solution is to add a NONE option to window action and make it as default. 7) THE RESPONSIBLE SETTINGS ARE TOO HARD TO FIND The option to turn it off is hidden way too deep and hard to find, causing the learning curve to be insanely steep. If anything, at least change how the options are presented. Most people could not figure out how to change kwin's ALT to META, or in fact, figure out what is happening at all. So what do they do? They go back to the last other OS/DE they use and they will be more reluctant to try KDE Plasma for another time. I have been retrying KDE every year, only ending in retreat, only because I am involved in KDE community. Normal people would leave for good after their first or second disappointment. 8) IN THE END This discussion is for kwin and thus for KDE Plasma. This is not for Krita. We are not trying to make Krita works better under KDE Plasma. We are trying to help KDE Plasma works better for the majority of applications. I'm not saying you MUST do what I suggested here, but I do believe I and David Revoy have shared valuable information. We explained the context, history, and our perspective circling this problem. I hope you have read and digested our words carefully and thoroughly. I do hope in the coming years of maintaining kwin, our shared knowledge can help you make your decision wisely. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 399427] New: How to configure the fonts and background color of the "preview of rendered R Markdown"
https://bugs.kde.org/show_bug.cgi?id=399427 Bug ID: 399427 Summary: How to configure the fonts and background color of the "preview of rendered R Markdown" Product: rkward Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: rkward-de...@kde.org Reporter: adleyv...@gmail.com Target Milestone: --- SUMMARY My desktop environment is GNOME and using the dark themes "Adwaita-dark". I found that, the results of the function "preview R markdown" can't read. It is because the themes "Adwaita-dark" forces all the background to black. However, the default font color of the preview also in black. Are there any ways to configure the font color of the "preview R markdown" ? Thanks. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION ---Problem description--- Please fill in the missing bits *in English*. Please give a brief summary on the problem: ###Please fill in### What - in detail - did you do directly before you encountered this problem? ###Please fill in### When you try to repeat the above, does the problem occur again (no, sometimes, always)? ###Please fill in### If applicable: When doing the same thing in an R session outside of RKWard, do you see the same problem? ###Please fill in### Do you have any further information that might help us to track this problem down? In particular, if applicable, can you provide sample data and sample R code to reproduce this problem? ###Please fill in### RKWard is available in many different packagings, and sometimes problems are specific to one method of installation. How did you install RKWard (which file(s) did you download)? ###Please fill in### ---Session Info--- -- Frontend -- RKWard version: 0.7.0z+0.7.1+devel1 KDE Frameworks version (runtime): 5.48.0 KDE Frameworks version (compile time): 5.48.0 Qt version (runtime): 5.11.1 Local config directory: /home//.config RKWard storage directory: /home//.rkward/ Backend version (as known to the frontend): 3.5.1 Debug message file (this may contain relevant diagnostic output in case of trouble): /tmp/rkward.frontend -- Backend -- Debug message file (this may contain relevant diagnostic output in case of trouble): /tmp/rkward.rbackend R version (compile time): 3.5.1 (2018-07-02 r74947) R runtime session info: R version 3.5.1 (2018-07-02) Platform: x86_64-redhat-linux-gnu (64-bit) Running under: Fedora 28 (Workstation Edition) Matrix products: default BLAS: /usr/lib64/R/lib/libRblas.so LAPACK: /usr/lib64/R/lib/libRlapack.so locale: [1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C [3] LC_TIME=en_US.UTF-8 LC_COLLATE=en_US.UTF-8 [5] LC_MONETARY=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 [7] LC_PAPER=en_US.UTF-8 LC_NAME=en_US.UTF-8 [9] LC_ADDRESS=en_US.UTF-8LC_TELEPHONE=en_US.UTF-8 [11] LC_MEASUREMENT=en_US.UTF-8LC_IDENTIFICATION=en_US.UTF-8 attached base packages: [1] stats graphics grDevices utils datasets methods base other attached packages: [1] rkward_0.7.1 loaded via a namespace (and not attached): [1] compiler_3.5.1 tools_3.5.1 -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 245741] wish to be able to move pulseaudio recording-streams to "monitor [soundcardname]" like in pavucontrol
https://bugs.kde.org/show_bug.cgi?id=245741 S changed: What|Removed |Added CC||sb56...@gmail.com --- Comment #5 from S --- Created attachment 115435 --> https://bugs.kde.org/attachment.cgi?id=115435=edit pavucontrol record from monitor I would also find this very useful. It would be nice to have a list of sources, including the monitor for the master recording device and for individual recording streams. The screenshot shows it in pavucontrol, and it would probably look almost identical in the Plasma volume widget and in the KCM. Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[docs] [Bug 399426] New: Display and Monitor Conpositor documentation missing from Help Menu
https://bugs.kde.org/show_bug.cgi?id=399426 Bug ID: 399426 Summary: Display and Monitor Conpositor documentation missing from Help Menu Product: docs Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Missing Content Assignee: kde-doc-engl...@kde.org Reporter: deano_ferr...@hotmail.com Target Milestone: --- SUMMARY No Compositor help information present in KDE Plasma 5 (v 5.12.6) documentation. I did find KDE 4 documentation that is largely still applicable and could be incorporated? https://userbase.kde.org/Desktop_Effects_Performance#OpenGL_mode STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399425] New: Missing and inconsistent DjVu icons
https://bugs.kde.org/show_bug.cgi?id=399425 Bug ID: 399425 Summary: Missing and inconsistent DjVu icons Product: Breeze Version: 5.13.5 Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: agram...@gmail.com CC: kain...@gmail.com Target Milestone: --- Problems: (1) Breeze( Dark) is missing icons for media type image/vnd.djvu+multipage (DjVu documents), leading to files with that type displaying the image/x-generic icon. (2) The colours for both 64px image/vnd.djvu Breeze and Breeze Dark differ from their smaller icons' colours. (3) Breeze Dark's 64px image/vnd.djvu has a folded top-right corner, but Breeze's version does not. The 32px versions of each theme also do not have this folded corner. Possible solution: (1) New image/vnd.djvu+multipage icons are added, that have binding lines (as seen in the pdf and epub icons) and no folded corners. (2) The colours for the image/vnd.djvu icons are all matched up (I think the 32px icon has the closest colour to the official icon [1], but it's a little off). (3) The 32px/64px image/vnd.djvu icons icons all have folded top-right corners, but no binding lines. I think it would be nice if the image/vnd.djvu+multipage icons also got a new design. Perhaps including a paper clip as in [1]? References: [1] https://upload.wikimedia.org/wikipedia/commons/thumb/9/98/Djvu_icon.svg/64px-Djvu_icon.svg.png -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 342003] Trim margins confuses ordering of zoom steps while zooming out
https://bugs.kde.org/show_bug.cgi?id=342003 --- Comment #5 from jimbo1qaz --- I'm not a maintainer, but I've done some digging and I think this is the issue. void PageView::updateItemSize( PageViewItem * item, int colWidth, int rowHeight ) - defines Okular::Page *page - okularPage->width() and okularPage->height() reflect the "uncropped unzoomed" dimensions of the page (in some units, IDK). - finds the unzoomed dimensions - if cropping enabled, crops them (multiplying by Okular::NormalizedRect[0,1] coordinates) (cropped unzoomed dimensions) - multiplies by the zoom factor - calls PageViewItem::setWHZC(cropped_w, cropped_h) with cropped w,h. - PageViewItem::setWHZC sets m_croppedGeometry. - PageViewItem::setWHZC divides by crop boundaries and sets m_uncroppedGeometry --- // compute the zoom factor value for FitWidth and FitPage mode double PageView::zoomFactorFitMode( ZoomMode mode ) - const double width = okularPage->width(), height = okularPage->height(); This is the bug. width()/height() are uncropped, but FitWidth and FitPage end up zooming the cropped page region. We need to use the cropped unzoomed dimensions. But they are not exposed by the code, instead buried as local variables within PageView::updateItemSize(), and overwritten by the cropped zoomed versions when calling PageViewItem::setWHZC. Consequently, currentItem->croppedWidth()/croppedHeight() is not a proper workaround. How should this bug be fixed? --- Sidenote: Why is Okular written in Qt-flavored C++03 without std::? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399393] show the total size of all packages with dependencies
https://bugs.kde.org/show_bug.cgi?id=399393 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 397242] Baloo gets confused when a file is renamed over existing one
https://bugs.kde.org/show_bug.cgi?id=397242 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 397242] Baloo gets confused when a file is renamed over existing one
https://bugs.kde.org/show_bug.cgi?id=397242 Nate Graham changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|1 |0 Status|RESOLVED|REPORTED --- Comment #2 from Nate Graham --- Whoops, it appears that this is actually fixed with https://phabricator.kde.org/D15944, which I forgot I was testing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385814] Some icons removed from the favorites list is back when plasma session is restarted
https://bugs.kde.org/show_bug.cgi?id=385814 Dr. Chapatin changed: What|Removed |Added CC||s...@mauch.me --- Comment #31 from Dr. Chapatin --- *** Bug 399413 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385814] Some icons removed from the favorites list are back when plasma session is restarted
https://bugs.kde.org/show_bug.cgi?id=385814 Dr. Chapatin changed: What|Removed |Added Summary|Some icons removed from the |Some icons removed from the |favorites list is back when |favorites list are back |plasma session is restarted |when plasma session is ||restarted -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399413] Kate reappearing in kicker favorites every login
https://bugs.kde.org/show_bug.cgi?id=399413 Dr. Chapatin changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #1 from Dr. Chapatin --- *** This bug has been marked as a duplicate of bug 385814 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 397242] Baloo gets confused when a file is renamed over existing one
https://bugs.kde.org/show_bug.cgi?id=397242 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Nate Graham --- This appears to be working now with Baloo 5.51. -- 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 Dr. Chapatin changed: What|Removed |Added CC||smelly...@gmail.com --- Comment #29 from Dr. Chapatin --- *** Bug 399411 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 399411] crashes on close
https://bugs.kde.org/show_bug.cgi?id=399411 Dr. Chapatin changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com --- Comment #1 from Dr. Chapatin --- *** This bug has been marked as a duplicate of bug 383127 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399424] New: loading of saved workspace overrides primary and secondary colors
https://bugs.kde.org/show_bug.cgi?id=399424 Bug ID: 399424 Summary: loading of saved workspace overrides primary and secondary colors Product: krita Version: nightly build (please specify the git hash!) Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: b...@fastmail.com Target Milestone: --- SUMMARY krita-4.1.3-1 krita-4.2.0-pre-alpha-c365356-x86_64.appimage Tested with fresh configuration (removing existing ~/.local/share/krita, ~/.config/krita*) STEPS TO REPRODUCE 1. New document (ctrl+n) 2. Change primary color to something else, in this case: gray 3. Create and save a new workspace: Top right button > name "test" > save 4. Switch to another workspace (Default) 5. Change primary color to something else, in this case: black 6. Switch to "test" workspace OBSERVED RESULT Primary and secondary colors are switched to pure white, though sometimes retain the color that was active during the workspace save. EXPECTED RESULT Keep the colors that are active prior to workspace switch Do not save active color when workspace is saved (if it is) SOFTWARE VERSIONS Qt Version: 5.11.2-1 ADDITIONAL INFORMATION This is disruptive to workflow because the current active colors are lost. It may be desirable to switch between 2 similar workspaces often, like between animation and regular painting. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 158647] changes on "entitätattribut" changes the attributes also on an copy
https://bugs.kde.org/show_bug.cgi?id=158647 Ralf Habacker changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||ralf.habac...@freenet.de --- Comment #4 from Ralf Habacker --- bug ist still present in 2.26.0 (KDE Applications 18.08.0) -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 151510] relations misplaced after deleting an existing one
https://bugs.kde.org/show_bug.cgi?id=151510 Ralf Habacker changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||2.26.0 Status|REPORTED|RESOLVED CC||ralf.habac...@freenet.de --- Comment #1 from Ralf Habacker --- > You should see that the remaining arrow is mis-placed. Not sure, what you are refering to. With version 2.26.0 the remaining arrow does not change it's position. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 399416] [Qt5.12]Plasma-pa opens in top left corner
https://bugs.kde.org/show_bug.cgi?id=399416 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from David Edmundson --- Fixed in 5.12 latest -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399415] [Qt5.12]Plasma wayland session crashes when attempting to open any app
https://bugs.kde.org/show_bug.cgi?id=399415 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org --- Comment #2 from Antonio Rojas --- please test kwin 5.13.90-2 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 355768] The design of the saved file is lost
https://bugs.kde.org/show_bug.cgi?id=355768 Ralf Habacker changed: What|Removed |Added Summary|Se pierde el diseño del |The design of the saved |archivo guardado. |file is lost CC||ralf.habac...@freenet.de --- Comment #1 from Ralf Habacker --- Translated with www.DeepL.com/Translator: When I create and design my use case diagram. After closing and opening it, the location of the objects is lost (I have to move them again to understand the diagram). Playable: Sometimes Steps to Reproduce: 1. I create, save and close the file. 2. I open, but most of the elements are put on top of each other. It is not the design created. 3. Actual Results: The file does not show the original design. Expected Results: Open and maintain the original design. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399423] New: Regressions with glide effect
https://bugs.kde.org/show_bug.cgi?id=399423 Bug ID: 399423 Summary: Regressions with glide effect Product: kwin Version: 5.13.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: l...@hotmail.com.br Target Milestone: --- There are some undesirable differences with the earlier version: 1 - Currently it's too similar with the scale effect. The window should appear/disappear from an infinite distance perspective. 2 - Default is too fast. 3 - When the max distance is chosen, the window still seem to appear from a close distance and not 100% transparent. It's not smooth. 4 - Same when max negative distance is chosen, it's not smooth 5 - It's not clear in the settings what the max and min values are. A slider is more adequate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399415] [Qt5.12]Plasma wayland session crashes when attempting to open any app
https://bugs.kde.org/show_bug.cgi?id=399415 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from David Edmundson --- Backtrace needed. Also please try with kwin as of midday today. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 399202] Shortcut "Alt+º" stop working on KDE neon 18.04
https://bugs.kde.org/show_bug.cgi?id=399202 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |MOVED --- Comment #2 from Christoph Feck --- Reported as bug 399402. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 336397] Getting "Unknown error code 150" when opening USB connected Android device in MTP mode
https://bugs.kde.org/show_bug.cgi?id=336397 jbf changed: What|Removed |Added Platform|Kubuntu Packages|Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383255] iOS device shows up as two cameras in Device Notifier
https://bugs.kde.org/show_bug.cgi?id=383255 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #9 from Nate Graham --- It's just two instances of /usr/share/solid/actions/solid_camera.desktop, which come from: $ dpkg -S /usr/share/solid/actions/solid_camera.desktop kamera: /usr/share/solid/actions/solid_camera.desktop Also, setting this to CONFIRMED because Kai told me he can reproduce it over chat this morning. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 336397] Getting "Unknown error code 150" when opening USB connected Android device in MTP mode
https://bugs.kde.org/show_bug.cgi?id=336397 jbf changed: What|Removed |Added CC||jbfm...@rochester.rr.com --- Comment #9 from jbf --- Same behavior in MTP & Camera mode. Rebooted laptop after initial failure, but encountered further errors with no file transfer. I can provide dmesg output if needed. See list of installed software below: Here's the error messages: Unknown error code 150 Bad parameters Please send a full bug report at http://bugs.kde.org. camera:/Samsung%2520Galaxy%2520models%2520(MTP)@usb:003,008 Galaxy 7 Phone Fedora 28, up-to-date mtp:/SAMSUNG-SM-G930V/ The process for the mtp protocol died unexpectedly. List of installed kio software: kf5-kio-widgets-5.48.0-1.fc28.x86_64 audiocd-kio-doc-16.08.3-6.fc28.noarch kio_mtp-0.75-17.20141221gitc418634.fc28.x86_64 audiocd-kio-16.08.3-6.fc28.x86_64 kf5-kio-gui-5.48.0-1.fc28.x86_64 kf5-kio-file-widgets-5.48.0-1.fc28.x86_64 kf5-kio-core-5.48.0-1.fc28.x86_64 kio-upnp-ms-1.0.0-13.2002git.fc28.x86_64 kf5-kio-ntlm-5.48.0-1.fc28.x86_64 kf5-kio-doc-5.48.0-1.fc28.noarch kf5-kio-widgets-libs-5.48.0-1.fc28.x86_64 audiocd-kio-libs-16.08.3-6.fc28.x86_64 kf5-kio-core-libs-5.48.0-1.fc28.x86_64 kio-extras-18.04.3-1.fc28.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 394230] Listpopupmenu needs refactoring
https://bugs.kde.org/show_bug.cgi?id=394230 --- Comment #12 from Ralf Habacker --- Git commit 6cb829c7d474edeb4073b385daa6cdad9853ca22 by Ralf Habacker. Committed on 05/10/2018 at 23:25. Pushed by habacker into branch 'master'. Refactor adding menu entries from action collection M +22 -26 umbrello/menus/listpopupmenu.cpp M +1-0umbrello/menus/listpopupmenu.h https://commits.kde.org/umbrello/6cb829c7d474edeb4073b385daa6cdad9853ca22 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 399422] New: kmymoney Crash when importing OFX file
https://bugs.kde.org/show_bug.cgi?id=399422 Bug ID: 399422 Summary: kmymoney Crash when importing OFX file Product: kmymoney Version: 5.0.0 Platform: RedHat RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: thierry.rouil...@laposte.net Target Milestone: --- Kmymoney is normaly open.. kmymoney WebConnect: Starting server failed. Try to remove stale socket. WebConnect: Running in server mode libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile some color defects but it does not matter if i'm importing a ofx file : LibOFX INFO: libofx_proc_file(): File format not specified, autodetecting... (Above message occured on Line 18446744073709551615, Column 18446744073709551615) LibOFX INFO: libofx_proc_file(): Detected file format: OFX (Open Financial eXchange (OFX or QFX)) (Above message occured on Line 18446744073709551615, Column 18446744073709551615) /usr/include/c++/8/bits/basic_string.h:1048: std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::reference std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::operator[](std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::size_type) [with _CharT = char; _Traits = std::char_traits; _Alloc = std::allocator; std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::reference = char&; std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::size_type = long unsigned int]: Assertion '__pos <= size()' failed. Aborted (core dumped) it's systematic SOFTWARE VERSIONS 5.00 (available in About System) Kernel: 4.18.10-200.fc28.x86_64 x86_64 bits: 64 Desktop: KDE Plasma 5.13.4 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399421] Debian binary package icon uses the deprecated media type name
https://bugs.kde.org/show_bug.cgi?id=399421 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399421] Debian binary package icon uses the deprecated media type name
https://bugs.kde.org/show_bug.cgi?id=399421 --- Comment #1 from Alex --- > SUMMARY > The icon used for .deb files is named application-x-deb, which has been > deprecated for several years. The new name[1] is vnd.debian.binary-package. > > I propose renaming the application-x-deb files to vnd.debian.binary-package > and adding symlinks from the deprecated name to the current name. Typo: vnd.debian.binary-package -> application-vnd.debian.binary-package -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399421] New: Debian binary package icon uses the deprecated media type name
https://bugs.kde.org/show_bug.cgi?id=399421 Bug ID: 399421 Summary: Debian binary package icon uses the deprecated media type name Product: Breeze Version: 5.13.5 Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: agram...@gmail.com CC: kain...@gmail.com Target Milestone: --- SUMMARY The icon used for .deb files is named application-x-deb, which has been deprecated for several years. The new name[1] is vnd.debian.binary-package. I propose renaming the application-x-deb files to vnd.debian.binary-package and adding symlinks from the deprecated name to the current name. STEPS TO REPRODUCE 1. Open a folder containing a .deb file in Dolphin. OBSERVED RESULT The icon presented for the .deb file is package-x-generic.svg. EXPECTED RESULT Icon used for the .deb file is the icon for debian packages (application-x-deb). SOFTWARE VERSIONS KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.49.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION [1] https://www.iana.org/assignments/media-types/application/vnd.debian.binary-package -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399371] offline update whitelist
https://bugs.kde.org/show_bug.cgi?id=399371 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399370] offline update state stability
https://bugs.kde.org/show_bug.cgi?id=399370 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 394230] Listpopupmenu needs refactoring
https://bugs.kde.org/show_bug.cgi?id=394230 --- Comment #11 from Ralf Habacker --- Git commit 4af37ad57f6622f49fb0ebe2a874b19c9cec5f00 by Ralf Habacker. Committed on 05/10/2018 at 22:15. Pushed by habacker into branch 'master'. Fix adding ports to components on component diagram M +11 -0umbrello/menus/widgetbasepopupmenu.cpp M +15 -0umbrello/umlwidgets/umlwidget.cpp https://commits.kde.org/umbrello/4af37ad57f6622f49fb0ebe2a874b19c9cec5f00 --- Comment #10 from Ralf Habacker --- Git commit a8dbaba8164ff1660e4fdfcf7c961f0fd6dd2b76 by Ralf Habacker. Committed on 05/10/2018 at 22:15. Pushed by habacker into branch 'master'. Fix adding subsystem from context menu to component diagrams M +1-0umbrello/menus/umlscenepopupmenu.cpp M +12 -0umbrello/umlscene.cpp https://commits.kde.org/umbrello/a8dbaba8164ff1660e4fdfcf7c961f0fd6dd2b76 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 393188] Add feature to add connected note
https://bugs.kde.org/show_bug.cgi?id=393188 --- Comment #4 from Ralf Habacker --- Git commit f5c5fb642044de93bc5cea951b84452c32ceb5f5 by Ralf Habacker. Committed on 05/10/2018 at 22:15. Pushed by habacker into branch 'master'. Add support for adding connected actors and use cases to sequence diagrams M +18 -0umbrello/umlwidgets/umlwidget.cpp https://commits.kde.org/umbrello/f5c5fb642044de93bc5cea951b84452c32ceb5f5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399349] destructive square created on layer rarely when using sliders
https://bugs.kde.org/show_bug.cgi?id=399349 --- Comment #4 from b...@fastmail.com --- Created attachment 115434 --> https://bugs.kde.org/attachment.cgi?id=115434=edit 2 squares Here is the example from today with 2 squares. Didn't capture the moment it happened. One of them fixed itself after painting over an erased section with the background color. It does not seem related to a square brush as like in the previous clip, as this one was without. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399349] destructive square created on layer rarely when using sliders
https://bugs.kde.org/show_bug.cgi?id=399349 --- Comment #3 from b...@fastmail.com --- Created attachment 115433 --> https://bugs.kde.org/attachment.cgi?id=115433=edit live moment of occurrence Here is an example from 2 months ago, it happened right when pressing 'ctrl+u', didn't notice until after. HSV slider window is hidden due to it only capturing Krita window. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 396435] emoji rendering broken
https://bugs.kde.org/show_bug.cgi?id=396435 --- Comment #23 from Martin Hostettler --- (In reply to Mariusz Glebocki from comment #22) > (In reply to Martin Hostettler from comment #21) > > tangent: > > I think in the long run we need some way for applications to download the > > actually used width mapping from the terminal to get decent interoperability > > across versions and different machines in a network. I just notices that > > emoji joining is yet another aspect that needs to be kept in sync between > > terminal and the application. > > There is already POSIX solution which could solve that - wcwidth() and > wcswidth(). The latter could even calculate widths of joined emojis. Sadly, > it works differently on every platform. And there are separate > implementations in Go, Python, etc. > This is why terminals and console programs sometimes try to make its own > table which works the same (or at least is up to date) on every platform. > > Or, if someone likes hacks, LD_PRELOAD=libkonsole_wcwidth.so ;) Well if that would be the solution konsole would just use it, right? But: * There's the private use area. Only a component with access to the font can know what would look right for these characters. (Or the user could configure that, i'm sure most users don't want to do that manually) * width mapping is a moving target as long as unicode evolves. With the current release cycle even a fast moving target. * Rendering breaks badly when values in the terminal and the client application don't match. (that happens to every terminal with a up to date table) * the usage of ssh with terminals means that connections will span systems with differently outdated libraries. * LD_PRELOAD hacks are not really a sustainable solution. For me that sounds a lot like there needs to be a single point of truth in every terminal session. As long as things move faster than installations update and there is no standard all stakeholders can agree on (and UAX #11 explicitly disclaims being for "modern terminal emulators") there needs *some* way for applications to get this information. From the terminals i looked at only urxvt really buys in to "trust the system libc". And konsole, vte and xterm (i have to assume) intentionally diverge from what libc does. I think from the perspective of a client library the equivalent of roughly one full screen update with a decently sized terminal in data transfer would be an quite attractive trade of ;) -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 57349] Wrong behaviour on repeated pressing operator buttons
https://bugs.kde.org/show_bug.cgi?id=57349 Albert Astals Cid changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kca ||lc/b0ce4ff01b5e1f7f4c2340b9 ||0f326491437c076c --- Comment #23 from Albert Astals Cid --- Git commit b0ce4ff01b5e1f7f4c2340b90f326491437c076c by Albert Astals Cid, on behalf of Maximilian Schiller. Committed on 05/10/2018 at 21:09. Pushed by aacid into branch 'master'. Corrected behaviour on repeated pressing of operator buttons Summary: Fixes "wrong" behavior to the correct one as described in the bug report. Before the fix pressing "10 * / 5 =" normally would result in 20 (Stack: (10,*), (10,/), (5,=)) but with those changes it results in 2 (Stack: (10, /), (5, =)). Internally this is achieved by "blocking" node adding after a operator (*,-,/,...) has been pressed until a number is entered. If another operator is pressed whilst blocked the top (last) operator is changed instead. Reviewers: cfeck, teran, #kde_applications Reviewed By: cfeck Subscribers: aacid, cfeck, kde-utils-devel Differential Revision: https://phabricator.kde.org/D15463 M +3-1kcalc.cpp M +17 -3kcalc_core.cpp M +3-0kcalc_core.h https://commits.kde.org/kcalc/b0ce4ff01b5e1f7f4c2340b90f326491437c076c -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399402] The shortcut "Alt + º", in spanish keyboard, stops working in KDE neon 18.04
https://bugs.kde.org/show_bug.cgi?id=399402 BugCoder changed: What|Removed |Added Summary|The keyboard shortcut "Alt |The shortcut "Alt + º", in |+ º" stops working in KDE |spanish keyboard, stops |neon 18.04 |working in KDE neon 18.04 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 395641] plasma-redshift-control manual mouse wheel control broken with recent redshift version
https://bugs.kde.org/show_bug.cgi?id=395641 Matthias changed: What|Removed |Added CC||shaloksha...@protonmail.ch --- Comment #2 from Matthias --- Its still not applied. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 394659] crash after compilation
https://bugs.kde.org/show_bug.cgi?id=394659 --- Comment #13 from manuel fernández --- I am trying to perform what you mentioned but now I cannot compile. when I run: cmake -DCMAKE_INSTALL_PREFIX:PATH=/tmp/usr -DCMAKE_BUILD_TYPE=release ../kbibtex I get the following error: CMake Error at CMakeLists.txt:23 (find_package): Could not find a package configuration file provided by "ECM" (requested version 5.19) with any of the following names: ECMConfig.cmake ecm-config.cmake Add the installation prefix of "ECM" to CMAKE_PREFIX_PATH or set "ECM_DIR" to a directory containing one of the above files. If "ECM" provides a separate development package or SDK, be sure it has been installed. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399324] Scrolling changes sliders, list widgets, and numeric fields, causing unintentional changes to controls on scrollable views
https://bugs.kde.org/show_bug.cgi?id=399324 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Component|general |general Product|kde |Breeze Summary|Mouse wheel changes |Scrolling changes sliders, |sliders, list widgets, and |list widgets, and numeric |numeric fields |fields, causing ||unintentional changes to ||controls on scrollable ||views Keywords||usability CC||n...@kde.org Status|REPORTED|CONFIRMED Assignee|unassigned-b...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399401] some installed programs are shown twice
https://bugs.kde.org/show_bug.cgi?id=399401 --- Comment #1 from Nate Graham --- Reported originally reported the same thing last year: Bug 380138 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 377694] Apps listed twice
https://bugs.kde.org/show_bug.cgi?id=377694 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=399401 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 397881] Duplicate items in Discover
https://bugs.kde.org/show_bug.cgi?id=397881 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=399401 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399401] some installed programs are shown twice
https://bugs.kde.org/show_bug.cgi?id=399401 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=380138, ||https://bugs.kde.org/show_b ||ug.cgi?id=377694, ||https://bugs.kde.org/show_b ||ug.cgi?id=397881 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 396435] emoji rendering broken
https://bugs.kde.org/show_bug.cgi?id=396435 --- Comment #22 from Mariusz Glebocki --- (In reply to Martin Hostettler from comment #21) > About the hangul: Konsole before this change did display NFD in a way that > looked correct to my untrained eye. After this change decomposed forms are > displayed as 1 wide and 2 narrow characters. At least OS X uses NFD for file > names, so i would expect that these decomposed forms will end up in places > where konsole will encounter them. Wow, I didn't know that. I'll send a patch which will change the widths to allow characters to compose. > For the regional indicator symbols: Those are a whole new bag of fun. I > wonder how other terminals handle emoji joining... > > glibc and glib (vte) consider them narrow. Unifont and Noto consider them > wide. And what users actually want to see is two of them joined together to > be a flag(supported in Noto seems to be 2 cells wide, not supported in > unifont). Konsole see two of them as 2 wide characters (i.e. 4 cells). > Interesting enough kitty displays a flag which is 4 cells wide. Not sure how > expected that is. > I wonder how much sense it makes to deviate from what glibc says when the > actual display is really not that great anyway (for flags / regional > indicator symbols). Nice idea in kitty. Looks as intended, but is still width-compatible (assuming each indicator is wide). Since glib(c) assume the indicators are narrow, it could be possible to display one wide flag and keep compatibility with wcwidth-using software (i.e. everything in ncurses, shells). It would work on FreeBSD too (wcwidth works only for 16 bit code points, higher CPs are narrow). Not sure how it would work on macOS. > I'm worried about proliferation of lots of slightly different width mapping > functions that applications *somehow* have to know about. > > tangent: > I think in the long run we need some way for applications to download the > actually used width mapping from the terminal to get decent interoperability > across versions and different machines in a network. I just notices that > emoji joining is yet another aspect that needs to be kept in sync between > terminal and the application. There is already POSIX solution which could solve that - wcwidth() and wcswidth(). The latter could even calculate widths of joined emojis. Sadly, it works differently on every platform. And there are separate implementations in Go, Python, etc. This is why terminals and console programs sometimes try to make its own table which works the same (or at least is up to date) on every platform. Or, if someone likes hacks, LD_PRELOAD=libkonsole_wcwidth.so ;) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380138] packages shown twice
https://bugs.kde.org/show_bug.cgi?id=380138 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=399401 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 399395] Use the saved file instead of tmp one after it has been saved for exporting
https://bugs.kde.org/show_bug.cgi?id=399395 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||n...@kde.org Keywords||junior-jobs, usability --- Comment #1 from Nate Graham --- Yeah, this has tripped me up as well. Essentially, when the user chooses "Export > [app or 'other application...']", spectacle should save the file to the default save location instead of to the /tmp directory. It should continue to use the /tmp directory for other Export operations. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 387672] baloo_file_extractor crashes in Baloo::PostingDB::put()
https://bugs.kde.org/show_bug.cgi?id=387672 Nate Graham changed: What|Removed |Added CC||raku...@outlook.com --- Comment #29 from Nate Graham --- *** Bug 399407 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 399407] Baloo crashes after each reboot.
https://bugs.kde.org/show_bug.cgi?id=399407 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE CC||n...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 387672 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399371] offline update whitelist
https://bugs.kde.org/show_bug.cgi?id=399371 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399370] offline update state stability
https://bugs.kde.org/show_bug.cgi?id=399370 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399377] dolphin incorrectly complains that systemd noauto,x-systemd.automount mounts must be mounted as root
https://bugs.kde.org/show_bug.cgi?id=399377 Nate Graham changed: What|Removed |Added Summary|dolphin & systemd |dolphin incorrectly |noauto,x-systemd.automount |complains that systemd ||noauto,x-systemd.automount ||mounts must be mounted as ||root CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399382] Description text in Application Launcher sometimes appears as cubes
https://bugs.kde.org/show_bug.cgi?id=399382 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||n...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- Are you using NVIDIA hardware and proprietary drivers? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396961] Empty space on interface on thumbnail view
https://bugs.kde.org/show_bug.cgi?id=396961 Andrius changed: What|Removed |Added CC||aegor...@gmail.com --- Comment #17 from Andrius --- The issue is still there. http://digikam.1695700.n4.nabble.com/digiKam-users-Space-reserved-for-Thumbbar-td4706924.html -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 399384] Baloo File Indexing Daemon crashes
https://bugs.kde.org/show_bug.cgi?id=399384 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Nate Graham --- Without a backtrace, we cannot triage this bug. See https://community.kde.org/Get_Involved/Bug_Reporting#Crash_reports_must_include_backtraces -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399393] show the total size of all packages with dependencies
https://bugs.kde.org/show_bug.cgi?id=399393 Nate Graham changed: What|Removed |Added Keywords||usability Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||n...@kde.org --- Comment #1 from Nate Graham --- I agree. Even if there's no exact way to know the size of an *installed* app due to shared dependencies, there is indeed a way to know the size of an app plus the new dependencies that need to be installed, which answers the question, "how much extra space will be taken up if I install this thing?" The answer is, "The size of the app package plus the size of the new dependencies that need to be installed" -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 387672] baloo_file_extractor crashes in Baloo::PostingDB::put()
https://bugs.kde.org/show_bug.cgi?id=387672 Nate Graham changed: What|Removed |Added Summary|Baloo File Extraction Error |baloo_file_extractor ||crashes in ||Baloo::PostingDB::put() -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 387672] Baloo File Extraction Error
https://bugs.kde.org/show_bug.cgi?id=387672 Nate Graham changed: What|Removed |Added CC||jvap...@yahoo.com --- Comment #28 from Nate Graham --- *** Bug 399391 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 399391] file indexer keeps crashing
https://bugs.kde.org/show_bug.cgi?id=399391 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE CC||n...@kde.org Status|REPORTED|RESOLVED --- Comment #2 from Nate Graham --- *** This bug has been marked as a duplicate of bug 387672 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 399380] XDG Portal support for KRun
https://bugs.kde.org/show_bug.cgi?id=399380 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399420] New: Dolphin crashes when moving files to SMB mounted NTFS drive
https://bugs.kde.org/show_bug.cgi?id=399420 Bug ID: 399420 Summary: Dolphin crashes when moving files to SMB mounted NTFS drive Product: dolphin Version: 18.08.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: carl.w.bai...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (18.08.1) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.15.0-36-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: - What I was doing when the application crashed: Moving files from my local drive (ext4) to a SMB mounted drive on a windows share (NTFS) using split view in dolphin - Unusual behavior I noticed: The file was actually copied even though the error mentioned a permissions issue. When I hit "retry" it said the original file does not exist, so it actually moved the file over but triggered the error message anyway. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8b5e3a5c80 (LWP 9582))] Thread 5 (Thread 0x7f8b2976b700 (LWP 9587)): #0 0x7f8b5dc24bf9 in __GI___poll (fds=0x7f8b200049b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f8b50695439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8b5069554c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8b57e0ea9b in QEventDispatcherGlib::processEvents (this=0x7f8b2b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f8b57db2dea in QEventLoop::exec (this=this@entry=0x7f8b2976ada0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7f8b57bddb8a in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7f8b57be8aab in QThreadPrivate::start (arg=0x557c632c3cc0) at thread/qthread_unix.cpp:367 #7 0x7f8b52a7d6db in start_thread (arg=0x7f8b2976b700) at pthread_create.c:463 #8 0x7f8b5dc3188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f8b324a7700 (LWP 9586)): #0 0x7f8b52a839f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x557c62effb48) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x557c62effaf8, cond=0x557c62effb20) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x557c62effb20, mutex=0x557c62effaf8) at pthread_cond_wait.c:655 #3 0x7f8b3caf746b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7f8b3caf7197 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7f8b52a7d6db in start_thread (arg=0x7f8b324a7700) at pthread_create.c:463 #6 0x7f8b5dc3188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f8b33cde700 (LWP 9585)): #0 0x7f8b52a839f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x557c630bf444) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x557c630bf3f0, cond=0x557c630bf418) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x557c630bf418, mutex=0x557c630bf3f0) at pthread_cond_wait.c:655 #3 0x7f8b3caf746b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7f8b3caf7197 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7f8b52a7d6db in start_thread (arg=0x7f8b33cde700) at pthread_create.c:463 #6 0x7f8b5dc3188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f8b3fb67700 (LWP 9584)): #0 0x7f8b5dc24bf9 in __GI___poll (fds=0x7f8b3801b0e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f8b50695439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8b5069554c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8b57e0ea9b in QEventDispatcherGlib::processEvents (this=0x7f8b38000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f8b57db2dea in QEventLoop::exec (this=this@entry=0x7f8b3fb66d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7f8b57bddb8a in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7f8b58256e45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f8b57be8aab in QThreadPrivate::start (arg=0x7f8b584ced60) at thread/qthread_unix.cpp:367 #8 0x7f8b52a7d6db in start_thread (arg=0x7f8b3fb67700) at pthread_create.c:463 #9 0x7f8b5dc3188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f8b5e3a5c80 (LWP 9582)): [KCrash Handler] #6 0x7f8b59782a84 in KJob::isAutoDelete (this=this@entry=0x557c638f2550)
[frameworks-kio] [Bug 279664] [KRun] Use EFF's rule set from HTTPS Everywhere
https://bugs.kde.org/show_bug.cgi?id=279664 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Summary|Use EFF's rule set from |[KRun] Use EFF's rule set |HTTPS Everywhere|from HTTPS Everywhere Product|kio |frameworks-kio Status|NEEDSINFO |REPORTED Component|http|general Assignee|kdelibs-b...@kde.org|fa...@kde.org CC||kdelibs-b...@kde.org --- Comment #4 from Nate Graham --- Thanks for the info. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397726] Error on install
https://bugs.kde.org/show_bug.cgi?id=397726 --- Comment #20 from Maik Qualmann --- Windows 10-1809 October Update is officially released. I have created a new VM and digiKam-6.0.0-beta1 runs without problems here. Maik -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 279664] Use EFF's rule set from HTTPS Everywhere
https://bugs.kde.org/show_bug.cgi?id=279664 --- Comment #3 from Thomas Fischer --- (In reply to Nate Graham from comment #1) > This is for Konqueror, or just in general? It should apply to all HTTP queries and may be handled on a similar level like proxy settings. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 394659] crash after compilation
https://bugs.kde.org/show_bug.cgi?id=394659 Thomas Fischer changed: What|Removed |Added Status|REOPENED|ASSIGNED --- Comment #12 from Thomas Fischer --- Something I missed earlier: your KBibTeX instance does not just crash because it starts, but because it opens a file at startup (or tries at least). Please locate and open in a text editor your kbibtexrc in your home directory or underneath /tmp/usr (open both if both exist). There should be sections starting with [DocumentList- The key-value pairs contain among others BibTeX filenames. If possible, send me those .bib files for inspection. You can remove the section [DocumentList-Open] if you want to remove all of KBibTeX's knowledge on previously opened files. KBibTeX will start without opening any files and should not crash. Then try to open one of the BibTeX files that were previously in the configuration files and see if KBibTeX then crashes again. -- You are receiving this mail because: You are watching all bug changes.
[bindings] [Bug 263715] wallpaper night/day settings segfaults on selection
https://bugs.kde.org/show_bug.cgi?id=263715 Lucas Yamanishi changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399419] New: Show Painting Assistants toggle is inconsistent between windows
https://bugs.kde.org/show_bug.cgi?id=399419 Bug ID: 399419 Summary: Show Painting Assistants toggle is inconsistent between windows Product: krita Version: 4.1.3 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tool/Assistants Assignee: krita-bugs-n...@kde.org Reporter: aut...@autumnlansing.com Target Milestone: --- When working with multiple windows, toggling the "View > Show Painting Assistants" option becomes confused as to which state each window is in and show inconsistencies. Toggling off the option on one window to hide the assistants (unchecking the menu option) and then switching to another window where the assistants are not hidden resets the toggle's checkmark in the menu to a global checked state. Switching back to the first window, where the assistants have been hidden, displays the checkmark in the menu next to the option though the assistants themselves are still hidden. Unchecking the option in that state, which one assumes would hide the assistants, shows the assistants instead. The checkmark in the menu ends up being very confusing as you can't rely on its state to tell if the option is off or on. If it makes a difference, I heavily use sessions. STEPS TO REPRODUCE 1. Create several windows with painting assistants in each. 2. Toggle off assistants in one window 3. Switch to a second window with assistants not hidden 4. Switch back to the first window with the hidden assistants. 3. Observe the state of the toggle checkmark versus the visible state of the assistants. OBSERVED RESULT The toggle checkmark does not consistently match the visibility state. EXPECTED RESULT The checkmark should be consistent for each window, showing when the assistants are visible in the window and not showing when they're hidden. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399349] destructive square created on layer rarely when using sliders
https://bugs.kde.org/show_bug.cgi?id=399349 --- Comment #2 from b...@fastmail.com --- (In reply to Boudewijn Rempt from comment #1) > "From observation/memory, this has happened only under i3wm/compton. It may > be unrelated to Krita in that case?" > > On the face of it, that would seem unlikely. If you save and load the > document, is the square still there? Happened again and can confirm. There were actually 2 this time, and one fixed itself. Square remains even after closing and loading, and also closing Krita. It's part of the file. However, it doesn't have the same behavior as the first video, it is just part of the layer now once opening. Will do more testing and a video later. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 398652] Add possibility to change the order of opened tabs if only two tabs are opened
https://bugs.kde.org/show_bug.cgi?id=398652 --- Comment #2 from Shubham --- Steps to reproduce: 1. Open 2 tabs in kate 2. Try to select any one tab to interchange it's position with the other tab. Expected result: Tabs should interchange their positions(As it happens in case of more than 2 tabs) Actual result: Nothing happens -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398626] Media controls became invisible but still work
https://bugs.kde.org/show_bug.cgi?id=398626 --- Comment #8 from mthw0 --- (In reply to mthw0 from comment #4) > OP: Qt 5.11.1, Arch Linux, Breeze Light + Breeze AlphaBlack Also Qt5.12-beta1 -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 399418] New: The new 'artwork view' could use an animation
https://bugs.kde.org/show_bug.cgi?id=399418 Bug ID: 399418 Summary: The new 'artwork view' could use an animation Product: elisa Version: 0.3.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: jari...@hotmail.com Target Milestone: --- Some kind of slide would be nice -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399417] New: [Qt5.12]App dashboard launcher show no search results
https://bugs.kde.org/show_bug.cgi?id=399417 Bug ID: 399417 Summary: [Qt5.12]App dashboard launcher show no search results Product: plasmashell Version: 5.13.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jari...@hotmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 ...altough pressing Enter launches the app that would have been found at first place. STEPS TO REPRODUCE 1. Open app dashboard (the fullscreen app launcher) 2. type a name of any app OBSERVED RESULT Middle space where search results are shown is always empty. EXPECTED RESULT Search results are shown. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.90 KDE Frameworks Version: 5.50 Qt Version: 5.12-beta1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 399416] [Qt5.12]Plasma-pa opens in top left corner
https://bugs.kde.org/show_bug.cgi?id=399416 mthw0 changed: What|Removed |Added CC||jari...@hotmail.com Keywords||wayland --- Comment #1 from mthw0 --- Wayland only... -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 399416] New: [Qt5.12]Plasma-pa opens in top left corner
https://bugs.kde.org/show_bug.cgi?id=399416 Bug ID: 399416 Summary: [Qt5.12]Plasma-pa opens in top left corner Product: plasma-pa Version: 5.13.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: jari...@hotmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY ...instead of its correct position STEPS TO REPRODUCE 1. Start plasma-wayland session 2. open plasma-pa OBSERVED RESULT Plasma-pa is shown in top left corner EXPECTED RESULT Plasma-pa should be shown on its correct position in bottom right corner. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.90 KDE Frameworks Version: 5.50 Qt Version: 5.12-beta1 ADDITIONAL INFORMATION The same happens with plasma-nm -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399415] New: [Qt5.12]Plasma wayland session crashes when attempting to open any app
https://bugs.kde.org/show_bug.cgi?id=399415 Bug ID: 399415 Summary: [Qt5.12]Plasma wayland session crashes when attempting to open any app Product: plasmashell Version: 5.13.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: jari...@hotmail.com Target Milestone: 1.0 1. Start Plasma Wayland session 2. Try to open any app either from taskbar or by keyboard shortcut OBSERVED RESULT Plasma Wayland crashes (SDDM shows up) or whole computeer freezes (black screen no response) EXPECTED RESULT Plasma won't crash SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.90 KDE Frameworks Version: 5.50 Qt Version: 5.12-beta1 ADDITIONAL INFORMATION Plasma probably has to be rebuilt with Qt 5.12 to work propertly. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399414] New: Discover krashes
https://bugs.kde.org/show_bug.cgi?id=399414 Bug ID: 399414 Summary: Discover krashes Product: Discover Version: 5.13.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: ribe...@gmail.com Target Milestone: --- Application: plasma-discover (5.13.5) Qt Version: 5.11.2 Frameworks Version: 5.50.0 Operating System: Linux 4.14.72-1-lts x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: Search whatever or just scroll applications list. My distro is Arch linux, lts kernel The crash can be reproduced every time. -- Backtrace: Application: Центр программ Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1c890c7800 (LWP 1064))] Thread 12 (Thread 0x7f1c5a4dc700 (LWP 1082)): #0 0x7f1c8e13bbb1 in poll () at /usr/lib/libc.so.6 #1 0x7f1c8c980ee0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1c8c980fce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f1c8e664fe4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1c8e6108cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f1c8e459eb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f1c8e463f65 in () at /usr/lib/libQt5Core.so.5 #7 0x7f1c8d404a9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f1c8e146a43 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f1c5adef700 (LWP 1076)): #0 0x7f1c8e13bbb1 in poll () at /usr/lib/libc.so.6 #1 0x7f1c8c980ee0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1c8c981f62 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #3 0x7f1c5beb8c28 in () at /usr/lib/libgio-2.0.so.0 #4 0x7f1c8c94a3eb in () at /usr/lib/libglib-2.0.so.0 #5 0x7f1c8d404a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f1c8e146a43 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f1c5b5f0700 (LWP 1075)): #0 0x7f1c8e13bbb1 in poll () at /usr/lib/libc.so.6 #1 0x7f1c8c980ee0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1c8c980fce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f1c8c981022 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f1c8c94a3eb in () at /usr/lib/libglib-2.0.so.0 #5 0x7f1c8d404a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f1c8e146a43 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f1c74bc0700 (LWP 1074)): #0 0x7f1c8d40aef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1c8e4645fd in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f1c8e45c024 in () at /usr/lib/libQt5Core.so.5 #3 0x7f1c8e463f65 in () at /usr/lib/libQt5Core.so.5 #4 0x7f1c8d404a9d in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f1c8e146a43 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f1c753c1700 (LWP 1073)): [KCrash Handler] #6 0x7f1c8d9d1ca4 in () at /usr/lib/libQt5Network.so.5 #7 0x7f1c8d9d059b in () at /usr/lib/libQt5Network.so.5 #8 0x7f1c8e63c352 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #9 0x7f1c8f427e14 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #10 0x7f1c8f42f6e1 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #11 0x7f1c8e611c39 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x7f1c8e614ccc in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #13 0x7f1c8e6659d4 in () at /usr/lib/libQt5Core.so.5 #14 0x7f1c8c97f3cf in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #15 0x7f1c8c980f89 in () at /usr/lib/libglib-2.0.so.0 #16 0x7f1c8c980fce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #17 0x7f1c8e664fc9 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #18 0x7f1c8e6108cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #19 0x7f1c8e459eb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #20 0x7f1c8e463f65 in () at /usr/lib/libQt5Core.so.5 #21 0x7f1c8d404a9d in start_thread () at /usr/lib/libpthread.so.0 #22 0x7f1c8e146a43 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f1c75bc2700 (LWP 1072)): #0 0x7f1c8e137734 in read () at /usr/lib/libc.so.6 #1 0x7f1c8c92f781 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1c8c97fa50 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f1c8c980e86 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f1c8c980fce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5
[plasmashell] [Bug 399413] New: Kate reappearing in kicker favorites every login
https://bugs.kde.org/show_bug.cgi?id=399413 Bug ID: 399413 Summary: Kate reappearing in kicker favorites every login Product: plasmashell Version: 5.13.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: s...@mauch.me CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 115432 --> https://bugs.kde.org/attachment.cgi?id=115432=edit Kate in Kicker favorite list SUMMARY Kate keeps reappearing in the Kicker favorites after every login. I never placed it there. STEPS TO REPRODUCE 1. Open Kicker 2. Remove Kate from favorite list 3. Logout 4. Login 5. Kate is in the favorite list again SOFTWARE VERSIONS KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION Happens on both my machines, one of which was freshly installed with Plasma 5.13.x -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 399318] Asks for password for WPA/TKIP network multiple times when it's already in KWallet (with PAM)
https://bugs.kde.org/show_bug.cgi?id=399318 --- Comment #8 from Filipe Azevedo --- Also, as noted, i'm using a mac book machine, the wifi driver does not seems in a very good shape, so maybe it does not help as well. I was not having the issue as well on a non apple machine. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 399318] Asks for password for WPA/TKIP network multiple times when it's already in KWallet (with PAM)
https://bugs.kde.org/show_bug.cgi?id=399318 --- Comment #7 from Filipe Azevedo --- There is no master password set on teh wallet so no password is being asked for that. The distribution comes with a pam wallet configuration, so i guess the wallet is being opened upon login. I did not tried to kill kded, but i can try to have a look at it in the next days. The work around i used previously no longer works, was just working by chance. The thing that just works reliably is to bypass kwallet entirely by using the network connection preference and create the connection on my own, using a non encrypted password for all users, not using auto connection. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399375] Default Window Actions Modifier Key is ALT and it breaks Krita's ALT modifier
https://bugs.kde.org/show_bug.cgi?id=399375 --- Comment #14 from Martin Flöser --- To make it quite clear: I'm totally open to improve the situation. I'm not open to change the default shortcut. As I said: changing the default shortcut doesn't fix the problem. It just shifts it somewhere else. Yes, it's the easy fix. But I don't like easy fixes. Those are mostly wrong and do more harm than good. What I like is analyze the situation and improve. What Krita needs is the possibility to tell the window manager which modifier+mouse shortcut it needs and the window manager should honor it. That is an important feature and very important in the light of Wayland where KWin supports modifier+mouse shortcuts in general and not just the alt+lmb as currently. We can work on making an universal solution which suits both Krita and KWin and many more applications. It needs that we stick our heads together and think about how this can be done. And yes that would require Krita to also add code. Nevertheless what I proposed as a short term solution is sane and can be easily done: just check whether the window manager is KWin (dbus service org.kde.KWin) open kwinrc, read the correct value and pop up a dialog "hey your window manger uses alt to move the window. This breaks our foo feature. Do you want to change it to windows key?" On yes, change the kconfig emit the dbus call for kwin to reload the config and call it a day. That are less than 100 lines of code and can be written in less than half an hour. And the mechanism is totally fine, that's just how kwin's config works. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399406] Digikam Crash on advance rename
https://bugs.kde.org/show_bug.cgi?id=399406 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- I can not reproduce the problem on Linux or Windows. But maybe we had a double deletion of a class here. We will see it with the next update. Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399368] Height of the window is resized when moving between screens
https://bugs.kde.org/show_bug.cgi?id=399368 --- Comment #5 from Martin Flöser --- Please try to align your screens on the left and test whether that changes the behavior. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399406] Digikam Crash on advance rename
https://bugs.kde.org/show_bug.cgi?id=399406 --- Comment #1 from Maik Qualmann --- Git commit 6bba3f447aa3ee11924e08529ccdde1fad5ad557 by Maik Qualmann. Committed on 05/10/2018 at 16:50. Pushed by mqualmann into branch 'master'. we do not need the ImageViewUtilities here M +1-2core/app/items/imageviewutilities.cpp M +8-1core/libs/database/utils/dio.cpp M +1-1core/libs/database/utils/dio.h M +3-7core/utilities/advancedrename/advancedrenameprocessdialog.cpp https://commits.kde.org/digikam/6bba3f447aa3ee11924e08529ccdde1fad5ad557 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 398969] Show previews not working in Ubuntu 18.04, XFCE 4
https://bugs.kde.org/show_bug.cgi?id=398969 Viktor changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 398969] Show previews not working in Ubuntu 18.04, XFCE 4
https://bugs.kde.org/show_bug.cgi?id=398969 --- Comment #3 from Viktor --- Thank you! This solved the problem, indeed. I was searching everywhere, couldn't find a solution. I hope this would help other people. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 399412] New: KRunner crash when using Calculator
https://bugs.kde.org/show_bug.cgi?id=399412 Bug ID: 399412 Summary: KRunner crash when using Calculator Product: krunner Version: 5.13.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: kopper.patr...@gmail.com Target Milestone: --- Application: krunner (5.13.5) Qt Version: 5.11.2 Frameworks Version: 5.50.0 Operating System: Linux 4.18.10-zen1-1-zen x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I often use KRunner to do simple maths while working inother applications. Occasionally, KRunner freezes for about 5 seconds seemingly trying to calculate the result, then crashes. Immediately restarting KRunner performs the calculation normally. I have yet failed to discern any pattern to this crashes, all of them happen with basic math (no root, ln, etc.). The crash can be reproduced sometimes. -- Backtrace: Application: krunner (krunner), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcd030d3840 (LWP 3338))] Thread 20 (Thread 0x7fccaa7fc700 (LWP 10958)): #0 0x7fcd08d73afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcd0a3b771c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fccf33be469 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fccf33c2339 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fccf33bd52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fccf33c0389 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fcd0a3b6f65 in () at /usr/lib/libQt5Core.so.5 #7 0x7fcd08d6da9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fcd0a099a43 in clone () at /usr/lib/libc.so.6 Thread 19 (Thread 0x7fccaaffd700 (LWP 10957)): #0 0x7fcd08d73afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcd0a3b771c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fccf33be469 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fccf33c2339 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fccf33bd52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fccf33c0389 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fcd0a3b6f65 in () at /usr/lib/libQt5Core.so.5 #7 0x7fcd08d6da9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fcd0a099a43 in clone () at /usr/lib/libc.so.6 Thread 18 (Thread 0x7fccab7fe700 (LWP 10956)): #0 0x7fcd08d73afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcd0a3b771c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fccf33be469 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fccf33c2339 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fccf33bd52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fccf33c0389 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fcd0a3b6f65 in () at /usr/lib/libQt5Core.so.5 #7 0x7fcd08d6da9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fcd0a099a43 in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7fccabfff700 (LWP 10955)): #0 0x7fcd08d73afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcd0a3b771c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fccf33be469 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fccf33c2339 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fccf33bd52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fccf33c0389 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fcd0a3b6f65 in () at /usr/lib/libQt5Core.so.5 #7 0x7fcd08d6da9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fcd0a099a43 in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7fccd4ff9700 (LWP 10954)): #0 0x7fcd08d73afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcd0a3b771c in
