[plasmashell] [Bug 330356] Panel auto-hide stops working after using desktop for a while.
https://bugs.kde.org/show_bug.cgi?id=330356 --- Comment #45 from Filipe Azevedo --- (In reply to RJVB from comment #42) > Are you using KWin and does the ghost disappear when you restart it > (`kwin_x11 --replace` for X11 or kwin_wayland for Wayland; personally I add > `--no-kactivities`). > I had plenty of glitches of (parts of) windows or the desktop not being > redrawn properly, which turned out to be related to compositing. That all > went away when I selected the XRender rendering backend. I'm not certain > what kind of compositing that does, but the few effects I like to see > (including windows turning semitransparent when moving) are supported. As a > bonus I seem to be getting less tearing when watching videos. Sorry for the long delay, I tested just now ad yes it disappear but still get ghosted as soon as I trigger the panel visibility. I did not tested xrender because I wan to use the opengl backend, and this would just hide the problem - not fixing it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 330356] Panel auto-hide stops working after using desktop for a while.
https://bugs.kde.org/show_bug.cgi?id=330356 --- Comment #41 from Filipe Azevedo --- (In reply to hugo_NL from comment #40) > (In reply to Filipe Azevedo from comment #39) > > On the bottom panel (auto hide) I have: > > * Icon only task manager > > * transparency panel addon > > Check the Task Manager settings and verify that "Unhide when a window wants > attention" is *not* checked. > > This preventing auto-hide working for me. Hope this helps. This does not seems to be my issue, but to be sure I tested - does not help. My issue is not that the panel remain visible as per say, but that a ghost of it remain on the desktop, so clicking this ghost does nothing. >From what I can see the reject / close animation is not operating and ghost appear. When I move the mouse cursor to the bottom to enable the panel visibility, the open animation operate and at this time the ghost disappear but to come again once the mouse cursor leave the panel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 330356] Panel auto-hide stops working after using desktop for a while.
https://bugs.kde.org/show_bug.cgi?id=330356 Filipe Azevedo changed: What|Removed |Added CC||pas...@gmail.com --- Comment #39 from Filipe Azevedo --- I'm affected as well by this bug, strangely, I have 2 computers using the same distribution, each uptodate at the exact same version, and only one is affected. The one being affected is having a fixed top panel, and an auto hide bottom panel. I'm using Plasma version 5.26.4, Frameworks version 5.101.0, Qt version 5.15.7 and Kernel version 6.0.12. I'm using X11 and nvidia proprietary drivers. On the top panel (fixed), I have: * the K application menu (Application dashboard) * A spacer * Systray * 2 app icons (table symbols, systemsettings) * Digital clock * User switcher * a folder view * trash bin icon * transparency panel addon On the bottom panel (auto hide) I have: * Icon only task manager * transparency panel addon -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 438864] Add streaming feature
https://bugs.kde.org/show_bug.cgi?id=438864 --- Comment #5 from Filipe Azevedo --- Yeah, QtMultimedia... I had my fight as well with it for Kaidan IM... AntennaPad on Android make teh flow quite nice. There is a setting preference : streaming vs downloading Then in the UI it swap the play button icon depending the user preference so that we know we would stream or download. It's available on F-Droid if you want to have a look. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 438864] Add streaming feature
https://bugs.kde.org/show_bug.cgi?id=438864 --- Comment #3 from Filipe Azevedo --- Which media backend is behind Kast ? Is not QtMultimedia able to stream directly ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393793] Can't correctly pin application desktop file
https://bugs.kde.org/show_bug.cgi?id=393793 Filipe Azevedo changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|DOWNSTREAM |--- --- Comment #9 from Filipe Azevedo --- sorry, looks like I forget to answer here at the time... I'm using 5.25.5 by now and still get the issue. I reported the issue upstream and they said (at the time, no idea now) that they will not change it, because *it's to share the settings between the 2 applications* I will try again the workaround you pointed before. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458096] Plasmashell restricted (variables) environment
https://bugs.kde.org/show_bug.cgi?id=458096 Filipe Azevedo changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #13 from Filipe Azevedo --- Fixed, the OS package was not enabling user session support for the dbus package leading to this break. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458096] Plasmashell restricted (variables) environment
https://bugs.kde.org/show_bug.cgi?id=458096 Filipe Azevedo changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|DOWNSTREAM |--- --- Comment #11 from Filipe Azevedo --- (In reply to Roman from comment #10) > Can confirm same thing happens on Manjaro(5.25.4). Like having the issue or working correctly! Please mark it confirmed if needed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458096] Plasmashell restricted (variables) environment
https://bugs.kde.org/show_bug.cgi?id=458096 Filipe Azevedo changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|DOWNSTREAM |--- --- Comment #8 from Filipe Azevedo --- (In reply to Nate Graham from comment #7) > Cool, I'm on Fedora and I can't. I would recommend that you bring this up > with the KaOS maintainers as it's quite possible that they're patching > something. Thanks! Yes, I have brig it to us already. Will try to collect from here if some other distrib users can reproduce or not as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458096] Plasmashell restricted (variables) environment
https://bugs.kde.org/show_bug.cgi?id=458096 --- Comment #6 from Filipe Azevedo --- (In reply to Filipe Azevedo from comment #5) > I'm running the KaOS distribution being up to date to today. > I can reproduce the issue with 2 different machines and users. https://kaosx.us/pages/download/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458096] Plasmashell restricted (variables) environment
https://bugs.kde.org/show_bug.cgi?id=458096 --- Comment #5 from Filipe Azevedo --- I'm running the KaOS distribution being up to date to today. I can reproduce the issue with 2 different machines and users. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458096] Plasmashell restricted (variables) environment
https://bugs.kde.org/show_bug.cgi?id=458096 --- Comment #2 from Filipe Azevedo --- (In reply to Nate Graham from comment #1) > Cannot reproduce; the commands set are identical for me: > DBUS_SESSION_BUS_ADDRESS > KONSOLE_DBUS_SERVICE > KONSOLE_DBUS_SESSION > KONSOLE_DBUS_WINDOW Did you run the second konsole from the panel pinned konsole ? What if you then close everything and try to start konsole from pinned only ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458096] Plasmashell restricted (variables) environment
https://bugs.kde.org/show_bug.cgi?id=458096 Filipe Azevedo changed: What|Removed |Added Summary|Plasmashell variable|Plasmashell restricted |environment |(variables) environment -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458096] New: Plasmashell variable environment
https://bugs.kde.org/show_bug.cgi?id=458096 Bug ID: 458096 Summary: Plasmashell variable environment Product: plasmashell Version: 5.25.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pas...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 151448 --> https://bugs.kde.org/attachment.cgi?id=151448=edit env issue SUMMARY Applications started from plasmashell (like kickoff, panels) get a restricted environment (variable environment), where some variables are missing compared to applications started from krunner. Especially, dbus related variables are not leaked making flatpak and AppImage applications would not be able to communicate with system dbus, and fails to get wallet access. By example, gajim, ruqola, chrome ran from flatpak / appimage can not access passwords. STEPS TO REPRODUCE 1. Start konsole from krunner 2. type command: export | grep DBUS 3. See there is 6 variables 4. Pin konsole to a panel 5. Right click this pined app and click open new window 6. Type command from 2. OBSERVED RESULT 6. Variables does not match the one from 2. EXPECTED RESULT 6. variables match one from 2. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97 Qt Version: 5.15.5+ ADDITIONAL INFORMATION The issue is there since some versions now, It was working fine before. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 443286] Insecure redirect break downlaods
https://bugs.kde.org/show_bug.cgi?id=443286 --- Comment #8 from Filipe Azevedo --- Just let me know if i can help you - I can test / update any PR you have. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 443286] Insecure redirect break downlaods
https://bugs.kde.org/show_bug.cgi?id=443286 --- Comment #7 from Filipe Azevedo --- Is this not yet fixed already ? Looks like downloads work again by now since some weeks. Maybe the CDN do no longer make redirects by now ? -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 443286] Insecure redirect break downlaods
https://bugs.kde.org/show_bug.cgi?id=443286 --- Comment #4 from Filipe Azevedo --- Yeah, I do truely understand Kasts is not the problem here. Maybe we can introduce some per subscription feed hints like 'Accept InsecureRedirect', and you can pass that to the downloader request. Looks like QNetworkReply has QNetworkRequest::FollowRedirectsAttribute attribute that can be used for that. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 443286] Insecure redirect break downlaods
https://bugs.kde.org/show_bug.cgi?id=443286 --- Comment #2 from Filipe Azevedo --- This podcast was working fine in Kasts for long until 2 weeks ago. I tested in some other podcast apps, like AntennaPod on Android and it works fine. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 443286] New: Insecure redirect break downlaods
https://bugs.kde.org/show_bug.cgi?id=443286 Bug ID: 443286 Summary: Insecure redirect break downlaods Product: kasts Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: pas...@gmail.com Target Milestone: --- SUMMARY While downloading entries "insecure redirect" error is thrown STEPS TO REPRODUCE 1. Click "download" for an entry 2. wait for error OBSERVED RESULT An error occurs and no download is performed. EXPECTED RESULT No error and download done. ADDITIONAL INFORMATION This seems a change on the podcast server, still it make the application not usable anymore. The incriminated podcast subscription feed is: https://www.europe1.fr/rss/podcasts/hondelatte-raconte.xml -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 443285] New: Add context menu entries
https://bugs.kde.org/show_bug.cgi?id=443285 Bug ID: 443285 Summary: Add context menu entries Product: kasts Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: pas...@gmail.com Target Milestone: --- SUMMARY Add context menu entries ADDITIONAL INFORMATION Currently, the application is highly focused for mobile interaction. This make it uncomfortable for desktops. Please allow context menu entries on any view element, usually, the one we are seeing while selected an entry. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 443284] New: Allow explicit selection
https://bugs.kde.org/show_bug.cgi?id=443284 Bug ID: 443284 Summary: Allow explicit selection Product: kasts Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: pas...@gmail.com Target Milestone: --- SUMMARY Allow explicit selection ADDITIONAL INFORMATION Currently, when clicking with desktop mouse on a subscription or entry, the view would not retain a strong focus, it's then fairly easy to not remember which entry is currently selected and on which we would act to mark read etc. While there, the currently playing view entry should also be made more visible. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 443283] New: Allow to clear queue
https://bugs.kde.org/show_bug.cgi?id=443283 Bug ID: 443283 Summary: Allow to clear queue Product: kasts Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: pas...@gmail.com Target Milestone: --- SUMMARY allow to clear queue -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 443282] New: Allow to copy a urls
https://bugs.kde.org/show_bug.cgi?id=443282 Bug ID: 443282 Summary: Allow to copy a urls Product: kasts Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: pas...@gmail.com Target Milestone: --- SUMMARY Add way to copy both the subscription url and an entry url ADDITIONAL INFORMATION This allow to share a podcast file with a friend, or just the podcast host subscription feed. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 438864] Add streaming feature
https://bugs.kde.org/show_bug.cgi?id=438864 Filipe Azevedo changed: What|Removed |Added CC||pas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 364873] Add support for command line --new-tab
https://bugs.kde.org/show_bug.cgi?id=364873 --- Comment #5 from Filipe Azevedo --- Thanks for taking the time to share your script. While i would have preferred to see a new command line added, this will fit perfectly. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 411684] Use web site fav icon as the plasmoid dashboard icon
https://bugs.kde.org/show_bug.cgi?id=411684 --- Comment #1 from Filipe Azevedo --- Still present and annoying... Also, in addition, enabling notifications would be a great feature as well. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 364873] Add support for command line --new-tab
https://bugs.kde.org/show_bug.cgi?id=364873 --- Comment #2 from Filipe Azevedo --- Any chance to get an answer some day ? :) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411657] Latte dock free when used with some combinations of plasmoids
https://bugs.kde.org/show_bug.cgi?id=411657 --- Comment #16 from Filipe Azevedo --- (In reply to Rylsm from comment #9) > Well it doesn't stop you from using AUR or install any Arch Linux packages. > You can install software from AUR from KaOS since it's using the same build > mechanism as Arch. > KaOS is like Manjaro but far more conservative and only focuses on KDE > Plasma DE. > I have the same issue and same debug output on Manjaro. Downgrading ostree > is the only solution for flatpak user. If you can build your own PKGBUILD > you can build your own patched version of ostree from this PR on ostree > Github: https://github.com/ostreedev/ostree/pull/1917 It in fact does (stop me using those packages), Arch / AUR packages are absolutely not compatible with KaOS. Thanks for ostree hint. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411657] Latte dock free when used with some combinations of plasmoids
https://bugs.kde.org/show_bug.cgi?id=411657 --- Comment #15 from Filipe Azevedo --- (In reply to Michail Vourlakos from comment #13) > Git commit 7cfcd8451122b8c990278375406fe9fde06accbe by Michail Vourlakos. > Committed on 07/09/2019 at 20:52. > Pushed by mvourlakos into branch 'v0.9'. > > track kwinrc file only on changes > > --instead of reading the kwin values all the time > when needed from user actions we now read them > only on startup and when the kwinrc file was > updated/changed > FIXED-IN:0.9.3 > > M +6-25 app/layout/centrallayout.cpp > M +2-2app/settings/settingsdialog.cpp > M +65 -24 app/settings/universalsettings.cpp > M +11 -6app/settings/universalsettings.h > M +4-4app/shortcuts/globalshortcuts.cpp > > https://commits.kde.org/latte-dock/7cfcd8451122b8c990278375406fe9fde06accbe Thanks ! -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 411684] New: Use web site fav icon as the plasmoid dashboard icon
https://bugs.kde.org/show_bug.cgi?id=411684 Bug ID: 411684 Summary: Use web site fav icon as the plasmoid dashboard icon Product: kdeplasma-addons Version: 5.16.5 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: webbrowser Assignee: plasma-b...@kde.org Reporter: pas...@gmail.com Target Milestone: --- When we use a lot of web browser plasmoid it's hardly distinguishable. I do use some for RocketChat instances at work, having the url fav icon as the plasmoid icon would be a great improvement. For web sites not having fav icon, it would be awesome to be able to set a user one as well. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 359073] web browser widget: shown website cannot be resized, always too small
https://bugs.kde.org/show_bug.cgi?id=359073 Filipe Azevedo changed: What|Removed |Added CC||mur...@gmail.com --- Comment #6 from Filipe Azevedo --- *** Bug 392254 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 392254] Fixed zoom factor in KDE Web Browser plasma widget settings
https://bugs.kde.org/show_bug.cgi?id=392254 Filipe Azevedo changed: What|Removed |Added CC||pas...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Filipe Azevedo --- *** This bug has been marked as a duplicate of bug 359073 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 359073] web browser widget: shown website cannot be resized, always too small
https://bugs.kde.org/show_bug.cgi?id=359073 Filipe Azevedo changed: What|Removed |Added CC||pas...@gmail.com --- Comment #5 from Filipe Azevedo --- Please do something for that zoom feature, it's clearly an annoying issue. I'm using a 4k screen and it hit me much harder now than before. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411657] Latte dock free when used with some combinations of plasmoids
https://bugs.kde.org/show_bug.cgi?id=411657 --- Comment #11 from Filipe Azevedo --- (In reply to Rylsm from comment #9) > Well it doesn't stop you from using AUR or install any Arch Linux packages. > You can install software from AUR from KaOS since it's using the same build > mechanism as Arch. > KaOS is like Manjaro but far more conservative and only focuses on KDE > Plasma DE. > I have the same issue and same debug output on Manjaro. Downgrading ostree > is the only solution for flatpak user. If you can build your own PKGBUILD > you can build your own patched version of ostree from this PR on ostree > Github: https://github.com/ostreedev/ostree/pull/1917 I can now see the relation to ostree ;) Thanks for the link. I will share it to the KaOS team. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411657] Latte dock free when used with some combinations of plasmoids
https://bugs.kde.org/show_bug.cgi?id=411657 --- Comment #10 from Filipe Azevedo --- (In reply to Michail Vourlakos from comment #8) > Hm > > If you disable in Latte Global Preferences option, "Press and Hold ⌘ to show > shortcuts badges" > > does it still occur? As say my second comment: As a workaround, disable meta shortcut support from latte dock configure dialog and restart the application hide the issue. I can not check if the badge stuff is still enabled, the config file only show "metaPressAndHoldEnabled=false". The reason why i can not check is that it seems it exist another bug that prevent the config dialog to be shown if a latte dock in panel mode does not contains the latte tasks plasmoid. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411657] Latte dock free when used with some combinations of plasmoids
https://bugs.kde.org/show_bug.cgi?id=411657 --- Comment #7 from Filipe Azevedo --- KaOS is not ARCH/AUR based at all. While it share something in common (pacman package manager), it is a from scratch distribution and it has its very own packages. Also from the output log, it would looks like a wrongly handled destroyed process, from that i can hardly see a relation to ostree. Using flatpak, i'm not able to delete this file. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411657] Latte dock free when used with some combinations of plasmoids
https://bugs.kde.org/show_bug.cgi?id=411657 --- Comment #3 from Filipe Azevedo --- KaOS -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411657] Latte dock free when used with some combinations of plasmoids
https://bugs.kde.org/show_bug.cgi?id=411657 --- Comment #1 from Filipe Azevedo --- As a workaround, disable meta shortcut support from latte dock configure dialog and restart the application hide the issue. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411657] New: Latte dock free when used with some combinations of plasmoids
https://bugs.kde.org/show_bug.cgi?id=411657
Bug ID: 411657
Summary: Latte dock free when used with some combinations of
plasmoids
Product: lattedock
Version: 0.9.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: application
Assignee: mvourla...@gmail.com
Reporter: pas...@gmail.com
Target Milestone: ---
When using some particular combinations of plasmoid with a "(panel) latte dock"
latte dock regularly freeze and need to be killed / restarted so it works
again.
Also, promoting a dock to panel then removing its latte plasmoid, always lead
to freeze, ie a plasmoid latte dock less panel always freeze.
STEPS TO REPRODUCE
1. Create a new user
2. Log in with this user
3. You should arrive on a plasma having a bottom latte dock
4. Create a top panel dock
5. Add 2 or 3 web browser plasmoids
6. Add system tray (or notifications) plasmoid
7. Open the web browser plasmoid popup
8. Use kde shortcut to resize / move windows: Meta+ Up/Left/Top/Bottom
9. Notice after the second shortcut trigger the popup does no longer render
correctly
10. Try to use your panel / dock
11. It's not working, it's frozen
OBSERVED RESULT
Latte dock freeze
EXPECTED RESULT
No freeze
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.61.0
Qt Version: 5.13.0
ADDITIONAL INFORMATION
Some combinations that works / freeze:
Panel + NO latte + browser = Freeze
Panel + latte + browser = OK
Panel + latte + browser + notifications = Freeze
Output traces from -d --with-window:
23:25:58.740 lattedock(2122/2122) WARNING:
QProcess::~QProcess|Latte::UniversalSettings::kwin_metaForwardedToLatte|Latte::GlobalShortcuts::showViews
QProcess: Destroyed while process ("kreadconfig5") is still running.
/!\ At this point i have a dead / zombie kreadconfig5 process.
Back trace at the time of the freeze:
#0 0x70e1cc12 in ppoll () at /lib/libc.so.6
#1 0x71c8e760 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2 0x71bcc92f in QProcessPrivate::waitForFinished(int) () at
/usr/lib/libQt5Core.so.5
#3 0x71bc2f3d in QProcess::waitForFinished(int) () at
/usr/lib/libQt5Core.so.5
#4 0x71bc3682 in QProcess::~QProcess() () at /usr/lib/libQt5Core.so.5
#5 0x004f8bad in Latte::UniversalSettings::kwin_metaForwardedToLatte()
const ()
#6 0x00506f6b in Latte::GlobalShortcuts::showViews() ()
#7 0x71c6a730 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#8 0x71c6a730 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#9 0x71c759e7 in QTimer::timeout(QTimer::QPrivateSignal) () at
/usr/lib/libQt5Core.so.5
#10 0x71c6adbb in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#11 0x73a8db81 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#12 0x73a94aa0 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#13 0x71c419f9 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#14 0x71c91ae3 in QTimerInfoList::activateTimers() () at
/usr/lib/libQt5Core.so.5
#15 0x71c922bc in idleTimerSourceDispatch(_GSource*, int (*)(void*),
void*) () at /usr/lib/libQt5Core.so.5
#16 0x7fffe852b51e in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#17 0x7fffe852b788 in () at /usr/lib/libglib-2.0.so.0
#18 0x7fffe852b80c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#19 0x71c925d3 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#20 0x71c406fb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#21 0x71c4839e in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#22 0x00471c9c in main ()
--
You are receiving this mail because:
You are watching all bug changes.
[lattedock] [Bug 409126] Too big memory usage
https://bugs.kde.org/show_bug.cgi?id=409126 --- Comment #4 from Filipe Azevedo --- Tried to remove web browser and quick chat, the memory did not shrink (but i did not rebooted in between). I will try to wipe the top toolbar (can i save it for a later restore ?) and reboot, and test for some time. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 409126] Too big memory usage
https://bugs.kde.org/show_bug.cgi?id=409126 --- Comment #2 from Filipe Azevedo --- In the top panel like late dock: - application dashboard - quick share - color picker - web brower (fb messenger) - quick chat - system tray - digital clock - system settings - user switcher - notifications (i prefer out of system tray notifications) In the bottom dock like latte dock: - latte plasmoid - trashcan -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 409126] New: Too big memory usage
https://bugs.kde.org/show_bug.cgi?id=409126 Bug ID: 409126 Summary: Too big memory usage Product: lattedock Version: 0.8.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: pas...@gmail.com Target Milestone: --- SUMMARY The latte dock framework is way using too much of memory. I don't use activities and I do use 2 simple latte dock panels, still it eat nearly 1gb of my RAM. I find this unacceptable for such *simple* application. Yeah i know that in reality it's not simple code, but the resulting UI (layout of icons) is really something to worry about. STEPS TO REPRODUCE 1. Create 2 panels 2. Run for several weeks without reboot 3. Use suspend / resume linux functionality OBSERVED RESULT Memory use 800mb of ram EXPECTED RESULT Use far less ram SOFTWARE/OS VERSIONS Linux: 5.0.9-1 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408064] Latte panel does not correctly move desktop elements, like the top right desktop menu item
https://bugs.kde.org/show_bug.cgi?id=408064 --- Comment #7 from Filipe Azevedo --- Hm, i tweaked a bit the desktop settings (moved from Desktop to folder view and back to Desktop) and now it works fine, no wrong geometry reserved on others screens, let forget then until i can reliably reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408064] Latte panel does not correctly move desktop elements, like the top right desktop menu item
https://bugs.kde.org/show_bug.cgi?id=408064 --- Comment #5 from Filipe Azevedo --- In plus of this issue, I also noticed the latte panel is wrongly reserving geometry of a panel in ALL screens / monitors. I'm usng a dial screen anv, and my primary screen top penal also register the same geometry on the second screen, render this area showing nothing but not usable as well (ie, a maximized window would not cover the area). -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408064] Latte panel does not correctly move desktop elements, like the top right desktop menu item
https://bugs.kde.org/show_bug.cgi?id=408064 --- Comment #2 from Filipe Azevedo --- Hm, i could live with a workaround - still did not find a way to add margin to desktop. How does one do that ? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408064] New: Latte panel does not correctly move desktop elements, like the top right desktop menu item
https://bugs.kde.org/show_bug.cgi?id=408064 Bug ID: 408064 Summary: Latte panel does not correctly move desktop elements, like the top right desktop menu item Product: lattedock Version: 0.8.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: pas...@gmail.com Target Milestone: --- SUMMARY Top placed panel latte docks covers desktop top right menu entry, leaving it partially not reachable. STEPS TO REPRODUCE 1. Create a top latte dock panel OBSERVED RESULT The desktop top right menu entry is covered by the panel making it partially unreachable depending the panel height. https://i.imgur.com/GeLVjhZ.png EXPECTED RESULT The desktop menu entry should be moved under the panel like with the standard panels. SOFTWARE/OS VERSIONS Linux: 5.0.9-1 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408063] New: Rendering corruption in items
https://bugs.kde.org/show_bug.cgi?id=408063 Bug ID: 408063 Summary: Rendering corruption in items Product: lattedock Version: 0.8.8 Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: pas...@gmail.com Target Milestone: --- Rendering corruption leaving linux suspend mode STEPS TO REPRODUCE 1. Add latte dock on the desktop 2. Go to suspend mode 3. Leave suspend mode OBSERVED RESULT Corrupted rendering in the latte dock items (https://i.imgur.com/jNCoqMM.png) EXPECTED RESULT No corruption SOFTWARE/OS VERSIONS Linux: 5.0.9-1 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION The rendering issues seems to be caused by what is caled 'GPU reset' when leaving suspend mode. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 404211] Ssl issue when sending email with (gmail) imap
https://bugs.kde.org/show_bug.cgi?id=404211 --- Comment #11 from Filipe Azevedo --- Fine, will test that with 5.13 at time. Thanks for the support ! -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 404211] Ssl issue when sending email with (gmail) imap
https://bugs.kde.org/show_bug.cgi?id=404211 --- Comment #9 from Filipe Azevedo --- The Trojita GUI does not specify SSL at all, it has: - Use encryption (STARTTLS) - Force encryption (TLS) Hence I selected the expected port 587 from the support page for gmail. My distribution is using Qt 5.12.1 and has no downstream patches for Qt. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 404211] Ssl issue when sending email with (gmail) imap
https://bugs.kde.org/show_bug.cgi?id=404211 --- Comment #7 from Filipe Azevedo --- Ah, just tested TLS port 465 for smtp and it worked fine ! Which is weird, google support page say 465 if for ssl. See https://support.google.com/mail/answer/7126229?hl=en So I guess my configuration was not wrong using TLS/587. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 404211] Ssl issue when sending email with (gmail) imap
https://bugs.kde.org/show_bug.cgi?id=404211 --- Comment #6 from Filipe Azevedo --- I do use those imap/smtp configurations: * imap: TLS on imap.gmail.com:993 * smtp: TLS on smtp.gmail.com:587 -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 404211] Ssl issue when sending email with (gmail) imap
https://bugs.kde.org/show_bug.cgi?id=404211 --- Comment #4 from Filipe Azevedo --- I did a full uninstall/resintall/restart of the package, the full output log clearly state it initiate ssl upon connection opening and correctly handle initial sychronization, only message sending fails. Could it be a missconfigured gmail account or a gmail imap issue in Trojita ? -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 404211] Ssl issue when sending email with (gmail) imap
https://bugs.kde.org/show_bug.cgi?id=404211 --- Comment #3 from Filipe Azevedo --- I did test again, and the error still occurs. Still i can read / load content being hosted on secure servers (ie, loading https images by examples). Here is the output log: 17:15:44.765 Submission STATE_INIT 17:15:44.772 Submission STATE_BUILDING_MESSAGE 17:15:44.772 Submission STATE_SAVING 17:15:45.688 Submission STATE_SUBMITTING 17:15:45.864 Submission gotError: Error during SSL handshake: error:1408F10B:SSL routines:ssl3_get_record:wrong version number 17:15:45.864 Submission STATE_FAILED -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 404211] Ssl issue when sending email with (gmail) imap
https://bugs.kde.org/show_bug.cgi?id=404211 --- Comment #2 from Filipe Azevedo --- Hm, the problem is ... only Trojita is having ssl issues. No other Qt apps nor KDE apps do have ssl issues. I can by example use KMail with the same gmail account, browse sftp / ssh remotes machines without issues etc. Using Dolphin for sftp/ssh remote connection works fine as well. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 398560] Kate preview crash Kate when closing documents from tab bar
https://bugs.kde.org/show_bug.cgi?id=398560 --- Comment #5 from Filipe Azevedo --- up ? -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 404211] New: Ssl issue when sending email with (gmail) imap
https://bugs.kde.org/show_bug.cgi?id=404211 Bug ID: 404211 Summary: Ssl issue when sending email with (gmail) imap Product: trojita Version: 0.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Cryptography Assignee: trojita-b...@kde.org Reporter: pas...@gmail.com Target Milestone: --- SUMMARY I can not send emails using Trojita 0.7 on my linux distribution (KaOSx). I'm using a gmail imap account. STEPS TO REPRODUCE 1. Setup a gmail imap account 2. Try to send an email 3. Error appear OBSERVED RESULT Error during SSL handshake: error:1408F10B:SSL routines:ssl3_get_record:wrong version number EXPECTED RESULT Email sent correctly with no error. SOFTWARE/OS VERSIONS LSB Version:1.4 Distributor ID: KaOS Description:KaOS Release:rolling Codename: n/a KDE Frameworks 5.55.0 Qt 5.12.1 (built against 5.12.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 401179] Allow lesser than 1 scale factor
https://bugs.kde.org/show_bug.cgi?id=401179 --- Comment #11 from Filipe Azevedo --- The Qt env var to scale screens is useless, because it would have to be applied correctly before even starting the plasma desktop (in reality it would be this app to change the scale) so that its inheriting apps render correctly. The only current solution is xrandr scale feature using .5 scale factor (hence my allow less than 1 scale factor, but in the end they are not the same scale factors). Any chance this being used instead of a global xorg things that serve nothing but create more problems ? Xrandr can do per screen scaling, and might be a better solution until wayland impose itself. There is nothing to wait for Qt because there is no issue to fix in it. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 401179] Allow lesser than 1 scale factor
https://bugs.kde.org/show_bug.cgi?id=401179 Filipe Azevedo changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #7 from Filipe Azevedo --- Let recap things, because i have the feeling i did not emphasized enough on the issue being *dual* screens with internal screen being a retina screen and the external one a full hd screen non retina, under X11. If you have only a retina screen - the kcm scale feature just work, but break as soon as you add another screen, simply because it's an all screens scale. To be honest this *global* scale feature is useless, i still can't understand how it was accepted. Note that I do know that wayland can do per screen scale factors, but i don't care because wayland/nouveau is all but stable on a mac machine. I did disable my script (command is: xrandr --output DP-2 --scale .5x.5 --output HDMI-0 --pos 1440x0) which is basically downscaling the screen picture of the retina screen half its size and move the other screen near it so that it make a contiguous plan. This script is executed by the user session autostart kcm - and it just do the job. The *only* draw back is that the downscale has a lower rendering quality, but clearly acceptable for what it fix. So, i the initial request title is somehow wrong - because in reality we may not speak about the same feature. kscreen kcm seems to apply a xorg screen scale feature, while i do speak about xrandr scale property. I have no idea what kscreen try to do behind the scene (but i really would like to know the details, even pointing the exact code applying the changes), but what i need is an out of the box working solution for a retina mac with external screens plugged. Hope it help understanding correctly the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 399318] Asks for password for WPA/TKIP network multiple times when it's already in KWallet (with PAM)
https://bugs.kde.org/show_bug.cgi?id=399318 --- Comment #16 from Filipe Azevedo --- Well, i have no idea of what to report because i have no idea what you mean with secret-flags to 0. Can you details or just open the bug yourself ? Also, my distribution is very cutting edge, if the fix would be resolved upstream already and released then most likely i would already have this patch. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 399318] Asks for password for WPA/TKIP network multiple times when it's already in KWallet (with PAM)
https://bugs.kde.org/show_bug.cgi?id=399318 Filipe Azevedo changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #14 from Filipe Azevedo --- connection.id: SoDream connection.uuid:18d4861f-a18f-4655-9425-e77824706fc6 connection.stable-id: -- connection.type:802-11-wireless connection.interface-name: -- connection.autoconnect: non connection.autoconnect-priority:0 connection.autoconnect-retries: -1 (default) connection.multi-connect: 0 (default) connection.auth-retries:-1 connection.timestamp: 1543349014 connection.read-only: non connection.permissions: -- connection.zone:-- connection.master: -- connection.slave-type: -- connection.autoconnect-slaves: -1 (default) connection.secondaries: -- connection.gateway-ping-timeout:0 connection.metered: inconnu connection.lldp:default connection.mdns:-1 (default) connection.llmnr: -1 (default) 802-11-wireless.ssid: SoDream 802-11-wireless.mode: infrastructure 802-11-wireless.band: -- 802-11-wireless.channel:0 802-11-wireless.bssid: -- 802-11-wireless.rate: 0 802-11-wireless.tx-power: 0 802-11-wireless.mac-address:60:03:08:A9:F5:E0 802-11-wireless.cloned-mac-address: -- 802-11-wireless.generate-mac-address-mask:-- 802-11-wireless.mac-address-blacklist: -- 802-11-wireless.mac-address-randomization:default 802-11-wireless.mtu:auto 802-11-wireless.seen-bssids:58:90:43:13:EB:87 802-11-wireless.hidden: non 802-11-wireless.powersave: 0 (default) 802-11-wireless.wake-on-wlan: 0x1 (default) 802-11-wireless-security.key-mgmt: wpa-psk 802-11-wireless-security.wep-tx-keyidx: 0 802-11-wireless-security.auth-alg: -- 802-11-wireless-security.proto: -- 802-11-wireless-security.pairwise: -- 802-11-wireless-security.group: -- 802-11-wireless-security.pmf: 0 (default) 802-11-wireless-security.leap-username: -- 802-11-wireless-security.wep-key0: 802-11-wireless-security.wep-key1: 802-11-wireless-security.wep-key2: 802-11-wireless-security.wep-key3: 802-11-wireless-security.wep-key-flags: 0 (aucun) 802-11-wireless-security.wep-key-type: unknown 802-11-wireless-security.psk: 802-11-wireless-security.psk-flags: 0 (aucun) 802-11-wireless-security.leap-password: 802-11-wireless-security.leap-password-flags:0 (aucun) 802-11-wireless-security.wps-method:0 (default) 802-11-wireless-security.fils: 0 (default) ipv4.method:auto ipv4.dns: -- ipv4.dns-search:-- ipv4.dns-options: "" ipv4.dns-priority: 0 ipv4.addresses: -- ipv4.gateway: -- ipv4.routes:-- ipv4.route-metric: -1 ipv4.route-table: 0 (unspec) ipv4.ignore-auto-routes:non ipv4.ignore-auto-dns: non ipv4.dhcp-client-id:-- ipv4.dhcp-timeout: 0 (default) ipv4.dhcp-send-hostname:oui ipv4.dhcp-hostname: -- ipv4.dhcp-fqdn: -- ipv4.never-default: non ipv4.may-fail: non ipv4.dad-timeout: -1 (default) ipv6.method:auto ipv6.dns: -- ipv6.dns-search:-- ipv6.dns-options: "" ipv6.dns-priority: 0 ipv6.addresses: -- ipv6.gateway: -- ipv6.routes:-- ipv6.route-metric: -1 ipv6.route-table: 0 (unspec) ipv6.ignore-auto-routes:non ipv6.ignore-auto-dns: non ipv6.never-default: non ipv6.may-fail: non ipv6.ip6-privacy: -1 (unknown) ipv6.addr-gen-mode: stable-privacy ipv6.dhcp-duid: -- ipv6.dhcp-send-hostname:oui ipv6.dhcp-hostname: -- ipv6.token:
[kate] [Bug 398560] Kate preview crash Kate when closing documents from tab bar
https://bugs.kde.org/show_bug.cgi?id=398560 Filipe Azevedo changed: What|Removed |Added Version|18.08.1 |18.08.3 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 398560] Kate preview crash Kate when closing documents from tab bar
https://bugs.kde.org/show_bug.cgi?id=398560 Filipe Azevedo changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #4 from Filipe Azevedo --- The issue is still present and i can now reliably reproduce it: - Have a tree of markdown files in a hierarchy of folders - Have the root folder be a git repository - open this repository as a project in kate - open multiple files from the project panel - activate the preview panel - click on each document in the top tab bar (please note that i enabled the top tabbar in plus to the document panel) - when the last tab bar entry on the right is active, close it from its close button - crash -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 401179] (5.14.3) Allow lesser than 1 scale factor
https://bugs.kde.org/show_bug.cgi?id=401179 --- Comment #4 from Filipe Azevedo --- Indeed, wayland is much better in this area, still wayland is not stable at all with my mac and nouveau driver and lead to frequent freeze. Also, using scale factor as a way to report the screen scale factor is plain wrong for user and lead to miss understood. A scale factor is something that would scale a given size. Wayland and X11 scale usage is totally inconsistent, and it's really wrong wrong wrong for the user switching wayland/x11. X11 use it as an upscale feature while wayland use it to reduce the screen hardware size by the factor. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 401179] (5.14.3) Allow lesser than 1 scale factor
https://bugs.kde.org/show_bug.cgi?id=401179 --- Comment #2 from Filipe Azevedo --- Retina screens in kscreen kcm for X11 does not have the possibility to change the screen resolution. The scale factor is an upscale factor, not a downscale factor. So moving the scale factor to x2 just make it twice bigger while i want to reduce it (downscale). -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 401179] New: (5.14.3) Allow lesser than 1 scale factor
https://bugs.kde.org/show_bug.cgi?id=401179 Bug ID: 401179 Summary: (5.14.3) Allow lesser than 1 scale factor Product: KScreen Version: git Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm Assignee: se...@kde.org Reporter: pas...@gmail.com Target Milestone: --- I'm using KDE Plasma and KDE SC on a macos hardware which comes with so called "retina" screen. Using a resolution of 2880x1800 is obviously useless, because too difficult to read, the list of screen resolution is also not changeable (fixed). Up to now i workaround the issue by using xrandr to downscale the screen to 1440x900 using a scale factor of 0.5 into an early system script. Works fine, still i had to workaround that in kcm kscreen again to position the second external screen correctly. ie, i have to put the position of the second screen half the width of the first screen (remember, kscreen only allow scaling from 1 to more) so that both my first screen downscale and second screen position does not get wrong. All works so fine, but at a manual maintains cost. I would like kscreen kcm allow less than 1 scale factor so that i can just correctly setup my screens without requiring work around / own script. STEPS TO REPRODUCE 1. Use a mac book laptop with a retina screen and an external non retina screen 2. Try to setup your screens so that it fit your needs OBSERVED RESULT First retina screen is too small to be usable EXPECTED RESULT Be able to downscale my retina screen resolution SOFTWARE/OS VERSIONS Linux/KDE Plasma: KaOS Linux KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 399318] Asks for password for WPA/TKIP network multiple times when it's already in KWallet (with PAM)
https://bugs.kde.org/show_bug.cgi?id=399318 --- Comment #9 from Filipe Azevedo --- Created attachment 115576 --> https://bugs.kde.org/attachment.cgi?id=115576=edit wifi log Some more info to add today. The usage of non encrypted (non wallet) passwords works far better, still it sometimes have the same issue. Sometimes the first manual click to connect the wifi don't works and desktop request a password, like it does for kwallet. I just ignore the dialog, and try to manually connect again - works. This mean that kwallet may not be the problem (but is much more impacted by the issue) but something other (the driver ?). Here is a small attached log file, not sure it can help though. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 399318] Asks for password for WPA/TKIP network multiple times when it's already in KWallet (with PAM)
https://bugs.kde.org/show_bug.cgi?id=399318 --- Comment #8 from Filipe Azevedo --- Also, as noted, i'm using a mac book machine, the wifi driver does not seems in a very good shape, so maybe it does not help as well. I was not having the issue as well on a non apple machine. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 399318] Asks for password for WPA/TKIP network multiple times when it's already in KWallet (with PAM)
https://bugs.kde.org/show_bug.cgi?id=399318 --- Comment #7 from Filipe Azevedo --- There is no master password set on teh wallet so no password is being asked for that. The distribution comes with a pam wallet configuration, so i guess the wallet is being opened upon login. I did not tried to kill kded, but i can try to have a look at it in the next days. The work around i used previously no longer works, was just working by chance. The thing that just works reliably is to bypass kwallet entirely by using the network connection preference and create the connection on my own, using a non encrypted password for all users, not using auto connection. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 399318] Asks for password for WPA/TKIP network multiple times when it's already in KWallet (with PAM)
https://bugs.kde.org/show_bug.cgi?id=399318 --- Comment #4 from Filipe Azevedo --- And if it matter, this is a mac book machine (mid 2014). -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 399318] NetworkManager applet unusable in combination with WPA/TKIP and KWallet (pam)
https://bugs.kde.org/show_bug.cgi?id=399318 Filipe Azevedo changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Filipe Azevedo --- Reproduction steps: 1/ Click a ssid being wpa 2/ enter password 3/ Wait it connect (or not, the bug) 4/ if it works fine, reboot the machine go to 1/ 5/ NM ask password again 6/ enter password again 7/ repeat 5/ and 6/ multiple times 8/ Open you kwallet in the NM section, see multiple entries for the same ssid 9/ Disable wifi 10/ Delete all NM passwords 11/ Enable wifi 12/ Go to 1/ Distribution: KaOS, up to date (no version, rolling release) KDE Software: 18.08.1-1 KDE Frameworks 5.50.0 Qt: 5.11.2, but does not matter, got the issues since more than a year (Qt 5.9 at least). -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 399318] New: NetworkManager applet unusable in combination with WPA/TKIP and KWallet (pam)
https://bugs.kde.org/show_bug.cgi?id=399318 Bug ID: 399318 Summary: NetworkManager applet unusable in combination with WPA/TKIP and KWallet (pam) Product: plasma-nm Version: master Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: pas...@gmail.com Target Milestone: --- Since nearly one year connecting to my WPA/TKIP wifi network is a nightmare. It was russian roulette to get it connected until i discovered the issue. The NetworkManager applet in combination with KWalllet / pam is unreliable. For some reason it's not able to pick the password associated with the connection, and keep requesting password to me. If I enter it again and again it's worse - Multiple connections are created in the network connections editor, still unable to pick the wallet password. The only reliable workaround i have is to disable wifi, delete all passwords in NetworkManager entry in the wallet, enable wifi, request conenction, fill password.. tada it works. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 398560] New: Kate preview crash Kate when closing documents from tab bar
https://bugs.kde.org/show_bug.cgi?id=398560 Bug ID: 398560 Summary: Kate preview crash Kate when closing documents from tab bar Product: kate Version: 18.08.1 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: pas...@gmail.com Target Milestone: --- Application: kate (18.08.1) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.17.17-1 x86_64 Distribution: "KaOS" -- Information about the crash: - What I was doing when the application crashed: I was closing a markdown document which is part of a git repository by clicking the tab bar close buton. Randomly, but reproducible very often; a document close cause the preview panel to crash the application. The crash can be reproduced every time. -- Backtrace: Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f793fcf1880 (LWP 9875))] Thread 19 (Thread 0x7f78fcff9700 (LWP 9894)): #0 0x7f7948c30585 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0 #1 0x7f794bcb1c6b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7929a7289d in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f7929a774f8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f7929a71e4f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f7929a74f1b in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f794bcb0ee8 in QThreadPrivate::start(void*) () at /usr/lib/libQt5Core.so.5 #7 0x7f7948c2a4a7 in start_thread () at /lib/libpthread.so.0 #8 0x7f794b5c0f9f in clone () at /lib/libc.so.6 Thread 18 (Thread 0x7f78fd7fa700 (LWP 9893)): #0 0x7f7948c30585 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0 #1 0x7f794bcb1c6b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7929a7289d in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f7929a774f8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f7929a71e4f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f7929a74f1b in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f794bcb0ee8 in QThreadPrivate::start(void*) () at /usr/lib/libQt5Core.so.5 #7 0x7f7948c2a4a7 in start_thread () at /lib/libpthread.so.0 #8 0x7f794b5c0f9f in clone () at /lib/libc.so.6 Thread 17 (Thread 0x7f78fdffb700 (LWP 9892)): #0 0x7f7948c30585 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0 #1 0x7f794bcb1c6b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7929a7289d in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f7929a774f8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f7929a71e4f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f7929a74f1b in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f794bcb0ee8 in QThreadPrivate::start(void*) () at /usr/lib/libQt5Core.so.5 #7 0x7f7948c2a4a7 in start_thread () at /lib/libpthread.so.0 #8 0x7f794b5c0f9f in clone () at /lib/libc.so.6 Thread 16 (Thread 0x7f78fe7fc700 (LWP 9891)): #0 0x7f7948c30585 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0 #1 0x7f794bcb1c6b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7929a7289d in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f7929a774f8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f7929a71e4f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f7929a74f1b in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f794bcb0ee8 in QThreadPrivate::start(void*) () at /usr/lib/libQt5Core.so.5 #7 0x7f7948c2a4a7 in start_thread () at /lib/libpthread.so.0 #8 0x7f794b5c0f9f in clone () at /lib/libc.so.6 Thread 15 (Thread 0x7f78feffd700 (LWP 9890)): #0 0x7f7948c30585 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0 #1 0x7f794bcb1c6b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2
[telepathy] [Bug 397527] New: Chat UI does not auto scroll when messages are received
https://bugs.kde.org/show_bug.cgi?id=397527 Bug ID: 397527 Summary: Chat UI does not auto scroll when messages are received Product: telepathy Version: git-latest Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: text-ui Assignee: kde-telepathy-b...@kde.org Reporter: pas...@gmail.com Target Milestone: Future When new messages are received in the Chat UI (QtWidgets) the content is not auto scrolled so we can read the message immediately. One need to constantly manually scroll the chat view, very boring. It is similar to #298392 but apply to the widget based version. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393793] Can't correctly pin application desktop file
https://bugs.kde.org/show_bug.cgi?id=393793 --- Comment #7 from Filipe Azevedo --- Eike: I did tested yur trick to add "StartupWMClass=quassel" - does not works. That still pin the WRONG desktop file. I want to emphasize that the issue is really the wrong desktop file being pinned, not the wrong binary launched by the pined desktop file. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393793] Can't correctly pin application desktop file
https://bugs.kde.org/show_bug.cgi?id=393793 --- Comment #6 from Filipe Azevedo <pas...@gmail.com> --- Done, https://bugs.quassel-irc.org/issues/1482 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393793] Can't correctly pin application desktop file
https://bugs.kde.org/show_bug.cgi?id=393793 --- Comment #5 from Filipe Azevedo <pas...@gmail.com> --- Will reprot to quassel team, thanks. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 226414] Kopete crash - doing nothing ( running in the background ) [free, QRingBuffer, QAbstractSocketPrivate::canWriteNotification]
https://bugs.kde.org/show_bug.cgi?id=226414 --- Comment #8 from Filipe Azevedo <pas...@gmail.com> --- Let close this one as well -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393793] Can't correctly pin application desktop file
https://bugs.kde.org/show_bug.cgi?id=393793 --- Comment #3 from Filipe Azevedo <pas...@gmail.com> --- Created attachment 112486 --> https://bugs.kde.org/attachment.cgi?id=112486=edit quasselclient desktop file -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393793] Can't correctly pin application desktop file
https://bugs.kde.org/show_bug.cgi?id=393793 --- Comment #2 from Filipe Azevedo <pas...@gmail.com> --- Created attachment 112485 --> https://bugs.kde.org/attachment.cgi?id=112485=edit xprop quasselclient -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 213329] msn crash while doing nothing MSN::SwitchboardServerConnection::handle_BYE
https://bugs.kde.org/show_bug.cgi?id=213329 --- Comment #7 from Filipe Azevedo <pas...@gmail.com> --- Let close this issue by now. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 212319] unknow crash msn multiuser chat ( QString alloc error )
https://bugs.kde.org/show_bug.cgi?id=212319 --- Comment #2 from Filipe Azevedo <pas...@gmail.com> --- I guess we can now close this issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 294572] panel icon of folderview for path "applications:/Games" is white icon instead of the one visible in dolphin
https://bugs.kde.org/show_bug.cgi?id=294572 Filipe Azevedo <pas...@gmail.com> changed: What|Removed |Added Target Milestone|--- |1.0 Version|4.8.0 |master Product|plasma4 |plasmashell CC||plasma-b...@kde.org Component|widget-folderview |Folder Platform|Ubuntu Packages |unspecified Assignee|i.semenov@gmail.com |h...@kde.org --- Comment #3 from Filipe Azevedo <pas...@gmail.com> --- Still present. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 364873] Add support for command line --new-tab
https://bugs.kde.org/show_bug.cgi?id=364873 Filipe Azevedo <pas...@gmail.com> changed: What|Removed |Added Platform|Kubuntu Packages|unspecified --- Comment #1 from Filipe Azevedo <pas...@gmail.com> --- Any chance to see that happen ? -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 326705] Can't reliably see current active device for a recording stream when activating the context menu of a recording stream
https://bugs.kde.org/show_bug.cgi?id=326705 --- Comment #4 from Filipe Azevedo <pas...@gmail.com> --- I guess we can now close this issue as kmix seems no longer the prefered kde sound mixer (not installed anymore on my distro). Looks like plasma sound plasmoid is fine enough. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393793] New: Can't correctly pin application desktop file
https://bugs.kde.org/show_bug.cgi?id=393793 Bug ID: 393793 Summary: Can't correctly pin application desktop file Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons-only Task Manager Assignee: h...@kde.org Reporter: pas...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 I'm a quassel-client user (and only client, not the full monolithic quassel application). When I want to pin it in the taskbar it does not works, instead it pin the normal full monolithic application. If I then tweak the plasma settings file to fix the pined desktop file for quassel and restart it correctly show the desired application, still clicking it will add a new desktop entry because the taskbar thing the just launched application is not the pined one. I did not noticed another application being broken, but quassel is one of the only one providing the same application in 2 different implementation. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393367] Make it possible to quickly duplicate files/folders
https://bugs.kde.org/show_bug.cgi?id=393367 --- Comment #2 from Filipe Azevedo <pas...@gmail.com> --- (In reply to Nate Graham from comment #1) > I submitted a patch for this last year that was rejected: > https://phabricator.kde.org/D8206 > > I'll re-open it and see if I can restart the discussion. The correct url is https://phabricator.kde.org/D8208 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393367] New: Make it possible to quickly duplicate files/folders
https://bugs.kde.org/show_bug.cgi?id=393367 Bug ID: 393367 Summary: Make it possible to quickly duplicate files/folders Product: dolphin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: pas...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Currently one need to select then copy then paste and enter a new name to duplicate files/folders. This is very not very handy, less again for a large list of items to duplicate in the same folder. Please allow a new 'duplicate' mode to the standard copy/paste/cut that operate on files and folders on the current selected items. Bonus point if Dolphin can generate suggested names on its own so no user interaction is needed at all. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392863] KWin does not recognize my macbook pro graphics card
https://bugs.kde.org/show_bug.cgi?id=392863 --- Comment #7 from Filipe Azevedo <pas...@gmail.com> --- Reverting the lib name change in libepoxy and rebuilding the package fixed the issue on reboot. thank you! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392863] KWin does not recognize my macbook pro graphics card
https://bugs.kde.org/show_bug.cgi?id=392863 --- Comment #5 from Filipe Azevedo <pas...@gmail.com> --- >From my package manager, libepoxy is 1.5.0-1, is this the one impacted ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392863] KWin does not recognize my macbook pro graphics card
https://bugs.kde.org/show_bug.cgi?id=392863 --- Comment #3 from Filipe Azevedo <pas...@gmail.com> --- That's KaOS up-to-date, arguing the cutting edge approach of the distribution, should be a very recent if not latest version of libepoxy. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392863] KWin does not recognize my macbook pro graphics card
https://bugs.kde.org/show_bug.cgi?id=392863 --- Comment #1 from Filipe Azevedo <pas...@gmail.com> --- Note that glxinfo and glxgears report correct vendor/version gl strings and everything using opengl is accelerated correctly, but kwin -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392863] New: KWin does not recognize my macbook pro graphics card
https://bugs.kde.org/show_bug.cgi?id=392863 Bug ID: 392863 Summary: KWin does not recognize my macbook pro graphics card Product: kwin Version: 5.12.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: glx Assignee: kwin-bugs-n...@kde.org Reporter: pas...@gmail.com Target Milestone: --- I have a macbook pro (11.3 version if i recall, the hardware, not the OS version) with a 64bits linux distribution natively installed on it and for some reason kwin does not recognize the nvidia graphics card. Sometimes, after some minutes i can enable desktop effects using Alt+Shift+F12, still kwin always report unknow gl vendor/version etc in the console. I tried to build myself kwin to add support for it without succes. For some reason the gl calls (proxied from the libepoxy) return null strings and even trying to force intialization of those variable manually in code does not help. Is there any chance to see kwin / gl working correctly on a mac with non free drivers ? (I can't use nouveau as it regulary freeze desktop). Here are the details: - lspci | grep NVIDIA: 01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 750M Mac Edition] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GK107 HDMI Audio Controller (rev a1) - pasnox ~ la /usr/lib/*nvidia* lrwxrwxrwx 1 root root 18 28.03.2018 20:50 /usr/lib/libEGL_nvidia.so -> libEGL_nvidia.so.0* lrwxrwxrwx 1 root root 23 28.03.2018 20:50 /usr/lib/libEGL_nvidia.so.0 -> libEGL_nvidia.so.390.48* -rwxr-xr-x 1 root root 918552 28.03.2018 20:50 /usr/lib/libEGL_nvidia.so.390.48* lrwxrwxrwx 1 root root 18 28.03.2018 20:50 /usr/lib/libnvidia-cfg.so -> libnvidia-cfg.so.1* lrwxrwxrwx 1 root root 23 28.03.2018 20:50 /usr/lib/libnvidia-cfg.so.1 -> libnvidia-cfg.so.390.48* -rwxr-xr-x 1 root root 190760 28.03.2018 20:50 /usr/lib/libnvidia-cfg.so.390.48* lrwxrwxrwx 1 root root 27 28.03.2018 20:50 /usr/lib/libnvidia-eglcore.so -> libnvidia-eglcore.so.390.48* -rwxr-xr-x 1 root root 27456672 28.03.2018 20:50 /usr/lib/libnvidia-eglcore.so.390.48* lrwxrwxrwx 1 root root 26 28.03.2018 20:50 /usr/lib/libnvidia-egl-wayland.so -> libnvidia-egl-wayland.so.1* lrwxrwxrwx 1 root root 30 28.03.2018 20:50 /usr/lib/libnvidia-egl-wayland.so.1 -> libnvidia-egl-wayland.so.1.0.2* -rwxr-xr-x 1 root root31976 28.03.2018 20:50 /usr/lib/libnvidia-egl-wayland.so.1.0.2* lrwxrwxrwx 1 root root 35 28.03.2018 20:50 /usr/lib/libnvidia-fatbinaryloader.so -> libnvidia-fatbinaryloader.so.390.48* -rwxr-xr-x 1 root root 291496 28.03.2018 20:50 /usr/lib/libnvidia-fatbinaryloader.so.390.48* lrwxrwxrwx 1 root root 26 28.03.2018 20:50 /usr/lib/libnvidia-glcore.so -> libnvidia-glcore.so.390.48* -rwxr-xr-x 1 root root 29256232 28.03.2018 20:50 /usr/lib/libnvidia-glcore.so.390.48* lrwxrwxrwx 1 root root 24 28.03.2018 20:50 /usr/lib/libnvidia-glsi.so -> libnvidia-glsi.so.390.48* -rwxr-xr-x 1 root root 554776 28.03.2018 20:50 /usr/lib/libnvidia-glsi.so.390.48* -rwxr-xr-x 1 root root 1472040 28.03.2018 20:52 /usr/lib/libnvidia-gtk2.so.390.48* -rwxr-xr-x 1 root root 1479400 28.03.2018 20:52 /usr/lib/libnvidia-gtk3.so.390.48* lrwxrwxrwx 1 root root 17 28.03.2018 20:50 /usr/lib/libnvidia-ml.so -> libnvidia-ml.so.1* lrwxrwxrwx 1 root root 22 28.03.2018 20:50 /usr/lib/libnvidia-ml.so.1 -> libnvidia-ml.so.390.48* -rwxr-xr-x 1 root root 1310336 28.03.2018 20:50 /usr/lib/libnvidia-ml.so.390.48* lrwxrwxrwx 1 root root 23 28.03.2018 20:50 /usr/lib/libnvidia-tls.so -> libnvidia-tls.so.390.48* -rwxr-xr-x 1 root root14480 28.03.2018 20:50 /usr/lib/libnvidia-tls.so.390.48* -- You are receiving this mail because: You are watching all bug changes.
