[frameworks-baloo] [Bug 474346] baloo_file_extractor fills swap space even though there's plenty of RAM available
https://bugs.kde.org/show_bug.cgi?id=474346 Branimir Amidzic changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from Branimir Amidzic --- (In reply to tagwerk19 from comment #1) > Two things to check... > > Is baloo running with the systemd memory limits? There's been a recent > change to limit baloo to using 512 MB. You can check with: > $ systemctl status --user kde-baloo > and look at "high" value in the "Memory:" line. > > This can tip baloo_file and baloo_file_extractor over to using swap. Have a > look at: > https://bugs.kde.org/show_bug.cgi?id=470382#c1 > > It's also possible you are hitting a file that does not want to be indexed. > Baloo_file_extractor tries to get readable text out of a file and some times > this just does not work in the time and space available (examples being a > multi-gigabyte .mbox file or large scientific graphs in a PDF). You would > need to watch, with "balooctl monitor" what was being indexed. Thanks! It seems this was false alarm. I guess that baloo_file_extractor behaves this way only when indexing files. Now, after it has finished indexing, the swap usage is back to 0%. Sorry for raising flags... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 474346] New: baloo_file_extractor fills swap space even though there's plenty of RAM available
https://bugs.kde.org/show_bug.cgi?id=474346 Bug ID: 474346 Summary: baloo_file_extractor fills swap space even though there's plenty of RAM available Classification: Frameworks and Libraries Product: frameworks-baloo Version: 5.109.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: m...@ambraspace.com Target Milestone: --- SUMMARY baloo_file_extractor fills swap space even though there's plenty of RAM available. STEPS TO REPRODUCE 1. Verify that file search (including file contents) is enabled and that the files have been indexed. 2. Check RAM and swap file usage. If there's plenty of RAM available and swap usage is couple of GB try following steps. 3. Open System activity (CTRL+ESC) and stop baloo_file_extractor (right click on baloo_file_extractor and go to Send signal -> STOP). 4. Remove swap file (swapoff -a) 5. Mount swap file (swapon -a) 6. Verify that swap usage is around 0%. 7. Resume baloo_file_extractor (Send signal -> CONT) 8. Monitor swap file usage. It should go up very quickly after you resume baloo_file_extractor. OBSERVED RESULT After starting or resuming baloo_file_extractor swap file usage goes up very quickly although there's plenty of RAM available. EXPECTED RESULT baloo_file_extractor should use RAM if it's available and use swap only if there's no RAM available SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Kernel Version: 6.4.12-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × 12th Gen Intel® Core™ i5-1235U Memory: 31,0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Dell Inc. Product Name: Latitude 5530 ADDITIONAL INFORMATION I haven't noticed similar with previous versions of KDE/Plasma/Baloo. I have set "vm.swappiness=10". It should use swap even less. I use swap file (not swap partition). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 473573] In twin view the location bar can be moved independently of the folder panel
https://bugs.kde.org/show_bug.cgi?id=473573 Branimir Amidzic changed: What|Removed |Added CC||m...@ambraspace.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 473573] New: In twin view the location bar can be moved independently of the folder panel
https://bugs.kde.org/show_bug.cgi?id=473573 Bug ID: 473573 Summary: In twin view the location bar can be moved independently of the folder panel Classification: Applications Product: dolphin Version: 23.04.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: m...@ambraspace.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 161081 --> https://bugs.kde.org/attachment.cgi?id=161081&action=edit Dolphin window with location bar moved relative to folder panel SUMMARY Location Bar can be moved by grabbing the slider regardless of the folder panel. STEPS TO REPRODUCE 1. Display folder in split view 2. Position mouse pointer left of the location bar and grab the slider. 3. Move the slider left or right (see the attachment) OBSERVED RESULT The location bar moves regardless of the folders panel and stays there until the location is changed. EXPECTED RESULT The slider for the location bar and for the folders panel should be the same. Moving the location bar should move the folder pane also and vice versa. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.4.11-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × 12th Gen Intel® Core™ i5-1235U Memory: 31,0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Dell Inc. Product Name: Latitude 5530 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 384902] Kmail2 modifies a BCCed message upon reception from server
https://bugs.kde.org/show_bug.cgi?id=384902 --- Comment #4 from Branimir Amidzic --- Unfortunately, I'm not using KMail any more. I had too many issues, not only with kmail, but with Akonadi also. I switched to Thinderbird long time ago, so I can't test it. Regards, Branimir -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 460442] Unable to use KAlarm because "no writable active calendar is enabled"
https://bugs.kde.org/show_bug.cgi?id=460442 Branimir Amidzic changed: What|Removed |Added CC||m...@ambraspace.com --- Comment #5 from Branimir Amidzic --- This seems to be libical problem. The most recent is 3.0.15. When I downgraded to 3.0.14 everything works fine. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411844] Info panel displays EXIF data for all documents (DOC etc.)
https://bugs.kde.org/show_bug.cgi?id=411844 --- Comment #2 from Branimir Amidzic --- I haven't seen it lately. Maybe this should be closed, since it is not known how to reproduce the behavior. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411844] New: Info panel displays EXIF data for all documents (DOC etc.)
https://bugs.kde.org/show_bug.cgi?id=411844 Bug ID: 411844 Summary: Info panel displays EXIF data for all documents (DOC etc.) Product: dolphin Version: 19.08.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: information Assignee: dolphin-bugs-n...@kde.org Reporter: m...@ambraspace.com Target Milestone: --- Created attachment 122622 --> https://bugs.kde.org/attachment.cgi?id=122622&action=edit Screenshot of document details SUMMARY Info panel (as well as document "tooltip") displays bogus data about files. If I select some MS Word document, it displays EXIF image data, like Width, Height, Camera, Exposure, Shutter Speed... (probably remained in cache from some JPG). STEPS TO REPRODUCE 1. In Gwenview in "Metadata" pane check that you want to display Camera details (manufacturer, model). 2. In Dolphin, move mouse pointer over some file that has no EXIF data (like MS Word document), or 3. in Dolphin, open info pane and select some file that has no EXIF data (like MS Word document). OBSERVED RESULT The file tooltip or info pane displays bogus data about the file. EXPECTED RESULT Info pane should display only data relevant to selected file. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (current, kernel 4.19.71-1-lts) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 357206] baloo_file crashes in Baloo::PostingDB::get()
https://bugs.kde.org/show_bug.cgi?id=357206 Branimir Amidzic changed: What|Removed |Added CC||m...@ambraspace.com --- Comment #30 from Branimir Amidzic --- I have the same problem. The bug exists in several versions. My current config: KDE Plasma: 5.14.5 KDE FW: 5.54.0 Qt: 5.11.3 Gentoo stable 64bit Kernel: 4.19.23 ambra@toshiba ~ $ balooctl indexSize Actual Size: 3,03 GiB Expected Size: 2,16 GiB PostingDB: 602,46 MiB27.288 % PositionDB: 921,75 MiB41.750 % DocTerms: 296,18 MiB13.415 % DocFilenameTerms: 18,70 MiB 0.847 % DocXattrTerms: 4,00 KiB 0.000 % IdTree: 2,48 MiB 0.112 % IdFileName: 13,74 MiB 0.622 % DocTime: 6,88 MiB 0.311 % DocData: 21,35 MiB 0.967 % ContentIndexingDB:0 B 0.000 % FailedIdsDB:0 B 0.000 % MTimeDB: 4,94 MiB 0.224 % Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f171c00f800 (LWP 29540))] Thread 3 (Thread 0x7f170f38c700 (LWP 29542)): [KCrash Handler] #6 0x7f1719a80c01 in ?? () from /lib64/libc.so.6 #7 0x7f171b02dae3 in ?? () from /usr/lib64/libKF5BalooEngine.so.5 #8 0x7f171b01f2b4 in Baloo::PostingDB::get(QByteArray const&) () from /usr/lib64/libKF5BalooEngine.so.5 #9 0x7f171b02b1e0 in Baloo::WriteTransaction::commit() () from /usr/lib64/libKF5BalooEngine.so.5 #10 0x7f171b0248d2 in Baloo::Transaction::commit() () from /usr/lib64/libKF5BalooEngine.so.5 #11 0x55e1d9aab577 in ?? () #12 0x7f171a50b0e1 in ?? () from /usr/lib64/libQt5Core.so.5 #13 0x7f171a51354f in ?? () from /usr/lib64/libQt5Core.so.5 #14 0x7f17178e896a in start_thread () from /lib64/libpthread.so.0 #15 0x7f1719a1b1af in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f170fd8e700 (LWP 29541)): #0 0x7f1715ecdea4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f1715e87528 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1715e87f0b in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f1715e880ec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f171a6fb12b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f171a6a711a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f171a509aea in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7f171b24ade5 in ?? () from /usr/lib64/libQt5DBus.so.5 #8 0x7f171a51354f in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x7f17178e896a in start_thread () from /lib64/libpthread.so.0 #10 0x7f1719a1b1af in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f171c00f800 (LWP 29540)): #0 0x7f1719a0f5d3 in poll () from /lib64/libc.so.6 #1 0x7f1715e87fd9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1715e880ec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f171a6fb12b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f171a6a711a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f171a6afb00 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x55e1d9aa071c in ?? () #7 0x7f1719938ae7 in __libc_start_main () from /lib64/libc.so.6 #8 0x55e1d9aa098a in ?? () -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 402120] "Pay to" field gets auto filled from previous transaction even if cleared manually
https://bugs.kde.org/show_bug.cgi?id=402120 --- Comment #2 from Branimir Amidzic --- (In reply to Jack from comment #1) > I'm pretty sure this is a duplicate, but I'll have to check later. However, > the issue is that if there is nothing entered in the payee field when you > either click or tab to another field, or save the transaction, KMM retains > what was already in that field. The temporary workaround is to enter a > single space for the payee and then either go to another field or save. The > program will ask if you want to create a payee with the name " " and if you > say "no" it will leave the field blank. It may be reported earlier, because it's quite annoying, but I couldn't find any earlier bug reports. Workaround would be not to type single space (because there may be many payees with a space in the name) but two spaces, and - when asked by the program to add a new payee - click No. This is only a workaround but it's quite tedious to think about this bug when entering each transaction. The other workaround would be to force some payee, for example "Unknown" or similar. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 402120] New: "Pay to" field gets auto filled from previous transaction even if cleared manually
https://bugs.kde.org/show_bug.cgi?id=402120 Bug ID: 402120 Summary: "Pay to" field gets auto filled from previous transaction even if cleared manually Product: kmymoney Version: 5.0.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: m...@ambraspace.com Target Milestone: --- SUMMARY When entering a new transaction the field "Pay to" gets the value from previous transaction even if it is manually deleted (empty). STEPS TO REPRODUCE 1. Enter a new transaction with any Payee in "Pay to" field, but not empty 2. Enter a new transaction with "Pay to" field cleared 3. Press Enter to save the transaction OBSERVED RESULT The second transaction gets the same Payee even if it was set to no payee. EXPECTED RESULT The second transaction should have empty payee assigned. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Frameworks 5.52.0 (available in About System) KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: Qt 5.11.1 (built against 5.11.1) ADDITIONAL INFORMATION I think the problem exists in all 5.* versions. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdelibs4support] [Bug 380973] KDE Calculates Hijri Calendar Incorrectly
https://bugs.kde.org/show_bug.cgi?id=380973 Branimir Amidzic changed: What|Removed |Added CC||m...@ambraspace.com --- Comment #1 from Branimir Amidzic --- I confirm that this is present in recent Plasma version (5.10.5). Looking at https://cgit.kde.org/kholidays.git/tree/holidays/plan2/holiday_ba-srp_sr@ijekavianlatin the "Kurban-bajram" is correctly set, but the system calculates the date to be 23-24.12.2017. while it should be 1.9.2017. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 384902] Kmail2 modifies a BCCed message upon reception from server
https://bugs.kde.org/show_bug.cgi?id=384902 --- Comment #2 from Branimir Amidzic --- Created attachment 107921 --> https://bugs.kde.org/attachment.cgi?id=107921&action=edit The message in Inbox folder This message is not displayed correctly. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 384902] Kmail2 modifies a BCCed message upon reception from server
https://bugs.kde.org/show_bug.cgi?id=384902 --- Comment #1 from Branimir Amidzic --- Created attachment 107920 --> https://bugs.kde.org/attachment.cgi?id=107920&action=edit The message in Sent folder and on server Kmail2 displays this message well. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 384902] New: Kmail2 modifies a BCCed message upon reception from server
https://bugs.kde.org/show_bug.cgi?id=384902 Bug ID: 384902 Summary: Kmail2 modifies a BCCed message upon reception from server Product: kmail2 Version: 5.5.3 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: m...@ambraspace.com Target Milestone: --- I have a problem with displaying of some emails. "Some" means that I noticed this problem only on mails that I send to myself (BCC) and not to mails that other people send to me. I don't know why it should make the difference... The problem is that these emails are displayed like source text. For example: START --- This is a multi-part message in MIME format. --nextPart18849102.z2M5TSk1NK Content-Type: multipart/related; boundary="nextPart1707749.fno8PCFPKE" Content-Transfer-Encoding: 7Bit This is a multi-part message in MIME format. --nextPart1707749.fno8PCFPKE Content-Type: multipart/alternative; boundary="nextPart1674577.pBNLayei6U" Content-Transfer-Encoding: 7Bit This is a multi-part message in MIME format. --nextPart1674577.pBNLayei6U Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Po=C5=A1tovani =C4=90or=C4=91e, --- STOP (The last line is the text contained in the mail.) After comparing this message in Inbox folder, Sent folder and on the server, I noticed that messages on the server and Sent folder are equal, but the message in Inbox folder differs from them in one line. Kmail2 changed this line: Content-Type: multipart/mixed; boundary="nextPart18849102.z2M5TSk1NK" to: Content-Type: text/plain; charset="US-ASCII" So, because in my Inbox folder I have this second line, the message is not displayed correctly. Why would this happen? Please see the two attachment for file differences (only showing relevant data and modified personal data). -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 363205] Akonadi stops synchronizing CalDAV calendar after awhile, due to Malformed URL error.
https://bugs.kde.org/show_bug.cgi?id=363205 Branimir Amidzic changed: What|Removed |Added CC||m...@ambraspace.com --- Comment #1 from Branimir Amidzic --- I'm having the same problem with eGroupware 16.1.005, while everything works as expected with ownCloud calendars and tasks. It seem that there was similar problem fixed in 4.14.10. See bug: https://bugs.kde.org/show_bug.cgi?id=338570 -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 373623] New: Wrong rm -i behaviour
https://bugs.kde.org/show_bug.cgi?id=373623 Bug ID: 373623 Summary: Wrong rm -i behaviour Product: kde-cli-tools Version: 5.8.3 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: m...@ambraspace.com Target Milestone: --- When I type rm -o in Konsole and reply "n" (for avoiding the deletion of a file) the file gets removed anyway. It doesn't matter what I type. The file always gets deleted. I thought this was specific to Konsole, but the same happens with xterm. The behaviour outside the GUI is as expected. I'm not sure which component is responsible, so please move it if it belongs to another package. Here's my environment: ANT_HOME=/usr/share/ant BROWSER=/usr/bin/firefox-bin CASROOT=/usr/lib64/opencascade-6.7.1/ros/lin CG_COMPILER_EXE=/opt/bin/cgc CG_INC_PATH=/opt/nvidia-cg-toolkit/include CG_LIB_PATH=/opt/nvidia-cg-toolkit/lib64 COLORFGBG=15;0 CONFIG_PROTECT_MASK=/etc/gentoo-release /etc/sandbox.d /etc/php/cli-php5.6/ext-active/ /etc/php/cgi-php5.6/ext-active/ /etc/php/apache2-php5.6/ext-active/ /etc/fonts/fonts.conf /etc/gconf /etc/terminfo /etc/dconf /etc/ca-certificates.conf /etc/revdep-rebuild CONFIG_PROTECT=/usr/share/maven-bin-3.3/conf /usr/share/gnupg/qualified.txt /usr/share/config /usr/share/themes/oxygen-gtk/gtk-2.0 CSF_EXCEPTION_PROMPT=1 CSF_GraphicShr=/usr/lib64/opencascade-6.7.1/ros/lin/lib64/libTKOpenGl.so CSF_IGESDefaults=/usr/lib64/opencascade-6.7.1/ros/lin/src/XSTEPResource CSF_LANGUAGE=us CSF_MDTVFontDirectory=/usr/lib64/opencascade-6.7.1/ros/lin/src/FontMFT CSF_MDTVTexturesDirectory=/usr/lib64/opencascade-6.7.1/ros/lin/src/Textures CSF_MIGRATION_TYPES=/usr/lib64/opencascade-6.7.1/ros/lin/src/StdResource/MigrationSheet.txt CSF_PluginDefaults=/usr/lib64/opencascade-6.7.1/ros/lin/src/StdResource CSF_SHMessage=/usr/lib64/opencascade-6.7.1/ros/lin/src/SHMessage CSF_StandardDefaults=/usr/lib64/opencascade-6.7.1/ros/lin/src/StdResource CSF_StandardLiteDefaults=/usr/lib64/opencascade-6.7.1/ros/lin/src/StdResource CSF_STEPDefaults=/usr/lib64/opencascade-6.7.1/ros/lin/src/XSTEPResource CSF_UnitsDefinition=/usr/lib64/opencascade-6.7.1/ros/lin/src/UnitsAPI/Units.dat CSF_UnitsLexicon=/usr/lib64/opencascade-6.7.1/ros/lin/src/UnitsAPI/Lexi_Expr.dat CSF_XCAFDefaults=/usr/lib64/opencascade-6.7.1/ros/lin/src/StdResource CSF_XmlOcafResource=/usr/lib64/opencascade-6.7.1/ros/lin/src/XmlOcafResource CSF_XSMessage=/usr/lib64/opencascade-6.7.1/ros/lin/src/XSMessage DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-BnphjHvbxa,guid=8db7b30f99605547cc72bc11584c230c DESKTOP_SESSION=/usr/share/xsessions/plasma DISPLAY=:0 EDITOR=/bin/nano GCC_SPECS= GSETTINGS_BACKEND=dconf GS_LIB=/home/ambra/.fonts GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/ambra/.gtkrc-2.0:/home/ambra/.config/gtkrc-2.0 GTK_RC_FILES=/etc/gtk/gtkrc:/home/ambra/.gtkrc:/home/ambra/.config/gtkrc GUILE_LOAD_PATH=/usr/share/guile/1.8 HISTCONTROL=ignoredups HOME=/home/ambra INFOPATH=/usr/share/info:/usr/share/gcc-data/x86_64-pc-linux-gnu/4.9.3/info:/usr/share/binutils-data/x86_64-pc-linux-gnu/2.25.1/info ITCL_LIBRARY=/usr/lib64/itcl3.4 ITK_LIBRARY=/usr/lib64/itk3.4 JAVAC=/etc/java-config-2/current-system-vm/bin/javac JAVA_HOME=/etc/java-config-2/current-system-vm JDK_HOME=/etc/java-config-2/current-system-vm KDE_FULL_SESSION=true KDE_MULTIHEAD=false KDE_SESSION_UID=1000 KDE_SESSION_VERSION=5 KONSOLE_DBUS_SERVICE=:1.3057 KONSOLE_DBUS_SESSION=/Sessions/4 KONSOLE_DBUS_WINDOW=/Windows/4 KONSOLE_PROFILE_NAME=Shell LANG=bs_BA.UTF-8 LANGUAGE=en_US LESSOPEN=|lesspipe %s LESS=-R -M --shift 5 LOGNAME=ambra LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.cfg=00;32:*.conf=00;32:*.
[kwalletmanager] [Bug 343718] after update to 14.12.1 I can't open my kde wallets
https://bugs.kde.org/show_bug.cgi?id=343718 --- Comment #55 from Branimir Amidzic --- Finally made it with openSuSE 13.2 with updated kwalletmanager and kdebase4-runtime... -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 343718] after update to 14.12.1 I can't open my kde wallets
https://bugs.kde.org/show_bug.cgi?id=343718 Branimir Amidzic changed: What|Removed |Added CC||m...@ambraspace.com --- Comment #54 from Branimir Amidzic --- Dear all, I have read this bug report and your comments thoroughly, However, I'm not able to open my wallets. I'm using Gentoo stable and updated release. KDE/KWallet version is 4.14.3. I can see that the patch is applied on my Gentoo system and I don't remember having troubles opening the wallets on my system. However, my computer is in service shop. I have full backup of my system, and I can't open my wallets and access my passwords. I'm having a nightmare. I tried: Kubuntu-14.04.4, Kubuntu-15.10, Mint-17.3, Sabayon-15.02.1, Slackel-16.02. Neither one of these distribution can open my wallets. Is it possible that neither one has applied the patch?! Gentoo has this patch since August 2015 and I'm pretty sure that my wallets are updated. Hex dump of both my wallets has "01 03 02 KWALLET" sequence. Does this mean that the wallets have been updated? Does anyone knows any distribution that I can boot and open my wallets? Kind regards! -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 346060] KAlarm calculates deferred alarm time wrongly
https://bugs.kde.org/show_bug.cgi?id=346060 --- Comment #4 from Branimir Amidzic --- Created attachment 96941 --> https://bugs.kde.org/attachment.cgi?id=96941&action=edit KAlarm settings -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 346060] KAlarm calculates deferred alarm time wrongly
https://bugs.kde.org/show_bug.cgi?id=346060 --- Comment #3 from Branimir Amidzic --- Created attachment 96940 --> https://bugs.kde.org/attachment.cgi?id=96940&action=edit Calendar file -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 346060] KAlarm calculates deferred alarm time wrongly
https://bugs.kde.org/show_bug.cgi?id=346060 --- Comment #2 from Branimir Amidzic --- Hi, David! Thanks for your interest in this bug. I've just tested it again and the bug is still there. I have the same KAlarm version as reported previously. I tied to test it with one-time alarm. I set one display alarm to trigger in several minutes. It did and I successfully deferred it for several more minutes. Time calculation was correct. Then I tried to reproduce the bug with repeating alarm with repeating interval in days. These are the steps I took; 1. File, New, New Display Alarm (Ctrl+D) 2. Type some display text 3. "At date/time" set to today and checked "Any time" 4. On Recurrence tab I set Daily and Recur every 15 days 5. After clinking OK, alarm immediately pops. 6. I chose Defer and defer it for 15 hours and 17 minutes, so that it time boxes above it displays that the alarm should trigger tomorrow at 3 a.m. 7. When I press OK the main KAlarm window shows that the alarm will trigger tomorrow at 1 p.m. - IT ADDED 10 HOURS. Furthermore (I just discovered this). After restarting KAlarm and opening main window, this alarm (previously set for 1 p.m.) was now set to 8 a.m. - it returned back 5 hours! I'm really puzzled. :) After repeated restart it stays at 8 a.m. My suggestion is to check calculation of deferred time for DATE-ONLY alarms. In my KAlarm settings for "start of day for date-only alarms" I set 5:00. I guess that that KAlarm added 5 hours to 3 a.m. that I wanted. Main window also added the same amount, but it only was reflected to display of alarms. After restart in effect was only first 5 hours added. After changing "start of day for date-only alarms" to 06:00, main KAlarm window displayed 3 p.m. and after restarting it got back to 9 a.m. - 6 hours added to 3 a.m. that I wanted. Please try taking the same steps I took. I'm pretty sure you'll will reproduce this bug, as I tried everything: deleting data and similar. Regarding your questions: - I haven't expresses myself correctly. The system is set to CET (GMT+1). Clock applet has three time zones set, but I guess it's only relevant to the clock applet. - Time zone in KAlarm is same as system time zone (Europe/Sarajevo) - No, I didn't edit the alarm. I just deferred it, and check if it was set correctly. - I will add the attachment so you can examine the calendar and KAlarm settings. -- You are receiving this mail because: You are watching all bug changes.
