[trojita] [Bug 419734] UID consistency error

2020-04-06 Thread Turtle 
https://bugs.kde.org/show_bug.cgi?id=419734

Turtle  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #1 from Turtle  ---
Upon furthur investigation this bug was likely caused by sending a 'killall' or
SIGTERM trojita

Deleting the file ~/.cache/flaska.net/trojita/imap.cache.sqlite
resolved the issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 419734] New: UID consistency error

2020-04-06 Thread Turtle 
https://bugs.kde.org/show_bug.cgi?id=419734

Bug ID: 419734
   Summary: UID consistency error
   Product: trojita
   Version: 0.7
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Core
  Assignee: trojita-b...@kde.org
  Reporter: tur...@think-electric.com
  Target Milestone: ---

SUMMARY
When opening a imap inbox hosed on dreamhost I get:
 imapError The IMAP server sent us a reply which we could not parse.
Please report this as a bug anyway. Here are the details:
MailboxException: FETCH response: UID consistency error for message #3955 --
expected UID 41643, got UID 41646
FETCH 3955 ( FLAGS \"\\Answered \\Seen\" UID \"41646\")

STEPS TO REPRODUCE
1. Open trojita
2. trojita reloads imap inbox


OBSERVED RESULT
Inbox does not finish loading, gets stuck.

EXPECTED RESULT
Inbox should load as expected.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 5.64.0
KDE Frameworks Version: 5.67
Qt Version: 5.13.2

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 416775] New: trojita: test_Imap_BodyParts.cpp fails to compile with qt 5.13 gcc 9.2

2020-01-25 Thread Turtle 
https://bugs.kde.org/show_bug.cgi?id=416775

Bug ID: 416775
   Summary: trojita: test_Imap_BodyParts.cpp fails to compile with
qt 5.13 gcc 9.2
   Product: trojita
   Version: 0.7
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Other
  Assignee: trojita-b...@kde.org
  Reporter: tur...@think-electric.com
  Target Milestone: ---

Created attachment 125421
  --> https://bugs.kde.org/attachment.cgi?id=125421=edit
patch

SUMMARY
A redefinition of ‘char* QTest::toString(const T&) in test_Imap_BodyParts.cpp

When compiling trojita-0.7/tests/Imap/test_Imap_BodyParts.cpp:56:7: 
I get the following error: 
redefinition of ‘char* QTest::toString(const T&) [with T = QModelIndex]’
STEPS TO REPRODUCE
1. Install gcc 9.2, qt 5.13.2, kde
2. download trojita
3. Compile will fail

(Gentoo) Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2

ADDITIONAL INFORMATION
Commenting out the redefinition fixes the compile failure.
Not sure if it causes any other issues.
Thank you

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 411774] New: Long-lived YAWP Bug (all flavors) Crashes Plasma

2019-09-09 Thread Walking Turtle 
https://bugs.kde.org/show_bug.cgi?id=411774

Bug ID: 411774
   Summary: Long-lived YAWP Bug (all flavors) Crashes Plasma
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: revwalkingtur...@yandex.com
  Target Milestone: ---

Application: plasma-desktop (4.11.13)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 4.9.0-0.bpo.9-amd64 x86_64
Distribution: MX-16.1 Metamorphosis

-- Information about the crash:
- What I was doing when the application crashed:
I was setting-up YAWP as follows:  
1) Invoked Debian Weather Service. 
2) Fed it my ZIP code (wrong move).  
3) On closing the "No Such Location" panel, the entire Desktop crashed to
blackscreen.  Then regenerated itself (minus some recent desktop mods done
following the most recent reboot) due to having set that feature up prior.

- Custom settings of the application:  None in particular.  Telling the
AccuWeather Service the ZIP worked fine.  (I still /will/ go back and try
telling the Debian Service some different Plausible Things.)  But the point is
the crashing of the desktop on failure (on the part of the currently-chosen
service)to accept the syntax and/or ZIP code as location data.

Note:  This key data requirement varies from service to service.  But Yours
truly has observed it across numerous platforms at setup-time over many years. 
 And no matter what:  Do it wrong for /any/ service (variable requirements;  do
not know them all yet) and down goes Plasma!  And that is all. 0{:-\o[

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6ea37d6800 (LWP 3916))]

Thread 17 (Thread 0x7f6e68115700 (LWP 3948)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f6e9c1dadea in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x7f6e9c1dae19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x7f6e96a08064 in start_thread (arg=0x7f6e68115700) at
pthread_create.c:309
#4  0x7f6ea30d762d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 16 (Thread 0x7f6de707f700 (LWP 3950)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f6e9df1006f in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f6e9df100a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f6e96a08064 in start_thread (arg=0x7f6de707f700) at
pthread_create.c:309
#4  0x7f6ea30d762d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 15 (Thread 0x7f6da677c700 (LWP 3959)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f6e9dc32973 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f6e9df3f7f6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f6e96a08064 in start_thread (arg=0x7f6da677c700) at
pthread_create.c:309
#4  0x7f6ea30d762d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 14 (Thread 0x7f6d9e441700 (LWP 4058)):
#0  0x7f6ea30ceaed in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f6e960e4ee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6e960e4ffc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6e9fb8fd37 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7f6e9fb5f271 in
QEventLoop::processEvents(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x7f6e9fb5f5d5 in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7f6e9fa53e99 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x7f6e9fb3fac3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x7f6e9fa5670f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7f6e96a08064 in start_thread (arg=0x7f6d9e441700) at
pthread_create.c:309
#10 0x7f6ea30d762d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 13 (Thread 0x7f6d9693f700 (LWP 4065)):
#0  0x7f6e96129379 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f6e960e4fe8 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6e9fb8fd37 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3  0x7f6e9fb5f271 in
QEventLoop::processEvents(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7f6e9fb5f5d5 in

[kdiff3] [Bug 410962] kdiff3 vs svn (subversion)

2019-09-09 Thread Turtle 
https://bugs.kde.org/show_bug.cgi?id=410962

--- Comment #2 from Turtle  ---
I did some poking around and this is defiantly something to do with the newer
QT port.
In main.cpp just after
initialiseCmdLineArgs(cmdLineParser);
// ignorable command options
There are some calls like:
cmdLineParser->addOption(QCommandLineOption(QStringList() <<
QLatin1String("m") << QLatin1String("merge"), i18n("Merge the input.")));

Then some calls to add the files:
cmdLineParser->addPositionalArgument(QLatin1String("[File1]"), i18n("file1
to open (base, if not specified via --base)"));
cmdLineParser->addPositionalArgument(QLatin1String("[File2]"), i18n("file2
to open"));
cmdLineParser->addPositionalArgument(QLatin1String("[File3]"), i18n("file3
to open"));

However the options seem to be clobbering the files, so my guess is another
cmdLineParser needs to loop for every option that == 'L'

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdiff3] [Bug 411602] New: Unable to choose a file for all unsolved whitespace conflicts in 1.8

2019-09-04 Thread Turtle 
https://bugs.kde.org/show_bug.cgi?id=411602

Bug ID: 411602
   Summary: Unable to choose a file for all unsolved whitespace
conflicts in 1.8
   Product: kdiff3
   Version: 1.8.x
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: reeves...@gmail.com
  Reporter: tur...@think-electric.com
  Target Milestone: ---

Created attachment 122494
  --> https://bugs.kde.org/attachment.cgi?id=122494=edit
Restores ability to choose a file for all unsolved whitespace conflicts

SUMMARY 1.8.1 (64 bit) Dropped support for choosing [A-C] for unsolved
whitespace conflicts


STEPS TO REPRODUCE
1. Install Version 0.9.98, merge some files with whitespace conflicts, you can
choose A B or C from the 'Merge' menu
2. Install 1.8.1 the choice is gone from the 'Merge' menu


OBSERVED RESULT
Unable to choose a file for all unsolved whitespace conflicts

EXPECTED RESULT
Same functions as 0.9.98, Should have a Merge menu option to chose A-C for all
unsolved conflicts and all unsolved whitespace conflicts.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.60.0
Qt Version: 5.12.3

ADDITIONAL INFORMATION

Attached patch putting functionality back in.
I am currently running the patch in Gentoo and it works.
Note: you might need to clean up the whitespace in the patch.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdiff3] [Bug 410962] kdiff3 vs svn (subversion)

2019-09-01 Thread Turtle 
https://bugs.kde.org/show_bug.cgi?id=410962

Turtle  changed:

   What|Removed |Added

Version|1.7.90  |1.8.x
 CC||tur...@think-electric.com

--- Comment #1 from Turtle  ---
I can confirm this bug in 1.8, as a workaround call this
shell script from svn.
#!/bin/sh
kdiff3 --base "$6" "$7" --output "$7"

-- 
You are receiving this mail because:
You are watching all bug changes.

[Falkon] [Bug 399898] New: Add ability to view frame source

2018-10-16 Thread Turtle 
https://bugs.kde.org/show_bug.cgi?id=399898

Bug ID: 399898
   Summary: Add ability to view frame source
   Product: Falkon
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: tur...@think-electric.com
  Target Milestone: ---

THIS IS A FEATURE REQUEST:

SUMMARY
It would be nice if Falkon could show me the html source of the curremt heml4
frame.

STEPS TO REPRODUCE
1.Go to a site that uses html 4.01 frame sets
like https://www.htmlgoodies.com/legacy/tutorials/frames/fr4t3.html
2. Right click on a frame and select view source


OBSERVED RESULT
 Sourcecode of the entire page will be displayed.

EXPECTED RESULT
Firefox has a feature that allows a user to "view frame source", it would be
cool if falkon could do the same.

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.12
KDE Frameworks Version: 
Qt Version: 5.9

ADDITIONAL INFORMATION
Kernel Linux-4.18.12
Platform x86_64-Intel-R-_Core-TM-_i7-3520M_CPU_@_2.90GHz
libtool:2.4.6-r3
make:   4.2.1-r4
glibc:   2.26-r7
I am running Falkon stand alone without KDE.

COMMENT:
I doubt that across the entire web html 4.01 frame sets will go away any time
soon.  It would make it handy for web developers to use Falkon.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Falkon] [Bug 399897] New: Falkon: Switching between tabs forces tab to reload

2018-10-16 Thread Turtle 
https://bugs.kde.org/show_bug.cgi?id=399897

Bug ID: 399897
   Summary: Falkon: Switching between tabs forces tab to reload
   Product: Falkon
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: tur...@think-electric.com
  Target Milestone: ---

SUMMARY
A webbrowser should only reload a webbage when requested to do so. Switching
between tabs in falkon reloads the tab. 

STEPS TO REPRODUCE
1. Open several tabs
2. Wait a short while
3. Switch between tabs
4. Browser will reload the tab.

OBSERVED RESULT
Browser will reload the tab.

EXPECTED RESULT
Tab should stay exactly as it was.

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version:5.12 
KDE Frameworks Version: 
Qt Version: 5.9

ADDITIONAL INFORMATION
I am running Falkon in openbox without a full KDE.
Kernel Linux-4.18.12
Platform x86_64-Intel-R-_Core-TM-_i7-3520M_CPU_@_2.90GHz
libtool:2.4.6-r3
make:   4.2.1-r4
glibc:   2.26-r7

-- 
You are receiving this mail because:
You are watching all bug changes.