[kdeconnect] [Bug 493958] Crash on android. After update it fully crash
https://bugs.kde.org/show_bug.cgi?id=493958 Lamarque V. Souza changed: What|Removed |Added CC||kde-b...@foobarlibre.net --- Comment #12 from Lamarque V. Souza --- *** Bug 493990 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 493990] App crashes immediately with SecurityException
https://bugs.kde.org/show_bug.cgi?id=493990 Lamarque V. Souza changed: What|Removed |Added CC||lamar...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Lamarque V. Souza --- *** This bug has been marked as a duplicate of bug 493958 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] With fractional scale, bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 Lamarque V. Souza changed: What|Removed |Added CC|lamar...@kde.org| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483137] Screencast plugin fails if PipeWire is started after KWin
https://bugs.kde.org/show_bug.cgi?id=483137 --- Comment #9 from Lamarque V. Souza --- I have found another workaround: Screencast works if I launch pipewire through a script in $HOME/.config/plasma-workspace/env/. In Gentoo the script is as simple as: /usr/bin/gentoo-pipewire-launcher & PS: there is no need for the script to be executable since plasma-session sources it. I also had to disable pipewire autostart by removing the file /etc/xdg/autostart/pipewire.desktop to avoid pipewire being restarted during startup. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483137] Screencast plugin fails if PipeWire is started after KWin
https://bugs.kde.org/show_bug.cgi?id=483137 --- Comment #6 from Lamarque V. Souza --- Created attachment 168354 --> https://bugs.kde.org/attachment.cgi?id=168354&action=edit Revert commit 37d2a7914329c65361eedfd995f25bd6867b68bc for kwin 6.0.3.1 I have updated the revert patch to apply to kwin 6.0.3.1 so we can use screencast until the problem is properly fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] Bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 Lamarque V. Souza changed: What|Removed |Added CC||lamar...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 473052] System monitor grid style widget doesn't apply configured update interval to sensors
https://bugs.kde.org/show_bug.cgi?id=473052 Lamarque V. Souza changed: What|Removed |Added CC||lamar...@kde.org --- Comment #2 from Lamarque V. Souza --- It happens for me too. Operating System: Gentoo Linux 2.14 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.6.16-lvs (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483137] Screencast plugin fails if PipeWire is started after KWin
https://bugs.kde.org/show_bug.cgi?id=483137 Lamarque V. Souza changed: What|Removed |Added CC||lamar...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482828] Task Manager icons disappear/move to the left when mouse is moved over them
https://bugs.kde.org/show_bug.cgi?id=482828 --- Comment #4 from Lamarque V. Souza --- I use Intel gpu for Plasma 5 and 6. I had tried to make Plasma 5 (kwin_wayland) use the nvidia gpu in the past with no success. However, I have tested with a new user and it does not have this problem. So I did a backup of my entire $HOME/.config folder, copied that user's configuration files over my configuration files and that solved that particular problem. After that I restored some configuration files from the backup, redid some other configurations and that is it: Plasma 6 is working better than Plasma 5 now. I does not know which configuration fixed the problem for me though. I guess everybody should test with a new user to make sure it is not just a configuration problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482828] Task bar/panel icons disappear when mouse is moved over them
https://bugs.kde.org/show_bug.cgi?id=482828 Lamarque V. Souza changed: What|Removed |Added CC||lamar...@kde.org --- Comment #2 from Lamarque V. Souza --- Same here with Gentoo. I own a dual gpu notebook (intel + nvidia). I have removed all offloading to nvidia configuration and still the same problem. The glitches looks like kwin_wayland 6 is using software rendering. Everything used to work with kwin_wayland 5. Version === KWin version: 6.0.1 Qt Version: 6.6.2 Qt compile version: 6.6.2 XCB compile version: 1.16 Operation Mode: Xwayland Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_X11_XCB: yes HAVE_GLX: yes X11 === Vendor: The X.Org Foundation Vendor Release: 12302004 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Plugin recommends border size: None onAllDesktopsAvailable: false alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 5, 1 decorationButtonsRight: 3, 4 borderSize: 2 gridUnit: 10 font: Noto Sans,9,-1,5,400,0,0,0,0,0,0,0,0,0,0,1 smallSpacing: 2 largeSpacing: 10 Output backend == Name: DRM Atomic Mode Setting on GPU 0: true Cursor == themeName: ComixCursors-custom themeSize: 24 Options === focusPolicy: FocusFollowsMouse xwaylandCrashPolicy: 1 xwaylandMaxCrashCount: 3 nextFocusPrefersMouse: true clickRaise: true autoRaise: false autoRaiseInterval: 750 delayFocusInterval: 100 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false activeMouseScreen: true placement: 4 activationDesktopPolicy: SwitchToOtherDesktop focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: false focusStealingPreventionLevel: 0 operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: MouseRaise commandActiveTitlebar2: MouseNothing commandActiveTitlebar3: MouseOperationsMenu commandInactiveTitlebar1: MouseActivateAndRaise commandInactiveTitlebar2: MouseNothing commandInactiveTitlebar3: MouseOperationsMenu commandWindow1: MouseActivateRaiseAndPassClick commandWindow2: MouseActivateAndPassClick commandWindow3: MouseActivateAndPassClick commandWindowWheel: MouseNothing commandAll1: MouseUnrestrictedMove commandAll2: MouseToggleRaiseAndLower commandAll3: MouseUnrestrictedResize keyCmdAllModKey: 16777251 condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true compositingMode: 1 useCompositing: true hiddenPreviews: 1 glSmoothScale: 1 glStrictBinding: true glStrictBindingFollowsDriver: true glPreferBufferSwap: AutoSwapStrategy glPlatformInterface: 2 windowsBlockCompositing: true allowTearing: true Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 100 reActivateThreshold: 200 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Active screen follows mouse: yes Number of Screens: 3 Screen 0: - Name: eDP-1 Enabled: 1 Geometry: 3840,0,1920x1080 Scale: 1 Refresh Rate: 60020 Adaptive Sync: incapable Screen 1: - Name: DP-1 Enabled: 1 Geometry: 1920,0,1920x1080 Scale: 1 Refresh Rate: 6 Adaptive Sync: incapable Screen 2: - Name: DP-2 Enabled: 1 Geometry: 0,0,1920x1080 Scale: 1 Refresh Rate: 6 Adaptive Sync: incapable Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) HD Graphics 530 (SKL GT2) OpenGL version string: 4.6 (Core Profile) Mesa 23.3.6 OpenGL platform interface: EGL OpenGL shading language version string: 4.60 Driver: Intel GPU class: Skylake OpenGL version: 4.6 GLSL version: 4.60 Mesa version: 23.3.6 X server version: 1.23.2 Linux kernel version: 6.6.16 Direct rendering: Requires strict binding: no Virtual Machine: no OpenGL 2 Shaders are used Loaded Effects: --- thumbnailaside screenshot outputlocator colorpicker zoom screenedge mousemark blur contrast sessionquit logout login slidingpopups windowaperture slide morphingpopups frozenapp fullscreen maximize squash scale fadingpopups dialogparent windowview tileseditor overview highlightwindow blendchanges startupfeedback screentransform kscreen Currently Active Effects: - blur
[kdeconnect] [Bug 442782] KDE Connect is draining battery
https://bugs.kde.org/show_bug.cgi?id=442782 --- Comment #11 from Lamarque V. Souza --- My vlc's problem is similar to this one: https://code.videolan.org/videolan/vlc/-/issues/26564 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 442782] KDE Connect is draining battery
https://bugs.kde.org/show_bug.cgi?id=442782 --- Comment #9 from Lamarque V. Souza --- I have figure out the problem: vlc sends a lot of Seeked dbus signals (about four per second) when I watch a tv channel stream in my notebook. kdeconnect-kde's mutimedia control receiver plugin in my Plasma desktop relays all those signals to the android app through the tcp link (four tcp packets per seconds!!!). One workaround is disabling the multimedia control receiver plugin, but then I cannot play/pause vlc anymore. I have created a patch to kdeconnect-kde to add a 5 seconds delay before sending any Seeked data and it improves my cellphone battery and I still can play/pause vlc. Of couse, that is not a solution, it is just a workaround. I think kdeconnect-kde should not send data that is useless to the android app. I mean, my cellphone is locked, there is no need to update the progress bar in android app's multimedia control plugin. There is still another reason: the tv channel stream is infinite stream, there is no way to calculate it's ending, so there is no way to calculate the progress bar's maximum value. By what I could guess, the android app uses 100 minutes as the default maximum value, but all vlc's Seeked values are bigger than that, so the progress is always at the end of the progress bar. In my opinion, the android app should send to the kdeconnect-kde if the cellphone is locked and if the app is visible. If the app is not visible, then the kdeconnect-kde should avoid sending any data that are only used to update the widgets in the android app. The if cellphone is locked, then the plasma applet should also increase the interval to send any data to the cellphone, so the cellphone can have a chance to save battery. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 442782] KDE Connect is draining battery
https://bugs.kde.org/show_bug.cgi?id=442782 --- Comment #8 from Lamarque V. Souza --- I have downgraded Android app to 1.19.1 and it works much better. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 442782] KDE Connect is draining battery
https://bugs.kde.org/show_bug.cgi?id=442782 Lamarque V. Souza changed: What|Removed |Added CC||lamar...@kde.org --- Comment #7 from Lamarque V. Souza --- I am also affected since last Android app update to version 1.20.1. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447116] kwin crashes after pressing alt-tab twice
https://bugs.kde.org/show_bug.cgi?id=447116
--- Comment #8 from Lamarque V. Souza ---
kwin_x11 also has this problem in my laptop when compositing is enabled. It was
disabled when I first tested, so I could not reproduce the problem. So both
kwin_x11 and kwin_wayland have this problem for me. The difference is that
kwin_x11 does not crash, it just disables compositing when the problem happens
('qdbus org.kde.KWin /Compositor org.kde.kwin.Compositing.active' returns
false). I have the re-enable compositing through systemsettings, using 'qdbus
org.kde.KWin /Compositor org.kde.kwin.Compositing.resume' does not work.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 447116] kwin crashes after pressing alt-tab twice
https://bugs.kde.org/show_bug.cgi?id=447116 --- Comment #7 from Lamarque V. Souza --- (In reply to Vlad Zahorodnii from comment #6) > > shows that qmlscene uses the nvidia gpu in my wayland session > That's really strange. Both kwin and qt should use the same render device. I think that was because I was using nvidia-drivers-495.46 (this one uses gbm). I downgraded to nvidia-drivers-470.94, which seems a bit more stable and qmlscene shows it is using the Intel gpu. > > pressing ALT-TAB twice before the switching app is loaded will crash kwin > > and switch off composer > Just to clarify, should alt-tab be pressed twice before the task switcher > window is shown? I created this video to show that happens: https://photos.app.goo.gl/pEbGALMLLDkyZ7Zs9 Just one Alt+Tab is enough to crash kwin_wayland in my case. kwin_wayland restarts after the crash (ps shows there is a new kwin_wayland instance with different pid), but it get stuck somehow. The gray window that appears three times at the end of the video is me pressing Alt+Tab three times. It seems it tries to render the thumbnail switcher, kwin_wayland does not crash this time, but also does not render anything besides that window. I have to 'killall kwayland' to get a new login screen in sddm. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447116] kwin crashes after pressing alt-tab twice
https://bugs.kde.org/show_bug.cgi?id=447116 --- Comment #4 from Lamarque V. Souza --- kwin_wayland still crashes and kwin_x11 still works even when I disabled the nvidia drivers and uses the intel gpu only. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447116] kwin crashes after pressing alt-tab twice
https://bugs.kde.org/show_bug.cgi?id=447116 --- Comment #3 from Lamarque V. Souza --- I forgot to say that kwin_x11 uses the nvidia gpu and kwin_wayland uses the intel gpu to renter. I have done a quick test and "QT_LOGGING_RULES=qt.scenegraph.*=true" shows that qmlscene uses the nvidia gpu in my wayland session. I should be using the intel gpu. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447116] kwin crashes after pressing alt-tab twice
https://bugs.kde.org/show_bug.cgi?id=447116 Lamarque V. Souza changed: What|Removed |Added CC||lamar...@kde.org --- Comment #2 from Lamarque V. Souza --- I have the same problema but with kwin_wayland. kwin_x11 works for me. #0 0x7f1f6f6eaad0 in QSGTexture::setFiltering(QSGTexture::Filtering) () from /usr/lib64/libQt5Quick.so.5 #1 0x7f1f700dd5b0 in KWin::ThumbnailTextureProvider::setTexture(QSharedPointer const&) () from /usr/lib64/libkwin.so.5 #2 0x7f1f700dec73 in KWin::ThumbnailItemBase::updatePaintNode(QSGNode*, QQuickItem::UpdatePaintNodeData*) () from /usr/lib64/libkwin.so.5 #3 0x7f1f6f7c0ba8 in QQuickWindowPrivate::updateDirtyNode(QQuickItem*) () from /usr/lib64/libQt5Quick.so.5 #4 0x7f1f6f7c115b in QQuickWindowPrivate::updateDirtyNodes() () from /usr/lib64/libQt5Quick.so.5 #5 0x7f1f6f7c2d8c in QQuickWindowPrivate::syncSceneGraph() () from /usr/lib64/libQt5Quick.so.5 #6 0x7f1f6f77ca88 in QSGSoftwareRenderLoop::renderWindow(QQuickWindow*, bool) () from /usr/lib64/libQt5Quick.so.5 #7 0x7f1f6f7d1497 in QQuickWindow::event(QEvent*) () from /usr/lib64/libQt5Quick.so.5 #8 0x7f1f6e833abf in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #9 0x7f1f6dd3d1e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #10 0x7f1f6e17ee4c in QPlatformWindow::deliverUpdateRequest() () from /usr/lib64/libQt5Gui.so.5 #11 0x7f1f6e17d3be in QPlatformWindow::windowEvent(QEvent*) () from /usr/lib64/libQt5Gui.so.5 #12 0x7f1f6e83ae1e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #13 0x7f1f6dd3d1e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #14 0x7f1f6dd93b9e in QTimerInfoList::activateTimers() () from /usr/lib64/libQt5Core.so.5 #15 0x7f1f6dd91a6f in QEventDispatcherUNIX::processEvents(QFlags for more, q to quit, c to continue without paging-- op::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #16 0x562822f3a6dd in QUnixEventDispatcherQPA::processEvents(QFlags) () #17 0x7f1f6dd3b71b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #18 0x7f1f6dd44470 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 My laptop has two gpus: Intel HD Graphics 530 (/dev/card/card0) and Nvidia GeForce GTX 970M (/dev/dri/card1). m_window->openglContext() returns null inside ThumbnailTextureProvider::setTexture. That's probably explains why m_window->createTextureFromNativeObject() also returns null. The point is why the OpenGL context is null there. Maybe it is related to the fact that there are two gpus involved? -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 398878] krdc crashes when disconnecting from VNC servers
https://bugs.kde.org/show_bug.cgi?id=398878 Lamarque V. Souza changed: What|Removed |Added Latest Commit||https://invent.kde.org/netw ||ork/krdc/commit/ba6baad9b49 ||a8a7fe57f27046631fc00c177e1 ||a0 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Lamarque V. Souza --- Git commit ba6baad9b49a8a7fe57f27046631fc00c177e1a0 by Lamarque V. Souza. Committed on 12/03/2021 at 15:26. Pushed by lvsouza into branch 'fix_crash_on_disconnect'. Fix crash when closing a tab. TabbedViewWidget::removePage is called twice for the same page, which leads to crash on the second run. It is called by those two signals in mainwindow.cpp: connect(disconnectAction, SIGNAL(triggered()), SLOT(disconnectHost())); connect(view, SIGNAL(disconnected()), this, SLOT(disconnectHost())); M +3-0tabbedviewwidget.cpp https://invent.kde.org/network/krdc/commit/ba6baad9b49a8a7fe57f27046631fc00c177e1a0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433064] systemmonitor line chart "amount of history to keep" has no effect
https://bugs.kde.org/show_bug.cgi?id=433064
Lamarque V. Souza changed:
What|Removed |Added
CC||lamar...@kde.org
--- Comment #5 from Lamarque V. Souza ---
The commit 10d8d20a3bc4016ee271aee234f7727e5640cedc causes a crash in
SensorDataModel::onMetaDataChanged during this call
beginInsertColumns(QModelIndex{}, column, column);
column is calculated using
auto column = d->sensors.indexOf(sensorId);
but since your commit removed this code
for (const auto& sensor : sensors) {
sensorInfos[sensor] = KSysGuard::SensorInfo();
}
the size of sensors and sensorInfos are not in sync for certain amount of time.
This is backtrace:
[08:07:24.435] unknown: ASSERT: "first <= columnCount(parent)" in file
/var/tmpfs/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/itemmodels/qabstractitemmodel.cpp,
line 3062
Thread 1 "plasmashell" received signal SIGABRT, Aborted.
0x75399a21 in raise () from /lib64/libc.so.6
(gdb) bt
#0 0x75399a21 in raise () at /lib64/libc.so.6
#1 0x75383536 in abort () at /lib64/libc.so.6
#2 0x7582da8d in qCleanupFuncinfo(QByteArray) [clone .cold] () at
/usr/lib64/libQt5Core.so.5
#3 0x7582c7f7 in unquote(char const*, char const*) [clone .cold] () at
/usr/lib64/libQt5Core.so.5
#4 0x7584a81e in QAbstractItemModel::beginInsertColumns(QModelIndex
const&, int, int) [clone .cold] () at /usr/lib64/libQt5Core.so.5
#5 0x7fffe9950355 in KSysGuard::SensorDataModel::onMetaDataChanged(QString
const&, KSysGuard::SensorInfo const&) () at /usr/lib64/libKSysGuardSensors.so.1
#6 0x75a83b5e in void doActivate(QObject*, int, void**) () at
/usr/lib64/libQt5Core.so.5
#7 0x7fffe994c297 in
KSysGuard::SensorDaemonInterface::metaDataChanged(QString const&,
KSysGuard::SensorInfo const&) () at /usr/lib64/libKSysGuardSensors.so.1
#8 0x7fffe99655d9 in
QtPrivate::QFunctorSlotObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () at
/usr/lib64/libKSysGuardSensors.so.1
#9 0x75a83b5e in void doActivate(QObject*, int, void**) () at
/usr/lib64/libQt5Core.so.5
#10 0x76442ccf in
QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () at
/usr/lib64/libQt5DBus.so.5
#11 0x76442ddb in QDBusPendingCallWatcher::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () at /usr/lib64/libQt5DBus.so.5
#12 0x75a7aaea in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#13 0x76765bbf in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#14 0x7676e0c0 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#15 0x75a4c2c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#16 0x75a4f17c in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#17 0x75aa81e3 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /usr/lib64/libQt5Core.so.5
#18 0x73e88ead in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#19 0x73e89130 in g_main_context_iterate.isra () at
/usr/lib64/libglib-2.0.so.0
#20 0x73e891bf in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#21 0x75aa7c2e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#22 0x75a4ac0b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#23 0x75a53790 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#24 0x555757fa in main ()
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 425625] "Automatically connect to VPN" causes the primary connection to not connect.
https://bugs.kde.org/show_bug.cgi?id=425625 --- Comment #1 from Lamarque V. Souza --- This looks like a upstream problem: https://bugzilla.gnome.org/show_bug.cgi?id=785699 As a workaround I do this in my Gentoo Linux: systemtray -> Notifications -> Applications: Configure -> Network Management -> Configure Events... -> Connection Activated In "Run command field" add the path of a script like this: #!/bin/sh CONNECTION_NAME=connection VPN_NAME=vpn if nmcli | grep -q "connected to $CONNECTION_NAME" && ! nmcli c show $VPN_NAME | grep -q ActiveConnection; then nmcli c up $VPN_NAME fi -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 224450] DBus signals on going to lock screen, suspend, hibernate and wake up
https://bugs.kde.org/show_bug.cgi?id=224450 --- Comment #4 from Lamarque V. Souza --- (In reply to Nate Graham from comment #2) > Are they still missing, or have they since been added? Most of them are still missing. Only PrepareForSleep is available now through login1 dbus interface (resumingFromSuspend from Solid's Powermanagement interface has been removed): qdbus --system org.freedesktop.login1 /org/freedesktop/login1 | grep signal signal void org.freedesktop.DBus.Properties.PropertiesChanged(QString interface, QVariantMap changed_properties, QStringList invalidated_properties) signal void org.freedesktop.login1.Manager.PrepareForShutdown(bool) signal void org.freedesktop.login1.Manager.PrepareForSleep(bool) signal void org.freedesktop.login1.Manager.SeatNew(QString, QDBusObjectPath) signal void org.freedesktop.login1.Manager.SeatRemoved(QString, QDBusObjectPath) signal void org.freedesktop.login1.Manager.SessionNew(QString, QDBusObjectPath) signal void org.freedesktop.login1.Manager.SessionRemoved(QString, QDBusObjectPath) signal void org.freedesktop.login1.Manager.UserNew(uint, QDBusObjectPath) signal void org.freedesktop.login1.Manager.UserRemoved(uint, QDBusObjectPath) I guess PrepareForSleep can be used for both hibernate (suspend to disk) and sleep (suspend to ram). I do not see how a signal for lock screen can be usefull. A signal for wake up (resuming from suspend) is usefull to overcome some gpu problems, though usually you need to run the commands for that as root. I usually use the directory /etc/pm/ from pm-utils to run scripts just before sleeping and after wake up. That is not exactly user friendly but works ok. -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 424112] Cannot run commands anymore
https://bugs.kde.org/show_bug.cgi?id=424112 Lamarque V. Souza changed: What|Removed |Added CC||k...@sdht.in --- Comment #4 from Lamarque V. Souza --- *** Bug 424390 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 424390] Regression in handling custom shortcut commands
https://bugs.kde.org/show_bug.cgi?id=424390 Lamarque V. Souza changed: What|Removed |Added Status|REPORTED|RESOLVED CC||lamar...@kde.org Resolution|--- |DUPLICATE --- Comment #1 from Lamarque V. Souza --- *** This bug has been marked as a duplicate of bug 424112 *** -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 424112] Cannot run commands anymore
https://bugs.kde.org/show_bug.cgi?id=424112 Lamarque V. Souza changed: What|Removed |Added CC||lamar...@kde.org --- Comment #2 from Lamarque V. Souza --- I am also affected by this change. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414890] Palette Docker does not show swatches 9 Version: 4.3.0-prealpha (git 818c841)
https://bugs.kde.org/show_bug.cgi?id=414890 --- Comment #5 from Lamarque V. Souza --- Git commit 8a0b7cbe060742024aca9169a03cc7d70ad1d71a by Lamarque V. Souza. Committed on 09/01/2020 at 19:51. Pushed by lvsouza into branch 'lvsouza/another_attempt_to_fix_crash_in_debug_mode'. Commit 97c03e0f3314dae5520deb901dda73d1cf8df201 was reverted by ef55574a4af75134a2a9be03fcd70e8b16aaf614 and then the crash happens again. I have tested this change and it does not break PalleteDocker. PS: KIS_ASSERT_RECOVER_RETURN_VALUE trigger an assert and krita fails to start up. KisPaletteModel::index works if I use KIS_SAFE_ASSERT_RECOVER_RETURN_VALUE and change KoColorSet::getGroup to return null pointer when its name parameter is an empty string, but KisSwatchGroup::rowCount crashes, so I think it is simpler to return an default QModelIndex as soon as possible in KisPaletteModel::index M +3-0libs/widgets/KisPaletteModel.cpp https://invent.kde.org/kde/krita/commit/8a0b7cbe060742024aca9169a03cc7d70ad1d71a -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 377058] KDE Connect : SD card empty
https://bugs.kde.org/show_bug.cgi?id=377058 Lamarque V. Souza changed: What|Removed |Added CC||lamar...@kde.org --- Comment #6 from Lamarque V. Souza --- If I change the url in Dolphin from /storage/B4BE-4FFD/ /mnt/media_rw/B4BE-4FFD/ then Dolphin lists the folder contents. KDE Connect's Android app [1] hardcodes "/storage" as the path to search for all storages, which makes sense except for the fact that Android does not provide a standard way to access the external sdcard (by what I could find on the Internet). In most cases /storage provides access to the internal storage and the emulated sdcard (a portion of the internal storage used to emulate a external sdcard). There seems not to be any standard way to access the real external sdcard. There are some hacks available [2] but they sometimes break due to changes made by phone manufacturers in their Android flavors. Maybe someone could add a configuration to the plugin to the "remote filesystem browser" plugin to indicate the correct path to the real external sdcard. [1] kdeconnect-android/src/org/kde/kdeconnect/Helpers/StorageHelper.java [2] https://stackoverflow.com/a/40582634 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 349282] Can't import OpenVPN configuration files with inline certificates and keys
https://bugs.kde.org/show_bug.cgi?id=349282 --- Comment #11 from Lamarque V. Souza --- Does your file name has any space in it? If it does then you must use quotation mark in the .ovpn to delimitate the file name. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 349282] Can't import OpenVPN configuration files with inline certificates and keys
https://bugs.kde.org/show_bug.cgi?id=349282 --- Comment #9 from Lamarque V. Souza --- Hi. Hmmm QFile was not able to open the source file (/home/psy/vpn/UKP/[inline]). Does your user has permission to open that file for reading? That error message is shown only if QFile::copy returns false [1] If the destination file already exists then QFile::copy returns false. That can be the problem too. In that case QFile::copy does not override the destination file. Probably we should ask the user if he/she wants to override it or keep the old one. [1] http://doc.qt.io/qt-5/qfile.html#copy OBS: since Plasma NM was not able to copy the file what it does is registering the source file's path (/home/psy/vpn/UKP/[inline]) in NetworkManager. Since NetworkManager run as root it probably has permission to read that file. OBS2: Plasma NM run as normal user. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 379279] NetworkManager "Ask For Password" Popup Focus
https://bugs.kde.org/show_bug.cgi?id=379279 Lamarque V. Souza changed: What|Removed |Added Version Fixed In||5.9.6 Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-nm/2c6b059626dedd1ae82f ||b06f0d6f8737dae8e5b5 Resolution|--- |FIXED --- Comment #10 from Lamarque V. Souza --- Git commit 2c6b059626dedd1ae82fb06f0d6f8737dae8e5b5 by Lamarque V. Souza. Committed on 04/05/2017 at 12:36. Pushed by lvsouza into branch 'master'. Workaround to fix PasswordDialog's focus. REVIEW: 130109 FIXED-IN: 5.9.6 M +7-1kded/passworddialog.cpp https://commits.kde.org/plasma-nm/2c6b059626dedd1ae82fb06f0d6f8737dae8e5b5 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 373393] Plasmashell crashes with signal 11 (SIGSEGV)
https://bugs.kde.org/show_bug.cgi?id=373393 Lamarque V. Souza changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Lamarque V. Souza --- (In reply to Lamarque V. Souza from comment #4) > I this patch can fix this problem. Can you recompile networkmanager-qt with > it? > > https://git.reviewboard.kde.org/r/130111/ Patch applied, reopen the bug if it does not solve the problem for you. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373993] Cannot change default Email client from kmail.
https://bugs.kde.org/show_bug.cgi?id=373993 Lamarque V. Souza changed: What|Removed |Added CC||lamar...@kde.org Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|FIXED |--- --- Comment #2 from Lamarque V. Souza --- Sorry, wrong bug in my commit. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373993] Cannot change default Email client from kmail.
https://bugs.kde.org/show_bug.cgi?id=373993 Lamarque V. Souza changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/net ||workmanager-qt/0d5a02e56274 ||9af42265c00fc3423817476d553 ||4 --- Comment #1 from Lamarque V. Souza --- Git commit 0d5a02e562749af42265c00fc3423817476d5534 by Lamarque V. Souza. Committed on 02/05/2017 at 12:59. Pushed by lvsouza into branch 'master'. Fix crash when retrieving active connection list. REVIEW: 130111 M +6-4src/manager.cpp https://commits.kde.org/networkmanager-qt/0d5a02e562749af42265c00fc3423817476d5534 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 350521] [RFE] [OpenVPN] kdeplasma-applets-plasma-nm does not support OTP Tokens for OpenVPN connections
https://bugs.kde.org/show_bug.cgi?id=350521 Lamarque V. Souza changed: What|Removed |Added CC||lamar...@kde.org --- Comment #5 from Lamarque V. Souza --- (In reply to vst from comment #2) > It does not work in Gnome. Here's a bug report: > https://bugzilla.gnome.org/show_bug.cgi?id=752740 > But this may also be a client issue, I cannot tell. It looks like [1] this has been implemented in networkmanager-openvpn 1.2.8. By what I can see in the implementation we do not need to change anything in Plasma NM for it to work. Can you upgrade networkmanager-openvpn an check if it works for you? [1] https://bugzilla.gnome.org/show_bug.cgi?id=751842 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 379279] NetworkManager "Ask For Password" Popup Focus
https://bugs.kde.org/show_bug.cgi?id=379279 --- Comment #6 from Lamarque V. Souza --- Yes, recompiling that plasma-nm is enough to test the patch. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 379279] NetworkManager "Ask For Password" Popup Focus
https://bugs.kde.org/show_bug.cgi?id=379279 Lamarque V. Souza changed: What|Removed |Added CC||lamar...@kde.org --- Comment #4 from Lamarque V. Souza --- Can you test this patch https://git.reviewboard.kde.org/r/130109/ and check if it works for you? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 373393] Plasmashell crashes with signal 11 (SIGSEGV)
https://bugs.kde.org/show_bug.cgi?id=373393 Lamarque V. Souza changed: What|Removed |Added CC||lamar...@kde.org --- Comment #4 from Lamarque V. Souza --- I this patch can fix this problem. Can you recompile networkmanager-qt with it? https://git.reviewboard.kde.org/r/130111/ -- You are receiving this mail because: You are watching all bug changes.
[Network Management] [Bug 313175] Plasma popup has different size when launched from systray or from individual widget
https://bugs.kde.org/show_bug.cgi?id=313175 Lamarque V. Souza changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REOPENED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Network Management] [Bug 312963] VPN network connection edit begins with long pause and error message
https://bugs.kde.org/show_bug.cgi?id=312963 Lamarque V. Souza changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Network Management] [Bug 327667] Network manager crushes plasma when attempting to see connection info. Using TL-WN721N usb wifi adapter.
https://bugs.kde.org/show_bug.cgi?id=327667 Lamarque V. Souza changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Network Management] [Bug 336485] Intermittant loss of Wi-Fi connection
https://bugs.kde.org/show_bug.cgi?id=336485 Lamarque V. Souza changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED -- You are receiving this mail because: You are watching all bug changes.
[Network Management] [Bug 322343] kde-plasma-networkmanagement-openvpnsupport for OpenVPN IPv6 tunnels (--tun-ipv6)
https://bugs.kde.org/show_bug.cgi?id=322343 Lamarque V. Souza changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #4 from Lamarque V. Souza --- The support for this has been implemented in NetworkManager according to https://bugzilla.gnome.org/show_bug.cgi?id=761907 . It should be working Plamsa NM already, if not reopen this bug. -- You are receiving this mail because: You are watching all bug changes.
[Network Management] [Bug 324681] USB 3G modem not recognized by Network Manager KDE applet
https://bugs.kde.org/show_bug.cgi?id=324681 Lamarque V. Souza changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED -- You are receiving this mail because: You are watching all bug changes.
[Network Management] [Bug 323995] DNS settings are lost after laptop resumes from sleep
https://bugs.kde.org/show_bug.cgi?id=323995 Lamarque V. Souza changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WAITINGFORINFO -- You are receiving this mail because: You are watching all bug changes.
[Network Management] [Bug 323864] Applet asks for PPP password twice while connecting to a mobile 3G network
https://bugs.kde.org/show_bug.cgi?id=323864 Lamarque V. Souza changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Network Management] [Bug 321983] Plasma Desktop crashed when 3G Modem was unplugged from the USB
https://bugs.kde.org/show_bug.cgi?id=321983 Lamarque V. Souza changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Network Management] [Bug 320917] The size of disconnect button in network manager is too tiny
https://bugs.kde.org/show_bug.cgi?id=320917 Lamarque V. Souza changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 279215] Log-out dialog is visually broken, and has no focus
https://bugs.kde.org/show_bug.cgi?id=279215 Lamarque V. Souza changed: What|Removed |Added Resolution|WORKSFORME |FIXED Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 370256] plasma crashed spontaneously on QNetworkManagerInterfaceDeviceWireless::accessPointAdded message
https://bugs.kde.org/show_bug.cgi?id=370256 --- Comment #3 from Lamarque V. Souza --- plasma-nm does not use QNetworkManagerInterfaceAccessPoint class, which is the class where the crash happened according to the backtrace. Send me a screenshot of your desktop's panel, so I can see the applets you are using. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 370256] plasma crashed spontaneously on QNetworkManagerInterfaceDeviceWireless::accessPointAdded message
https://bugs.kde.org/show_bug.cgi?id=370256 --- Comment #1 from Lamarque V. Souza --- This crash happens inside Qt. As far as I know no KDE software uses QNetworkManagerInterfaceAccessPoint class. What plasmoid do you use to manage network connections? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366708] Set default network priority not to zero
https://bugs.kde.org/show_bug.cgi?id=366708 --- Comment #6 from Lamarque V. Souza --- (In reply to Simone Gaiarin from comment #5) > Great! Thanks You're welcome and thanks for spotting this issue. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366708] Set default network priority not to zero
https://bugs.kde.org/show_bug.cgi?id=366708 Lamarque V. Souza changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/plas ||ma-nm/634dd971a997d8d2f7cf0 ||ead3c80f8cd47091aab Version Fixed In||5.7.5 Resolution|--- |FIXED --- Comment #3 from Lamarque V. Souza --- Git commit 634dd971a997d8d2f7cf0ead3c80f8cd47091aab by Lamarque V. Souza. Committed on 06/09/2016 at 08:36. Pushed by lvsouza into branch 'master'. Allow negative priorities since NetworkManager's specification allows that [1] [1] https://developer.gnome.org/NetworkManager/stable/ref-settings.html FIXED-IN: 5.7.5 M +8-0libs/editor/settings/ui/connectionwidget.ui http://commits.kde.org/plasma-nm/634dd971a997d8d2f7cf0ead3c80f8cd47091aab -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366708] Set default network priority not to zero
https://bugs.kde.org/show_bug.cgi?id=366708 Lamarque V. Souza changed: What|Removed |Added Latest Commit|http://commits.kde.org/plas |http://commits.kde.org/plas |ma-nm/634dd971a997d8d2f7cf0 |ma-nm/65391985791da862adf2f |ead3c80f8cd47091aab |6f678a540b3963db3db --- Comment #4 from Lamarque V. Souza --- Git commit 65391985791da862adf2f6f678a540b3963db3db by Lamarque V. Souza. Committed on 06/09/2016 at 08:37. Pushed by lvsouza into branch 'Plasma/5.7'. Allow negative priorities since NetworkManager's specification allows that [1] [1] https://developer.gnome.org/NetworkManager/stable/ref-settings.html FIXED-IN: 5.7.5 M +8-0libs/editor/settings/ui/connectionwidget.ui http://commits.kde.org/plasma-nm/65391985791da862adf2f6f678a540b3963db3db -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366708] Set default network priority not to zero
https://bugs.kde.org/show_bug.cgi?id=366708 Lamarque V. Souza changed: What|Removed |Added CC||lamar...@kde.org --- Comment #1 from Lamarque V. Souza --- Hi Simone. Well, this goes against NetworkManager's specification [1]. I would rather prefer you open a bug report in http://bugs.gnome.org (component NetworkManager) so it can be changed in the specification and for all other NM's clients. Plasma NM is a NM client, like nm-applet, nmcli, etc. We need to change this for all clients to make this change consistent across all of them. [1] https://developer.gnome.org/NetworkManager/stable/ref-settings.html -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 365458] [RFE] [OpenVPN] plasma editor doesn't save tls-auth info while exporting vpn profile
https://bugs.kde.org/show_bug.cgi?id=365458 Lamarque V. Souza changed: What|Removed |Added Latest Commit|http://commits.kde.org/plas |http://commits.kde.org/plas |ma-nm/48db82bc5b5801eeb7cbb |ma-nm/4eede9a350e36c8459495 |ad838cca6460a4afce5 |2dd1f2c999c0d02d2ec Version Fixed In||5.7.5 --- Comment #2 from Lamarque V. Souza --- Git commit 4eede9a350e36c84594952dd1f2c999c0d02d2ec by Lamarque V. Souza. Committed on 05/09/2016 at 13:31. Pushed by lvsouza into branch 'Plasma/5.7'. Export tls-auth tag for the other connection types too. FIXED-IN: 5.7.5 M +5-3vpn/openvpn/openvpn.cpp http://commits.kde.org/plasma-nm/4eede9a350e36c84594952dd1f2c999c0d02d2ec -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 365458] [RFE] [OpenVPN] plasma editor doesn't save tls-auth info while exporting vpn profile
https://bugs.kde.org/show_bug.cgi?id=365458 Lamarque V. Souza changed: What|Removed |Added Latest Commit||http://commits.kde.org/plas ||ma-nm/48db82bc5b5801eeb7cbb ||ad838cca6460a4afce5 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Lamarque V. Souza --- Git commit 48db82bc5b5801eeb7cbbad838cca6460a4afce5 by Lamarque V. Souza. Committed on 05/09/2016 at 13:25. Pushed by lvsouza into branch 'master'. Export tls-auth tag for the other connection types too. M +5-3vpn/openvpn/openvpn.cpp http://commits.kde.org/plasma-nm/48db82bc5b5801eeb7cbbad838cca6460a4afce5 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366668] Plasma network manager "hijacks" the launch of apps when connected to a WEP wifi
https://bugs.kde.org/show_bug.cgi?id=38 --- Comment #17 from Lamarque V. Souza --- (In reply to eemantsal from comment #15) > Hi, Lamarque. > > I suppose you probably have many bugs and stuff to take care of, but do you > remember this one is still pending? > Not in a hurry at all, take your time; just wanted to make sure you didn't > miss it. > > Regards. Hi, can you please try reproducing the problem, then using the following command and check if the problem still happen? xhost + -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366668] Plasma network manager "hijacks" the launch of apps when connected to a WEP wifi
https://bugs.kde.org/show_bug.cgi?id=38 --- Comment #16 from Lamarque V. Souza --- Hi, I also use Gentoo and but long ago I decided to keep using sysklogd instead of metalog. You can find the metalog's log in /var/log/everything/current. NetworkManager can use dhclient, dhcpcd or its internal dhcp client. I use the internal one because it is stabler for me. If you want to try it add these lines to /etc/NetworkManager/NetworkManager.conf: [main] dhcp=internal and restart NetworkManager NM passes some arguments to the dhcp client which can change its behaviour, so NM and iwconfig can work differently. By the way, why use WEP? It is not secure. Can you still ping Juan-PC when the problem happen? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366668] Plasma network manager "hijacks" the launch of apps when connected to a WEP wifi
https://bugs.kde.org/show_bug.cgi?id=38 --- Comment #13 from Lamarque V. Souza --- Since you do not have the host command installed, the output of the second command is useless. Can you ping your hostname? Like this: $ ping -c 1 Juan-PC NetworkManager does not directly change computer's hostname. The dhcp client does. Let's first try to understand what is causing your problem before messing with xauth and DISPLAY. What is you Linux distribution? I need you to send me NetworkManager's log and the way to retrieve it depends on which distribution you use. If you use one that uses journald you can retrieve it running the following command as root: journalctl -u NetworkManager.service -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366668] Plasma network manager "hijacks" the launch of apps when connected to a WEP wifi
https://bugs.kde.org/show_bug.cgi?id=38 Lamarque V. Souza changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #11 from Lamarque V. Souza --- By what I can see in the logs, somehow the WEP connection is changing your computer's hostname and that is probably breaking Xorg. Your computer should be named Juan-PC (name used in xauth's cookie) but strace shows it is dhcppc4 for the WEP connection. One should always use localhost in xauth's cookies and DISPLAY to prevent that (and for performance reasons too) unless you really need Xorg's network transparency feature. What is the output of the commands below in both working and non-working setup: $ hostname -f $ host $(hostname -f) $ ip addr $ ip route If you create a new connection to the same WEP access point does the problem still happen? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366668] Plasma network manager "hijacks" the launch of apps when connected to a WEP wifi
https://bugs.kde.org/show_bug.cgi?id=38 --- Comment #8 from Lamarque V. Souza --- Please repeat the the command when no problem happen (when using wpa for instance): $ xauth list $ strace -f -o log.txt kate -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366668] Plasma network manager "hijacks" the launch of apps when connected to a WEP wifi
https://bugs.kde.org/show_bug.cgi?id=38 --- Comment #4 from Lamarque V. Souza --- kcalc was just example. I need the log.txt file that strace command created. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366668] Plasma network manager "hijacks" the launch of apps when connected to a WEP wifi
https://bugs.kde.org/show_bug.cgi?id=38 --- Comment #1 from Lamarque V. Souza --- What is the output of the command below? $ xauth list Run the following command and send me the log.txt file that it will create: $ strace -f -o log.txt kcalc -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366164] Plasmashell crash when plasma-nm applet exists trying to connect to a VPN
https://bugs.kde.org/show_bug.cgi?id=366164 Lamarque V. Souza changed: What|Removed |Added Latest Commit|http://commits.kde.org/plas |http://commits.kde.org/plas |ma-nm/669c25e2153c64733ed6f |ma-nm/e6e341a5c2c1bc9292e1e |64c9600aa182c0eb156 |67603ea52795e33fe8a --- Comment #10 from Lamarque V. Souza --- Git commit e6e341a5c2c1bc9292e1e67603ea52795e33fe8a by Lamarque V. Souza. Committed on 28/07/2016 at 13:20. Pushed by lvsouza into branch 'Plasma/5.7'. Fix crash when activating VPN connection. std::sort() expects the lambda to return true if left is less than right, but it returns true when they are equal too. According to this [1] that can lead to an unsorted array internally and that can lead to a crash like this one. [1] http://stackoverflow.com/questions/7767998/should-stdsort-work-with-lambda-function-in-c0x-c11 M +1-1libs/declarative/networkstatus.cpp http://commits.kde.org/plasma-nm/e6e341a5c2c1bc9292e1e67603ea52795e33fe8a -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 362175] Can't create pppoe connection using KNetworkManager
https://bugs.kde.org/show_bug.cgi?id=362175 Lamarque V. Souza changed: What|Removed |Added Latest Commit|http://commits.kde.org/plas |http://commits.kde.org/plas |ma-nm/31b7547ce99281e8de5eb |ma-nm/ad421d63cdeb9751dfd4f |457fd36b924b53bcac0 |411e6c114a703b9e3e9 --- Comment #5 from Lamarque V. Souza --- Git commit ad421d63cdeb9751dfd4f411e6c114a703b9e3e9 by Lamarque V. Souza. Committed on 28/07/2016 at 13:20. Pushed by lvsouza into branch 'Plasma/5.7'. Fix data validation when creating new pppoe connections. FIXED-IN: 5.7.3 M +3-1libs/editor/settings/pppoewidget.cpp M +5-1libs/editor/settings/ui/pppoe.ui http://commits.kde.org/plasma-nm/ad421d63cdeb9751dfd4f411e6c114a703b9e3e9 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 362175] Can't create pppoe connection using KNetworkManager
https://bugs.kde.org/show_bug.cgi?id=362175 Lamarque V. Souza changed: What|Removed |Added Version Fixed In|5.6.4 |5.7.3 Latest Commit|http://commits.kde.org/plas |http://commits.kde.org/plas |ma-nm/c2be0336226cf27263ed2 |ma-nm/31b7547ce99281e8de5eb |34f69cddd3b5214c267 |457fd36b924b53bcac0 --- Comment #4 from Lamarque V. Souza --- Git commit 31b7547ce99281e8de5eb457fd36b924b53bcac0 by Lamarque V. Souza. Committed on 28/07/2016 at 12:11. Pushed by lvsouza into branch 'master'. Fix data validation when creating new pppoe connections. FIXED-IN: 5.7.3 M +3-1libs/editor/settings/pppoewidget.cpp M +5-1libs/editor/settings/ui/pppoe.ui http://commits.kde.org/plasma-nm/31b7547ce99281e8de5eb457fd36b924b53bcac0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366164] Plasmashell crash when plasma-nm applet exists trying to connect to a VPN
https://bugs.kde.org/show_bug.cgi?id=366164 Lamarque V. Souza changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/plas ||ma-nm/669c25e2153c64733ed6f ||64c9600aa182c0eb156 --- Comment #9 from Lamarque V. Souza --- Git commit 669c25e2153c64733ed6f64c9600aa182c0eb156 by Lamarque V. Souza. Committed on 28/07/2016 at 11:57. Pushed by lvsouza into branch 'master'. Fix crash when activating VPN connection. std::sort() expects the lambda to return true if left is less than right, but it returns true when they are equal too. According to this [1] that can lead to an unsorted array internally and that can lead to a crash like this one. [1] http://stackoverflow.com/questions/7767998/should-stdsort-work-with-lambda-function-in-c0x-c11 M +1-1libs/declarative/networkstatus.cpp http://commits.kde.org/plasma-nm/669c25e2153c64733ed6f64c9600aa182c0eb156 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366164] Plasmashell crash when plasma-nm applet exists trying to connect to a VPN
https://bugs.kde.org/show_bug.cgi?id=366164 --- Comment #5 from Lamarque V. Souza --- Hmmm std::sort() expects the lambda to return true if left is less than right, but it returns true when they are equal too. According to this [1] that can lead to an unsorted array internally and that can lead to a crash like this one. Can you recompile the lamba to use < instead of <= and test if it solves your problem? [1] http://stackoverflow.com/questions/7767998/should-stdsort-work-with-lambda-function-in-c0x-c11 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366164] Plasmashell crash when plasma-nm applet exists trying to connect to a VPN
https://bugs.kde.org/show_bug.cgi?id=366164 Lamarque V. Souza changed: What|Removed |Added CC||lamar...@kde.org --- Comment #3 from Lamarque V. Souza --- Do you know the compiler version used to compile Plasma NM? That can be a compiler bug. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 --- Comment #151 from Lamarque V. Souza --- (In reply to whites11 from comment #150) > (In reply to Lamarque V. Souza from comment #149) > > (In reply to whites11 from comment #148) > > > anyway I still see no backtrace. > > > Could you help me using gdb directly without coredumpctl? > > > > In konsole: > > > > $ kquitapp5 plasmashell > > $ gdb plasmashell > > gdb> run > > Thanks. > this is a (kind of) backtrace I got from the above procedure: > > Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault. > 0x7fff39443179 in NetworkStatus:: Ptr&)>::operator() (__closure=, right=..., left=...) > at > /home/whites/Downloads/plasma-nm/src/plasma-nm-5.7.2/libs/declarative/ > networkstatus.cpp:168 > 168 return > NetworkStatus::connectionTypeToSortedType(left->type()) <= > NetworkStatus::connectionTypeToSortedType(right->type()); This is definitely a different bug than this one. Please open a different bug report to continue this conversation there. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 --- Comment #149 from Lamarque V. Souza --- (In reply to whites11 from comment #148) > anyway I still see no backtrace. > Could you help me using gdb directly without coredumpctl? In konsole: $ kquitapp5 plasmashell $ gdb plasmashell gdb> run -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 --- Comment #145 from Lamarque V. Souza --- (In reply to whites11 from comment #144) > I recompiled plasma-desktop and plasma-nm with debug enabled but I must have > done something wrong because I cannot produce a significative backtrace. > If you guide me I can reproduce the problem very precisely to get the > backtrace. The assert triggered here is in QtDeclarative, so you must load Qt's symbols to get a good backtrace. Have you tried this? https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces > Stack trace of thread 19230: > #0 0x7fe55ce10179 operator() > (/usr/lib/qt/qml/org/kde/plasma/networkmanagement/libplasmanm_qmlplugins.so) This indicates a problem in an operator() function. I do not recall any operator() in the backtraces about this bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 362736] Compile vs. runtime symbols discrepancy
https://bugs.kde.org/show_bug.cgi?id=362736 Lamarque V. Souza changed: What|Removed |Added Latest Commit|http://commits.kde.org/netw |http://commits.kde.org/netw |orkmanager-qt/751f79ea7b054 |orkmanager-qt/bb8f19e961751 |c2fa7d5c1e7d996b70198e2dcc9 |1c4fff449af1daa563c16dd1e7d --- Comment #9 from Lamarque V. Souza --- Git commit bb8f19e9617511c4fff449af1daa563c16dd1e7d by Lamarque V. Souza. Committed on 02/07/2016 at 10:08. Pushed by lvsouza into branch 'master'. Fix unit test. Wimax support was removed in NM 1.2.0. M +2-2src/manager.cpp http://commits.kde.org/networkmanager-qt/bb8f19e9617511c4fff449af1daa563c16dd1e7d -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 362736] Compile vs. runtime symbols discrepancy
https://bugs.kde.org/show_bug.cgi?id=362736 Lamarque V. Souza changed: What|Removed |Added Version Fixed In||5.24 Latest Commit||http://commits.kde.org/netw ||orkmanager-qt/751f79ea7b054 ||c2fa7d5c1e7d996b70198e2dcc9 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #8 from Lamarque V. Souza --- Git commit 751f79ea7b054c2fa7d5c1e7d996b70198e2dcc9 by Lamarque V. Souza, on behalf of Palo Kisa. Committed on 19/06/2016 at 20:03. Pushed by lvsouza into branch 'master'. Make network manager version checks in runtime (to avoid compile vs. run-time discrepancies). FIXED-IN: 5.24 REVIEW: 128093 M +1-1CMakeLists.txt M +18 -35 src/CMakeLists.txt M +3-9src/accesspoint.cpp M +2-4src/accesspoint.h M +0-2src/accesspoint_p.h M +0-19 src/activeconnection.cpp M +0-4src/activeconnection.h M +0-2src/activeconnection_p.h M +5-10 src/connection.cpp M +1-8src/connection.h M +0-2src/connection_p.h M +12 -37 src/device.cpp M +13 -28 src/device.h M +0-6src/device_p.h M +116 -134 src/ipconfig.cpp M +2-6src/ipconfig.h M +40 -72 src/manager.cpp M +39 -30 src/manager.h M +6-10 src/manager_p.h M +4-32 src/settings.cpp M +0-4src/settings.h M +5-16 src/settings/bondsetting.cpp M +1-1src/settings/bondsetting.h M +2-16 src/settings/bridgesetting.cpp M +24 -73 src/settings/connectionsettings.cpp M +0-10 src/settings/connectionsettings.h M +0-6src/settings/connectionsettings_p.h M +6-29 src/settings/gsmsetting.cpp M +2-2src/settings/gsmsetting.h M +0-12 src/settings/infinibandsetting.cpp M +0-2src/settings/infinibandsetting.h M +0-2src/settings/infinibandsetting_p.h M +0-6src/settings/setting.cpp M +6-16 src/settings/teamsetting.cpp M +1-1src/settings/teamsetting.h M +9-2src/settings/tunsetting.cpp M +5-16 src/settings/vlansetting.cpp M +1-1src/settings/vlansetting.h M +5-16 src/settings/wirelesssetting.cpp M +1-0src/settings/wirelesssetting.h M +0-7src/settings_p.h M +9-9src/vlandevice.cpp M +2-4src/vlandevice.h M +0-2src/vlandevice_p.h M +0-14 src/wimaxdevice.cpp M +0-15 src/wirelessdevice.cpp M +1-2src/wirelessdevice.h http://commits.kde.org/networkmanager-qt/751f79ea7b054c2fa7d5c1e7d996b70198e2dcc9 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 Lamarque V. Souza changed: What|Removed |Added Latest Commit||http://commits.kde.org/plas ||ma-nm/ee14918070204deabcf48 ||a669edf97a427f1d0f2 Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #131 from Lamarque V. Souza --- Git commit ee14918070204deabcf48a669edf97a427f1d0f2 by Lamarque V. Souza. Committed on 15/06/2016 at 18:08. Pushed by lvsouza into branch 'master'. Reset the whole model instead of emitting dataChanged() for each item. Emitting several dataChanged() in a row, without going back to Qt's event loop in between seems to cause reentrancy problems in the QML delegates connected to this model. Upstream version of our bug #346118: https://bugreports.qt.io/browse/QTBUG-53677 Tentative patch to fix the bug above: https://codereview.qt-project.org/#/c/160884/ M +9-3libs/models/networkmodel.cpp http://commits.kde.org/plasma-nm/ee14918070204deabcf48a669edf97a427f1d0f2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 --- Comment #121 from Lamarque V. Souza --- (In reply to Diego from comment #120) > (In reply to Lamarque V. Souza from comment #119) > > > > This bug entry is about the crash when changing MTU value. You have to open > > another bug report about other bugs. > > Weird thing is that: > - VPN crash reports get marked (for example by Jan Grulich) as a duplicate > of this bug > - you previous patch against qtdeclarative fixed the problem with VPN too. > > So there's probably no need to open separate reports yet (or we can just > "unduplicate" one of the VPN ones). If the vpn crash has simular backtrace as this one then they are the same bug and there is no need to open a new bug report. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 --- Comment #119 from Lamarque V. Souza --- (In reply to Roland from comment #118) > (In reply to Lamarque V. Souza from comment #115) > > Created attachment 99393 [details] > > Fix problem without changing libQt5Qml. > > > > Can someone test this patch against Plasma NM? You must revert the patch to > > qtdeclarative. This is another attempt to fix the crash, it works for me. > > The issue with the other patch is that it probably fixes a symptom instead > > of the real problem: https://codereview.qt-project.org/#/c/160884/ > > This patch refelcts the plasama-nm crashes when connecting to a vpn? > > How do i apply this patch? This matter is new for me. This bug entry is about the crash when changing MTU value. You have to open another bug report about other bugs. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 --- Comment #115 from Lamarque V. Souza --- Created attachment 99393 --> https://bugs.kde.org/attachment.cgi?id=99393&action=edit Fix problem without changing libQt5Qml. Can someone test this patch against Plasma NM? You must revert the patch to qtdeclarative. This is another attempt to fix the crash, it works for me. The issue with the other patch is that it probably fixes a symptom instead of the real problem: https://codereview.qt-project.org/#/c/160884/ -- You are receiving this mail because: You are watching all bug changes.
[solid] [Bug 330720] kded4 - powerdevil - dbus - missing xmlns in introspect xml markup
https://bugs.kde.org/show_bug.cgi?id=330720 Lamarque V. Souza changed: What|Removed |Added CC||lamar...@kde.org Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Lamarque V. Souza --- I cannot reproduce this in Plasma NM 5.6.90 (Frameworks 5 version). I looked at the xml file used to create that interface and it contains the tp:docstring namespace, so it should be working, although I was not able to use the dbus-send command to retrieve the introspection. Reopen if you think this is still a problem. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 --- Comment #108 from Lamarque V. Souza --- Created attachment 99222 --> https://bugs.kde.org/attachment.cgi?id=99222&action=edit Fix crash in libQt5Qml This patch against qtdeclarative-opensource-src-5.5.1 fixes the problem for me. Somehow the items QList shrinks from 12 items to 10 items during the for loop, which causes the crash. Please test this patch and report if it fixes the problem for you too. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 362175] Can't create pppoe connection using KNetworkManager
https://bugs.kde.org/show_bug.cgi?id=362175 Lamarque V. Souza changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/plas ||ma-nm/c2be0336226cf27263ed2 ||34f69cddd3b5214c267 Version Fixed In||5.6.4 --- Comment #2 from Lamarque V. Souza --- Git commit c2be0336226cf27263ed234f69cddd3b5214c267 by Lamarque V. Souza. Committed on 24/04/2016 at 13:23. Pushed by lvsouza into branch 'Plasma/5.6'. Fix data validation when creating new pppoe connections. FIXED-IN: 5.6.4 M +3-1libs/editor/settings/pppoewidget.cpp M +5-1libs/editor/settings/ui/pppoe.ui http://commits.kde.org/plasma-nm/c2be0336226cf27263ed234f69cddd3b5214c267 -- You are receiving this mail because: You are watching all bug changes.
[Network Management] [Bug 307869] Network Management can't handle VLANs
https://bugs.kde.org/show_bug.cgi?id=307869 Lamarque V. Souza changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||0.9.3.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-modemmanager-qt] [Bug 358261] SMS messages list is not update when calling ModemManager::ModemMessaging::createMessage
https://bugs.kde.org/show_bug.cgi?id=358261 --- Comment #1 from Lamarque V. Souza --- Hi, MMQt API is assynchronous and MMQt needs to receive signals from ModemManager to update the message list. That is probably not happening because you are doing everything in synchronous mode. Try adding the line below after *before* step 7 and check if your example works: // Include QCoreApplication if compiler complains about qApp not defined. qApp->processEvents(); That will make Qt process any pending event (like ModemManager's signal to update the message list). If that works then you need to update your code to work in asynchronous mode. Using processEvent() must be avoided since it is a costly method call. -- You are receiving this mail because: You are watching all bug changes.
