https://bugs.kde.org/show_bug.cgi?id=462170
Nate Graham changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=462170
luca changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=462170
--- Comment #27 from luca ---
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027831
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=462170
--- Comment #26 from Nate Graham ---
Ah, PackageKitQt uses different version numbers, I see.
Regardless, please report the issue upstream.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=462170
--- Comment #25 from luca ---
In debian testing/unstable the DiscoverNotifier issue starts with
libpackagekitqt5-1:amd64 Vers.1.1.0-1 released one mounth ago
https://github.com/PackageKit/PackageKit-Qt
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=462170
Nate Graham changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=462170
--- Comment #23 from luca ---
If you can not wait and you are brave can try this workaround:
- extract libpackagekitqt5.so.1.0.2 from previous libpackagekitqt5-1
- replace libpackagekitqt5.so.1.0.3(first save it with another name) in
/usr/lib/x86_64-lin
https://bugs.kde.org/show_bug.cgi?id=462170
Floreal changed:
What|Removed |Added
CC||k...@alypie.fr
--- Comment #22 from Floreal ---
Same
https://bugs.kde.org/show_bug.cgi?id=462170
rdparis changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |R
https://bugs.kde.org/show_bug.cgi?id=462170
--- Comment #21 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=462170
--- Comment #20 from rdparis ---
(In reply to Nate Graham from comment #14)
> Seems pretty clear that it's a PackageKit regression, then.
>
> Nico, does this fix the issue for you as well?
I found this thread while trying to figure out why Discover wa
https://bugs.kde.org/show_bug.cgi?id=462170
rdparis changed:
What|Removed |Added
CC||rdpa...@sent.com
--- Comment #19 from rdparis ---
Cr
https://bugs.kde.org/show_bug.cgi?id=462170
--- Comment #18 from luca ---
Maybe the reasons why Discover does not notify about updates are more than one
;)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=462170
--- Comment #17 from Nico Dorn ---
Nothing for packagekit, some for DiscoverNotifier, but not the same as yours
and quite irregular (not every day). There are three different types, but none
of them appear on a daily basis:
Nov 13 10:23:54 nico systemd
https://bugs.kde.org/show_bug.cgi?id=462170
--- Comment #16 from luca ---
@Nico
in your journal are there rows related DiscoverNotifier or packagekit?
try
$ journalctl --user | grep DiscoverNotifier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=462170
--- Comment #15 from Nico Dorn ---
(In reply to Nate Graham from comment #14)
> Nico, does this fix the issue for you as well?
I'd like to test that, but don't know how, Nate. I think, the version of my
packagekit libraries is acutally lower than the o
https://bugs.kde.org/show_bug.cgi?id=462170
Nate Graham changed:
What|Removed |Added
Status|CONFIRMED |NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=462170
--- Comment #13 from luca ---
reverting packagekit to previous version
gir1.2-packagekitglib-1.0 1.2.5-3+b1, libpackagekit-glib2-18:amd64 1.2.5-3+b1,
libpackagekitqt5-1:amd64 1.0.2-1, packagekit
1.2.5-3+b1, packagekit-
https://bugs.kde.org/show_bug.cgi?id=462170
luca changed:
What|Removed |Added
CC||luca.pedrie...@gmail.com
--- Comment #12 from luca ---
https://bugs.kde.org/show_bug.cgi?id=462170
--- Comment #11 from Nico Dorn ---
In addition to Stefans comment: I made a fresh install of KDE neon some weeks
ago after the rebase on jammy. Since then I face this bug.
I might have found a way to reproduce the notifier's behaviours: Establishing a
https://bugs.kde.org/show_bug.cgi?id=462170
Stefan Zurucker changed:
What|Removed |Added
CC||s...@posteo.at
--- Comment #9 from Stefan Zur
https://bugs.kde.org/show_bug.cgi?id=462170
Stefan Zurucker changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=462170
--- Comment #8 from Nico Dorn ---
Yes, the process was running. But the icon in the tray said "offline".
Another thing I disovered right now that might have something to do with it: I
wrote a script that pops up at startup and executes
`/usr/lib/x86_64
https://bugs.kde.org/show_bug.cgi?id=462170
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--- Comment #7 from Nate Graham ---
https://bugs.kde.org/show_bug.cgi?id=462170
--- Comment #6 from Aleix Pol ---
Weird... 🤔
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=462170
--- Comment #5 from Nico Dorn ---
That works. Unfortunately, I have to do it every time I reboot the system.
Otherwise the system tray icon states "offline".
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=462170
--- Comment #4 from Aleix Pol ---
Does restarting DiscoverNotifier help there? You can do so by running the
following command:
/usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier --replace
--
You are receiving this mail because:
You are watching all b
https://bugs.kde.org/show_bug.cgi?id=462170
--- Comment #3 from Nico Dorn ---
I forgot: If I open Discover manually, right now it shows 13 Updates available.
It's only about the missing notification.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=462170
--- Comment #2 from Nico Dorn ---
No, unfortunately not. "pkcon refresh" doesn't do the trick.
I should maybe mention that in System Tray Settings the icon Updates is set to
"Shown when relevant" (which is the default, I guess).
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=462170
--- Comment #1 from Aleix Pol ---
Does it suddenly notice there's updates if you run "pkcon refresh"?
--
You are receiving this mail because:
You are watching all bug changes.
30 matches
Mail list logo
