[Powerdevil] [Bug 340892] System Settings's Power management complains about power management service

[Germano Massullo]

https://bugs.kde.org/show_bug.cgi?id=340892

--- Comment #2 from Germano Massullo  ---
Created attachment 89556
  --> https://bugs.kde.org/attachment.cgi?id=89556&action=edit
Background services

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 340892] New: System Settings's Power management complains about power management service

[Germano Massullo]

https://bugs.kde.org/show_bug.cgi?id=340892

Bug ID: 340892
   Summary: System Settings's Power management complains about
power management service
   Product: Powerdevil
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-devel@kde.org
  Reporter: germano.massu...@gmail.com

Entering into System Settings->Power management
you will get an error message about power management service not running.
I checked the status of power management service inside System
Settings->Background serices and it is running.
System: Fedora 21 with Dvratil's repository (
https://copr.fedoraproject.org/coprs/dvratil/plasma-5/ ) running in a
VirtualBox virtual machine

Reproducible: Always

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 340892] System Settings's Power management complains about power management service

[Germano Massullo]

https://bugs.kde.org/show_bug.cgi?id=340892

--- Comment #1 from Germano Massullo  ---
Created attachment 89555
  --> https://bugs.kde.org/attachment.cgi?id=89555&action=edit
power manager options

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 340892] System Settings's Power management complains about power management service

[Germano Massullo]

https://bugs.kde.org/show_bug.cgi?id=340892

Germano Massullo  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #7 from Germano Massullo  ---
The bug has been fixed (KDE 5.8.0)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Plasmate] [2015-08-01] Automatic crash report generated by DrKonqi

[Germano Massullo]

Application: plasmate (1.0)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 4.1.3-200.fc22.x86_64 x86_64
Distribution: "Fedora release 22 (Twenty Two)"

-- Information about the crash:


-- Backtrace:
Application: Plasmate (plasmate), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
81 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7fe7876e3900 (LWP 21894))]

Thread 2 (Thread 0x7fe76b90a700 (LWP 21965)):
#0 0x0038f300c540 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1 0x00390c39db5a in QTWTF::TCMalloc_PageHeap::scavengerThread() ()
at /lib64/libQtScript.so.4
#2 0x00390c39db89 in () at /lib64/libQtScript.so.4
#3 0x0038f3007555 in start_thread (arg=0x7fe76b90a700) at
pthread_create.c:333
#4 0x0038f2902b9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fe7876e3900 (LWP 21894)):
[KCrash Handler]
#6 0x7fe76a0ec734 in
KateBuffer::computeFoldingRangeForStartLine(int) () at
/lib64/libkatepartinterfaces.so.4
#7 0x7fe76a182836 in KateIconBorder::showBlock() () at
/lib64/libkatepartinterfaces.so.4
#8 0x0038fcd9e0c0 in QMetaObject::activate(QObject*, QMetaObject
const*, int, void**) () at /lib64/libQtCore.so.4
#9 0x0038fcda3d33 in QObject::event(QEvent*) () at /lib64/libQtCore.so.4
#10 0x0038fd7c43ac in QApplicationPrivate::notify_helper(QObject*,
QEvent*) () at /lib64/libQtGui.so.4
#11 0x0038fd7cb206 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQtGui.so.4
#12 0x003907a5505a in KApplication::notify(QObject*, QEvent*) () at
/lib64/libkdeui.so.5
#13 0x0038fcd89f1d in QCoreApplication::notifyInternal(QObject*,
QEvent*) () at /lib64/libQtCore.so.4
#14 0x0038fcdbc9a0 in QTimerInfoList::activateTimers() () at
/lib64/libQtCore.so.4
#15 0x0038fcdb9b49 in idleTimerSourceDispatch(_GSource*, int
(*)(void*), void*) () at /lib64/libQtCore.so.4
#16 0x0038f4849a8a in g_main_context_dispatch (context=0x15eb1a0) at
gmain.c:3122
#17 0x0038f4849a8a in g_main_context_dispatch
(context=context@entry=0x15eb1a0) at gmain.c:3737
#18 0x0038f4849e20 in g_main_context_iterate
(context=context@entry=0x15eb1a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3808
#19 0x0038f4849ecc in g_main_context_iteration (context=0x15eb1a0,
may_block=1) at gmain.c:3869
#20 0x0038fcdba4ce in
QEventDispatcherGlib::processEvents(QFlags)
() at /lib64/libQtCore.so.4
#21 0x0038fd86a626 in
QGuiEventDispatcherGlib::processEvents(QFlags)
() at /lib64/libQtGui.so.4
#22 0x0038fcd88791 in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#23 0x0038fcd88b05 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#24 0x0038fcd8e6a9 in QCoreApplication::exec() () at
/lib64/libQtCore.so.4
#25 0x004250d1 in main(int, char**) (argc=1,
argv=0x7ffefcfdc0b8) at /usr/src/debug/plasmate-1.0/plasmate/main.cpp:56

___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[kio-extras] [Bug 366638] [16.04] sftp stuck operations. Can operate only if reopening Dolphin

[Germano Massullo]

https://bugs.kde.org/show_bug.cgi?id=366638

--- Comment #5 from Germano Massullo  ---
Confirming on 16.08.1 / 5.26.0 / Plasma 5.7.5

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Wayland] plasma crashes and cannot attach gdb to kwin_wayland

[Germano Massullo]

Hi there, I am testing Plasma 5.9.4 on Wayland (on Fedora 25) and I am
filling various bugreports.
If I run plasmashell from bash, when it crashes I obtain message

so I started trying to attach gdb to kwin_wayland process. I followed
https://community.kde.org/KWin/Debugging
and I tried to run
$ gdb --pid 1450  2>&1 | tee kwin.gdb
but I still obtained message
ptrace: Operation not permitted.

What can I do to retrieve useful informations?
Thank you

Re: [Wayland] plasma crashes and cannot attach gdb to kwin_wayland

[Germano Massullo]

Il 13/04/2017 13:12, David Edmundson ha scritto:
> ​"echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope"  (or run GDB
> as root)
>
> David
# cat /proc/sys/kernel/yama/ptrace_scope
0
so it seems that ptrace_scope is already setted to 0

Re: [Wayland] plasma crashes and cannot attach gdb to kwin_wayland

[Germano Massullo]

Il 13/04/2017 13:12, David Edmundson ha scritto:
> ​"echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope"  (or run GDB
> as root)
>
> David
As root in tty3 I attached GDB to kwin_wayland and as soon I got back to
the graphical session, the system got stuck and I could not neither
return back to tty3, so I had to use Magic SysRq key to restart the system.
The wiki says to try to use SSH, but it would be useless too since I am
not able to use the graphical session if kwin_wayland is attached to GDB

Re: [Wayland] plasma crashes and cannot attach gdb to kwin_wayland

[Germano Massullo]

Il 13/04/2017 16:49, Martin Gräßlin ha scritto:
> Am 2017-04-13 16:08, schrieb Germano Massullo:
>> Il 13/04/2017 13:12, David Edmundson ha scritto:
>>> ​"echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope"  (or run GDB
>>> as root)
>>>
>>> David
>> As root in tty3 I attached GDB to kwin_wayland and as soon I got back to
>> the graphical session, the system got stuck and I could not neither
>> return back to tty3, so I had to use Magic SysRq key to restart the
>> system.
>> The wiki says to try to use SSH, but it would be useless too since I am
>> not able to use the graphical session if kwin_wayland is attached to GDB
>
> Of course you need to continue once you attached gdb. I'm not sure
> what you want to achieve but debugging the running display manager on
> the same system - well it's even more impossible than debugging the
> running window manager on X11. I'm working with nested kwin_wayland
> running in gdb to do debugging.
>
> Cheers
> Martin
>

A running from bash Plasma, when it crashes[1], sends a message like
> The Wayland connection broke. Did the Wayland compositor die?
so I was trying to figure out if kwin_wayland crashes too
[1]: https://bugs.kde.org/show_bug.cgi?id=378707

Re: [Wayland] plasma crashes and cannot attach gdb to kwin_wayland

[Germano Massullo]

Il 13/04/2017 18:41, Martin Gräßlin ha scritto:
> Am 2017-04-13 17:19, schrieb Germano Massullo:
>> Il 13/04/2017 16:49, Martin Gräßlin ha scritto:
>>> Am 2017-04-13 16:08, schrieb Germano Massullo:
>>>> Il 13/04/2017 13:12, David Edmundson ha scritto:
>>>>> ​"echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope"  (or run GDB
>>>>> as root)
>>>>>
>>>>> David
>>>> As root in tty3 I attached GDB to kwin_wayland and as soon I got
>>>> back to
>>>> the graphical session, the system got stuck and I could not neither
>>>> return back to tty3, so I had to use Magic SysRq key to restart the
>>>> system.
>>>> The wiki says to try to use SSH, but it would be useless too since
>>>> I am
>>>> not able to use the graphical session if kwin_wayland is attached
>>>> to GDB
>>>
>>> Of course you need to continue once you attached gdb. I'm not sure
>>> what you want to achieve but debugging the running display manager on
>>> the same system - well it's even more impossible than debugging the
>>> running window manager on X11. I'm working with nested kwin_wayland
>>> running in gdb to do debugging.
>>>
>>> Cheers
>>> Martin
>>>
>>
>> A running from bash Plasma, when it crashes[1], sends a message like
>>> The Wayland connection broke. Did the Wayland compositor die?
>> so I was trying to figure out if kwin_wayland crashes too
>> [1]: https://bugs.kde.org/show_bug.cgi?id=378707
>
> I think you are looking at a false positive here. Given the backtrace
> I think the message is a side effect not the cause. If the Wayland
> server had problems everything would die not just Plasma. And it would
> not crash - at least not directly. It could only crash in the cleanup
> handler and that's not the case here.
>
> Cheers
> Martin
>

Mmh ok. Does the bugreport contain anything useful?

[kio-extras] [Bug 366638] [16.04] sftp stuck operations. Can operate only if reopening Dolphin

[Germano Massullo]

https://bugs.kde.org/show_bug.cgi?id=366638

--- Comment #6 from Germano Massullo  ---
Confirming on kio-extras 16.12.3

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 379680] MTP protocol died unexpectedly

[Germano Massullo]

https://bugs.kde.org/show_bug.cgi?id=379680

--- Comment #6 from Germano Massullo  ---
A few logs, while trying to browse a Samsung Galaxy S5

Note: VID and PID have been edited to avoid any privacy problem

$ Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session,
trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
ERROR: Could not close session!
inep: usb_get_endpoint_status(): Device or resource busy
outep: usb_get_endpoint_status(): Device or resource busy
Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session,
trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
ERROR: Could not close session!
inep: usb_get_endpoint_status(): Device or resource busy
outep: usb_get_endpoint_status(): Device or resource busy
ERROR: Could not close session!
Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session,
trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session,
trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
ERROR: Could not close session!
inep: usb_get_endpoint_status(): Device or resource busy
outep: usb_get_endpoint_status(): Device or resource busy
ERROR: Could not close session!
Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
ERROR: Could not close session!
inep: usb_get_endpoint_status(): Device or resource busy
outep: usb_get_endpoint_status(): Device or resource busy
ERROR: Could not close session!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 366638] [16.04] sftp stuck operations. Can operate only if reopening Dolphin

[Germano Massullo]

https://bugs.kde.org/show_bug.cgi?id=366638

--- Comment #7 from Germano Massullo  ---
Is anybody working on this?

-- 
You are receiving this mail because:
You are the assignee for the bug.

Proposal: passing user idle time to systemd-logind

[Germano Massullo]

Hello, I am writing to you to propose the following reasoning, hoping
that it can help making easier (just a bit) third parties development
work on Linux.
I am currently developing BOINC client user idle time detection on
Linux systems (both graphical or tty sessions)
After some studies I started writing a little piece of code that that
is able to print on standard output the user idle time by retrieving
it from systemd-logind IdleSinceHint property (that is exposed on
DBus). By the way I found out that this value was always 0 [1], so I
asked why [2]. I have been told that logind relies on the desktop
environment to pass this information.
Many d.e. expose user idle time to their own DBus path, (i.e.
org.gnome.Mutter.IdleMonitor), so I will be forced to write code that
depends on the specific desktop environment. Since:
1) systemd-logind is just ready for exposing user idle time;
2) for a developer writing code for Linux it would be much easier to
retrieve user idle time from a unique place rather than having to deal
with all various desktop environments;
I would like to ask you what do you think about passing the user idle
time to logind [3] [4] ?

Best regards

[1]: you can try with system console command
$ sleep 2 && gdbus introspect --system --dest org.freedesktop.login1
--object-path /org/freedesktop/login1 | grep IdleSinceHint
[2]: https://lists.freedesktop.org/archives/systemd-devel/2019-May/042726.html
[3]: 
https://www.freedesktop.org/wiki/Software/systemd/writing-desktop-environments/
[4]: https://www.freedesktop.org/wiki/Software/systemd/writing-display-managers/

Volunteer to help multi screen support development

[Germano Massullo]

KDE Plasma has always been my favourite desktop environment since KDE
3. Recently I had the feeling that there may be a lack of resources to
fix some problems [*] of multi screen support. So, when my schedule
allows it, I would like to volunteer to help. I had a short Qt
development experience for work and I am also a Fedora package
maintainer.
I already went through
https://community.kde.org/Get_Involved/development so I would like to
ask you what could I do in practice to help multi screen support
development.

Best regards


[*] for example:
Screens overlapping after screen unlock
https://bugs.kde.org/show_bug.cgi?id=412368

that triggers 404295

"show only application on current screen" shows no applications
https://bugs.kde.org/show_bug.cgi?id=404295

Panel added to the wrong screen
https://bugs.kde.org/show_bug.cgi?id=408060

Plasma on Wayland detects only one screen
https://bugs.kde.org/show_bug.cgi?id=412601

Second screen rotated triggers Ark to appear on primary screen exceeding borders
https://bugs.kde.org/show_bug.cgi?id=412535

Second screen rotated triggers Gwenview to appear on primary screen
exceeding borders
https://bugs.kde.org/show_bug.cgi?id=409454

Second screen rotated triggers Gwenview to appear on primary screen
exceeding borders
https://bugs.kde.org/show_bug.cgi?id=412536

Overlapping screens
https://bugs.kde.org/show_bug.cgi?id=401774

D25062: fix(kded): read rotated output size

[Germano Massullo]

gmassullo added a comment.


  I tested this patch on Plasma 5.17.2 [1] and it fixes
  Screens overlapping after screen lock 

  
  I would like to give a comment about the following KDE bugreports, even if 
they may be not related: I am not yet sure, but I think that it also has fixed
  Second screen rotated triggers Okular to appear on primary screen exceeding 
borders 
  Second screen rotated triggers Gwenview to appear on primary screen exceeding 
borders 
  I will keep testing them.
  
  The following bug instead still happens
  Second screen rotated triggers Ark to appear on primary screen exceeding 
borders 
  
  [1]: https://copr.fedorainfracloud.org/coprs/germano/kscreen

REPOSITORY
  R104 KScreen

REVISION DETAIL
  https://phabricator.kde.org/D25062

To: romangg, #plasma
Cc: gmassullo, plasma-devel, LeGast00n, The-Feren-OS-Dev, jraleigh, 
fbampaloukas, GB_2, ragreen, ZrenBot, ngraham, alexeymin, himcesjf, lesliezhai, 
ali-mohamed, jensreuterberg, abetts, sebas, apol, ahiemstra, mart

[Powerdevil] [Bug 376037] Plasma ignores screen lid action settings

[Germano Massullo]

https://bugs.kde.org/show_bug.cgi?id=376037

Germano Massullo  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #2 from Germano Massullo  ---
I am no longer experiencing the problem

-- 
You are receiving this mail because:
You are the assignee for the bug.