[plasmashell] [Bug 370180] New: Widgets moved to secondary monitor upon reboot
https://bugs.kde.org/show_bug.cgi?id=370180 Bug ID: 370180 Summary: Widgets moved to secondary monitor upon reboot Product: plasmashell Version: 5.8.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: rnd...@nm.ru CC: plasma-b...@kde.org When i upgraded to 5.8 all widgets/panels from my left (primary) monitor get moved to the right (secondary) monitor after reboot. Secondary monitor is not even on. Some widget settings also reset like panel being able to go behind window. Reproducible: Always Steps to Reproduce: 1. Place widgets/panels on the primary (left) screen 2. Reboot Actual Results: Widgets/panels end up on secondary monitor that is also turned off. Expected Results: Widgets should remain on the screen they were placed on. Similar issue existed on 5.7, however it was the other way around: widgets/panels moved to secondary screen were moved back to primary screen upon reboot. Screens are placed one next to another: [DVI-0 2560x1080][VGA-0 1920x1080] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360333] New system tray: icons do not scale with panel height, stay very small
https://bugs.kde.org/show_bug.cgi?id=360333 Jens Reuterberg changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #18 from Jens Reuterberg --- (In reply to Marco Martin from comment #6) > this bug is pretty much mutually exclusive with > https://bugs.kde.org/show_bug.cgi?id=353834 > I fear icons are either going to be too big for some people or too small for > some other people (and i don't want to add a configure icon size ui) I guess that any variant will rub some people wrong. We simply can't account for all tastes and any change will make one group or another angry. The question is: which group do we want to piss off, or do we accept the problems that come with such a configuration UI. Also if Guillame is correct above, that HiDPI screens make the icons stick to 16x16, that's the main issue since that would make them close to unusable. One solution would be to create a third size of 32x32 icons and simply skip to that size when the panel is resized to something that could accomade them. But that means recreating the icon theme (so its pixel aligned) and that will take a while (IIRC only a few of the panel icons exists in 32x32) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 370181] New: partiotionmanager crashes while opening and scaning device /dev/sda
https://bugs.kde.org/show_bug.cgi?id=370181 Bug ID: 370181 Summary: partiotionmanager crashes while opening and scaning device /dev/sda Product: neon Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: hrvo...@jankovci.net CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org When I run 'sudo /usr/bin/partiotionmanager' it opens and throws a message 'scaning device /dev/sda'. After that it crashes with a message in terminal 'QFileInfo::absolutePath: Constructed with empty filename' and 'terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted Reproducible: Always Steps to Reproduce: 1. run sudo /usr/bin/partiotionmanager 2.opens with a message 'scaning device /dev/sda' 3.crashes with a message terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted Actual Results: Crashes every time Expected Results: Opening Kpartiotion manager Kde Mint 18, KDE Plasma 5.6.5 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 369852] xea2kmt does not import account flags
https://bugs.kde.org/show_bug.cgi?id=369852 --- Comment #1 from Ralf Habacker --- Git commit 3495037aef2d98af340e905943a95b02612816ff by Ralf Habacker. Committed on 06/10/2016 at 07:07. Pushed by habacker into branch '4.8'. xea2kmt: Parse and export gnucash account flag 'tax-related'. KMymoney supports the account flag 'Tax' indicating that the related account is tax related. When enabled with --with-tax-related on xea2kmt command line the gnucash related xml tag 'tax-related' will be exported to the kmt file as as child of he related account. Signed-off-by: Ralf Habacker M +63 -7tools/xea2kmt.cpp http://commits.kde.org/kmymoney/3495037aef2d98af340e905943a95b02612816ff -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370182] Panel pushes out widget settings to second screen
https://bugs.kde.org/show_bug.cgi?id=370182 --- Comment #1 from rnd...@nm.ru --- Created attachment 101441 --> https://bugs.kde.org/attachment.cgi?id=101441&action=edit Image depicting the problem -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370182] New: Panel pushes out widget settings to second screen
https://bugs.kde.org/show_bug.cgi?id=370182 Bug ID: 370182 Summary: Panel pushes out widget settings to second screen Product: plasmashell Version: 5.8.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: rnd...@nm.ru CC: plasma-b...@kde.org If i have a panel on left side of the screen it will push widget settings panel to secondary screen of the right. Reproducible: Always Steps to Reproduce: 1. Have two-screen setup with screens placed side-by-side. 2. Create panel on the left screen, left side of screen and make it always visible 3. Create panel on the bottom of the left screen 4. Open panel settings of the bottom panel Actual Results: Settings panel sticks out to the screen on the right. Expected Results: Settings panel should be contained in the screen it was opened on. Picture will be attached in next post. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360333] New system tray: icons do not scale with panel height, stay very small
https://bugs.kde.org/show_bug.cgi?id=360333 rnd...@nm.ru changed: What|Removed |Added CC||rnd...@nm.ru --- Comment #19 from rnd...@nm.ru --- Reality is that screen sizes are increasing, not decreasing, and downscaled icon looks better than upscaled. If plasma wants to be future-proof then you kind of have to have icons in bigger size available. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 370183] New: Deleted folder reappears on next kmail2 session
https://bugs.kde.org/show_bug.cgi?id=370183 Bug ID: 370183 Summary: Deleted folder reappears on next kmail2 session Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: bingmyb...@btinternet.com You can happily delete an empty folder but as soon as run kmail2 again, that "deleted" folder reappears. Reproducible: Always Steps to Reproduce: 1. Highlight empty folder (below "Local Folders") 2. Delete via menu option 3. Delete confirmed and successful 4. Exit kmail2 5. reload kmail2 6. Deleted folder is present Actual Results: The Deleted folder is back in the folder list below "Local Folders" Expected Results: The deleted folder to stay deleted -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 370183] Deleted folder reappears on next kmail2 session
https://bugs.kde.org/show_bug.cgi?id=370183 --- Comment #1 from BingMyBong --- Version Information opensuse:tumbleweed:20161003 Qt: 5.7.0 KDE Frameworks: 5.26.0 KDE Plasma: 5.7.4 kwin5-5.7.4-1.3.x86_64 kmail5-16.08.1-1.2.x86_64 Kernel: 4.7.5-1-default -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360333] New system tray: icons do not scale with panel height, stay very small
https://bugs.kde.org/show_bug.cgi?id=360333 --- Comment #20 from Dainius Masiliūnas --- (In reply to Jens Reuterberg from comment #18) > I guess that any variant will rub some people wrong. We simply can't account > for all tastes and any change will make one group or another angry. The > question is: which group do we want to piss off, or do we accept the > problems that come with such a configuration UI. > Also if Guillame is correct above, that HiDPI screens make the icons stick > to 16x16, that's the main issue since that would make them close to > unusable. Or, you know, make use of the thing KDE is renowned for: configuration options. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 370184] New: Existing Filter search value field gets deleted when clicking on it
https://bugs.kde.org/show_bug.cgi?id=370184 Bug ID: 370184 Summary: Existing Filter search value field gets deleted when clicking on it Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: bingmyb...@btinternet.com Currently the field containing the data to compare against does not display the contents fully so if you click on the right hand side of the data in the box to see what is there, the data is immediately deleted so you cannot see what was there. Reproducible: Always Steps to Reproduce: 1. Select Filter rules 2. Select exiting filter 3. Select a data field where the data is larger than the display area 4. Click on the right hand side of the data in the box 5. The contents of the is deleted Actual Results: Depending where you click in the data box when the contents exceed the displayable area, the content will be deleted, i.e. on the far right of the data - see attachments Expected Results: You should be able to click anywhere in the data entry area to view existing contents -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 370184] Existing Filter search value field gets deleted when clicking on it
https://bugs.kde.org/show_bug.cgi?id=370184 --- Comment #1 from BingMyBong --- Created attachment 101443 --> https://bugs.kde.org/attachment.cgi?id=101443&action=edit Shows area before any changes 1. Before any changes Display of 3 out of the 4 data entry areas are larger than the displayable area -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 370184] Existing Filter search value field gets deleted when clicking on it
https://bugs.kde.org/show_bug.cgi?id=370184 --- Comment #2 from BingMyBong --- Created attachment 101444 --> https://bugs.kde.org/attachment.cgi?id=101444&action=edit Data area display after clicking in box 2. Clicked on right hand side of data in 3rd box - data cleared -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 370184] Existing Filter search value field gets deleted when clicking on it
https://bugs.kde.org/show_bug.cgi?id=370184 --- Comment #3 from BingMyBong --- Created attachment 101445 --> https://bugs.kde.org/attachment.cgi?id=101445&action=edit Display of data field to show data field diaplay area not large enough 3. Click on left hand side of data and move cursor to the left to show data display area stops in the middle of the box -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370185] New: On task switcher (Informative, Breeze, Compact,..) can not control switching with arrow keys
https://bugs.kde.org/show_bug.cgi?id=370185 Bug ID: 370185 Summary: On task switcher (Informative, Breeze, Compact,..) can not control switching with arrow keys Product: plasmashell Version: master Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: b...@i-creativ.net CC: plasma-b...@kde.org On some task switcher themes, after Alt+Tab (and holding Alt) I can switch the tasks back and forward by pushing arrow keys. Such themes are "Cover Switch" and "Flip Switch". But on themes like "Informative" or "Compact" this is not possible. Reproducible: Always Steps to Reproduce: 1. Choose "Informative" as task switcher theme. Set Alt+Tab as a primary forward shortcut. 2. Open few random app windows. 3. Push Alt+Tab, to switch the tasks. While holding Alt, push Arrow Up key. (Nothing happens.) 4. Change the task switcher theme to "Flip Switch" and repeat the upper. (It works, the tasks are switched on Arrow key while holding Alt). Actual Results: Arrow keys work only on Flip Switch theme. Expected Results: Arrow keys to work on all available task switcher themes. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 370160] System Load Viewer with Circular Mode: Gaps between circles are too large
https://bugs.kde.org/show_bug.cgi?id=370160 --- Comment #1 from Bastian Beischer --- Possibly related error messages from my journalctl: plasmashell[6708]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:79: TypeError: Cannot read property of null plasmashell[6708]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:79: TypeError: Cannot read property of null plasmashell[6708]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:253: TypeError: Cannot read property 'value' of undefined -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370030] Digital Clock is too wide on smaller panels
https://bugs.kde.org/show_bug.cgi?id=370030 --- Comment #1 from Bastian Beischer --- Possibly related from my journalctl: plasmashell[6708]: file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:443:5: QML Text: Cannot anchor to a null item -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370185] On task switcher (Informative, Breeze, Compact,..) can not control switching with arrow keys
https://bugs.kde.org/show_bug.cgi?id=370185 Eike Hein changed: What|Removed |Added CC||h...@kde.org --- Comment #1 from Eike Hein --- Unrelated to Task Manager, reassigning. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370185] On task switcher (Informative, Breeze, Compact,..) can not control switching with arrow keys
https://bugs.kde.org/show_bug.cgi?id=370185 Eike Hein changed: What|Removed |Added Target Milestone|1.0 |--- Component|Task Manager|tabbox Product|plasmashell |kwin Version|master |unspecified Assignee|h...@kde.org|kwin-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370163] Regression: can no longer mouse-scroll through windows in a group.
https://bugs.kde.org/show_bug.cgi?id=370163 --- Comment #2 from Eike Hein --- Can't reproduce it on my system. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 370186] New: Dolphin crashed on right-click for list-menu options
https://bugs.kde.org/show_bug.cgi?id=370186 Bug ID: 370186 Summary: Dolphin crashed on right-click for list-menu options Product: dolphin Version: 15.12.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: admon@gmail.com Application: dolphin (15.12.3) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.7.5-100.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - Unusual behavior I noticed: Error kde connect init: Error al cargar archivo QML: file:///usr/share/plasma/plasmoids/org.kde.kdeconnect/contents/ui/main.qml:24:1: plugin cannot be loaded for module "org.kde.kdeconnect": Cannot load library /usr/lib64/qt5/qml/org/kde/kdeconnect/libkdeconnectdeclarativeplugin.so: (/usr/lib64/qt5/qml/org/kde/kdeconnect/libkdeconnectdeclarativeplugin.so: undefined symbol: _ZTI21DevicesSortProxyModel) The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6febe43940 (LWP 2630))] Thread 4 (Thread 0x7f6fe254c700 (LWP 2631)): #0 0x7f6ffb324b7d in poll () at /lib64/libc.so.6 #1 0x7f6ff7519272 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f6ff751aee7 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f6fe528a039 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f6ffbf2f00c in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f6ff8ec261a in start_thread () at /lib64/libpthread.so.0 #6 0x7f6ffb3305fd in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f6fe1198700 (LWP 2632)): #0 0x7f6ff69b7794 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7f6ff6972a09 in g_main_context_query () at /lib64/libglib-2.0.so.0 #2 0x7f6ff6973107 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f6ff697329c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f6ffc119b5b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f6ffc0ca25a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f6ffbf2abd4 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f6ffc31e675 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #8 0x7f6ffbf2f00c in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f6ff8ec261a in start_thread () at /lib64/libpthread.so.0 #10 0x7f6ffb3305fd in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f6fda9f2700 (LWP 2650)): #0 0x7f6ff69b7779 in g_mutex_lock () at /lib64/libglib-2.0.so.0 #1 0x7f6ff6972951 in g_main_context_query () at /lib64/libglib-2.0.so.0 #2 0x7f6ff6973107 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f6ff697329c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f6ffc119b5b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f6ffc0ca25a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f6ffbf2abd4 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f6ffbf2f00c in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f6ff8ec261a in start_thread () at /lib64/libpthread.so.0 #9 0x7f6ffb3305fd in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f6febe43940 (LWP 2630)): [KCrash Handler] #6 0x7f6fcf291204 in _GLOBAL__sub_I_qprinterinfo.cpp () at /lib64/libQtGui.so.4 #7 0x7f7002a9573a in call_init.part () at /lib64/ld-linux-x86-64.so.2 #8 0x7f7002a9584b in _dl_init () at /lib64/ld-linux-x86-64.so.2 #9 0x7f7002a9a3a2 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2 #10 0x7f7002a955e4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2 #11 0x7f7002a996a3 in _dl_open () at /lib64/ld-linux-x86-64.so.2 #12 0x7f6ff392dfc9 in dlopen_doit () at /lib64/libdl.so.2 #13 0x7f7002a955e4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2 #14 0x7f6ff392e631 in _dlerror_run () at /lib64/libdl.so.2 #15 0x7f6ff392e061 in dlopen@@GLIBC_2.2.5 () at /lib64/libdl.so.2 #16 0x7f6ffc0c8610 in QLibraryPrivate::load_sys() () at /lib64/libQt5Core.so.5 #17 0x7f6ffc0c2d95 in QLibraryPrivate::load() () at /lib64/libQt5Core.so.5 #18 0x7f6ffc0c2fcb in QLibraryPrivate::loadPlugin() () at /lib64/libQt5Core.so.5 #19 0x7f6ffdd196fa in KPluginLoader::load() () at /lib64/libKF5CoreAddons.so.5 #20 0x7f6ffdd1982a in KPluginLoader::instance() () at /lib64/libKF5CoreAddons.so.5 #21 0x7f6ffdd1987c in KPluginLoader::factory() () at /lib64/libKF5CoreAddons.so.5 #22 0x7f70027fbf02 in DolphinContextMenu::addFileItemPluginActions() () at /lib64/libkdeinit5_dolphin.so #23
[plasmashell] [Bug 360333] New system tray: icons do not scale with panel height, stay very small
https://bugs.kde.org/show_bug.cgi?id=360333 --- Comment #21 from Guillaume Martres --- (In reply to Jens Reuterberg from comment #18) > (In reply to Marco Martin from comment #6) > > this bug is pretty much mutually exclusive with > > https://bugs.kde.org/show_bug.cgi?id=353834 > > I fear icons are either going to be too big for some people or too small for > > some other people (and i don't want to add a configure icon size ui) > > I guess that any variant will rub some people wrong. We simply can't account > for all tastes and any change will make one group or another angry. The > question is: which group do we want to piss off, or do we accept the > problems that come with such a configuration UI. I disagree with this, looking at https://bugs.kde.org/show_bug.cgi?id=353834 the issue is specifically with two rows of systray icons where the icons almost overlap, the bug report title even says "(ok if single row)". No one is clamoring for one row of very small icons. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 343386] Wishlist: Make Paths to videofiles relative in KF5
https://bugs.kde.org/show_bug.cgi?id=343386 Paul Konecny changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Paul Konecny --- Hi guys, sorry it took me so long to get back to you. I was burried in my thesis over the summer... I just tried Wegwerf/DiveO's solution and I think it does what I wanted. Thanks Guys! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 Yvan Broccard changed: What|Removed |Added CC||yvan.brocc...@gmail.com --- Comment #79 from Yvan Broccard --- Hi, I'm experiencing this problem as well, with Fedora 24, KDE 5.7.5. 2nd monitor in black, no context menu. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 353066] WISHLIST - Add keyframeable speed effect with intact audio (like iPhone slow-motion)
https://bugs.kde.org/show_bug.cgi?id=353066 Paul Konecny changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO --- Comment #2 from Paul Konecny --- Sorry I got back to you so late. As I said I was burried in my thesis. I think that the speed effect as it is now is a great improvement and I consider the most part of my initial bug report fixed. The only thing that still bugs me it the keyframeability of the effect. I have an idea how to deal with it but I don't know whether I should open a new whishlist or post it here. (The idea would be to keep the clip at a constant length and stretch or compress the part with different speed) See the gui on this page. http://www.cultofmac.com/408250/how-to-speed-up-slo-mo-videos-on-your-iphone/ Cheers! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361374] 16.04-62fa29e SIGABRT when detaching / rejoining project and clip monitor with movit enabled
https://bugs.kde.org/show_bug.cgi?id=361374 --- Comment #9 from Paul Konecny --- Farid can you confirm this only happens on nvidia with the proprietary driver? I tested this on radeonsi, Intel and r600g and didn't get this SIGABRT. My guess it is a driver bug with nvidia's non standard conformant implementation in some areas. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370163] Regression: can no longer mouse-scroll through windows in a group.
https://bugs.kde.org/show_bug.cgi?id=370163 --- Comment #3 from Eike Hein --- I misunderstood this ticket; I thought the problem was that the wheel doesn't descend into groups, but the problem is that you want it to only switch windows within the group. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 350556] 15.08 - Segfault when editing large project with many "Speed" effects
https://bugs.kde.org/show_bug.cgi?id=350556 Paul Konecny changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Paul Konecny --- Jep, it's fixed. Cheers! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370163] Regression: can no longer mouse-scroll through windows in a group.
https://bugs.kde.org/show_bug.cgi?id=370163 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/plas ||ma-desktop/caa85c116afaf68d ||86896b6dac760bd83ac75c34 Resolution|--- |FIXED --- Comment #4 from Eike Hein --- Git commit caa85c116afaf68d86896b6dac760bd83ac75c34 by Eike Hein. Committed on 06/10/2016 at 08:41. Pushed by hein into branch 'Plasma/5.8'. Only switch between windows within the group when using the wheel above a group parent. M +11 -3applets/taskmanager/package/contents/code/tools.js M +1-1applets/taskmanager/package/contents/ui/MouseHandler.qml M +1-1applets/taskmanager/package/contents/ui/Task.qml http://commits.kde.org/plasma-desktop/caa85c116afaf68d86896b6dac760bd83ac75c34 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 350558] 15.08 - Segfault when trying to add title clip
https://bugs.kde.org/show_bug.cgi?id=350558 --- Comment #6 from Paul Konecny --- Jep, fixed. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 240009] file selection dialog is very slow, because loading non-cached icons is very slow
https://bugs.kde.org/show_bug.cgi?id=240009 Lubos Dolezel changed: What|Removed |Added CC||lu...@dolezel.info --- Comment #14 from Lubos Dolezel --- This bug still exists in KDE 5. I think a reasonable solution would be to display the files and directories first with generic icons and look for more appropriate icons on the background. The file dialog is *extremely* slow if / is NFS mounted. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357153] Increasing "Video quality" number in render panel actually reduces quality + increases compression
https://bugs.kde.org/show_bug.cgi?id=357153 --- Comment #8 from Paul Konecny --- ^This. And we have to be careful to wire the slider up differently for CRF and fixed bitrate codecs (FBR) respectively. CRF: Slider to better quality --> decrease CRF parameter in command line. FBR: Slider to better qulaity --> increase Bitrate parameter in command line. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 370186] Dolphin crashed on right-click for list-menu options
https://bugs.kde.org/show_bug.cgi?id=370186 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 368367 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 368367] Dolphin Crashes on right-click for list-menu options
https://bugs.kde.org/show_bug.cgi?id=368367 Christoph Feck changed: What|Removed |Added CC||admon@gmail.com --- Comment #15 from Christoph Feck --- *** Bug 370186 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 370012] ark messes up filenames when unpacking
https://bugs.kde.org/show_bug.cgi?id=370012 --- Comment #3 from Elvis Angelaccio --- Can you copy-paste here the *actual* filename that was cropped? Even better if you could provide the ark debug output: from terminal run $ export QT_LOGGING_RULES=ark.*.debug=true $ ark -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 370187] New: [wayland] krunner crashes if two displays are aligned anything other then default
https://bugs.kde.org/show_bug.cgi?id=370187 Bug ID: 370187 Summary: [wayland] krunner crashes if two displays are aligned anything other then default Product: krunner Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: bhus...@gmail.com Thread 1 (Thread 0x7f4a054cd840 (LWP 7780)): [KCrash Handler] #6 0x7f49ffd1904f in raise () from /usr/lib/libc.so.6 #7 0x7f49ffd1a47a in abort () from /usr/lib/libc.so.6 #8 0x7f4a009ba4a1 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/libQt5Core.so.5 #9 0x7f4a009b596e in qt_assert(char const*, char const*, int) () from /usr/lib/libQt5Core.so.5 #10 0x0040af4d in View::positionOnScreen (this=0x7ffe825f5e50) at /home/bshah/kdesrc/source/plasma-workspace/krunner/view.cpp:300 #11 0x0040aae8 in View::resetScreenPos (this=0x7ffe825f5e50) at /home/bshah/kdesrc/source/plasma-workspace/krunner/view.cpp:283 #12 0x00408c6a in QtPrivate::FunctorCall, QtPrivate::List<>, void, void (View::*)()>::call(void (View::*)(), View*, void**) (f=(void (View::*)(View * const)) 0x40aaa0 , o=0x7ffe825f5e50, arg=0x7ffe825f4ed0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:507 #13 0x00408be0 in QtPrivate::FunctionPointer::call, void>(void (View::*)(), View*, void**) (f=(void (View::*)(View * const)) 0x40aaa0 , o=0x7ffe825f5e50, arg=0x7ffe825f4ed0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:526 #14 0x00408b16 in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x14720b0, r=0x7ffe825f5e50, a=0x7ffe825f4ed0, ret=0x0) at /usr/include/qt/QtCore/qobject_impl.h:149 #15 0x7f4a00bd985e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #16 0x7f4a011006b2 in QWindow::visibleChanged(bool) () from /usr/lib/libQt5Gui.so.5 #17 0x7f4a01105a64 in QWindow::setVisible(bool) () from /usr/lib/libQt5Gui.so.5 #18 0x0040a3bc in View::displayOrHide (this=0x7ffe825f5e50) at /home/bshah/kdesrc/source/plasma-workspace/krunner/view.cpp:346 #19 0x00408c6a in QtPrivate::FunctorCall, QtPrivate::List<>, void, void (View::*)()>::call(void (View::*)(), View*, void**) (f=(void (View::*)(View * const)) 0x40a340 , o=0x7ffe825f5e50, arg=0x7ffe825f51d0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:507 #20 0x00408be0 in QtPrivate::FunctionPointer::call, void>(void (View::*)(), View*, void**) (f=(void (View::*)(View * const)) 0x40a340 , o=0x7ffe825f5e50, arg=0x7ffe825f51d0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:526 #21 0x00408b16 in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0xe7df10, r=0x7ffe825f5e50, a=0x7ffe825f51d0, ret=0x0) at /usr/include/qt/QtCore/qobject_impl.h:149 #22 0x7f4a00bd985e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #23 0x7f4a01b5a472 in QAction::triggered(bool) () from /usr/lib/libQt5Widgets.so.5 #24 0x7f4a01b5ce60 in QAction::activate(QAction::ActionEvent) () from /usr/lib/libQt5Widgets.so.5 #25 0x7f4a034a5127 in QAction::trigger (this=0xe7d290) at /usr/include/qt/QtWidgets/qaction.h:183 #26 0x7f4a034a11b4 in KGlobalAccelPrivate::_k_invokeAction (this=0x107ca60, componentUnique=..., actionUnique=..., timestamp=0) at /home/bshah/kdesrc/source/kglobalaccel/src/kglobalaccel.cpp:467 #27 0x7f4a034a28e0 in KGlobalAccel::qt_static_metacall (_o=0x7f4a036c5688 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7ffe825f5490) at /home/bshah/kdesrc/build/kglobalaccel/src/moc_kglobalaccel.cpp:91 #28 0x7f4a00bd94e9 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #29 0x7f4a034b5a5b in OrgKdeKglobalaccelComponentInterface::globalShortcutPressed (this=0x107d180, _t1=..., _t2=..., _t3=0) at /home/bshah/kdesrc/build/kglobalaccel/src/kglobalaccel_component_interface.moc:221 #30 0x7f4a034b562a in OrgKdeKglobalaccelComponentInterface::qt_static_metacall (_o=0x107d180, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7ffe825f5730) at /home/bshah/kdesrc/build/kglobalaccel/src/kglobalaccel_component_interface.moc:118 #31 0x7f4a034b5bd5 in OrgKdeKglobalaccelComponentInterface::qt_metacall (this=0x107d180, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7ffe825f5730) at /home/bshah/kdesrc/build/kglobalaccel/src/kglobalaccel_component_interface.moc:190 #32 0x7f4a0285a2f0 in ?? () from /usr/lib/libQt5DBus.so.5 #33 0x7f4a00bda349 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #34 0x7f4a01b60e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #35 0x7f4a01b68
[krunner] [Bug 370187] [wayland] krunner crashes if two displays are aligned anything other then default
https://bugs.kde.org/show_bug.cgi?id=370187 Martin Gräßlin changed: What|Removed |Added CC||mgraess...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370146] Window rule to block global shortcuts doesn't block meta
https://bugs.kde.org/show_bug.cgi?id=370146 --- Comment #4 from aiwend...@googlemail.com --- Well...that was fast...thanks a lot. :-) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 369104] [Regression] Selected text is not pasted in search field when search is initiated
https://bugs.kde.org/show_bug.cgi?id=369104 Brandner changed: What|Removed |Added CC||florian.brandner@telecom-pa ||ristech.fr -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370188] New: Ctrl+drag in the Timeline to copy multiple frames not working
https://bugs.kde.org/show_bug.cgi?id=370188 Bug ID: 370188 Summary: Ctrl+drag in the Timeline to copy multiple frames not working Product: krita Version: 3.0.2 Alpha Platform: Other OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: shortcuts Assignee: krita-bugs-n...@kde.org Reporter: bee...@bitmessage.ch Ctrl does not appear to be properly mapped to command (since ctrl + click is a special behavior on Macs). As a result, attempts to copy multiple frames by ctrl+dragging them only moves the frames to the new location without copying them. Reproducible: Always Steps to Reproduce: 1. Open/create a multiple frame animation .kra file. 2. Select multiple frames. 3. Attempt to copy them by ctrl + dragging them to somewhere else on the timeline. Actual Results: The selected frames are moved to their new location. Expected Results: The selected frames are copied to their new location. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368140] In 16.08.0 the project monitor remains blank (gray) while clips are playing
https://bugs.kde.org/show_bug.cgi?id=368140 Paul Konecny changed: What|Removed |Added CC||p...@konecny.at --- Comment #4 from Paul Konecny --- I think it has something to do with your nvidia card. Are you using tthe nvidia driver only or the bumblebee project? Can you try it with a live system without the nvidia driver installed? This seems related to this issue: https://bugs.kde.org/show_bug.cgi?id=361374 Cheers! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 366441] Kdenlive instantly crashing if GPU acceleration is activated
https://bugs.kde.org/show_bug.cgi?id=366441 Paul Konecny changed: What|Removed |Added CC||p...@konecny.at --- Comment #1 from Paul Konecny --- What GPU are you using? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 370189] New: kwallet-query does not work
https://bugs.kde.org/show_bug.cgi?id=370189 Bug ID: 370189 Summary: kwallet-query does not work Product: frameworks-kwallet Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: va...@kde.org Reporter: cf...@kde.org CC: kdelibs-b...@kde.org To reproduce: - type "kwallet-query -l kdewallet" in Konsole - enter password for in the dialog Actual result: - Error "Pass a valid window to KWallet::Wallet::openWallet()." Expected result: - List of passwords in kdewallet -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 370190] New: Trash is shown twice
https://bugs.kde.org/show_bug.cgi?id=370190 Bug ID: 370190 Summary: Trash is shown twice Product: digikam Version: 5.2.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: AlbumsView Assignee: digikam-de...@kde.org Reporter: her...@web.de Created attachment 101446 --> https://bugs.kde.org/attachment.cgi?id=101446&action=edit Screenshot showing trash twice Hello, I work with digiKam 5.2.0 on a Win 7 system. For each local collection of albums one non existing (virtual) album - called trash - is shown. It is very good that digiKam works with trash. But when I move an item into trash - a new subdirectory called .dtrash (with 2 subdirectories files and info ) is created on disc and - this directory is also handled like a real existing album (with name .dtrash). So I think it is much better to not display this "trash" twice. The real existing directory .dtrash should not be displayed, only the virtual album "trash" should be used instead. See attached screenshot. Best regards Herb -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 361764] Cannot add event to calendar with correct time: Add event window will not accept an "A.M." time
https://bugs.kde.org/show_bug.cgi?id=361764 stephane changed: What|Removed |Added CC||steph...@scachemaille.ch --- Comment #11 from stephane --- Someone has kind of the same problem with greek time locale. (el_GR) And I could reproduce it with the same locale as him. see here for more info https://forum.manjaro.org/t/korganizer-not-setting-properly-event-time/10397 here is a video you can see what happen. https://vimeo.com/185548052 (password: korganizer) what we can see. - When the user select a start date, the end day change to 1 day before the start day. - When the user save the event, the start time and end time is change and saved to 12:00 M.M (12:00 PM) korganizer 16.08.1 Qt 5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369547] When using a mouse, the stabilizer function of the freehand brush creates random lines by snapping to a point and back
https://bugs.kde.org/show_bug.cgi?id=369547 Boudewijn Rempt changed: What|Removed |Added Summary|The stabilizer function of |When using a mouse, the |the freehand brush creates |stabilizer function of the |random lines by snapping to |freehand brush creates |a point and back|random lines by snapping to ||a point and back -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368660] Wireless and aeroplane mode Oxygen icons missing in plasma-nm
https://bugs.kde.org/show_bug.cgi?id=368660 --- Comment #24 from Wolfgang Bauer --- Actually they were provided by the KDE4 plasma-nm itself, as I already wrote. And I repeat, it should not be difficult to take them from there (they were designed for Air anyway which was the default in KDE4), and add them to the Plasma5/plasma-framework Oxygen/Air desktop themes. I suppose I will try to do that myself, if/when I find the time (maybe next weekend?). I haven't checked if the KDE4 icons are 100% complete in regards to Plasma5 (there may have been some additions), but it would definitely be an improvement. Btw, a fresh install of Leap would use breeze by default, so that's maybe why you saw them... ;-) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 Juha Tuomala changed: What|Removed |Added CC||t...@iki.fi --- Comment #104 from Juha Tuomala --- I can imagine how KDE key figures are wondering how they could get more users into KDE community. With this kind of issues being open couple years, keep dreaming suckers. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #105 from Juha Tuomala --- I can imagine how KDE key figures are wondering how they could get more users into KDE community. With this kind of issues being open couple years, keep dreaming suckers. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 Jérôme Borme changed: What|Removed |Added CC||jerome.bo...@gmail.com --- Comment #106 from Jérôme Borme --- (In reply to Juha Tuomala from comment #105) We agree it's a regression (I added my vote) but there's no need to become disrespectful. I hope the developers are going to ignore your comment so they don't get demotivated and keep contributing to this wonderful code base. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370191] New: Look and Feel restores user customized desktop
https://bugs.kde.org/show_bug.cgi?id=370191 Bug ID: 370191 Summary: Look and Feel restores user customized desktop Product: plasmashell Version: 5.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Look & Feel package Assignee: plasma-b...@kde.org Reporter: leszek.les...@web.de CC: plasma-b...@kde.org Look and feel packages with layouts defined (like the maui one, see: https://github.com/maui-artwork/artwork-lookandfeel-maui/tree/master ) seem to restore the layout partly (at least the used desktop containment) on every start. So custom user settings like the switch to Desktop Containment instead of Folder View containment and wallpaper are reset everytime. Though the default plasma wallpaper is used instead of the one defined in the layouts file in the look and feel package Reproducible: Always Steps to Reproduce: 1. Install Maui Look and Feel and set as default, relogin 2. Change from Folder View containment to Desktop Containment and set a different wallpaper 3. relogin Actual Results: Resets back to Folder View desktop containment with default plasma wallpaper Expected Results: Should stay and Desktop Containment with selected wallpaper -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #107 from Juha Tuomala --- (In reply to Jérôme Borme from comment #106) > We agree it's a regression (I added my vote) but there's no need to become > disrespectful. The fact is that I'm disrespectful. Funny, that you mention 'regression'. Years back I wanted to start systematically collect regressions between releases. I was told that it's not wanted. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369547] When using a mouse, the stabilizer function of the freehand brush creates random lines by snapping to a point and back
https://bugs.kde.org/show_bug.cgi?id=369547 chris-1...@o2.pl changed: What|Removed |Added CC||chris-1...@o2.pl --- Comment #2 from chris-1...@o2.pl --- Hi I have the same problem also I have noticed that even when I'm using tablet when I press "V" to make straight line my stroke snaps to left upper corner of the canvas and return to the start of my line. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 367576] Some audio effects doesn't work after rendering
https://bugs.kde.org/show_bug.cgi?id=367576 Elias changed: What|Removed |Added URL|https://www.youtube.com/wat |https://youtu.be/xX2JJU9QWA |ch?v=AJgZPpsUTMg|U -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356175] [wayland] plasmashell crashes at startup
https://bugs.kde.org/show_bug.cgi?id=356175 --- Comment #15 from Lóránt Farkas --- I did half an hour ago, after a full system refresh. I still have have crash. The spalsh screen shows up, then the ktorrent windows shows up, and that's all. Now at least I have a coredump. But it is 19mb. I cannot attach here. here is a link for the coredump: https://drive.google.com/open?id=0B5EdsRKfDCNqWloxVjFfLTNhS2c I would like to use wayland under KDE but in this state is useless. No panel, No menu for right button, nothing, just black screen. I would like to help (though I am not a developer) with anything that i can. But I do not know how to help. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=343803 iraklis changed: What|Removed |Added CC||irts...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360333] New system tray: icons do not scale with panel height, stay very small
https://bugs.kde.org/show_bug.cgi?id=360333
Anthony Vital changed:
What|Removed |Added
CC||anthony.vi...@gmail.com
--- Comment #22 from Anthony Vital ---
Could the problem be the method used to scale the icon size on hidpi monitors?
Looking in plasma-framework/src/declarativeimports/core/units.cpp:
// Scale the icon sizes up using the devicePixelRatio
// This function returns the next stepping icon size
// and multiplies the global settings with the dpi ratio.
const qreal ratio = devicePixelRatio();
if (ratio < 1.5) {
return size;
} else if (ratio < 2.0) {
return size * 1.5;
} else if (ratio < 2.5) {
return size * 2.0;
} else if (ratio < 3.0) {
return size * 2.5;
} else if (ratio < 3.5) {
return size * 3.0;
} else {
return size * ratio;
}
My ratio is 1.47674, that means I have no scaling at all when there is a 1.5
factor existing. Is it reasonable? Wouldn't it make more sense to use the
factor the closest to the ratio rather than what is done here?
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 360333] New system tray: icons do not scale with panel height, stay very small
https://bugs.kde.org/show_bug.cgi?id=360333
--- Comment #23 from Guillaume Martres ---
(In reply to Anthony Vital from comment #22)
> Could the problem be the method used to scale the icon size on hidpi
> monitors?
> Looking in plasma-framework/src/declarativeimports/core/units.cpp:
> // Scale the icon sizes up using the devicePixelRatio
> // This function returns the next stepping icon size
> // and multiplies the global settings with the dpi ratio.
> const qreal ratio = devicePixelRatio();
>
> if (ratio < 1.5) {
> return size;
> } else if (ratio < 2.0) {
> return size * 1.5;
> } else if (ratio < 2.5) {
> return size * 2.0;
> } else if (ratio < 3.0) {
> return size * 2.5;
> } else if (ratio < 3.5) {
> return size * 3.0;
> } else {
> return size * ratio;
> }
> My ratio is 1.47674, that means I have no scaling at all when there is a 1.5
> factor existing. Is it reasonable? Wouldn't it make more sense to use the
> factor the closest to the ratio rather than what is done here?
Good point, but even if you fix that, I think that devicePixelRatio() will
still return 1 because of:
qunsetenv("QT_DEVICE_PIXEL_RATIO");
QCoreApplication::setAttribute(Qt::AA_DisableHighDpiScaling)
in
https://quickgit.kde.org/?p=plasma-workspace.git&a=blob&h=ec117f3bf9c12894bc7d3f80858256fab0026da4&hb=e88b52a18ff9c7ed43a9bed4e4ba270a8ee18355&f=shell%2Fmain.cpp
(cf https://bugs.kde.org/show_bug.cgi?id=356446)
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 357616] Add a way to select the region of the screen to record
https://bugs.kde.org/show_bug.cgi?id=357616 --- Comment #3 from xdmx --- Hi Farid, I've been using Vokoscreen so far and it's very good, I don't feel a need of having it integrated into Kdenlive since I can just import the video and edit it when I need. Thanks Wegwerf for the suggestion! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370188] Ctrl+drag in the Timeline to copy multiple frames not working
https://bugs.kde.org/show_bug.cgi?id=370188 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com --- Comment #1 from wolthera --- And cmd+drag doesn't do anything? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370188] Ctrl+drag in the Timeline to copy multiple frames not working
https://bugs.kde.org/show_bug.cgi?id=370188 --- Comment #2 from bee...@bitmessage.ch --- No, cmd+drag doesn't do anything either. Sorry I forgot to mention that. I tried other meta keys too. No dice. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 368808] No Notification Settings for Plasma 5 based Klipper
https://bugs.kde.org/show_bug.cgi?id=368808 Martin Gräßlin changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/plas ||ma-workspace/77aaa88eb2a148 ||f0955eb35b3043d3f0f81fae5b Version Fixed In||5.8.1 --- Comment #3 from Martin Gräßlin --- Git commit 77aaa88eb2a148f0955eb35b3043d3f0f81fae5b by Martin Gräßlin. Committed on 06/10/2016 at 11:25. Pushed by graesslin into branch 'Plasma/5.8'. [klipper] Move notification from tray to Klipper Summary: Klipper shows a notification when the shortcuts next/prev history item gets triggered. This notification used to be implemented in the class KlipperTray. With the switch from SNI based clipper to a Plasmoid the notification got lost as the Plasmoid doesn't use the KlipperTray class at all. This change moves the notification handling from KlipperTray to Klipper so that it gets emitted for both SNI and Plasmoid based klipper. FIXED-IN: 5.8.1 Test Plan: Set the shortcuts, triggered them and verified the notification gets shown. Reviewers: #plasma Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D2942 M +1-0klipper/CMakeLists.txt M +12 -0klipper/klipper.cpp M +3-0klipper/klipper.h M +0-13 klipper/tray.cpp M +0-5klipper/tray.h http://commits.kde.org/plasma-workspace/77aaa88eb2a148f0955eb35b3043d3f0f81fae5b -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368885] The plasma panel has no shadow on Wayland
https://bugs.kde.org/show_bug.cgi?id=368885 Bhushan Shah changed: What|Removed |Added CC||bhus...@gmail.com Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 Sebastian Kügler changed: What|Removed |Added CC||se...@kde.org --- Comment #108 from Sebastian Kügler --- @Juha: Your behavior makes me stop reading here, and that's counter-productive to everyone involved. Also, your disrespectfulness has no business here, you're just destroying the base people work together on. Ask yourself this question: Do you really want to drive developers away from issues you and other people care about? Please strongly consider the Code of Conduct ( https://www.kde.org/code-of-conduct/ ) before posting again. If you don't, you simply do not have the right of speaking. "I just behave that way" is not an excuse. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370146] Window rule to block global shortcuts doesn't block meta
https://bugs.kde.org/show_bug.cgi?id=370146 Martin Gräßlin changed: What|Removed |Added Version Fixed In||5.8.1 Latest Commit||http://commits.kde.org/kwin ||/db2ff13d4fa83307b85cbe8622 ||a8e37cb309c4a2 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Martin Gräßlin --- Git commit db2ff13d4fa83307b85cbe8622a8e37cb309c4a2 by Martin Gräßlin. Committed on 06/10/2016 at 11:28. Pushed by graesslin into branch 'Plasma/5.8'. Only trigger mod-only-shortcuts if global shortcuts are enabled Summary: KWin supports blocking global shortcuts when a window is active through window specific rules. This change ensures that the modifier only shortcuts also honor the blocking of global shortcuts. If global shortcuts are disabled, they won't trigger any more. FIXED-IN: 5.8.1 Reviewers: #kwin, #plasma Subscribers: plasma-devel, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D2952 M +0-1autotests/integration/modifier_only_shortcut_test.cpp M +2-1keyboard_input.cpp http://commits.kde.org/kwin/db2ff13d4fa83307b85cbe8622a8e37cb309c4a2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368989] Alt+F4 shortcut works only with XWayland windows
https://bugs.kde.org/show_bug.cgi?id=368989 Martin Gräßlin changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kwin ||/421824b654a5301fe1c0ed97ca ||ded66936c91385 Version Fixed In||5.8.1 --- Comment #10 from Martin Gräßlin --- Git commit 421824b654a5301fe1c0ed97caded66936c91385 by Martin Gräßlin. Committed on 06/10/2016 at 11:28. Pushed by graesslin into branch 'Plasma/5.8'. Workaround xkbcommon behavior concerning consumed modifiers Summary: If a key could be turned into a keysym with a modifier xkbcommon considers the modifier as consumed even if not pressed. E.g. Alt+F3 considers alt as consumed as there is a keysym gnerated with Ctrl+Alt+F3 (vt switching). This change tries to workaround the problem by ignoring the consumed modifiers if there are more modifiers consumed than active. It's possible that this will create regressions for other shortcuts - we need to test it in the wild. Although this might cause regressions I'm aiming for Plasma/5.8 branch with the change. It only affects Wayland and fixes quite important shortcuts from window manager perspective (desktop switching (ctrl+f1 to ctrl+f4), desktop grid (ctrl+f8), present windows (ctrl+f9, ctrl+10), cube (ctrl+f11), user actions (alt+f3), close window (alt+f4)). If it causes regressions they need to be fixed as well in the Plasma/5.8 branch. A new API entry point for xkbcommon was proposed, but is not yet merged and there is no release with it yet. Once that is available the workaround should get removed and replaced by the new API call. FIXED-IN: 5.8.1 Test Plan: Going to restart session now with the change Reviewers: #kwin, #plasma_on_wayland Subscribers: plasma-devel, kwin Tags: #plasma_on_wayland, #kwin Differential Revision: https://phabricator.kde.org/D2945 M +0-1autotests/integration/globalshortcuts_test.cpp M +18 -0keyboard_input.cpp http://commits.kde.org/kwin/421824b654a5301fe1c0ed97caded66936c91385 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 369091] Volume control shortcuts stuck (on Wayland)
https://bugs.kde.org/show_bug.cgi?id=369091 Martin Gräßlin changed: What|Removed |Added Latest Commit||http://commits.kde.org/kwin ||/3bc608939444f88dd855130982 ||ce176d393d3ab5 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||5.8.1 --- Comment #11 from Martin Gräßlin --- Git commit 3bc608939444f88dd855130982ce176d393d3ab5 by Martin Gräßlin. Committed on 06/10/2016 at 11:26. Pushed by graesslin into branch 'Plasma/5.8'. Only repeat one key Summary: So far KWin tried to repeat all pressed keys which should repeat. But this is not how X11 and e.g. QtWayland handle it. There only one key - the last one which got pressed - repeats. And this makes sense as the key is used to generate a keysym and that one KWin caches. Thus the logic so far resulted in incorrect keysyms to be generated during the repeat. E.g. pressing a, pressing b, releasing b would repeat b instead of the hold a as b was the last generated keysym. This change addresses this problem and let's only one key repeat at a time. When the currently repeating key gets released the repeat timer is stopped and other hold keys won't repeat any more. This also matches the behavior of X11 and QtWayland. FIXED-IN: 5.8.1 Reviewers: #kwin, #plasma_on_wayland Subscribers: plasma-devel, kwin Tags: #plasma_on_wayland, #kwin Differential Revision: https://phabricator.kde.org/D2941 M +0-1autotests/integration/globalshortcuts_test.cpp M +19 -23 keyboard_input.cpp M +5-1keyboard_input.h http://commits.kde.org/kwin/3bc608939444f88dd855130982ce176d393d3ab5 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 370184] Existing Filter search value field gets deleted when clicking on it
https://bugs.kde.org/show_bug.cgi?id=370184 Laurent Montel changed: What|Removed |Added Version Fixed In||5.3.2 Latest Commit||http://commits.kde.org/mail ||common/2cc7f743cc28a32604a9 ||34605c588932bdbd164e Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Laurent Montel --- Git commit 2cc7f743cc28a32604a934605c588932bdbd164e by Montel Laurent. Committed on 06/10/2016 at 11:30. Pushed by mlaurent into branch 'Applications/16.08'. Fix Bug 370184 - Existing Filter search value field gets deleted when clicking on it FIXED-IN: 5.3.2 M +4-0src/search/widgethandler/headersrulerwidgethandler.cpp M +4-0src/search/widgethandler/messagerulewidgethandler.cpp M +4-0src/search/widgethandler/tagrulewidgethandler.cpp M +4-0src/search/widgethandler/textrulerwidgethandler.cpp http://commits.kde.org/mailcommon/2cc7f743cc28a32604a934605c588932bdbd164e -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360333] New system tray: icons do not scale with panel height, stay very small
https://bugs.kde.org/show_bug.cgi?id=360333
--- Comment #24 from Anthony Vital ---
(In reply to Guillaume Martres from comment #23)
> Good point, but even if you fix that, I think that devicePixelRatio() will
> still return 1 because of:
> qunsetenv("QT_DEVICE_PIXEL_RATIO");
> QCoreApplication::setAttribute(Qt::AA_DisableHighDpiScaling)
> in
> https://quickgit.kde.org/?p=plasma-workspace.
> git&a=blob&h=ec117f3bf9c12894bc7d3f80858256fab0026da4&hb=e88b52a18ff9c7ed43a9
> bed4e4ba270a8ee18355&f=shell%2Fmain.cpp (cf
> https://bugs.kde.org/show_bug.cgi?id=356446)
I don't think this problem affects icon sizes. Also I used the code from
devicePixelRatio() to find the value 1.47674.
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 370188] Ctrl+drag in the Timeline to copy multiple frames not working
https://bugs.kde.org/show_bug.cgi?id=370188 --- Comment #3 from bee...@bitmessage.ch --- Okay it works now, but only if you press the meta key during the drag rather than at the start or before the drag, and only with the alt key. As for the actual alt key function, I have no idea about it. Should we fix it so that it should use cmd instead of alt and try and figure out why the actual alt function doesn't work on OSX? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 369104] [Regression] Selected text is not pasted in search field when search is initiated
https://bugs.kde.org/show_bug.cgi?id=369104 --- Comment #3 from Brandner --- Some additional observations: - the selection is correctly copied into the text field on the first search - the selection is correctly copied into the text field when alternating between different modes of the search bar (e.g., CTRL-F then CTRL-R then again CTRL-F). The problem appears to be in the method KateNormalInputMode::searchBar. On the first search, the selection is copied into the text field within the constructor of KateSearchBar, which actually invokes KateSearchBar::enterIncrementalMode. On subsequent searches, the constructor is not called anymore. Consequently, KateSearchBar::enterIncrementalMode is not invoked unless the mode variable switches between the "power" and "incremental" search modes. Calling KateSearchBar::enterIncrementalMode within GDB at this moment fixes the problem. So, an obvious fix might be to always invoke KateSearchBar::enterIncrementalMode/ KateSearchBar::enterPowerMode independent from mode changes? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 370192] New: Better handling of menu with language signs
https://bugs.kde.org/show_bug.cgi?id=370192 Bug ID: 370192 Summary: Better handling of menu with language signs Product: digikam Version: 5.2.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Usability Assignee: digikam-de...@kde.org Reporter: her...@web.de Created attachment 101447 --> https://bugs.kde.org/attachment.cgi?id=101447&action=edit menu with many many entries of languages Hello, I work with digiKam 5.2.0 on a Win 7 system. Suppose the following scenario: Select an image item and open window to edit metadata (with menu: item -> edit metadata). Select there "edit xmp" and click on button "x-default" to select a language for tag caption. Now a menu is displayed that contains all available language signs and this menu contains more items than can be displayed on screen. See attached screenshot. I have the following proposal for a better handling of this high amount of language items: 1) A typical digiKam user will only work with (lets say) up to 5 or 10 different languages. So it would be very helpful to have an additional setting that allows to preselect those language signs that a user will work with. Now clicking on button "x-default" will open a menu that contains only these preselected language items. "x-default" should of course be always preselected. For me it would be much more comfortable to work with about 5 language signs than about 100. 2) For e.g German Languages the menu contains the following entries: de-DE, de-AT, de-CH, de-LI and de-LU But it is not possible to select only language "de" For me this is a missing feature. Best regards Herb -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368660] Wireless and aeroplane mode Oxygen icons missing in plasma-nm
https://bugs.kde.org/show_bug.cgi?id=368660 --- Comment #25 from pinheiro --- currently making all the icons using breeze as a reference will push later -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #81 from Marcelo Rocha --- (In reply to Yvan Broccard from comment #79) > Hi, I'm experiencing this problem as well, with Fedora 24, KDE 5.7.5. > 2nd monitor in black, no context menu. Did you try to unninstall your video driver? I tried removing my xf86-video-intel and let it run only with modsetting, and the issue was fixed for me now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #80 from Marcelo Rocha --- (In reply to Yvan Broccard from comment #79) > Hi, I'm experiencing this problem as well, with Fedora 24, KDE 5.7.5. > 2nd monitor in black, no context menu. Did you try to unninstall your video driver? I tried removing my xf86-video-intel and let it run only with modsetting, and the issue was fixed for me now. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366072] Cannot switch the wireless checkbox on automatically when laptop function key enable the wireless interface
https://bugs.kde.org/show_bug.cgi?id=366072 --- Comment #7 from Jan Grulich --- I tested this couple of times but I'm unable to reproduce it. Tested with: - pressing Fn + F8 (in my case to turn off the wifi) - using rfkill - disabling the wifi over DBus -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 367846] KMail2 and akonadiconsole continuously lose connection to akonadi server - happens every 30 secs to 2 minutes.
https://bugs.kde.org/show_bug.cgi?id=367846 --- Comment #13 from Frank Mehnert --- I'm getting desperate and I would like to work around this problem by recreating the akonadi DB. In the above comments I see ''This now seems to be resolved for me after deleting all imap accounts in KMail, then dropping and recreating the akonadi database, then recreating the imap accounts. Since doing that I've not seen KMail2 lose connection to the akonadi server.'' Could someone explain these steps a little bit more in detail? I don't want to lose mails... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #82 from Greg White --- I've seen this with intel, modesetting and AMDGPU (running on either card.) Generally, I can recover by switching to a console (Alt+F2) and then back, though monitor 2 almost always loses its settings (wallpaper and so on.) This is a show stopper. I switched to lxqt until this is fixed. LXQT doesn't show this. FWIW. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 364973] [RFE] please expose 802-1x.subject-match property in gui
https://bugs.kde.org/show_bug.cgi?id=364973 --- Comment #4 from Jan Grulich --- *** Bug 364972 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 364973] [RFE] please expose 802-1x.subject-match property in gui
https://bugs.kde.org/show_bug.cgi?id=364973 Jan Grulich changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #3 from Jan Grulich --- Closing, subject match property was implemented a year ago. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 364972] hidden options are overwritten when using the gui editor
https://bugs.kde.org/show_bug.cgi?id=364972 Jan Grulich changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Jan Grulich --- Closing, subject match property was implemented a year ago. *** This bug has been marked as a duplicate of bug 364973 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370193] New: Save file didn't save work
https://bugs.kde.org/show_bug.cgi?id=370193 Bug ID: 370193 Summary: Save file didn't save work Product: krita Version: 3.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: bunf2...@apps.opensourcelaw.biz I opened up my file from yesterday to find that roughly an hour or so of work I did yesterday wasn't saved. I thought I had saved it, so I checked the file's timestamp. It was timestamped when I finished work (just after midnight), so I don't know what happened there. I was working on a saved "incremental version". Just renamed and opened the "~" file and my work is in there. Reproducible: Always Steps to Reproduce: 1. I can't reproduce it. This is really just here in case someone else also has the problem. 2. 3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369886] Screen goes infinitively brigher without moving cursor
https://bugs.kde.org/show_bug.cgi?id=369886 --- Comment #2 from Karmo Rosental --- This happens already in live session before install. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370194] New: Random plasmoids can make plasmashell to crash
https://bugs.kde.org/show_bug.cgi?id=370194 Bug ID: 370194 Summary: Random plasmoids can make plasmashell to crash Product: plasmashell Version: 5.8.0 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: m...@debian.org CC: bhus...@gmail.com, plasma-b...@kde.org plasmashell currently provides most of what the users consider their desktop, a plasmashell crash leaves the user with blank screen and little or no way to recover it. Sadly, crashing plasmashell is easier than it should, for example: https://bugs.debian.org/839710 Reproducible: Always Expected Results: plasmashell should be resilient to crashing plasmoids. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370195] New: Bug#839716: plasma-widgets: For easier bug reports widgets should have an "About" Section containing the package they belong to.
https://bugs.kde.org/show_bug.cgi?id=370195 Bug ID: 370195 Summary: Bug#839716: plasma-widgets: For easier bug reports widgets should have an "About" Section containing the package they belong to. Product: plasmashell Version: master Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: wettererschein...@bb-goettingen.de CC: bhus...@gmail.com, plasma-b...@kde.org Link to Debian Wishlist-Bug which I hereby send upstream: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839716 Thanks, Maria! Package: plasma-widgets-workspace Version: 4:4.11.13-2 Severity: wishlist File: plasma-widgets Dear Maintainer, writing bug reports about bugs in Plasma widgets or addons is sometimes quite difficult as it is not clear to which package they belong to. Especially if you use a non-english language, you don't even know the official name of the widget/addon, so it is really hard work to find out where to write the bug report to. Even in the forums people sometimes can't help you, especially if your used language is much different than english therefore using completely different names. Fazit: Widgets should have an "About" Section containing at least information about the package they belong to. This would make reporting of bug alot easier. Thanks for your work and time! Maria -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages plasma-widgets-workspace depends on: ii libc6 2.24-3 ii libkdecore5 4:4.14.23-1 ii libkdeui5 4:4.14.23-1 ii libkdewebkit5 4:4.14.23-1 ii libkio5 4:4.14.23-1 ii libkunitconversion4 4:4.14.23-1 ii libplasma34:4.14.23-1 ii libplasmaclock4abi4 4:4.11.13-2 ii libqt4-declarative4:4.8.7+dfsg-9 ii libqt4-network4:4.8.7+dfsg-9 ii libqt4-xml4:4.8.7+dfsg-9 ii libqtcore44:4.8.7+dfsg-9 ii libqtgui4 4:4.8.7+dfsg-9 ii libqtwebkit4 2.3.4.dfsg-8.1 ii libstdc++66.1.1-11 ii libx11-6 2:1.6.3-1 ii libxcomposite11:0.4.4-1 ii libxdamage1 1:1.1.4-2+b1 ii libxfixes31:5.0.2-1 ii libxrender1 1:0.9.9-2 ii plasma-dataengines-workspace 4:4.11.13-2 plasma-widgets-workspace recommends no packages. plasma-widgets-workspace suggests no packages. -- no debconf information Maximiliano Curia wrote: ¡Hola Maria! El 2016-10-04 a las 11:24 +0200, Maria escribió: > Package: plasma-widgets-workspace Version: 4:4.11.13-2 Severity: wishlist > File: plasma-widgets > Dear Maintainer, > writing bug reports about bugs in Plasma widgets or addons is sometimes quite > difficult as it is not clear to which package they belong to. > Especially if you use a non-english language, you don't even know the > official name of the widget/addon, so it is really hard work to find out > where to write the bug report to. Even in the forums people sometimes can't > help you, especially if your used language is much different than english > therefore using completely different names. > Fazit: Widgets should have an "About" Section containing at least information > about the package they belong to. This would make reporting of bug alot > easier. I don't see how this could be feasible under the Debian scope, but it shouldn't be too hard to do this on the upstream side of things, reporting the corresponding group (plasma, apps, extragear) and component (kdeplasma-addons, etc) a particular plasmoid belongs to. The relation between the upstream component names and the Debian source package names should be similar enough, and are probably easy to find, although you'll need to know how to report to the source package directly. On the other hand, most kde applications have a Report Bug menu entry, that reports the issue upstream, which is the preferred report method for the not Debian specific issues, so it would make sense to add this "report bug" option to the plasmoids. Could you please send the feature request upstream? Happy hacking, -- "Fighting patents one by one will never eliminate the danger of software patents, any more than swatting mosquitoes will eliminate malaria." -- Richard M. Stallman Saludos /\/\ /\ >< `/
[digikam] [Bug 370192] Better handling of menu with language signs
https://bugs.kde.org/show_bug.cgi?id=370192 caulier.gil...@gmail.com changed: What|Removed |Added Component|Usability |Metadata-Editor CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356175] [wayland] plasmashell crashes at startup
https://bugs.kde.org/show_bug.cgi?id=356175 --- Comment #16 from Martin Gräßlin --- @Lorant: is this the same backtrace as the one in this bug report? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370196] New: Allow Selection (marching ants) boundaries to be hidden
https://bugs.kde.org/show_bug.cgi?id=370196 Bug ID: 370196 Summary: Allow Selection (marching ants) boundaries to be hidden Product: krita Version: 3.0.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: phoenix.en...@gmail.com I find the marching ants distracting when working on a document. For example: isolating an clearly-defined area so that the rest isn't affected by brush strokes. I find that having the marching ants around screws with my value and color perception. A workaround is to make a completely-transparent mask selection. However, this seems more like a hack and it's better to have a completely separate option for toggling selection display. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #83 from Enrico Tagliavini --- (In reply to Marcelo Rocha from comment #81) > Did you try to unninstall your video driver? > > I tried removing my xf86-video-intel and let it run only with modsetting, > and the issue was fixed for me now. Let's try to avoid confusion, this is a KDE bug, not a video driver bug. I don't say switching to modesetting didn't helped you (especially for Skylake many distros are switching to modesetting over intel, including Fedora 24 which uses modesetting only by default), but the black screen issue might have been a fluke. It has also been officially confirmed that Plasma releases before 5.7 has sup-par multi screen support. The first system change a user might attempt to fix this problem should be trying Plasma 5.8, not messing with the video driver (it's messy, a lot of time is usually needed and here it's not the most likely cause). See also https://vizzzion.org/blog/2016/09/lts-releases-align-neatly-for-plasma-5-8/ and let me quote Sebastian Kügler's comment "Especially support for multi-screen systems in 5.7 is sub-par, those users would really benefit from getting Plasma 5.8." -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370196] Allow Selection (marching ants) boundaries to be hidden
https://bugs.kde.org/show_bug.cgi?id=370196 Nicholas LaPointe changed: What|Removed |Added CC||nicholaslapoin...@gmail.com --- Comment #1 from Nicholas LaPointe --- Thanks for the report! You should be able to toggle the marching ants by clicking "Display Selection" in the Select menu, or, if you are using the default keyboard shortcuts, by pressing Control + H. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 370197] New: Moved messages in folders still show in Inbox
https://bugs.kde.org/show_bug.cgi?id=370197 Bug ID: 370197 Summary: Moved messages in folders still show in Inbox Product: kontact Version: 5.3.1 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: gkour...@gmail.com When a message is moved from inbox to a dedicated subfolder, it is still shown in inbox after some seconds while a copy is kept in the subfolder used. This also applies to messages that are sent while the sent-mail folder is specified and still reside in outbox. Reproducible: Always Steps to Reproduce: 1. Click on message in inbox. 2. Drag message to a subfolder and then click on move 3. Message is moved from inbox. After 3-5 seconds it comes back while a copy is kept in the subfolder OR 1. Open a new message. 2. Specify the sent-mail folder as different from standard SENT. 3. Send the message. Notification is seen that the message was sent. 4. After some seconds, message appears in the outbox folder as unread. Actual Results: Messages comes back in inbox. Expected Results: Message to be moved correctly and to stay in these folders without returning to inbox. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 370197] Moved messages in folders still show in Inbox
https://bugs.kde.org/show_bug.cgi?id=370197 GK changed: What|Removed |Added CC||gkour...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370198] [multiscreen] context menus are not correctly positioned
https://bugs.kde.org/show_bug.cgi?id=370198 --- Comment #1 from Martin Gräßlin --- please check with WAYLAND_DEBUG=1 what's the transient offset position passed to the context menu. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370198] New: [multiscreen] context menus are not correctly positioned
https://bugs.kde.org/show_bug.cgi?id=370198 Bug ID: 370198 Summary: [multiscreen] context menus are not correctly positioned Product: kwin Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bhus...@gmail.com I've two monitor setup which are positioned as below |||. | |||. | ||| A. | |||. | |||. C| |||. | |. | | B. | || Now for explanation lets divide the screen 2 in 3 parts. Where Area A is similarly sized as Screen 1 (smaller screen.) Now if I do right click in Area B, its contextmenu appears displaced on area C. context menu in Area A and C are correctly positioned but not ones in area B. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370198] [multiscreen] context menus are not correctly positioned
https://bugs.kde.org/show_bug.cgi?id=370198 --- Comment #3 from Martin Gräßlin --- Qt sends stupid coordinates. Not much we can do about it. We can try to ensure that popups are always positioned on top of the window at least -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370198] [multiscreen] context menus are not correctly positioned
https://bugs.kde.org/show_bug.cgi?id=370198 --- Comment #2 from Bhushan Shah --- For record, [671827.448] -> wl_shell_surface@71.set_popup(wl_seat@7, 26381, wl_surface@47, 1366, 798, 0) [672702.706] -> wl_shell_surface@84.set_popup(wl_seat@7, 26383, wl_surface@47, 1366, 798, 0) Popup is positioned at 1366x798 which is original height of click but offset by size of screen 0. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 370199] New: Dolphin interprets a slash "/" in the foldername as a two different folders
https://bugs.kde.org/show_bug.cgi?id=370199 Bug ID: 370199 Summary: Dolphin interprets a slash "/" in the foldername as a two different folders Product: dolphin Version: 16.08.1 Platform: Archlinux Packages URL: https://youtu.be/h0Q3_No-c9I OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: luca.emanuel.we...@gmail.com The problem is demonstrated in the video using kio-gdrive as Google Drive allows a foldername with a slash in the name. The same thing surely could also be done with other methods. When a foldername contains a slash character eg "asd/fgh", Dolphin interprets the folder sometimes as "folder asd which contains the folder fgh" or "folder asd which contains the folder asd/fgh". Sometimes one happens, sometimes the other happens (can't reproduce when what happens exactly). Reproducible: Always Steps to Reproduce: 1. Create a folder which contains a slash "/" in its name (I used kio-gdrive, details about that in "Details") 2. Enter that folder with Dolphin and see it break Actual Results: Dolphin interpreted the slash as a subfolder and handled it like that. Expected Results: Dolphin should handle the slash as a character. I can still open files which are in such a folder (example kio-gdrive), but I can't copy the folder to another directory with the error message "The file or folder /@gmail.com/dolphin_demo/Test/flash_folder does not exist." -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #86 from Nick Cross --- I occasionally see it on Fedora 24 if the screen locks itself and turns off. The laptop screen on a dual head docked display then doesn't come back to life. My workaround (until I get Plasma 5.8 :-) ) is, using the working monitor, resize the laptop display. That seems to kick it back to life and then I resize it back to normal. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370193] Save file didn't save work
https://bugs.kde.org/show_bug.cgi?id=370193 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Hi Brendan, Thanks for taking the trouble to make a report. It's just that without a way to reproduce it, we really cannot do much with it... -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 370028] Reduce the number of compiler warnings on MIPS platforms
https://bugs.kde.org/show_bug.cgi?id=370028 --- Comment #7 from Aleksandar Rikalo --- Patch 1/4 (warn01.diff) removes 98 "cast-align" warnings caused by including vki-linux.h from various sources. PTR_CAST macro from this patch can be used in future, to avoid "cast-align" warnings. Patch 2/4 (warn02.diff) removes few "cast-align" warnings from coregrind/launcher-linux.c. Patch 3/4 (warn03.diff) removes "cast-align" warning from coregrind/m_syswrap/syswrap-generic.c. Patch 4/4 (warn04.diff) is MIPS specific and removes 32 "cast-equal" warnings from coregrind/m_coredump/coredump-elf.c. These numbers are relevant for MIPS build. -- You are receiving this mail because: You are watching all bug changes.
