[kdeconnect] [Bug 419897] Error when accessing filesystem. sshfs finished with exit code 1
https://bugs.kde.org/show_bug.cgi?id=419897 sasha changed: What|Removed |Added Version|22.12.0 |22.12.3 CC||sa...@goldnet.ca --- Comment #8 from sasha --- (In reply to SP from comment #7) This is the same behaviour as here still in version 22.12.3 Dropping files on the widget is nice, temporary, workaround - thanks. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 419897] Error when accessing filesystem. sshfs finished with exit code 1
https://bugs.kde.org/show_bug.cgi?id=419897 --- Comment #12 from sasha --- It works as expected in kdeconnect 22.12.3 (on ubuntu 23.04, KDE 5.104) -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 488453] New: Permission Options "Everyone" and "Only root" are swapped
https://bugs.kde.org/show_bug.cgi?id=488453 Bug ID: 488453 Summary: Permission Options "Everyone" and "Only root" are swapped Classification: Applications Product: partitionmanager Version: 24.05.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: sasha1ur...@gmail.com Target Milestone: --- SUMMARY In "Create new partition" window options "Everyone" and "Only root" are swapped. The do exactly opposite of what they proclaim. STEPS TO REPRODUCE 1. Evoke "Create new partition" window 2. Set permissions - "Everyone" option 3. Finish creating the partition. OBSERVED RESULT After mounting this new partition, the system asks for a password. EXPECTED RESULT System shouldn't ask for a password. STEPS TO REPRODUCE 1. Evoke "Create new partition" window 2. Set permissions - "Root only" option 3. Finish creating the partition. OBSERVED RESULT After mounting this new partition, the system DO NOT ask for a password EXPECTED RESULT System SHOULD ask for a password. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.6.32-1-MANJARO (64-bit) (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 419897] Error when accessing filesystem. sshfs finished with exit code 1
https://bugs.kde.org/show_bug.cgi?id=419897 sasha changed: What|Removed |Added CC|sa...@goldnet.ca| -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 357051] KDE Connect fails to detect my PC and my PC fails to detect my Android 6.0 Phone.
https://bugs.kde.org/show_bug.cgi?id=357051 Sasha changed: What|Removed |Added CC||sasha.mishche...@gmail.com --- Comment #4 from Sasha --- Kubuntu 18.10 with last updates, last app version on Android. Can not pair devices. Both see nothing. Firtewall on PC disabled. When trying to connect I can see on PC side that exist short connection to 1716 port by using next command: sudo netstat -tnp | grep 1716 I can see open ports: LANG=C netstat -tlnp | grep kdeconnect (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) tcp6 0 0 :::1716 :::* LISTEN 8448/kdeconnectd May be this is a reason? It listen only IPv6... How it can be repaired? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] New: A very big volume of RAM
https://bugs.kde.org/show_bug.cgi?id=388854 Bug ID: 388854 Summary: A very big volume of RAM Product: okular Version: 0.25.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: mos.ca...@yandex.ru Target Milestone: --- Sorry for my English. A couple days ago i found that ocular uses more than 1 gigabyte of RAM. The PDF document was 3.2 megabytes at all and consists of about 200 pages. I don't know is it normal. So may be you have some memory leaks.I'm sorry if not. Thanks :). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] A very big volume of RAM
https://bugs.kde.org/show_bug.cgi?id=388854 --- Comment #2 from Sasha --- Created attachment 109856 --> https://bugs.kde.org/attachment.cgi?id=109856&action=edit Here is a file -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 --- Comment #13 from Sasha --- So thank you for your responding! I catched the reason of this behavior. But what will be with the program if i want to read for example 500 pages or work with some documents with lower number of pages. Are there any limits in the programm for this case? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 --- Comment #14 from Sasha --- And some about memory leaks. I tried to move up and down thrue the ocument from side by side and after a couple of times i have about 50 additional megabites in my RAM. But couple of minutes ago the volume of memory become +- 10Mb normal again. So, yes, i don't think thap there are any leaks. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 --- Comment #16 from Sasha --- Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394944] New: Kwin crashes after switching the application
https://bugs.kde.org/show_bug.cgi?id=394944 Bug ID: 394944 Summary: Kwin crashes after switching the application Product: kwin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: activities Assignee: kwin-bugs-n...@kde.org Reporter: mos.ca...@yandex.ru Target Milestone: --- Created attachment 113007 --> https://bugs.kde.org/attachment.cgi?id=113007&action=edit stack For a long period of time after switching current application ( by using Alt+Tab or by using mouse) I see the message that "Kwin had crashed". After that (it depends on application I use) I can't use my system further(for exampe when 2 programs are open in full-screeen mode) here is a stack I found. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394944] Kwin crashes after switching the application
https://bugs.kde.org/show_bug.cgi?id=394944 Sasha changed: What|Removed |Added Platform|Other |Neon Packages --- Comment #1 from Sasha --- I use the latest Kde Neon user -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394944] Kwin crashes after switching the application
https://bugs.kde.org/show_bug.cgi?id=394944 --- Comment #3 from Sasha --- Thank You! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377813] New: Plasma fails
https://bugs.kde.org/show_bug.cgi?id=377813 Bug ID: 377813 Summary: Plasma fails Product: kwin Version: 5.8.5 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mul.sa...@gmail.com Target Milestone: --- Application: kwin_x11 (5.8.5) Qt Version: 5.6.1 Frameworks Version: 5.28.0 Operating System: Linux 4.4.0-66-generic x86_64 Distribution: Linux Mint 18.1 Serena -- Information about the crash: - What I was doing when the application crashed: - Unusual behavior I noticed: - Custom settings of the application: Да просто упала плазма, как обічно она падает, что тут писать? Ну установил я Mint 18.1 kde, на нетбук 131 Леново, проц амд, видео тоже амд, да какая разница что и как? просто падает плазма на ровном месте, вас самим не противно такое делать?) The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb179ece940 (LWP 1680))] Thread 6 (Thread 0x7fb158d53700 (LWP 3451)): #0 0x7fb1799cb9e3 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb177839bcf in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fb17783b60e in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fb17783bb22 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb1777e6ffa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb17760f9e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb1728066b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fb177614808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb1736a36ba in start_thread (arg=0x7fb158d53700) at pthread_create.c:333 #9 0x7fb1799d582d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7fb142ab0700 (LWP 1802)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb1769ad574 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7fb1769ad5b9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7fb1736a36ba in start_thread (arg=0x7fb142ab0700) at pthread_create.c:333 #4 0x7fb1799d582d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fb143dea700 (LWP 1800)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb14b9950f3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #2 0x7fb14b994817 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #3 0x7fb1736a36ba in start_thread (arg=0x7fb143dea700) at pthread_create.c:333 #4 0x7fb1799d582d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fb159d84700 (LWP 1798)): #0 0x7fb1799cb9e3 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb177839bcf in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fb17783b60e in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fb17783bb22 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb1777e6ffa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb17760f9e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb1728066b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fb177614808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb1736a36ba in start_thread (arg=0x7fb159d84700) at pthread_create.c:333 #9 0x7fb1799d582d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fb15bfff700 (LWP 1782)): #0 0x7ffd5c0c89a7 in ?? () #1 0x7ffd5c0c8cd5 in clock_gettime () #2 0x7fb1799e3c86 in __GI___clock_gettime (clock_id=1, tp=0x7fb15bffea00) at ../sysdeps/unix/clock_gettime.c:115 #3 0x7fb1776c06c6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb17783bf09 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb17783b30b in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb17783bb22 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb1777e6ffa in QEven
[plasmashell] [Bug 372229] nvidia
https://bugs.kde.org/show_bug.cgi?id=372229 --- Comment #2 from Sasha Unspecified --- Tell me if I should provide some info. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372229] nvidia
https://bugs.kde.org/show_bug.cgi?id=372229 Sasha Unspecified changed: What|Removed |Added CC||sasha2...@gmail.com --- Comment #1 from Sasha Unspecified --- I confirm this (or at least, automatic bug reporter considered my bug to be a duplicate of this). It appeared after software upgrade (I don't know what exactly triggered it: either KDE packages upgrade, or nvidia package upgrade, or some other packages). Now I just can't start plasma. It's persistent. Workaround is to purge nvidia-304, nvidia-opencl-icd-304, nvidia-settings packages (note: xserver-xorg-video-nouveau shouldn't be installed too, because it displays screen full of different colors and hands the system; hovewer, such nouveau behavior is from the very beginning; while plasma crash with nvidia is regression). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372229] nvidia
https://bugs.kde.org/show_bug.cgi?id=372229 --- Comment #3 from Sasha Unspecified --- I discovered that in my case the crash is caused by upgrade: - from: nvidia-304 package of version 304.131-0ubuntu3 - to: nvidia-304 package of version 304.132-0ubuntu0.16.04.2 (within KUbuntu Xenial 16.04.1). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372229] nvidia
https://bugs.kde.org/show_bug.cgi?id=372229 --- Comment #8 from Sasha Unspecified --- Please confirm that this bug affects your within a distro-level report: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1640451. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372352] Plasmashell crashes on boot after "weekly" update
https://bugs.kde.org/show_bug.cgi?id=372352 Sasha Unspecified changed: What|Removed |Added CC||sasha2...@gmail.com --- Comment #2 from Sasha Unspecified --- It's related to upgrade from nvidia-304=304.131-0ubuntu3 to nvidia-304=304.132-0ubuntu0.16.04.2 (or, maybe, other versions in your case). You can (temporarily) downgrade your ndivia package as workaround. Also, please support this Ubuntu bug-report: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1640451 -- to make it confirmed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372400] Plasma shell aborts - apparently some sort of timeout - every time I try to log in since system updated.
https://bugs.kde.org/show_bug.cgi?id=372400 Sasha Unspecified changed: What|Removed |Added CC||sasha2...@gmail.com --- Comment #2 from Sasha Unspecified --- It's related to upgrade from nvidia-304=304.131-0ubuntu3 to nvidia-304=304.132-0ubuntu0.16.04.2 (or, maybe, other versions in your case). You can (temporarily) downgrade your ndivia package as workaround. Also, please support this Ubuntu bug-report: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1640451 -- to make it confirmed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372405] Plasma crashes consistantly & immediately following startx since 1st reboot following last system auto-update
https://bugs.kde.org/show_bug.cgi?id=372405 Sasha Unspecified changed: What|Removed |Added CC||sasha2...@gmail.com --- Comment #2 from Sasha Unspecified --- It's related to upgrade from nvidia-304=304.131-0ubuntu3 to nvidia-304=304.132-0ubuntu0.16.04.2 (or, maybe, other versions in your case). You can (temporarily) downgrade your ndivia package as workaround. Also, please support this Ubuntu bug-report: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1640451 -- to make it confirmed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372213] plasmashell összeomlott az nvidia.- driver telepítése után
https://bugs.kde.org/show_bug.cgi?id=372213 Sasha Unspecified changed: What|Removed |Added CC||sasha2...@gmail.com --- Comment #4 from Sasha Unspecified --- It's related to upgrade from nvidia-304=304.131-0ubuntu3 to nvidia-304=304.132-0ubuntu0.16.04.2 (or, maybe, other versions in your case). You can (temporarily) downgrade your ndivia package as workaround. Also, please support this Ubuntu bug-report: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1640451 -- to make it confirmed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372229] nvidia
https://bugs.kde.org/show_bug.cgi?id=372229 --- Comment #13 from Sasha Unspecified --- Please support this Ubuntu bug-report: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1640451 -- to make it confirmed. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 426682] New: CSS support in the Markdown backend
https://bugs.kde.org/show_bug.cgi?id=426682
Bug ID: 426682
Summary: CSS support in the Markdown backend
Product: okular
Version: 1.9.3
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: okular-de...@kde.org
Reporter: sasha2...@gmail.com
Target Milestone: ---
SUMMARY
The Markdown Library (mkd_functions,
https://manpages.debian.org/stretch/libmarkdown2-dev/mkd-functions.3.en.html)
supports extracting the CSS sections from a markdown document via mkd_css. The
Markdown Backend for Okular doesn't use that function. It should.
STEPS TO REPRODUCE
1. Create a markdown document with a stylesheet, e.g. “*
{color: red !important} Hello”.
2. Open the markdown document with Okular.
OBSERVED RESULT
Stylesheet is ignored.
EXPECTED RESULT
Stylesheet is taken into account.
SOFTWARE/OS VERSIONS
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8 (built against 5.12.8)
Kernel Version: 5.4.0-47-generic
OS Type: 64-bit
ADDITIONAL INFORMATION
Additionally it would be good for the configuration window of the Markdown
backend to allow to specifying custom/user CSS (via a multiline textbox) to be
included into EVERY document (see also #400529, where another user asks to have
not a single textbox but a set of editable stylesheets).
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 426682] CSS support in the Markdown backend
https://bugs.kde.org/show_bug.cgi?id=426682 --- Comment #1 from Sasha Unspecified --- Additionally it would be good for the configuration window of the Markdown backend to allow to specifying custom/user CSS (via a multiline textbox) to be included into EVERY document (see also https://bugs.kde.org/show_bug.cgi?id=400529, where another user asks to have not a single textbox but a set of editable stylesheets). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400529] Ship multiple CSS files for markdown backend
https://bugs.kde.org/show_bug.cgi?id=400529 Sasha Unspecified changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||sasha2...@gmail.com --- Comment #1 from Sasha Unspecified --- I agree. See also https://bugs.kde.org/show_bug.cgi?id=426682. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371560] Do not automatically append the Meta key to the list of shortcuts when Alt+F1 is set; instead let the actual Meta key itself be used or removed as a shortcut
https://bugs.kde.org/show_bug.cgi?id=371560 --- Comment #18 from Sasha Unspecified --- (In reply to skierpage from comment #17) > It is documented in https://userbase.kde.org/Plasma/Tips#Windows.2FMeta_Key Even being documented, it's very counterintuitive. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 352903] "Preferred Languages" are applied very strangely
https://bugs.kde.org/show_bug.cgi?id=352903 --- Comment #2 from Sasha Unspecified --- (In reply to Nate Graham from comment #1) > Is this still happening for you with a recent version of Plasma, like 5.18 > or 5.20? I use different settings now, so I can't say for sure, but, I think, we can assume that the bug is gone. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371560] Add a way to disable Kickoff launch with Meta key
https://bugs.kde.org/show_bug.cgi?id=371560 Sasha Unspecified changed: What|Removed |Added CC||sasha2...@gmail.com Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #6 from Sasha Unspecified --- Why is it marked as "resolved"? The Application Menu clearly has to have an **intuitive** way to disable its opening on release of the Meta key (but **without** unassigning the Alt+F1 shortcut, which is **unrelated** to the Meta-key shortcut from user's perspective). I suppose, there should be a checkbox for that in Application Menu Settings (currently there is a "Keyboard shortcuts" section in Application Menu Settings, but it allows only to change/reassign regular (on-key-down) shortcut, but not to assign/unassign on-key-up-style Meta-key shortcut). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371560] Add a way to disable Kickoff launch with Meta key
https://bugs.kde.org/show_bug.cgi?id=371560 Sasha Unspecified changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #8 from Sasha Unspecified --- I know that. But that's not a user-friendly way. That setting should be in "Application Menu Settings" or at least somewhere in GUI settings. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371560] Don't magically turn Alt+F1 into the Meta key and make a separate checkbox for disabling the Meta key in "App Menu Settings"
https://bugs.kde.org/show_bug.cgi?id=371560 Sasha Unspecified changed: What|Removed |Added Summary|Document the fact that an |Don't magically turn Alt+F1 |Alt+F1 keyboard shortcut is |into the Meta key and make |turned into the meta key|a separate checkbox for ||disabling the Meta key in ||"App Menu Settings" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371560] Don't magically turn Alt+F1 into the Meta key and make a separate checkbox for disabling the Meta key in "App Menu Settings"
https://bugs.kde.org/show_bug.cgi?id=371560 --- Comment #10 from Sasha Unspecified --- (In reply to Nate Graham from comment #9) > The one thing we should probably do is document the fact that Alt-F1 is > magically turned into the meta key. I strongly disagree. The Meta key (key-up) should have no relation with Alt+F1 key. For example, I use Alt+F1, but don't use Meta. (There's setting for this in ~/.config/kwinrc — "[ModifierOnlyShortcuts]\nMeta=", but it's quite counter-intuitive. I think, it should be a separate checkbox in the settings of "Application Menu" widget.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371560] Make a separate checkbox for disabling the Meta key in the settings of the "Application Menu" widget instead of magically turning Alt+F1 into the Meta key
https://bugs.kde.org/show_bug.cgi?id=371560 Sasha Unspecified changed: What|Removed |Added Summary|Don't magically turn Alt+F1 |Make a separate checkbox |into the Meta key and make |for disabling the Meta key |a separate checkbox for |in the settings of the |disabling the Meta key in |"Application Menu" widget |"App Menu Settings" |instead of magically ||turning Alt+F1 into the ||Meta key --- Comment #12 from Sasha Unspecified --- (In reply to Nate Graham from comment #11) I understand that there might be some technical limitations. (Though I can't imagine what they can be: even if KWin just sends Alt+F1 when the Meta key is pressed (and Alt+F1 is later processed independently by the Menu widget) — I think, it's possible for KWin to send arbitrary other key key-combination (the one that is configured as the primary shortcut in the Menu widget), not hard-coded Alt+F1 or not to generate any if the checkbox is unchecked; as the last resort, I think it's better to have an explicit "Turn Meta key into […] key" in the KWin GUI settings than hard-coded Alt+F1.) Of course I agree that if nothing else can be done, it should be at least documented. (P.S.: Now I'll change the title again — just for more readability.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371560] Make a separate checkbox for disabling the Meta key in the settings of the "Application Menu" widget instead of magically turning Alt+F1 into the Meta key
https://bugs.kde.org/show_bug.cgi?id=371560 --- Comment #13 from Sasha Unspecified --- (In reply to Sasha Unspecified from comment #12) > send arbitrary other key key-combination sorry, it should read as "send arbitrary key-combination" > or not to generate any if the checkbox is unchecked sorry, it should read as "and not to generate any if the checkbox is unchecked" Anyway, great thanks. -- You are receiving this mail because: You are watching all bug changes.
[ksnapshot] [Bug 309335] KSnapshot should not bind "new screenshot" to the space key
https://bugs.kde.org/show_bug.cgi?id=309335 Sasha Unspecified changed: What|Removed |Added Ever confirmed|0 |1 CC||sasha2...@gmail.com Status|UNCONFIRMED |CONFIRMED --- Comment #3 from Sasha Unspecified --- I confirm this for 0.8.2. Pressing Space when "Send to..." is focused causes starting a new snapshot instead of opening the "Send to..." menu. -- You are receiving this mail because: You are watching all bug changes.
[ksnapshot] [Bug 391066] Pressing the "Take a New Snapshot" button with the Space key causes KSnapshot to crash/hang
https://bugs.kde.org/show_bug.cgi?id=391066 --- Comment #2 from Sasha Unspecified --- Isn't this caused by #309335? -- You are receiving this mail because: You are watching all bug changes.
[ksnapshot] [Bug 309335] KSnapshot should not bind "new screenshot" to the space key
https://bugs.kde.org/show_bug.cgi?id=309335 --- Comment #4 from Sasha Unspecified --- BTW, isn't this bug a one that causes #391066? -- You are receiving this mail because: You are watching all bug changes.
[ksnapshot] [Bug 309335] KSnapshot should not bind "new screenshot" to the space key
https://bugs.kde.org/show_bug.cgi?id=309335 --- Comment #5 from Sasha Unspecified --- I mean that bug 391066 may be caused by the fact that due to binding "new snapshot" to Space pressing Space when the "new snapshot" is focused causes the "new snapshot" action to be initiated twice. -- You are receiving this mail because: You are watching all bug changes.
[ksnapshot] [Bug 391066] Pressing the "Take a New Snapshot" button with the Space key causes KSnapshot to crash/hang
https://bugs.kde.org/show_bug.cgi?id=391066 --- Comment #3 from Sasha Unspecified --- I mean bug 309335. -- You are receiving this mail because: You are watching all bug changes.
[ksnapshot] [Bug 309335] KSnapshot should not bind "new screenshot" to the space key
https://bugs.kde.org/show_bug.cgi?id=309335 --- Comment #7 from Sasha Unspecified --- Christoph Feck, thanks, I didn't know about that software. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 397821] Up/down/page-up/page-down keys don't work to scroll
https://bugs.kde.org/show_bug.cgi?id=397821 Sasha Unspecified changed: What|Removed |Added Platform|Other |Ubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 397821] New: Up/down/page-up/page-down keys don't work to scroll
https://bugs.kde.org/show_bug.cgi?id=397821 Bug ID: 397821 Summary: Up/down/page-up/page-down keys don't work to scroll Product: Discover Version: 5.6.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: sasha2...@gmail.com Target Milestone: --- Up, down, page-up and page-down keys don't scroll the window in discover when in Update section. A user needs to use mouse for that. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 390975] New: KRunner crashes when typing "4." (without quotes)
https://bugs.kde.org/show_bug.cgi?id=390975 Bug ID: 390975 Summary: KRunner crashes when typing "4." (without quotes) Product: krunner Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: sasha2...@gmail.com Target Milestone: --- Application: krunner (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-109-generic x86_64 Distribution: Ubuntu 16.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: I pressed Alt+F2 and typed "4." (without quotes) This happens almost every time. The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f75b6d19900 (LWP 18694))] Thread 20 (Thread 0x7f75757fa700 (LWP 19008)): #0 0x7f75b194d360 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f75b3e36a5b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x25cffb0) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x1e95ec0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f758e3ea50b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x22d4f90, th=) at ../../src/weaver.cpp:594 #4 0x7f758e3eb2bf in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x22d4f90, th=th@entry=0x7f75600013d0, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at ../../src/weaver.cpp:554 #5 0x7f758e3ef4e8 in ThreadWeaver::WorkingHardState::applyForWork (this=0x25cf280, th=0x7f75600013d0, wasBusy=) at ../../src/workinghardstate.cpp:66 #6 0x7f758e3ea46d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f75600013d0, wasBusy=) at ../../src/weaver.cpp:568 #7 0x7f758e3ef542 in ThreadWeaver::WorkingHardState::applyForWork (this=0x25cf280, th=0x7f75600013d0, wasBusy=) at ../../src/workinghardstate.cpp:73 #8 0x7f758e3ea46d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f75600013d0, wasBusy=) at ../../src/weaver.cpp:568 #9 0x7f758e3ef542 in ThreadWeaver::WorkingHardState::applyForWork (this=0x25cf280, th=0x7f75600013d0, wasBusy=) at ../../src/workinghardstate.cpp:73 #10 0x7f758e3ea46d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f75600013d0, wasBusy=) at ../../src/weaver.cpp:568 #11 0x7f758e3ef542 in ThreadWeaver::WorkingHardState::applyForWork (this=0x25cf280, th=0x7f75600013d0, wasBusy=) at ../../src/workinghardstate.cpp:73 #12 0x7f758e3ea46d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f75600013d0, wasBusy=) at ../../src/weaver.cpp:568 #13 0x7f758e3ed353 in ThreadWeaver::Thread::run (this=0x7f75600013d0) at ../../src/thread.cpp:103 #14 0x7f75b3e357be in QThreadPrivate::start (arg=0x7f75600013d0) at thread/qthread_unix.cpp:331 #15 0x7f75b0022754 in ?? () from /usr/lib/nvidia-304/libGL.so.1 #16 0x7f75b19476ba in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #17 0x7f75b373f41d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 19 (Thread 0x7f7575ffb700 (LWP 19007)): #0 0x7f75b194d360 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f75b3e36a5b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x25cffb0) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x1e95ec0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f758e3ea50b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x22d4f90, th=) at ../../src/weaver.cpp:594 #4 0x7f758e3eb2bf in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x22d4f90, th=th@entry=0x7f755c0013d0, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at ../../src/weaver.cpp:554 #5 0x7f758e3ef4e8 in ThreadWeaver::WorkingHardState::applyForWork (this=0x25cf280, th=0x7f755c0013d0, wasBusy=) at ../../src/workinghardstate.cpp:66 #6 0x7f758e3ea46d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f755c0013d0, wasBusy=) at ../../src/weaver.cpp:568 #7 0x7f758e3ef542 in ThreadWeaver::WorkingHardState::applyForWork (this=0x25cf280, th=0x7f755c0013d0, wasBusy=) at ../../src/workinghardstate.cpp:73 #8 0x7f758e3ea46d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f755c0013d0, wasBusy=) at ../../src/weaver.cpp:568 #9 0x7f758e3ef542 in ThreadWeaver::WorkingHardState::applyForWork (this=0x25cf280, th=0x7f755c0013d0, wasBusy=) at ../../src/worki
[ksnapshot] [Bug 391066] New: Pressing the "Take a New Snapshot" button with the Space key causes KSnapshot to crash/hang
https://bugs.kde.org/show_bug.cgi?id=391066 Bug ID: 391066 Summary: Pressing the "Take a New Snapshot" button with the Space key causes KSnapshot to crash/hang Product: ksnapshot Version: 0.8.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: ase...@kde.org Reporter: sasha2...@gmail.com Target Milestone: --- Application: ksnapshot (0.8.2) KDE Platform Version: 4.14.16 Qt Version: 4.8.7 Operating System: Linux 4.4.0-109-generic x86_64 Distribution: Ubuntu 16.04.4 LTS -- Information about the crash: - What I was doing when the application crashed: I ran KSnapshot, chose specific settings (see below), ensured that the "Take a New Snapshot" button is focused and pressed the Space key on my keyboard. The KSnapshot entered "Select a region using the mouse. To take the snapshot, press the Enter key or double click. Press Esc to quit." mode (as usually). But when I try to exit this mode, either by pressing Enter, or by double-clicking or by pressing Esc, it fails. More specifically: * if I press Enter, it seems to restart the region-selection mode (chosen rectange is reset); * if I press Esc, I'm still in the region-selection mode; * double-clicking usually causes KSnapshot to crash. The problem doesn't occur when the "Take a New Snapshot" button is clicked by mouse. - Custom settings of the application: The problem occurs when the application is used with the following settings: * Capture mode: Rectangular Region; * Snapshot delay: No delay. The problem seems not to occur in other modes (at least, I couldn't reproduce it in "Full Screen"+"No delay" and "Rectangular Region"+"1 second" modes). The crash can be reproduced every time. -- Backtrace: Application: KSnapshot (ksnapshot), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 0x7fb3f7baebd6 in QListData::size (this=0x7fb3f6688f28) at ../../include/QtCore/../../src/corelib/tools/qlist.h:98 #7 QList::size (this=0x7fb3f6688f28) at ../../include/QtCore/../../src/corelib/tools/qlist.h:137 #8 QCoreApplication::compressEvent (this=, event=0x1147b60, receiver=0x10d93d0, postedEvents=0x7fb3f6688f28) at kernel/qcoreapplication.cpp:1431 #9 0x7fb3f7bb28de in QCoreApplication::postEvent (receiver=0x10d93d0, event=0x1147b60, priority=0) at kernel/qcoreapplication.cpp:1380 #10 0x00413959 in ?? () #11 0x00417439 in ?? () #12 0x7fb3f7bc3010 in QMetaObject::activate (sender=0x1098640, m=, local_signal_index=, argv=) at kernel/qobject.cpp:3567 #13 0x0041da3c in ?? () #14 0x7fb3f6f48450 in QWidget::event (this=0x1098640, event=0x7ffd32a44480) at kernel/qwidget.cpp:8393 #15 0x7fb3f6ef0fdc in QApplicationPrivate::notify_helper (this=this@entry=0xf2da40, receiver=receiver@entry=0x1098640, e=e@entry=0x7ffd32a44480) at kernel/qapplication.cpp:4570 #16 0x7fb3f6ef80d6 in QApplication::notify (this=, receiver=0x1098640, e=0x7ffd32a44480) at kernel/qapplication.cpp:4113 #17 0x7fb3f88c264a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #18 0x7fb3f7bae90d in QCoreApplication::notifyInternal (this=0x7ffd32a44cb0, receiver=receiver@entry=0x1098640, event=event@entry=0x7ffd32a44480) at kernel/qcoreapplication.cpp:955 #19 0x7fb3f6ef76dd in QCoreApplication::sendEvent (event=, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #20 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x1098640, event=event@entry=0x7ffd32a44480, alienWidget=alienWidget@entry=0x0, nativeWidget=nativeWidget@entry=0x1098640, buttonDown=buttonDown@entry=0x7fb3f7a1c368 , lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3178 #21 0x7fb3f6f753f2 in QETWidget::translateMouseEvent (this=this@entry=0x1098640, event=event@entry=0x7ffd32a447e0) at kernel/qapplication_x11.cpp:4638 #22 0x7fb3f6f74c83 in QApplication::x11ProcessEvent (this=0x7ffd32a44cb0, event=event@entry=0x7ffd32a447e0) at kernel/qapplication_x11.cpp:3626 #23 0x7fb3f6f9e542 in x11EventSourceDispatch (s=0xf40a80, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #24 0x7fb3f300e197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7fb3f300e3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7fb3f300e49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7fb3f7bdf2ae in QEventDispatcherGlib::processEvents (this=0xf2b5b0, flags=...) at kernel/qeventdispatcher_glib.cpp:450 #28 0x7fb3f6f9e616 in QGuiEventDispatcherGlib::processEvents (this=, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #29 0x7fb3f7bad18f in QEventLoop::processEvents (this=this@entry=0x7ffd32a4
[ksnapshot] [Bug 391066] Pressing the "Take a New Snapshot" button with the Space key causes KSnapshot to crash/hang
https://bugs.kde.org/show_bug.cgi?id=391066 --- Comment #1 from Sasha Unspecified --- Notes: 1. Sorry, I described behavior imprecisely. - Pressing Esc key (when in region-selection mode caused by pressing Space on the "Take a New Snapshot" button) exits region-selection mode. But, unlike the normal behavior (when in region-selection mode caused by clicking "Take a New Snapshot" with mouse), Esc needs to be pressed *twice*: first does nothing and second causes both the region-selection mode and KSnapshow to quit. - Choosing a rectangle and double-clicking it (when in region-selection mode caused by pressing Space on the "Take a New Snapshot" button) hides the rectangle, but doesn't exit the region-selection mode. In this state, choosing a rectangle and double-clicking it again causes KSnapshow to crash in 100% cases (i.e. first selection and double-click does nothing, second selection and double-click causes crash). - Pressing Enter (when in region-selection mode caused by pressing Space on the "Take a New Snapshot" button) causes some strange behavior. More than one rectangle-selector may appear and etc. But, no matter how many times I select the rectangle and press Enter, the region-selection mode is still on. 2. Surprisingly, pressing Enter on the "Take a New Snapshot" button behaves similarly to pressing it with mouse, not to pressing it with Space key. I.e. pressing Enter when the "Take a New Snapshot" button is focused causes the normal region-selection mode, which can be then finished/cancelled without any problems. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 390975] KRunner crashes when typing "4." (without quotes)
https://bugs.kde.org/show_bug.cgi?id=390975 Sasha Unspecified changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #2 from Sasha Unspecified --- I've just tried to type "=4" (with the hope that if I start my input with "=" it won't start that queries and will work just in calculator mode), but everything crashed with losing all my windows :(. $ balooctl indexSize Actual Size: 103,42 MiB Expected Size: 3,99 GiB PostingDB: 1,23 MiB 0.030 % PosistionDB: 3,99 GiB 100.114 % DocTerms: 800,00 KiB 0.019 % DocFilenameTerms: 264,00 KiB 0.006 % DocXattrTerms:0 B 0.000 % IdTree: 76,00 KiB 0.002 % IdFileName: 244,00 KiB 0.006 % DocTime: 144,00 KiB 0.003 % DocData: 64,00 KiB 0.002 % ContentIndexingDB: 4,00 KiB 0.000 % FailedIdsDB:0 B 0.000 % MTimeDB: 40,00 KiB 0.001 % -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 390975] KRunner crashes when typing "4." (without quotes)
https://bugs.kde.org/show_bug.cgi?id=390975 --- Comment #3 from Sasha Unspecified --- Wow. I've just visited "System Settings"/"Search"/"Plasma Search" and disabled all plugins except "Calculator" and "Command Line". It now works! (Thank you for suggestion that it's related to balloo, I supposed the bug to be in the KRunner core before, now I have a workaround.) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 375953] New: Often "Edit|Crop" and "File|Save As..." buttons are disabled without any reason
https://bugs.kde.org/show_bug.cgi?id=375953 Bug ID: 375953 Summary: Often "Edit|Crop" and "File|Save As..." buttons are disabled without any reason Product: gwenview Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: sasha2...@gmail.com CC: myr...@kde.org Target Milestone: --- For example, when opening from "http://…"; URLs. However the same (at least, disabled "Edit|Crop") sometimes happen to be for local files. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 373720] Settings for Krusader user and Krusader root are identical
https://bugs.kde.org/show_bug.cgi?id=373720 --- Comment #8 from Sasha Unspecified --- There is another report #162417, which complains that root-mode krusader DOES NOT use settings from current user (actually written by me, but up-voted by other users). I actually can't find any use-case when user needs different settings for root-mode (so why to bother with configuring krusader twice?; and if several users share the same PC, even configuring krusader twice may not help — because different users may want different settings, but all of them may user root-mode from time to time). Anyway — this seems to be platform-specific — but neither behavior satisfies all users — so it should turn into platform-independent, but CONFIGURABLE — so that "start root-mode Krusader" menu items does what the current chooses (not just silently uses current-user or root-user home dir). -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 373720] Settings for Krusader user and Krusader root are identical
https://bugs.kde.org/show_bug.cgi?id=373720 --- Comment #9 from Sasha Unspecified --- I write here, because somebody marked bug 162417 as duplicate of this one. Ideal solution (as for me) is the following: * user clicks "start root-mode krusader" in the menu; * the current instance of krusader, before launching anything, first looks for a special flag in the current user settings: "Do the current user likes the root-mode krusader to use the same settings or settings from the root user?" (as for me, the first should be default — but I don't insist on that, because opinions may vary); * depending on the value of that flag in current-user settings, the current instance of krusader launches a new root-mode instance of krusader either in a way that it continues to use current user settings, or in a way that in uses settings from the root user; * (this behavior should be platform-independent; i.e. whether root-mode krusader uses current user settings or root user settings should depend on a value of the flag in the current user settings — not on the platform; I believe that every platform allows both ways) * (this requires a new flag to be introduced into user settings) * (additionally, root-mode krusader, when it uses non-root-user settings, may need to be careful not to overwrite user settings with wrong rights (i.e. to create files in user's config dir owned not by root, but by the inherited user) — if needed to create something — but it may be a matter of a separate bug-report if such case arises) -- You are receiving this mail because: You are watching all bug changes.
[ksnapshot] [Bug 309335] KSnapshot should not bind "new screenshot" to the space key
https://bugs.kde.org/show_bug.cgi?id=309335 --- Comment #9 from Sasha Unspecified --- That's actually good news :). -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 167986] calculator runner of krunner outputs wrong results
https://bugs.kde.org/show_bug.cgi?id=167986 Sasha Unspecified changed: What|Removed |Added CC|sasha2...@gmail.com | --- Comment #47 from Sasha Unspecified --- I was subscribed to this report, because another report was marked as duplicate of this one. But that other report was about a more important thing: some formulas were evaluated absolutely wrong, e.g. =(2^2)^1 returned 1; now that bug is de-facto resolved. So now I unsubscribe. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 376606] New: Wish: Make bookmark menu more clear
https://bugs.kde.org/show_bug.cgi?id=376606
Bug ID: 376606
Summary: Wish: Make bookmark menu more clear
Product: krusader
Version: 2.4.0-beta3 "Single Step"
Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: general
Assignee: m...@fork.pl
Reporter: sasha2...@gmail.com
Target Milestone: ---
Bookmark menu (invoked by Ctrl+D) is quite useful thing.
It's especially useful because it allows to assign a mnemonic key to a bookmark
by giving it a title like "&Desktop", "&Work" or "Ente&rtainment" so that
pressing Ctrl+D, {D,W,R} goes to the specific folder (first Ctrl+D opens the
bookmarks menu, second key activates a specific item within it). Such way is
more handy than assigning explicit shortcut to a bookmark because:
* allows reusing the same Ctrl+D key as initial for shortcut sequence (which is
quite intuitive);
* allows possible bookmarks/shortcuts to appear visually when initial key of
the shortcut sequence is triggered;
* allows assigning shortcuts in one step (just by entering "&Desktop": instead
of first creating "Desktop" bookmark and then searching for it within
"Configure Shortcuts" dialog.
Still, the problem is that the predefined items of the bookmarks menu (i.e.:
&Trash bin, &Local Network, &Virtual Filesystem, J&ump back, &Set Jump Back
Point, Bookmark Current, Manage Bookmarks) may conflict with user-assigned
mnemonics, thus reducing set of available mnemonics to more limited range).
I propose one or more of the following:
1. Logically: to make priority of user bookmark mnemonics higher that priority
of predefined bookmark menu items. Technically: if one of user bookmarks uses
&u mnemonic, then "J&ump back" should appear as "Jump back". It can be checked
when popping up the menu.
2. To reorganize predefined bookmark menu items by putting (some of) them into
submenus. This will not only allow more mnemonics, but also make menu more
visually clean and provide more visual space for user-defined items. Proposed
structure:
* User bookmark 1
* User bookmark 2
* …
* Predefined places:
** &Trash bin
** &Local Network
** &Virtual Filesystem
* Popular URLs:
** …
* Other:
** Bookmark Current
** Manage Bookmarks
** Set Jump Back Point
** Jump Back
3. Make &Trash bin, &Local Network, &Virtual Filesystem to be predefined
(default) bookmarks themselves, not just items within the bookmark menu. So
that user can remove them, if he don't likes or move them into folder. The
"Manage Bookmarks" dialog may also have a "Reinsert all default bookmarks here"
command (not really necessary).
Thanks!
--
You are receiving this mail because:
You are watching all bug changes.
[kdelibs] [Bug 179504] Global shortcuts doesn't work with Ctrl+Alt+Shift+...
https://bugs.kde.org/show_bug.cgi?id=179504 --- Comment #32 from Sasha Unspecified --- Matthias Heinz, in KDE 5.18 it still doesn't. What shortcut did you try in 5.28. Did you assign it through systemsettings? -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 179504] Global shortcuts doesn't work with Ctrl+Alt+Shift+...
https://bugs.kde.org/show_bug.cgi?id=179504 --- Comment #34 from Sasha Unspecified --- What exactly shortcut did you assign in 5.28? (As I've said, my is 5.18, so I can't test 5.28 yet.) -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 179504] Global shortcuts doesn't work with Ctrl+Alt+Shift+...
https://bugs.kde.org/show_bug.cgi?id=179504 Sasha Unspecified changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #36 from Sasha Unspecified --- Matthias Heinz, OK, thank you. I just wanted to ensure that you really tried the thing (for example, not Ctrl+Shift+Letter, not a local shortcut). OK, then it really should be closed. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[forum.kde.org] [Bug 322866] KDE Identity: knowledge of username is required to reset password and to obtain information about username
https://bugs.kde.org/show_bug.cgi?id=322866 sasha changed: What|Removed |Added CC||sa...@goldnet.ca --- Comment #69 from sasha --- Same here. I do not remember my user name. My email is the same as on this KDE bugs account. -- You are receiving this mail because: You are watching all bug changes.
[forum.kde.org] [Bug 322866] KDE Identity: knowledge of username is required to reset password and to obtain information about username
https://bugs.kde.org/show_bug.cgi?id=322866 sasha changed: What|Removed |Added CC|sa...@goldnet.ca| -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 356432] New: Cannot update message tag icon and name
https://bugs.kde.org/show_bug.cgi?id=356432 Bug ID: 356432 Summary: Cannot update message tag icon and name Product: kmail2 Version: 4.14.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: config dialog Assignee: kdepim-b...@kde.org Reporter: sa...@goldnet.ca Once message tag has been created and saved in configuration window, its name and icon cannot be updated. Reproducible: Always Steps to Reproduce: 1. Create new message tag and save it 2. Exit configuration window 3. Open configuration window > Appearance > Message Tags and selected tag previously created Actual Results: Message tag name and Icon cannot be updated. Expected Results: Being able to update message tag icon and name New tag can be created with desired properties and then all messages with old tag could be selected and tagged with new one, and then old tag could be deleted. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 347825] qt-recordMyDesktop does not show a systray icon and recording cannot be stopped
https://bugs.kde.org/show_bug.cgi?id=347825 Sasha Unspecified changed: What|Removed |Added CC||sasha2...@gmail.com --- Comment #4 from Sasha Unspecified --- FYI: KUbuntu 16.04.1, gtk-recordmydesktop 0.3.8-4.1ubuntu1 — systray button exists, but has no icon; i.e. looks like a gap between other systray buttons (Keyboard Layout and Audio Volume), so not easy to guess that it belongs to recordmydesktop. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356409] New: Plasma fails to start when using old video driver
https://bugs.kde.org/show_bug.cgi?id=356409 Bug ID: 356409 Summary: Plasma fails to start when using old video driver Product: plasmashell Version: 5.4.2 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sasha2...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Plasma fails to start when using old video driver (e.g. vesa). The same happens when X server is using dummy driver (e.g. I want to allow PC be properly booted even when no monitor is attached, to make it accessible with VNC). On start plasma displays the following message: "Plasma is unable to start as it couldn't correctly use OpenGL 2. Please check that your graphic drivers are set up correctly." The biggest disappointment is that plasma displays this message in nice graphic window. I could understand if that message would appear in stderr/log file -- that would mean that the driver is really unusable. Desktop effects are turned off, of course. Reproducible: Always Steps to Reproduce: There are to proposed ways to reproduce that: A -- by downgrading your graphics driver to vesa. Determine which graphics drivers are currently in use, and then disable them (either by blacklisting or by uninstalling correspondent packages). For example, I reach this state when I uninstall the persistently hanging xserver-xorg-video-nouveau package (but binary NVIDIA packages aren't yet installed). B -- by forcing your X server to run without monitor and then connecting with VNC: 1. Install and turn on the dummy driver on server (as per http://ubuntuforums.org/showthread.php?t=1452600&page=7&p=11419677#post11419677). 2. Connect with SSH to the server, install x11vnc package and launch x11vnc. 3. Connect to the server with xtightvncviewer. Actual Results: The "Plasma is unable to start as it couldn't correctly use OpenGL 2. Please check that your graphic drivers are set up correctly." message in the graphic window. Expected Results: I expect plasma to be working. Maybe slowly, maybe with glitches. But somehow working. Is kwin is able to display windows, then plasma should be able to display widgets. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356409] Plasma fails to start when using old video driver
https://bugs.kde.org/show_bug.cgi?id=356409 Sasha Unspecified changed: What|Removed |Added Resolution|WONTFIX |--- Status|RESOLVED|UNCONFIRMED --- Comment #2 from Sasha Unspecified --- 1. Well... Could you please tell me what QT_XCB_FORCE_SOFTWARE_OPENGL is? I mean: is it environment variable, or value in some config file, or what? 2. Shouldn't be this a default behavior? I mean, if not OpenGL support available, then use simpler graphics API/software emulation. Cause a user who've installed new (buggy) video driver/uses old graphic card/connects with VNC to monitor-less server/whatsoever will certainly prefer to see his plasma running, then displaying such useless message at start-up. Graphic wow-effects on desktop are not so important to prevent the whole X-server be started in case when video-driver configuration is not ideal. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356409] Plasma fails to start when using old video driver
https://bugs.kde.org/show_bug.cgi?id=356409 --- Comment #4 from Sasha Unspecified --- Sorry for my rude speech in the last comment, it was inappropriate. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 358322] New: Pressing Enter during crop causes going 1 level up instead of confirming the crop
https://bugs.kde.org/show_bug.cgi?id=358322 Bug ID: 358322 Summary: Pressing Enter during crop causes going 1 level up instead of confirming the crop Product: gwenview Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: sasha2...@gmail.com CC: myr...@kde.org See subj. Reproducible: Always Steps to Reproduce: 1. Open some image in gwenview. 2. Press the "Crop" button within the "Image Operations" panel. 3. (Optionally) Specify crop region with mouse. 4. Press Enter. Actual Results: Gwenview goes one level up, now showing all images within directory of the original image. Expected Results: I expected the crop to be done. The "Crop" button at the bottom of the windows looks like the default button (see attach). Even if it looked the same as the "Cancel" button, I'd anyway expected it to be default. Version 15.08.2 Using: - KDE Frameworks 5.15.0 - Qt 5.5.1 (built against 5.4.2) - The xcb windowing system (This happened in prev versions too.) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 358322] Pressing Enter during crop causes going 1 level up instead of confirming the crop
https://bugs.kde.org/show_bug.cgi?id=358322 --- Comment #1 from Sasha Unspecified --- Created attachment 96771 --> https://bugs.kde.org/attachment.cgi?id=96771&action=edit Buttons with breeze style -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 358322] Pressing Enter during crop causes going 1 level up instead of confirming the crop
https://bugs.kde.org/show_bug.cgi?id=358322 --- Comment #2 from Sasha Unspecified --- Created attachment 96772 --> https://bugs.kde.org/attachment.cgi?id=96772&action=edit Buttons with gtk+ style -- You are receiving this mail because: You are watching all bug changes.
