---
Thanks,
Jekyll Wu
versions (revised edition)
http://git.reviewboard.kde.org/media/uploaded/files/2013/05/30/bugzilla-version-cheking-improved.png
Thanks,
Jekyll Wu
/drkonqi-version-checking.png
reject disabled versions (revised edition)
http://git.reviewboard.kde.org/media/uploaded/files/2013/05/30/bugzilla-version-cheking-improved.png
Thanks,
Jekyll Wu
a outdated version is still useless.
This addresses bug 315073.
http://bugs.kde.org/show_bug.cgi?id=315073
Diffs
-
Diff: http://git.reviewboard.kde.org/r/110687/diff/
Testing
---
Thanks,
Jekyll Wu
Thanks,
Jekyll Wu
On May 24, 2013, 9:44 p.m., Jekyll Wu wrote:
Bugzilla itself (since 4.2.5) already rejects any attempt against disabled
versions. So even without this patch, DrKonqi users won't be able to create
crash report against disabled versions in the end. From developers POV, you
don't need
On May 24, 2013, 9:44 p.m., Jekyll Wu wrote:
Bugzilla itself (since 4.2.5) already rejects any attempt against disabled
versions. So even without this patch, DrKonqi users won't be able to create
crash report against disabled versions in the end. From developers POV, you
don't need
] https://bugs.kde.org/show_bug.cgi?id=315073#c3
[2] https://bugs.kde.org/show_bug.cgi?id=318769#c1
- Jekyll Wu
On May 24, 2013, 2:54 p.m., Martin Gräßlin wrote:
---
This is an automatically generated e-mail. To reply, visit:
http
On 2013年02月07日 19:02, Jan Kundrát wrote:
Are most of these reports coming from DrKonqi? If so, have it fetch the
list of supported versions from somewhere and tell the user to upgrade
when their version is too old, then. (And don't accidentally prevent the
automated reporting when the version is
On 2013年02月07日 01:56, Kevin Krammer wrote:
Hi
at FOSDEM I was approached by a person who asked me to relay his
dissatisfaction with the requirement of having a KDE Bugzilla account to
report crashes via the KDE crash handler dialog.
The issue in his case was kind of made worse by having this
On 2013年02月07日 17:21, Kevin Krammer wrote:
It was definitely the process of creating an account, the developer was
explicitly stating that providing an email address isn't the problem.
Does the crash report dialog offer the option of creating an account? Does it
store the password so that it
On 2013年02月07日 18:29, Martin Gräßlin wrote:
Also spend a moment and look at the report. There is multiple times written
that we don't want any further comments on the bug and that doesn't help
anything. Still attachements, still duplicates.
I guess you are talking about
On 2013年01月09日 08:09, Martin Sandsmark wrote:
Any reason not to use bugs.kde.org?
Fixed.
Hi, I see you made the change :
-aboutData-setBugAddress(QByteArray(bugs.mango...@tarmack.eu));
+aboutData-setBugAddress(QByteArray(https://bugs.kde.org/;));
Hmm, that is not going to work.
On Jan. 5, 2013, 7:49 a.m., Erwan MATHIEU wrote:
Well, what am I supposed to do now ? I don't have a write access to the
git, so do I have to wait for someone to include the patch ?
You need to first get a Ship It! approval of the patch from some maintainer.
Only then should you worry
On Jan. 4, 2013, 8:13 p.m., John Tapsell wrote:
Ship It!
Well, I will push this patch with the assumption that you are busy and Arnav
doesn't have commit access yet.
- Jekyll
---
This is an automatically generated e-mail. To
drkonqi/drkonqidialog.cpp f2e4edf
Diff: http://git.reviewboard.kde.org/r/107775/diff/
Testing
---
Screenshots
---
show crash in General tab
http://git.reviewboard.kde.org/r/107775/s/905/
Thanks,
Jekyll Wu
the proposed change (timeout
adjusted to 15min) tomorrow so that it can catch 4.9.5
- Jekyll Wu
On Dec. 10, 2012, 8:16 a.m., Jekyll Wu wrote:
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/107657
---
show crash in General tab
http://git.reviewboard.kde.org/r/107775/s/905/
Thanks,
Jekyll Wu
/
Testing
---
Thanks,
Jekyll Wu
于 2012年12月10日 19:27, Rolf Eike Beer 写道:
The only downside is some backtrace might be lost. But I don't think
that is a big deal. Crashes during shutdown are rare cases nowadays(I
hope I'm right), and users noticing those crashes only hours later are
the rare case in rare cases (but very
combinations .
This addresses bug 242760.
http://bugs.kde.org/show_bug.cgi?id=242760
Diffs (updated)
-
ksmserver/server.cpp a65b35a
Diff: http://git.reviewboard.kde.org/r/107276/diff/
Testing
---
Thanks,
Jekyll Wu
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/107276/#review21816
---
On Dec. 9, 2012, 7:50 a.m., Jekyll Wu wrote
---
Thanks,
Jekyll Wu
=242760
Diffs (updated)
-
ksmserver/server.cpp eb3ac18
Diff: http://git.reviewboard.kde.org/r/107276/diff/
Testing
---
Thanks,
Jekyll Wu
the bug report. Put a simple patch here just in case that bug report gets
forgotten.
This addresses bug 292378.
http://bugs.kde.org/show_bug.cgi?id=292378
Diffs
-
mimetypes/kde.xml f72eb2f
Diff: http://git.reviewboard.kde.org/r/107167/diff/
Testing
---
Thanks,
Jekyll Wu
wrapper for kcodecaction.h. I guess that is an omission.
This simple patch adds it.
Diffs
-
includes/CMakeLists.txt 157d321
includes/KCodecAction PRE-CREATION
Diff: http://git.reviewboard.kde.org/r/105818/diff/
Testing
---
Thanks,
Jekyll Wu
://git.reviewboard.kde.org/r/105483/diff/
Testing
---
Thanks,
Jekyll Wu
---
Thanks,
Jekyll Wu
---
The sample code works fine with kdelibs/4.8 and konsole built from master.
Thanks,
Jekyll Wu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I am trying to fix bug 259539. The real problem is some global
shortcuts of klipper keep resetting to 'None' after it restarts. Here
is one problematic line:
action-setGlobalShortcut(KShortcut(.), KAction::DefaultShortcut);
The
30 matches
Mail list logo
