[kontact] [Bug 319465] Kmail crashed on reply
https://bugs.kde.org/show_bug.cgi?id=319465 --- Comment #13 from abulak <abu...@gmail.com> --- (In reply to Denis Kurz from comment #12) > This bug has never been confirmed for a Kontact version that is based on KDE > Frameworks, except possibly a Technology Preview version 5.0.x. Those > versions differ significantly from the old 4.x series. Therefore, I plan to > close it in around two or three months. In the meantime, it is set to > WAITINGFORINFO to give reporters the opportunity to check if it is still > valid. As soon as someone confirms it for a recent version (at least 5.1, > ideally even more recent), I'll gladly reopen it. > > Please understand that we lack the manpower to triage bugs reported for > versions almost two years beyond their end of life. Feel free to close it now -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371199] Dragging windows on my left screen causes them to jump down to the bottom
https://bugs.kde.org/show_bug.cgi?id=371199 abulak <abu...@gmail.com> changed: What|Removed |Added CC||abu...@gmail.com --- Comment #7 from abulak <abu...@gmail.com> --- Do You have a fix/patch to test? would be glad to test; (As I understand this is related to recent changes in kwin (i.e. August 2016: https://blog.martin-graesslin.com/blog/2016/08/panels-on-shared-screen-edges/) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 327291] Memory Leak
https://bugs.kde.org/show_bug.cgi?id=327291 --- Comment #13 from abulak <abu...@gmail.com> --- No problem, I moved to plasma 5; You may as well close it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 362622] New: baloo ignores "exclude folders[$e]=$HOME/"
https://bugs.kde.org/show_bug.cgi?id=362622 Bug ID: 362622 Summary: baloo ignores "exclude folders[$e]=$HOME/" Product: frameworks-baloo Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: m...@vhanda.in Reporter: abu...@gmail.com CC: pinak.ah...@gmail.com Since some time baloosearch spits almost only empty strings as results, (I reported it somewhere here, was supposed to be fixed by 5.15, but weren't) I tried adding $HOME to exclude folders but it turns out that this option is ignored. cat ./.config/baloofilerc: [Basic Settings] Indexing-Enabled=true [General] dbVersion=2 exclude filters=*.nvram,CMakeTmp,confstat,CVS,*.loT,*.m4,config.status,.xsession-errors*,*.rcore,*.pc,lzo,litmain.sh,*.pyc,*.la,cmake_install.cmake,*.tmp,ui_*.h,CMakeTmpQmake,.git,*.class,Makefile.am,*.po,*.o,CMakeCache.txt,*.swap,.svn,*~,core-dumps,*.omf,.bzr,.hg,.pch,*.elc,*.lo,CTestTestfile.cmake,po,*.aux,*.moc,*.orig,.obj,_darcs,confdefs.h,__pycache__,*.part,*.rej,*.gmo,libtool,conftest,CMakeFiles,.uic,autom4te,moc_*.cpp,.moc,qrc_*.cpp,.histfile.*,*.vm*,*.csproj,lost+found exclude filters version=2 exclude folders[$e]=$HOME/ first run=false only basic indexing=true Reproducible: Always Steps to Reproduce: 1. balooctl disable 2. edit add home to exclude folders (in UI or directly to baloofilerc) 3. balooctl enable Actual Results: (balooctl status) Baloo File Indexer is running Indexer state: Idle Indexed 70373 / 70373 files Current size of index is 39.93 MiB Expected Results: most files have status: Scheduled; some actually turn in the search results kf-5.21 (the fact that in the bugzilla You can only select 5.20 is strange... does it mean that "kde is dying" ;-)?? this is i686, i.e. 32-bit installation. I have none of these problems on 64-bits installations I own -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 359156] Plasma 5.5.4: Configure baloo to only index filenames but no content?
https://bugs.kde.org/show_bug.cgi?id=359156 abulak <abu...@gmail.com> changed: What|Removed |Added CC||abu...@gmail.com --- Comment #1 from abulak <abu...@gmail.com> --- add only basic indexing=true into [General] section of Your ~/.config/baloofilerc -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361371] Desktop Grid: invisible windows during drag operations
https://bugs.kde.org/show_bug.cgi?id=361371 --- Comment #6 from abulak <abu...@gmail.com> --- ok, it's Present Windows ;-) The window doesn't disappear, yet it crosses the border between desktops in a jerky way : first only part of the windows visible on the initial desktop and nothing on the one You move to, then (when cursor crosses the border) the windows disappears from the initial desktop and appears on the second. Is it an intended behaviour? (Just to be extra sure I tried with only DesktopGrid and PresentWindows enabled and all enabled but PresentWindows disabled -- thanks for the kwinrc tip ;-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361371] Desktop Grid: invisible windows during drag operations
https://bugs.kde.org/show_bug.cgi?id=361371 --- Comment #4 from abulak <abu...@gmail.com> --- Still the same; this happens on OpenGL(2/3.1) Rendering backend; on XRender I don't observe the bug -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361371] Desktop Grid: invisible windows during drag operations
https://bugs.kde.org/show_bug.cgi?id=361371 --- Comment #2 from abulak <abu...@gmail.com> --- Created attachment 98246 --> https://bugs.kde.org/attachment.cgi?id=98246=edit qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361371] Desktop Grid: invisible windows during drag operations
https://bugs.kde.org/show_bug.cgi?id=361371 abulak <abu...@gmail.com> changed: What|Removed |Added Summary|Desktop Grid: invisible |Desktop Grid: invisible |windows during dragging |windows during drag |operations |operations -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361371] New: Desktop Grid: invisible windows during dragging operations
https://bugs.kde.org/show_bug.cgi?id=361371 Bug ID: 361371 Summary: Desktop Grid: invisible windows during dragging operations Product: kwin Version: 5.6.1 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: abu...@gmail.com If I activate Desktop Grid effect and drag a widows to move it to other Desktop it becomes invisible; On mouse release at the end it appears on the correct desktop (with zoom-animation, like a newly created window? not sure). definitely not critical, but a little bit annoying; Reproducible: Always Steps to Reproduce: 1. create a window 2. Activate DesktopGrid 3. drag the window to a different desktop Actual Results: the dragged window becomes invisible to appear on the right desktop after mouse release Expected Results: the dragged windows is visible during drag (to provide visual feedback to the user, blah, blah...) happens both on gentoo with fglrx and arch with intel graphics; started on 5.6.0 -- You are receiving this mail because: You are watching all bug changes.
[Baloo KCM] [Bug 351647] implement all config-features in the KCM
https://bugs.kde.org/show_bug.cgi?id=351647 abulak <abu...@gmail.com> changed: What|Removed |Added CC||abu...@gmail.com --- Comment #2 from abulak <abu...@gmail.com> --- Please add a checkbox (maybe under the Enable File Search checkbox, as a suboption) to make filename-only indexing. This should add only basic indexing=true to the [General] section of ./.config/baloorc -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 352710] baloo stops indexing after few file
https://bugs.kde.org/show_bug.cgi?id=352710 --- Comment #11 from abulak <abu...@gmail.com> --- I'm on 5.19 and indexing still stops (32bit system); @Vishesh: queries by baloosearch still return plenty of empty results (despite multiple database resets) And by the way: I found the ultimate switch: Add only basic indexing=true to the [General] section of ./.config/baloorc On my workstation (where indexing works as expected) Baloo indexes only filenames; this replaces fsrunner (almost) perfectly. (creating index took ~1s for 100k files, searches are instant!) How about adding a switch to gui for this extremely useful option? e.g. as a suboption under Enable File Search tickbox? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358262] time dataEngine has empty Local source
https://bugs.kde.org/show_bug.cgi?id=358262 --- Comment #4 from abulak <abu...@gmail.com> --- Good guess! I have plasma_engine_time.so and /usr/share/kservices5/plasma-dataengine-time.desktop. HOWEVER I don't have plasma_engine_time.so in QT_PLUGIN_PATH: QT_PLUGIN_PATH points to /usr/lib64/kde4/plugins kf5-config --qt-plugins points to /usr/lib64/qt5/plugins so this should be added somewhere in /etc/env.d I guess?? Anyway it seems more a distribution problem than kde Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358262] time dataEngine has empty Local source
https://bugs.kde.org/show_bug.cgi?id=358262 --- Comment #2 from abulak <abu...@gmail.com> --- dev-qt/qtcore (4)4.8.6-r2 (5)5.5.1 I don't have TZ env var set (env|grep TZ is null) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358262] New: time dataEngine has empty Local source
https://bugs.kde.org/show_bug.cgi?id=358262 Bug ID: 358262 Summary: time dataEngine has empty Local source Product: plasmashell Version: 5.5.3 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: DataEngines Assignee: plasma-b...@kde.org Reporter: abu...@gmail.com This results in no clock shown in sddm and default plasma clock. I have no idea how to debug it; using systemd; timedatectl: Local time: Wed 2016-01-20 16:43:37 CET Universal time: Wed 2016-01-20 15:43:37 UTC RTC time: Wed 2016-01-20 15:43:37 Time zone: Europe/Warsaw (CET, +0100) Network time on: yes NTP synchronized: yes RTC in local TZ: no /etc/localtime points where it should (/usr/share/zoneinfo/Europe/Warsaw Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356412] Windows are maximized under panel
https://bugs.kde.org/show_bug.cgi?id=356412 abulak <abu...@gmail.com> changed: What|Removed |Added CC||abu...@gmail.com --- Comment #3 from abulak <abu...@gmail.com> --- Something like this happens for me also, but: a) only with second display attached, and b) for the vertical panel on the edge connecting displays. There is a similar bug filled (323230) but for much older version (4.11?) This happens with kwin and kscreen from 5.5.3. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356412] Windows are maximized under panel
https://bugs.kde.org/show_bug.cgi?id=356412 --- Comment #5 from abulak <abu...@gmail.com> --- Created attachment 96736 --> https://bugs.kde.org/attachment.cgi?id=96736=edit output of xrandr -q -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356412] Windows are maximized under panel
https://bugs.kde.org/show_bug.cgi?id=356412 --- Comment #4 from abulak <abu...@gmail.com> --- Created attachment 96735 --> https://bugs.kde.org/attachment.cgi?id=96735=edit output of panels xprop -- You are receiving this mail because: You are watching all bug changes.
