[bugs.kde.org] [Bug 371501] Se traba el programa cuando se usa la acción Cerrar desde la Barra de Herramientas
https://bugs.kde.org/show_bug.cgi?id=371501 Nicolás Alvarez changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID CC||nicolas.alva...@gmail.com --- Comment #1 from Nicolás Alvarez --- bugs.kde.org es para reportar problemas directamente a los programadores, en inglés. Tu reporte ni siquiera dice con qué programa de KDE tienes problemas... Deberías publicar tu pregunta en https://forum.kde.org/, tiene una categoría en español. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 370164] SSL certificate for planetkde.org has expired
https://bugs.kde.org/show_bug.cgi?id=370164 Nicolás Alvarez changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||nicolas.alva...@gmail.com Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 369369] New: Methods get wrong arguments marked as optional in tooltip
https://bugs.kde.org/show_bug.cgi?id=369369 Bug ID: 369369 Summary: Methods get wrong arguments marked as optional in tooltip Product: kdev-python Version: 5.0.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Code completion Assignee: m...@svenbrauch.de Reporter: nicolas.alva...@gmail.com If a function has optional arguments (arguments with default values), the tooltip that appears when typing the arguments in a call shows square brackets around the optional arguments: def func1(arg1, arg2, arg3=None, arg4=42, arg5='default'): pass func1( # argument tooltip says void func1 (arg1, arg2, [arg3, arg4, arg5]) However, an instance method with optional arguments shows the square brackets in the wrong set of arguments: class C: def func1(self, arg1, arg2, arg3=None, arg4=42, arg5='default'): pass c = C() c.func1( # argument tooltip says void func1 (arg1, arg2, arg3, [arg4, arg5]) It appears as if arg3 was not optional, but it is. This is probably because it's not compensating for the presence of the implicit 'self' parameter. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 369367] Caught exceptions get wrong scope (py3 change)
https://bugs.kde.org/show_bug.cgi?id=369367 Nicolás Alvarez changed: What|Removed |Added Priority|NOR |LO --- Comment #1 from Nicolás Alvarez --- Ugh, this is trickier than I thought because it's not really a "scope". Python pretty much runs 'del exc' after the except block. exc = "hello world" try: a=1/0 except Exception as exc: print(exc) print(exc) The second print statement will raise a NameError, it will neither print the exception nor "hello world". So it's not a matter of using a different setup of DUContexts to create a scope; you would need support for deleting individual variables. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 369367] New: Caught exceptions get wrong scope (py3 change)
https://bugs.kde.org/show_bug.cgi?id=369367
Bug ID: 369367
Summary: Caught exceptions get wrong scope (py3 change)
Product: kdev-python
Version: 5.0.1
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language support
Assignee: m...@svenbrauch.de
Reporter: nicolas.alva...@gmail.com
Python3 has changed the scoping for exceptions caught in an 'except..as'
statement. The Python3 documentation says: "When an exception has been assigned
using "as target", it is cleared at the end of the except clause. This means
the exception must be assigned to a different name to be able to refer to it
after the except clause."
Sample code:
try:
a=1/0
except Exception as exc:
print("1", exc)
print("2", exc)
If I run this on Python2, it prints "division by zero" twice. If I run it on
Python3, it prints "division by zero" in print #1, and then raises a NameError
in #2 because 'exc' is not defined.
KDevelop still follows the Python2 scoping in this case, and 'exc' is still
highlighted as a use of the variable in the second 'print' call.
--
You are receiving this mail because:
You are watching all bug changes.
[kdev-python] [Bug 309817] Wrong scope in the list of superclasses
https://bugs.kde.org/show_bug.cgi?id=309817 --- Comment #5 from Nicolás Alvarez --- (In reply to Sven Brauch from comment #4) > Note: This corner-case is still broken (discivered by Nicolas): > [...] > To be fixed for 1.5. I confirm this is still broken in 5.0.1... -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 369364] New: Calling an instance method through the class deduces arg types wrong
https://bugs.kde.org/show_bug.cgi?id=369364 Bug ID: 369364 Summary: Calling an instance method through the class deduces arg types wrong Product: kdev-python Version: 5.0.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language support Assignee: m...@svenbrauch.de Reporter: nicolas.alva...@gmail.com If an instance method is called 'directly' through the class, like this: class MyClass: def method(self, arg1): pass obj = MyClass() MyClass.method(obj, 42) The argument type is deduced wrong. It thinks the 'obj' argument matches with the 'arg1' parameter, but it should be matched with 'self'. This means it deduces 'arg1' to be of type 'MyClass', when it should be 'int'. A notable common case where this causes problems is when a constructor calls the constructor of the base class: class Base: def __init__(self, foo): self.foo = foo class Derived(Base): def __init__(self, foo): Base.__init__(self, foo) # ...more Derived-specific initialization... Now it thinks Base.__init__'s 'foo' argument is of type 'Derived', which also affects the type of the 'foo' attribute of the object, which cascades into breaking types in many other places :( -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 369363] Type not inferred when iterating objects with __next__
https://bugs.kde.org/show_bug.cgi?id=369363
--- Comment #1 from Nicolás Alvarez ---
By the way, as another example for the unit tests:
class Foo:
def __iter__(self):
return Bar()
def __next__(self):
return "blah"
class Bar:
def __next__(self):
return {}
for x in Foo():
pass
Here 'x' should be of type 'dict', not 'str'!
--
You are receiving this mail because:
You are watching all bug changes.
[kdev-python] [Bug 369363] New: Type not inferred when iterating objects with __next__
https://bugs.kde.org/show_bug.cgi?id=369363 Bug ID: 369363 Summary: Type not inferred when iterating objects with __next__ Product: kdev-python Version: 5.0.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language support Assignee: m...@svenbrauch.de Reporter: nicolas.alva...@gmail.com If I have a generator implemented as a function, iterating over it with a for loop (or list comprehension) correctly deduces the type of the item variable: def gen1(): yield "blah" for item1 in gen1(): print(item1) Here, KDevelop knows item1 is a str, because that is what gen1 yields. However, if I do the same with a class that has a custom __next__ method, the type is not deduced: class Gen2: def __iter__(self): return self def __next__(self): return "blah" gen2 = Gen2() for item2 in gen2: print(item2) The tooltip shows item2 as 'mixed', its attributes are not highlighted or completed, etc. This affects a few built-in types, such as I/O classes that yield strings (lines) when iterated. (In many cases the definitions in documentation_files don't have a __next__ and they should, but the point of this bug is that adding the missing __next__ makes no difference) -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 369265] New: Autocomplete __main__ check
https://bugs.kde.org/show_bug.cgi?id=369265 Bug ID: 369265 Summary: Autocomplete __main__ check Product: kdev-python Version: 5.0.1 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Code completion Assignee: m...@svenbrauch.de Reporter: nicolas.alva...@gmail.com KDevelop currently autocompletes the Python shebang and the encoding declaration, at appropriate places in the file and if they aren't already present. It would be useful to also complete other common boilerplate constructs, such as: if __name__ == "__main__": which checks if the current module is being executed directly by the Python interpreter, and not imported from something else. Maybe it could complete the == "__main__" part after seeing the "if __name__" part. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 179289] Improve dolphin behaviour in situations when user "doesn't have enough permission".
https://bugs.kde.org/show_bug.cgi?id=179289 Nicolás Alvarez changed: What|Removed |Added CC||kdelibs-b...@kde.org, ||nicolas.alva...@gmail.com Component|general |general Product|kio |frameworks-kio -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 366981] Mailto URL does not allows a body with line breaks
https://bugs.kde.org/show_bug.cgi?id=366981 Nicolás Alvarez changed: What|Removed |Added Assignee|n...@kde.org|kdepim-b...@kde.org CC||nicolas.alva...@gmail.com Component|Spam|general Version|unspecified |5.1.3 Group|sysadmin| Product|Spam|kmail2 --- Comment #2 from Nicolás Alvarez --- My apologies, I accidentally selected this bug while deleting a lot of spam. Restoring data... -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 365083] sundtek - missing initialization for dvb device + patch
https://bugs.kde.org/show_bug.cgi?id=365083 Nicolás Alvarez changed: What|Removed |Added CC||nicolas.alva...@gmail.com Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|WONTFIX |--- --- Comment #10 from Nicolás Alvarez --- I don't even care what weird proprietary hardware would be fixed by this: the existing code looks buggy and the patch seems to fix it. DvbLinuxDeviceManager::componentAdded(QString node, int adapter, int index) is creating a DvbLinuxDevice with heap garbage in the 'adapter', 'index', and 'dvbv5_parms' members. Unless I'm missing something, they are not initialized anywhere, not even in the constructor. How is that not a bug, and why not merge the patch? If different future changes break support for this hardware again because the driver is doing things fundamentally wrong, we'll discuss it then, but it's orthogonal. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 357158] bangla soft
https://bugs.kde.org/show_bug.cgi?id=357158 Nicolás Alvarez changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||nicolas.alva...@gmail.com Resolution|--- |INVALID -- You are receiving this mail because: You are watching all bug changes.
[Trash] [Bug 364908] 1866.388.3501 Quickbooks s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r usa
https://bugs.kde.org/show_bug.cgi?id=364908 Nicolás Alvarez changed: What|Removed |Added Component|docs.kde.org|Trash Product|docs|Trash CC||nicolas.alva...@gmail.com Assignee|kde-doc-engl...@kde.org |sysad...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359603 --- Comment #48 from Nicolás Alvarez --- Since we're not going to write and maintain a custom patch to deal with this, please take this problem to upstream Bugzilla. I'm sure you would be interested in not having this problem with any other bugtracker either, rather than just KDE... -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359603 --- Comment #33 from Nicolás Alvarez --- (In reply to Pali Rohár from comment #32) > 2) If such anti-spam protection drops more than 30% of non-spam emails > then it is not only useless but must be avoided because it drop regular > non-spam messages. Same as sending all emails to /dev/null. It is > absolute anti-spam protection but totally useless. Yup, I agree. But it's not our fault. Go complain to Yahoo and to the inventors of DMARC. We can't fix it, we can only apply workarounds to ensure our mail reaches our users. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359603 --- Comment #19 from Nicolás Alvarez --- What email client are you using? I see "Pali Rohár via KDE Bugzilla" in the notifications about your comments. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359603 --- Comment #21 from Nicolás Alvarez --- Then maybe we should tweak Bugzilla to use the email address if there is no name. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 360642] New: Add notes to watch list entries
https://bugs.kde.org/show_bug.cgi?id=360642 Bug ID: 360642 Summary: Add notes to watch list entries Product: konversation Version: 1.5 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: nicolas.alva...@gmail.com It's happening often that I add someone to my watch list, and by the time they come online, I forget why I added them to the watch list. I would like a way to assign a note to a watch list entry, so that Konversation can remind me of why I'm watching that user. For example, someone asks a question I knew the answer for, but goes offline before I can answer, I add him to my watch list with the question (or answer) as the note, and when he comes online (possibly days later!), the "user has come online" notice will include the note to remind me what I had to tell him. (I may implement this myself... some day) -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359603 --- Comment #26 from Nicolás Alvarez --- (In reply to Pali Rohár from comment #24) > Ben, but there is no difference between email sent by Bugzilla and email > sent by kde.org list (both with d=kde.org DKIM signature). In both cases > that email is sent by outgoing kde.org SMTP server. Yes there is a difference, there is a huge difference. If a GMail user posts to a mailing list, that message will be DKIM-signed by Google. We will *also* add a kde.org DKIM signature, but that doesn't matter. From: someth...@gmail.com and properly signed by Google. A message automatically sent by Bugzilla can't possibly have a DKIM signature from your provider. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 338854] Support Windows calling conventions
https://bugs.kde.org/show_bug.cgi?id=338854 --- Comment #1 from Nicolás Alvarez --- I haven't tested, but *presumably* __declspec and macros using it (like __stdcall) can now be parsed with no problems in clang. However, the code completion for overrides would still give the mentioned problem. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 359915] New: Tuple unpacking in a list comprehension not supported
https://bugs.kde.org/show_bug.cgi?id=359915
Bug ID: 359915
Summary: Tuple unpacking in a list comprehension not supported
Product: kdev-python
Version: frameworks
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language support
Assignee: m...@svenbrauch.de
Reporter: nicolas.alva...@gmail.com
When a list comprehension has multiple identifiers in the 'for' clause, it's
supposed to do sequence unpacking. This has several problems in kdev-python.
In the simplest case, variables are identified but not given the correct types:
data = [('a',1), ('b',2)] # data is 'list of tuple of (str,int)'
strs = [a for a,b in data] # 'a' is mixed, 'b' is mixed, 'strs' is 'list of
mixed'
It should be able to recognize that 'a' is str and 'b' is int.
If there are nested tuples, the inner ones aren't even recognized as variable
declarations (related: bug 314024):
data2 = [(1, ('x', 3.0)), (2, ('y', 4.5))] # list of tuple of ( int, tuple
of ( str, float ) )
[a for (a,(b,c)) in data2] # 'a' is mixed, 'b' and 'c' are underlined as
undefined variables
And here is an almost-realistic ultimate sample that would go great in the test
suite :)
users = {'a':19, 'b':42, 'c':35}
sorted_list = sorted(users.items(), key=lambda kv: (-kv[1], kv[0]))
result = [(r,k,v) for r,(k,v) in enumerate(sorted_list, 1)] # 'result'
should be a tuple of (int, str, int)
--
You are receiving this mail because:
You are watching all bug changes.
[kdev-python] [Bug 359914] New: Sequence unpacking with nested tuples doesn't recognize types
https://bugs.kde.org/show_bug.cgi?id=359914
Bug ID: 359914
Summary: Sequence unpacking with nested tuples doesn't
recognize types
Product: kdev-python
Version: frameworks
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language support
Assignee: m...@svenbrauch.de
Reporter: nicolas.alva...@gmail.com
When unpacking nested tuples, kdev-python doesn't recognize the types of the
unpacked variables.
For example:
data = (1, ('x', 3.0))
iii, ttt = data # 'iii' is int, 'ttt' is tuple
sss, fff = ttt # 'sss' is str, 'fff' is float
aaa, (bbb, ccc) = data # however aaa, bbb and ccc are all 'mixed' here
Related: bug 314024 where this was implemented (it gave 'undefined variable'
before)
--
You are receiving this mail because:
You are watching all bug changes.
[kdev-python] [Bug 359912] New: Type not recognized in expressions with multiple subscripts
https://bugs.kde.org/show_bug.cgi?id=359912 Bug ID: 359912 Summary: Type not recognized in expressions with multiple subscripts Product: kdev-python Version: frameworks Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language support Assignee: m...@svenbrauch.de Reporter: nicolas.alva...@gmail.com If I use multiple subscripts like a[0][1], the type of the expression is shown as 'mixed', even in cases where doing the subscripts separately with a temporary variable gives the correct type. Example code: class Inner: pass class Middle: def __getitem__(self, key): return Inner() class Outer: def __getitem__(self, key): return Middle() aaa = Outer() # 'aaa' is Outer bbb = aaa[0] # 'bbb' is Middle ccc = bbb[0] # 'ccc' is Inner ggg = aaa[0][0] # 'ggg' is mixed, should be Inner hhh = (aaa[0])[0] # this doesn't help, still mixed Curiously, it does work for list (and maybe for all TypeContainers?): mylist = [[['a']]] x1 = mylist[0][0] # list of str x2 = mylist[0][0][0] # str -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 359907] New: Module imported twice makes first one become undefined
https://bugs.kde.org/show_bug.cgi?id=359907 Bug ID: 359907 Summary: Module imported twice makes first one become undefined Product: kdev-python Version: frameworks Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language support Assignee: m...@svenbrauch.de Reporter: nicolas.alva...@gmail.com If a module is imported twice in a script, it becomes undefined between the first and the second import. For example: import os print(os.name) # 'os' is underlined in green, tooltip says 'Undefined variable', 'name' is black import os print(os.name) # both 'os' and 'name' are highlighted green, no underline -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 359905] New: Crash when generating documentation for unknown module
https://bugs.kde.org/show_bug.cgi?id=359905 Bug ID: 359905 Summary: Crash when generating documentation for unknown module Product: kdev-python Version: frameworks Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: m...@svenbrauch.de Reporter: nicolas.alva...@gmail.com CC: m...@svenbrauch.de I opened a .py file which has 'import requests', 'requests' was underlined in red. I moved the mouse over 'requests', and selected Solve -> Generate documentation in the tooltip. Then in the dialog I clicked Generate, then Save and Close, at which point KDevelop crashed: Thread 1 (Thread 0x7feeaea6a940 (LWP 11407)): [KCrash Handler] #6 0x7feec4a62f3e in QObjectPrivate::isSignalConnected (signal_index=3, this=0x4) at kernel/qobject_p.h:250 #7 QMetaObject::activate (sender=0x4abc3c0, signalOffset=, local_signal_index=, argv=0x7ffe6c2efc20) at kernel/qobject.cpp:3588 #8 0x7feec8ce5c3c in KDevelop::IAssistantAction::executed(KDevelop::IAssistantAction*) () from /home/nicolas/local/lib/x86_64-linux-gnu/libKDevPlatformInterfaces.so.10 #9 0x7fee91807326 in Python::DocumentationGeneratorAction::execute() () from /home/nicolas/local/lib/x86_64-linux-gnu/libkdevpythonduchain.so #10 0x7feec8cd5723 in QtPrivate::FunctorCall, QtPrivate::List<>, void, void (KDevelop::IAssistantAction::*)()>::call(void (KDevelop::IAssistantAction::*)(), KDevelop::IAssistantAction*, void**) () from /home/nicolas/local/lib/x86_64-linux-gnu/libKDevPlatformInterfaces.so.10 #11 0x7feec8cd5690 in void QtPrivate::FunctionPointer::call, void>(void (KDevelop::IAssistantAction::*)(), KDevelop::IAssistantAction*, void**) () from /home/nicolas/local/lib/x86_64-linux-gnu/libKDevPlatformInterfaces.so.10 #12 0x7feec8cd54f8 in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /home/nicolas/local/lib/x86_64-linux-gnu/libKDevPlatformInterfaces.so.10 #13 0x7feec4a63537 in QtPrivate::QSlotObjectBase::call (a=0x7ffe6c2effe0, r=0x4abc3c0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #14 QMetaObject::activate (sender=sender@entry=0x4ab7330, signalOffset=, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffe6c2effe0) at kernel/qobject.cpp:3698 #15 0x7feec4a63ea7 in QMetaObject::activate (sender=sender@entry=0x4ab7330, m=m@entry=0x7feec582af00 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffe6c2effe0) at kernel/qobject.cpp:3578 #16 0x7feec531e3b2 in QAction::triggered (this=this@entry=0x4ab7330, _t1=false) at .moc/moc_qaction.cpp:365 #17 0x7feec5320838 in QAction::activate (this=0x4ab7330, event=) at kernel/qaction.cpp:1162 #18 0x7feec54a3202 in QMenuPrivate::activateCausedStack (this=this@entry=0x4a1e570, causedStack=..., action=action@entry=0x4ab7330, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1130 #19 0x7feec54a94ac in QMenuPrivate::activateAction (this=this@entry=0x4a1e570, action=action@entry=0x4ab7330, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1207 #20 0x7feec54ad420 in QMenu::mouseReleaseEvent (this=, e=0x7ffe6c2f0620) at widgets/qmenu.cpp:2540 #21 0x7feec536afe8 in QWidget::event (this=this@entry=0x449f750, event=event@entry=0x7ffe6c2f0620) at kernel/qwidget.cpp:9044 #22 0x7feec54ade63 in QMenu::event (this=0x449f750, e=0x7ffe6c2f0620) at widgets/qmenu.cpp:2654 #23 0x7feec5327ffc in QApplicationPrivate::notify_helper (this=this@entry=0x110d920, receiver=receiver@entry=0x449f750, e=e@entry=0x7ffe6c2f0620) at kernel/qapplication.cpp:3716 #24 0x7feec532dbc9 in QApplication::notify (this=, receiver=0x449f750, e=0x7ffe6c2f0620) at kernel/qapplication.cpp:3276 #25 0x7feec4a34b5b in QCoreApplication::notifyInternal (this=0x7ffe6c2f2e78, receiver=receiver@entry=0x449f750, event=event@entry=0x7ffe6c2f0620) at kernel/qcoreapplication.cpp:965 #26 0x7feec532cad2 in QCoreApplication::sendSpontaneousEvent (event=0x7ffe6c2f0620, receiver=0x449f750) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:227 #27 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x449f750, event=event@entry=0x7ffe6c2f0620, alienWidget=alienWidget@entry=0x0, nativeWidget=0x449f750, buttonDown=buttonDown@entry=0x7feec5859b20 , lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:2770 #28 0x7feec538594d in QWidgetWindow::handleMouseEvent (this=this@entry=0x4da6600, event=event@entry=0x7ffe6c2f0a30) at kernel/qwidgetwindow.cpp:452 #29 0x7feec5387bab in QWidgetWindow::event (this=0x4da6600, event=0x7ffe6c2f0a30) at kernel/qwidgetwindow.cpp:210 #30 0x7feec5327ffc in QApplicationPrivate::notify_helper (this=this@entry=0x110d920, receiver=receiver@entry=0x4da6600, e
[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359603 --- Comment #14 from Nicolás Alvarez --- "DMARC protects the domain name of the RFC5322:From field against spoofing" -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359603 --- Comment #12 from Nicolás Alvarez --- People are sending DKIM-signed messages from their respective providers into our mailing lists, and we're forwarding them without modifying anything that would break the DKIM signature. Other subscribers then get messages with From: foo...@yahoo.com and the DKIM signature matches the public key from yahoo.com. Bugzilla can't auto-generate messages with From: foo...@yahoo.com and DKIM-sign them with Yahoo's key. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359603 --- Comment #7 from Nicolás Alvarez --- Will *you* explain to all our GMail and Yahoo user that it is "their problem" if every bugzilla message arrives to their spam folder? -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359603 Nicolás Alvarez changed: What|Removed |Added CC||nicolas.alva...@gmail.com --- Comment #5 from Nicolás Alvarez --- Complain to the creators of DMARC. Complain to the email providers following DMARC and sending RFC-compliant messages to the spam folder. We can't do anything about it. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 358446] Non free file
https://bugs.kde.org/show_bug.cgi?id=358446 Nicolás Alvarez changed: What|Removed |Added CC||nicolas.alva...@gmail.com --- Comment #5 from Nicolás Alvarez --- CC-BY-NC doesn't comply with our licensing policy, and can't be "linked" with eg. GPL code. However, it *is* redistributable. It's not like someone committed EULA-protected software like Adobe Flash into the repository (where Linux distros have to workaround the fact that it's non-redistributable). We're in no legal trouble by simply having this file in our server. I see no need to remove it from the repository history. Just rm it from the latest version. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 271073] Argument completion stops working after invalid previous arg
https://bugs.kde.org/show_bug.cgi?id=271073 --- Comment #4 from Nicolás Alvarez --- Oh wow, I really imagined it would work now. Thanks for testing! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 271073] Argument completion stops working after invalid previous arg
https://bugs.kde.org/show_bug.cgi?id=271073 --- Comment #2 from Nicolás Alvarez --- This is probably fixed in KDevelop5, but your screenshot is not really evidence for it. You should write a comma and see what completion you get on the *second* argument. It should offer 'foo' (because the type matches) above other local variables. I don't currently have KDevelop5 to try it myself. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 336228] pressing f12 (or the equivalent closekey) causes respawn of yakuake if mouse is in yakuake
https://bugs.kde.org/show_bug.cgi?id=336228 Nicolás Alvarez changed: What|Removed |Added CC||nicolas.alva...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 357268] Leakage of user information
https://bugs.kde.org/show_bug.cgi?id=357268 Nicolás Alvarez changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID CC||nicolas.alva...@gmail.com --- Comment #2 from Nicolás Alvarez --- This is not a leakage, email addresses on Bugzilla are public. Move mouse over your name in your bug comments and you will see your email address is visible there too. When you create a Bugzilla account, there is a warning saying "KDE Bugtracking System is an open bug tracking system. Activity on most bugs, including email addresses, will be visible to the public. We recommend using a secondary account or free web email service (such as Gmail, Yahoo, Hotmail, or similar) to avoid receiving spam at your primary email address." -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 356177] New: Tab completion clears undo history for input line
https://bugs.kde.org/show_bug.cgi?id=356177 Bug ID: 356177 Summary: Tab completion clears undo history for input line Product: konversation Version: 1.5 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: inputline Assignee: konversation-de...@kde.org Reporter: nicolas.alva...@gmail.com When editing text in the input line, I can use Ctrl-Z to undo individual changes. But as soon as I hit Tab to do tab completion (even if it fails!), Ctrl-Z doesn't work anymore, as if it cleared the undo history completely. -- You are receiving this mail because: You are watching all bug changes.
