[Bug 1240673] Re: Reports 0% charged for fully charged batteries

2013-10-20 Thread costavi
I have the same problem with mye Dell Latitude E5530, as reported on this (duplicate) bug report: https://bugs.launchpad.net/ubuntu/+source/kde-baseapps/+bug/1235633 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report.

[Bug 1242293] Re: Plasma-desktop crashes regularly every 5 minutes after 13.10 update

2013-10-20 Thread Harald Sitter
Please report the crash backtrace to http://bugs.kde.org if you do not have one, then I suggest that you turn off apport because we do not support usage of apport on stable releases for KDE software. ** Changed in: kde-workspace (Ubuntu) Status: New = Invalid -- You received this bug

[Bug 1207589]

2013-10-20 Thread josephk
here (arch 64 ktorrent 4.3.1 kde 4.11.2) bug is still present with the well known warning There are no IP addresses to convert in XYZ compressed ip lists do get decompressed, but do not get loaded. loading archives in formats that my system doesn't support, produces the same warning. even if i

[Bug 1235633] Re: kde battery applet shows 0% on full charged battery with Dell Latitude e5530: kubuntu 13.10

2013-10-20 Thread David Cecchin
*** This bug is a duplicate of bug 1240673 *** https://bugs.launchpad.net/bugs/1240673 Confirmed on Dell Latitude E6530. Unplugging the power makes the correct power usage show, the indicator also says Discharging. Plugging it back, you get Not Charging. (But it is actually charging). --

[Bug 1242404] [NEW] Kopete never finishes logging in into facebook account

2013-10-20 Thread bcmpinc
Public bug reported: Upon connecting to a facebook account using kopete, the account will remain in 'connecting' state indefenitely. Kopete is able to receive messages, which will show up in the chat window normally. However, when trying to send a message, a messagebox appears with Please connect

[Bug 1242404] Re: Kopete never finishes logging in into facebook account

2013-10-20 Thread bcmpinc
It has been reported at https://bugs.kde.org/show_bug.cgi?id=324937. ** Bug watch added: KDE Bug Tracking System #324937 https://bugs.kde.org/show_bug.cgi?id=324937 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kopete-facebook in

[Bug 959151] Re: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.

2013-10-20 Thread pazuzuthewise
It happens to me also in Saucy x86. Ktorrent would not start, and when invoked from console, it gives the respective error message. Disabling nepomuk (in System settings Desktop search), seems to fix the problem. With Nepomuk disabled, Ktorrent starts normally. -- You received this bug

[Bug 1242479] Re: Device notifier always shows a removable device of 0 Bytes

2013-10-20 Thread Harald Sitter
Hi there! Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct

[Bug 1242137] [NEW] brightness control keys don't work after upgrade to 13.10

2013-10-20 Thread Launchpad Bug Tracker
You have been subscribed to a public bug: Right after upgrade to Kubuntu 13.10 the 'fn' keys for brightness controll stopped working. Hardware: HP ProBook 4525s Software: Kubuntu 13.10, uname -a: 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:12:00 UTC 2013 i686 athlon i686 GNU/Linux **

[Bug 1242137] Re: brightness control keys don't work after upgrade to 13.10

2013-10-20 Thread Ales
I'm really not sure if 'kwin' is the source of the problem. ** Package changed: ubuntu = kdebase-workspace (Ubuntu) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1242137 Title: