[Bug 1449583] Re: notifications won't stop popping
Launchpad has imported 15 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=346622. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2015-04-25T07:47:47+00:00 Abdeljalil wrote: a notification about system update has appeared, I clicked on closing button in the notification applet, the notification gone, but after nearly 2 or 3 seconds it shows again, and still popping and disappearing and can't stop it. this is very annoying behaviour Reproducible: Didn't try Actual Results: The notification disappeared then pops out again after clicking on close button Expected Results: The notification should go forever after clicking the close button after a while, may be 10 minutes the notification disappeared and this behaviour stopped automatically Reply at: https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1449583/comments/0 On 2015-04-25T08:03:54+00:00 Mklapetek wrote: Thanks for the report. First of all please always attach the images directly here, never use sites like imgur because then they can expire whenever and then this report would have no image :) Second, I've noticed this in Kubuntu as well and I think this is a fault in some of their component which keeps emitting the notification. Harald - which is the component emitting this and where can I look at the code? Reply at: https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1449583/comments/1 On 2015-04-25T08:52:44+00:00 Harald Sitter wrote: Muon. Reply at: https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1449583/comments/2 On 2015-04-25T08:54:37+00:00 Harald Sitter wrote: FWIW I am actually reasonable certain that the problem is muon monitoring some file to notice when there are changes on debian distros and that file gets touched more than once per apt update run, so muon notifies for each file modification. Reply at: https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1449583/comments/3 On 2015-04-27T09:50:12+00:00 Mklapetek wrote: Yeah I had a similar guess. It can be observed especially during "apt- get update". I'm looking into this. Reply at: https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1449583/comments/4 On 2015-04-27T09:52:05+00:00 Jonathan Riddell wrote: ApplicationNotifier.cpp has a watch stampDirWatch which gets called a lot ApplicationNotifier::distUpgradeEvent could also do with being called less often or checking the notification hasn't already been shown today Reply at: https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1449583/comments/5 On 2015-04-27T09:53:02+00:00 Jonathan Riddell wrote: they're both called stampDirWatch for some reason recheckSystemUpdateNeeded is the system release upgrade notification and gets called lots Reply at: https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1449583/comments/6 On 2015-04-27T14:02:54+00:00 Aleix Pol wrote: Git commit 217834e6a20d07b7f99415525a27928329cae88c by Aleix Pol. Committed on 27/04/2015 at 14:01. Pushed by apol into branch 'Plasma/5.3'. Only emit about found updates when they change M +11 -3libmuon/backends/ApplicationBackend/ApplicationNotifier.cpp M +2-0libmuon/backends/ApplicationBackend/ApplicationNotifier.h http://commits.kde.org/muon/217834e6a20d07b7f99415525a27928329cae88c Reply at: https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1449583/comments/7 On 2015-04-27T14:11:43+00:00 Mklapetek wrote: Well, so much for "I'm looking into this" :P /me drops it then Reply at: https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1449583/comments/8 On 2015-04-27T17:04:25+00:00 Aleix Pol wrote: Well, it's not fixed, it will still be called more times than needed (if it really does happen every now and then while upgrading). Reply at: https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1449583/comments/9 On 2015-05-14T11:18:15+00:00 Aleix Pol wrote: *** Bug 345823 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1449583/comments/15
[Bug 373302] Re: Kopete can't insert new line
Launchpad has imported 8 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=187120. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2009-03-14T10:44:49+00:00 gneman wrote: Version: 4.2.1 (using KDE 4.2.1) Compiler: GCC-4.3.3 OS:Linux Installed from:Unspecified Linux After upgrading to Qt-4.5, I cannot start a new line in Kopete's message window. It used to work with Ctrl+return, but now it stopped working. I don't know if it's a Kopete bug or a Qt one, or just some configuration change. If you think I should report it to Qt please let me know. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/373302/comments/0 On 2009-03-26T10:20:00+00:00 Rastos-kdebugs wrote: A new line can be entered in chat window by pressing the Enter key on the numeric keypad. However I would also prefer to have Ctrl+Enter available. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/373302/comments/1 On 2009-03-29T20:25:44+00:00 Matt Rogers wrote: oh, that is annoying. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/373302/comments/2 On 2009-04-10T14:36:46+00:00 Martin-batora wrote: hi! shift + enter works for me Reply at: https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/373302/comments/3 On 2009-04-10T14:58:40+00:00 gneman wrote: Aha, shift + enter does work here too. So it seems it was a configuration change in QT and not a bug? Go figure why they changed it, but anyway thanks for the tip. Maybe the bug can be closed, but it would be nice to document the change somewhere, no? Reply at: https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/373302/comments/4 On 2009-05-03T08:51:10+00:00 Kde-bugzilla-2 wrote: Keep the bug open. If necessary, add an explicit "Insert newline" entry in the shortcuts dialog which I can set to Ctrl+Enter, but I don't consider Shift+Enter to be a solution worthy of RESO. If I was OK with all my apps having unconfigurable, potentially mutually-incompatible keybindings, I'd use GNOME as my desktop, emacs as my code editor, Firefox as my main browser, and I'd give up on ever enjoying the efficiency that muscle memory can bring. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/373302/comments/5 On 2021-03-09T22:40:50+00:00 Justin Zobel wrote: Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/373302/comments/12 On 2021-03-09T22:48:12+00:00 gneman wrote: After 12 years I guess it can certainly be closed. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/373302/comments/13 ** Changed in: kopete Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdenetwork in Ubuntu. https://bugs.launchpad.net/bugs/373302 Title: Kopete can't insert new line To manage notifications about this bug go to: https://bugs.launchpad.net/kopete/+bug/373302/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 206396]
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdenetwork in Ubuntu. https://bugs.launchpad.net/bugs/206396 Title: kopete with meanwhile sametime protocol can't handle accents To manage notifications about this bug go to: https://bugs.launchpad.net/kopete/+bug/206396/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 104171] Re: KGPG editor decrypt fails if > 3 recipients
Launchpad has imported 11 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=143935. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2007-04-07T18:18:55+00:00 LanceHaverkamp wrote: Version: 1.2.2 (using KDE KDE 3.5.3) Installed from:Ubuntu Packages OS:Linux If a message encrypted to several recipients is pasted into (or opened in) the KGPG editor; KGPG seems to try only the first 3 keys. It asks for the password for each of the first 3 keys then fails. When you start clicking cancel to close the multiple password windows the application crashes. I believe KGPG should first determine if the the user actually has any secret keys that will decrypt the message, then ask for only the password for the correct key. Thanks, Lance Reply at: https://bugs.launchpad.net/ubuntu/+source/kdeutils/+bug/104171/comments/1 On 2007-08-30T21:38:09+00:00 JimmyGilles wrote: Hello, could you explain how I can reproduce this issue ? I have gpg 1.4.6 and kgpg 1.2.2 I tried but can't reproduce this problem. My steps: - i go to the editor - i write something - i click "encrypt" - i select more than 3 recipients - there are two cases : the option "Hide user id" is selected or is not selected First case: "Hide user id" is NOT selected When I want to decrypt, gpg will automatically detect if I have a secret key that will decrypt the message (because all userid are stored in the encrypted message) If I have a good key, kgpg asks me to give the password and decrypt the message. If I don't have any key, kgpg will fail. Second case: "Hide user id" is selected When I want to decrypt the message, gpg will try with every secret keys in my keyring until it can decrypt the message. Thanks Reply at: https://bugs.launchpad.net/ubuntu/+source/kdeutils/+bug/104171/comments/2 On 2007-08-31T01:59:31+00:00 LanceHaverkamp wrote: Created attachment 21516 error message Reply at: https://bugs.launchpad.net/ubuntu/+source/kdeutils/+bug/104171/comments/3 On 2007-08-31T02:23:11+00:00 LanceHaverkamp wrote: For some reason the message portion of the above attachment was discarded, here is a repost: The behavior seems to have changed since it was first reported, something must have upgraded. Now it does appear to work sometimes. Other times kgpg correctly identifies the message as having been encrypted to my key & asks for my passphrase 3 times very quickly, without waiting for a reply. When this happens I receive the error message above (MISSING_PASSPHRASE). When entering passphrase or closing the 3 passphrase windows, kgpg usually crashes. I suggest you subscribe to the public PGP chat group, http://groups.yahoo.com/group/PGPNET/ You will be able to collect several examples of pgp encrypted messages that are encrypted to well over a dozen people using various OpenPGP programs. You should be able to see that some work in kgpg, but others do not. These are not bad postings...they decrypt using enigmail (and the exact same version of GnuPG). I don't know enough what to look for, but something is different about some messages. It seems dependent on what software or settings the sender has chosen, as the same senders' messages usually (always?) crash. Certain algorithms? Certain hashes? Thanks, Lance Reply at: https://bugs.launchpad.net/ubuntu/+source/kdeutils/+bug/104171/comments/4 On 2007-08-31T03:02:56+00:00 LanceHaverkamp wrote: OK, I think I've got a resolution...You're not gonna believe this: Normally, plain text following the encrypted message is ignored; it's just left there to be read either before or after the decryption takes place. For some reason I can't explain, the YahooGroups trailing text crashes kgpg! the bad text follows this line & starts with some blank lines: Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/PGPNET/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/PGPNET/join (Yahoo! ID required) <*> To change settings via email: mailto:pgpnet-dig...@yahoogroups.com mailto:pgpnet-fullfeatu...@yahoogroups.com <*> To unsubscribe from this group, send an email to: pgpnet-unsubscr...@yahoogroups.com <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/ Reply at: https://bugs.launchpad.net/ubuntu/+source/kdeutils/+bug/104171/comments/5
[Bug 1205842]
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qapt in Ubuntu. https://bugs.launchpad.net/bugs/1205842 Title: qapt-deb-installer's Status and Details misleading and confusing To manage notifications about this bug go to: https://bugs.launchpad.net/qapt/+bug/1205842/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1912262] Re: Kubuntu 21.04 QA Test Installer Crashed during OEM Install
** Tags added: kubuntu ** Changed in: ubiquity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to ubiquity in Ubuntu. https://bugs.launchpad.net/bugs/1912262 Title: Kubuntu 21.04 QA Test Installer Crashed during OEM Install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1912262/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 975056]
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/975056 Title: KWin shortcuts don't work on second monitor To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/975056/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1916857] Re: Color corections not sticking in Plasma
Forgot to say I tried colormgr device-make-profile-default but it didn't work ** Summary changed: - Color corections not sticking in Plasma + colord not working correctly in KDE / Plasma 5.21 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1916857 Title: colord not working correctly in KDE / Plasma 5.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1916857/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1916857] Re: Color corections not sticking in Plasma
It appears to be colord. When the service is stopped KDE / Plasma is able to dictate the colour profile to be used. So KDE / Plasma 5.21 is unable to act as a client to colord and its desires are being overridden by colord on a polled basis. Ubuntu / Gnome is able to override what colord defaults to, but only as long as you're using Ubuntu / Gnome. So what is colord using as its default? This is different from the default profile in KDE / Plasma. How is colord configured? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1916857 Title: colord not working correctly in KDE / Plasma 5.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1916857/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
