https://bugs.kde.org/show_bug.cgi?id=477673
--- Comment #15 from MikeC ---
I just checked Google Play:
https://play.google.com/store/apps/details?id=org.kde.kdeconnect_tp=en_GB=1
which has:
What's new
1.31
* Allow sharing URLs to disconnected devices, to be opened when they become
available
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #56 from MikeC ---
It would be better to find the correct code for kdeconnect to fix the
incompatibility with the current ssh/sshfs than to downgrade the openssh
version.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=477673
--- Comment #7 from MikeC ---
kdeconnect does make the connection to the phone and the android phone
correctly receives a ping from the linked laptop, and the laptop correctly
receives a ping initiated on the phone. However the sshfs filesystem
https://bugs.kde.org/show_bug.cgi?id=477673
--- Comment #5 from MikeC ---
It looks like some settings were broken by an update, possibly on the Android
phone with the monthly feature system update. I ended up unpairing all laptops
from the phone, clearing the cache and data, uninstalling
https://bugs.kde.org/show_bug.cgi?id=477673
--- Comment #4 from MikeC ---
Created attachment 170877
--> https://bugs.kde.org/attachment.cgi?id=170877=edit
Journal log
This is a complete journal log with attempts to connect to a phone to expose
the filesystem in kdeconnect
--
https://bugs.kde.org/show_bug.cgi?id=477673
MikeC changed:
What|Removed |Added
CC||mike.cloa...@gmail.com
--- Comment #3 from MikeC
https://bugs.kde.org/show_bug.cgi?id=484015
--- Comment #6 from MikeC ---
That is a blocker for me - I won't sensibly be able to choose to run sddm
wayland as the login manager unless the monitor can go into powersave - I hope
that sddm adoption might happen sooner rather than later
https://bugs.kde.org/show_bug.cgi?id=485011
--- Comment #14 from MikeC ---
Created attachment 168282
--> https://bugs.kde.org/attachment.cgi?id=168282=edit
journal that includes lines for logout fail from plasma 6
Journal log including logout fail lines prior to masking the
drkonqi-cored
https://bugs.kde.org/show_bug.cgi?id=485011
--- Comment #4 from MikeC ---
I can also confirm that uninstalling drkonqi and plasma-meta leads to the
logout problem no longer occurring. Hopefully this will allow the underlying
cause of this bug to be fixed so that installing fixed a fixed version
https://bugs.kde.org/show_bug.cgi?id=485011
MikeC changed:
What|Removed |Added
CC||mike.cloa...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=484015
--- Comment #1 from MikeC ---
https://github.com/sddm/sddm/issues/1897 is related
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=484015
Bug ID: 484015
Summary: SDDM Wayland does not go into monitor powersave
timeout with no user logged in
Classification: Plasma
Product: kwin
Version: 6.0.2
Platform: Arch
https://bugs.kde.org/show_bug.cgi?id=483469
--- Comment #3 from MikeC ---
Thank you - I wasn't aware that you can drag the icon directly from the kicker
to the panel at any desired location - that does solve what I would want to do
so this can be marked as solved.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=483469
--- Comment #1 from MikeC ---
I am running Plasma 6 in Wayland though presume that would not affect this
issue, if the desktop was x11
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=483469
Bug ID: 483469
Summary: Right click on launcher only allows Pin to Task
Manager but not Add to Panel
Classification: Plasma
Product: plasmashell
Version: 6.0.1
Platform: Arch
https://bugs.kde.org/show_bug.cgi?id=438478
--- Comment #18 from MikeC ---
This is fixed in 5.23
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443708
--- Comment #27 from MikeC ---
The github commit I referred to is only for the arch package kwin - so I guess
is not an upstream plasma fix - so should that be referred to a separate kde
bug report to see if it can go in at source?
--
You
https://bugs.kde.org/show_bug.cgi?id=443708
--- Comment #26 from MikeC ---
(In reply to Antonio Rojas from comment #23)
> Please open a separate report, that's unrelated to the original crash
> tracked here.
Does your commit at
https://github.com/archlinux/svntogit-packages/commits/pa
https://bugs.kde.org/show_bug.cgi?id=443708
--- Comment #22 from MikeC ---
I can now confirm that on two user accounts where there were additional lines
in the [compositing] section of kwinrc changing the lines to include only two
lines as per:
[Compositing]
GLCore=true
OpenGLIsUnsafe=false
https://bugs.kde.org/show_bug.cgi?id=443708
--- Comment #20 from MikeC ---
By the way on the two machines where there was no problem logging in after the
update that section of the kwinrc file has only the lines:
[Compositing]
GLCore=true
OpenGLIsUnsafe=false
So perhaps removing all other
https://bugs.kde.org/show_bug.cgi?id=443708
--- Comment #19 from MikeC ---
@Ardith Metz thank you. I will certainly move that file aside on another
machine when I update that in a couple of days - it will save quite a bit of
work if that is the only change needed.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=443708
MikeC changed:
What|Removed |Added
CC||mike.cloa...@gmail.com
--- Comment #17 from MikeC
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #14 from MikeC ---
Fixing the android app for kdeconnect seems the most straightforward way to get
this resolved. Hopefully the developers will get that implemented soon. Moving
to more modern and secure key algorithm would make sense, even
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #12 from MikeC ---
OK - I had assumed this came from upstream - presumably the work-around in the
arch packages provides the basis for the upstream source to be fixed if the kde
developers make the same changes to the source files?
--
You
https://bugs.kde.org/show_bug.cgi?id=443155
MikeC changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #9 from MikeC ---
This bug from 2020 is not dissimilar to the current bug
https://bugs.kde.org/show_bug.cgi?id=417787
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #8 from MikeC ---
I had a look at the private key for the connection using the command:
$ openssl pkey -in .config/kdeconnect/privateKey.pem -text
and in the output there is a line:
RSA Private-Key: (2048 bit, 2 primes)
SO
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #7 from MikeC ---
The matter of using the RSA signatures with sha-1 looks like a possible cause
of the issue. Is there a way to get kdeconnect to use an alternative sig to
test that idea?
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #5 from MikeC ---
Also I have tested sshfs with the newest openssh package and it works without
issue, such as making a directory mnt as a mount point and doing:
$ sshfs remotemachine:/home/mike/Documents/ mnt
then enter ssh password
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #3 from MikeC ---
Thank you for comment 1 - I have changed the title to the correct package
involved.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443155
MikeC changed:
What|Removed |Added
Summary|kdeconnect breaks when |kdeconnect breaks when
|openssl
https://bugs.kde.org/show_bug.cgi?id=442967
--- Comment #7 from MikeC ---
I have entered a new report at https://bugs.kde.org/show_bug.cgi?id=443155
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443155
Bug ID: 443155
Summary: kdeconnect breaks when openssl is upgraded to version
8.8p1-1
Product: kdeconnect
Version: unspecified
Platform: Archlinux Packages
OS:
https://bugs.kde.org/show_bug.cgi?id=442967
--- Comment #6 from MikeC ---
The original report concerns kdeconnect not transferring files to an android
phone in Ubuntu - which does not have the latest version of openssl, but the
later report refers to a working system in Arch Linux where
https://bugs.kde.org/show_bug.cgi?id=442967
MikeC changed:
What|Removed |Added
CC||mike.cloa...@gmail.com
--- Comment #3 from MikeC
https://bugs.kde.org/show_bug.cgi?id=438874
--- Comment #33 from MikeC ---
This has been running a couple of months - it would be nice if this could now
be worked towards a patch to fix it. It seems not to be taken by a developer
yet.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=356225
MikeC changed:
What|Removed |Added
CC|mike.cloa...@gmail.com |
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=440602
--- Comment #6 from MikeC ---
I have found the solution to this issue in my case. The problem was that the
nftables firewall did not flush the firewall rules when the nftables service
was stopped. A recent change to nft meant that previous behaviour
https://bugs.kde.org/show_bug.cgi?id=440202
--- Comment #10 from MikeC ---
I have found the solution to this issue in my case. The problem was that the
nftables firewall did not flush the firewall rules when the nftables service
was stopped. A recent change to nft meant that previous
https://bugs.kde.org/show_bug.cgi?id=440688
MikeC changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=440202
--- Comment #9 from MikeC ---
I created a new bug https://bugs.kde.org/show_bug.cgi?id=440688
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=440602
--- Comment #5 from MikeC ---
I created a new bug https://bugs.kde.org/show_bug.cgi?id=440688
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=440688
Bug ID: 440688
Summary: kdeconnect needs to have updated connection code for
QT5
Product: kdeconnect
Version: unspecified
Platform: Archlinux Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=440602
--- Comment #4 from MikeC ---
The system journal on my laptop has multiple repeated lines with the same
content:
Aug 07 12:43:30 lenovo1 kdeconnect-app[4768]:
qrc:/kdeconnect/qml/PluginChecker.qml:20:47: QML Connections: Implicitly
defined onFoo
https://bugs.kde.org/show_bug.cgi?id=440202
--- Comment #8 from MikeC ---
The stack overflow link should have been
https://stackoverflow.com/questions/62297192/qml-connections-implicitly-defined-onfoo-properties-in-connections-are-deprecat
in my previous comment.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=440202
--- Comment #7 from MikeC ---
The system journal on my laptop has multiple repeated lines with the same
content:
Aug 07 12:43:30 lenovo1 kdeconnect-app[4768]:
qrc:/kdeconnect/qml/PluginChecker.qml:20:47: QML Connections: Implicitly
defined onFoo
https://bugs.kde.org/show_bug.cgi?id=438874
--- Comment #22 from MikeC ---
OK so it looks like it needs fixing in the plasma packages.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=440602
--- Comment #3 from MikeC ---
I believe it is kdeconnect on my laptop running in the plasma desktop - my
version is the latest on arch linux - kdeconnect 21.04.3-1 (that version was
installed as an update on July 7 2021)
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=440202
--- Comment #5 from MikeC ---
Yes I believe it is kdeconnect on my laptop running in the plasma desktop - my
version is the latest on arch linux - kdeconnect 21.04.3-1 (that version was
installed as an update on July 7 2021)
My network setup is a LAN
https://bugs.kde.org/show_bug.cgi?id=440602
--- Comment #2 from MikeC ---
My plasma version is plasma-desktop 5.22.4-1
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=440202
--- Comment #3 from MikeC ---
My plasma version is plasma-desktop 5.22.4-1
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=440602
MikeC changed:
What|Removed |Added
CC||mike.cloa...@gmail.com
--- Comment #1 from MikeC
https://bugs.kde.org/show_bug.cgi?id=440202
MikeC changed:
What|Removed |Added
CC||mike.cloa...@gmail.com
--- Comment #2 from MikeC
https://bugs.kde.org/show_bug.cgi?id=438874
--- Comment #18 from MikeC ---
I wonder if this is related: https://github.com/indilib/indi/pull/1521
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438478
--- Comment #14 from MikeC ---
I was wrong - the bug is still there - but seems to depend on the partition
structure of the drives being plugged in to usb. With two ssd usb drives, both
with a single ext4 partition, the first is offered a mount via
https://bugs.kde.org/show_bug.cgi?id=438874
--- Comment #17 from MikeC ---
I went back to trying two external usb ssds that I had used previously for the
test - each of those has a single ext4 partition - and the original problem is
still there in that once one has been mounted, dismounted
https://bugs.kde.org/show_bug.cgi?id=438478
--- Comment #12 from MikeC ---
With the update to kde-applications 21.04.3-1 this seems to be fixed.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438874
--- Comment #15 from MikeC ---
With the update to kde-applications 21.04.3-1 this seems to be fixed.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438874
--- Comment #14 from MikeC ---
Not fixed in plasma 5.22.3
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438478
--- Comment #11 from MikeC ---
This seems related to https://bugs.kde.org/show_bug.cgi?id=438874
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438874
MikeC changed:
What|Removed |Added
CC||mike.cloa...@gmail.com
--- Comment #12 from MikeC
https://bugs.kde.org/show_bug.cgi?id=438478
--- Comment #10 from MikeC ---
Prior to a commit to fix this bug, is there a work around that will allow more
than one external drive to be mounted successively during a single login
session? There are scenarios where it is highly desirable to be able
https://bugs.kde.org/show_bug.cgi?id=438478
--- Comment #9 from MikeC ---
In my comment concerning usb drives - yes, it was selected to be unmounted,
then physically disconnected, and then physically connected back in - no
pop-up offered a mount, and indeed going to the Disks and Devices option
https://bugs.kde.org/show_bug.cgi?id=438478
--- Comment #5 from MikeC ---
In my case this bug appeared with Plasma 5.22.1-1 Frameworks 5.83.0-1 in Arch
Linux.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438478
MikeC changed:
What|Removed |Added
CC||mike.cloa...@gmail.com
--- Comment #4 from MikeC
https://bugs.kde.org/show_bug.cgi?id=425992
MikeC changed:
What|Removed |Added
CC|mike.cloa...@gmail.com |
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=425992
--- Comment #44 from MikeC ---
The other applet I referred to in the previous comment is the Netspeed Widget
1.9 - that works fine in displaying network speeds. I am not using Neon but
running plasma in arch linux and that was working fine both before
https://bugs.kde.org/show_bug.cgi?id=425992
--- Comment #43 from MikeC ---
I am running the separate applet called the Netspeed applet - and it displays
the download and upload speeds numerically, continuously and correctly, but
without a graph of the values. That works consistently without any
https://bugs.kde.org/show_bug.cgi?id=425992
--- Comment #41 from MikeC ---
If you run ksysguard I believe that it loads the process /usr/bin/ksystemstats
if you want to check if that makes a difference to being able to access the
network data?
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=425992
--- Comment #33 from MikeC ---
I note that in Arch Linux I have now added the Netspeed Widget, and it shoes
the correct download and upload speeds without any problem at all, where the
Network Monitor applet fails to do so completely on my Arch
https://bugs.kde.org/show_bug.cgi?id=425992
--- Comment #29 from MikeC ---
Which update versions give the working speed monitor applet? Was it an update
to plasma or to this specific applet?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=425992
--- Comment #24 from MikeC ---
Another data point - I added the hardware sensors -> k10temp and selected my
CPU temp values - they load and display without problems, so it seems that it
is the network interfaces that are not available to be loa
https://bugs.kde.org/show_bug.cgi?id=425992
--- Comment #23 from MikeC ---
Is there any chance that this is actually a bug in ksysguard? The failure to
execute ksystemstats could be due to a bug in the libksysguard package? Is
there a way to debug this?
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=425992
--- Comment #22 from MikeC ---
If it is any help I ran the konsole command:
plasmaengineexplorer
and in the GUI that opens selected "Network" and clicked "Request source" and
then in the search bar "wlan0" - and then
https://bugs.kde.org/show_bug.cgi?id=425992
--- Comment #20 from MikeC ---
The output of the iwd status on my laptop is (with mac address obscured)
$ sudo systemctl status iwd
● iwd.service - Wireless service
Loaded: loaded (/usr/lib/systemd/system/iwd.service; enabled; vendor
preset
https://bugs.kde.org/show_bug.cgi?id=425992
--- Comment #19 from MikeC ---
I don't know if it helps but on the laptop I am working on at the moment the
network interface is wlan0, which is working without any problems, and the send
and the receive error rate is zero. ifconfig shows all normal
https://bugs.kde.org/show_bug.cgi?id=425992
--- Comment #18 from MikeC ---
On arch linux on m systems I do not use NetworkManager. The wireless is iwd and
I use systemd-networkd for networking. If I go into the applet configuration
and select Sensors Details Then click Sensors -> All Netw
https://bugs.kde.org/show_bug.cgi?id=425992
--- Comment #11 from MikeC ---
On my arch linux systems the two commands as follows both seem to hang with no
output and I have to use ctrl c to kill them:
[mike@lenovo2 ~]$ kstatsviewer network/all/download
^C
[mike@lenovo2 ~]$ kstatsviewer network
https://bugs.kde.org/show_bug.cgi?id=427693
MikeC changed:
What|Removed |Added
Summary|System Minitor Sensor 1.0 |System Monitor Sensor 1.0
|does
https://bugs.kde.org/show_bug.cgi?id=427693
Bug ID: 427693
Summary: System Minitor Sensor 1.0 does not retain interfaces
after logout in plasma 5.20
Product: plasmashell
Version: master
Platform: Archlinux Packages
https://bugs.kde.org/show_bug.cgi?id=420549
MikeC changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=420549
--- Comment #7 from MikeC ---
The workaround in comment #4 creating a soft link for ktp_integration_module.so
does resolve the problem for me also. Perhaps it is simply a typo in the
source code that results in this issue?
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=420549
--- Comment #2 from MikeC ---
Yes I have the analogous entry in my log:
$ sudo journalctl -b -1 | grep KdedIntegrationModule
Apr 24 15:46:51 home1 dbus-daemon[583]: [session uid=1000 pid=583] Activating
service name
https://bugs.kde.org/show_bug.cgi?id=420549
Bug ID: 420549
Summary: Telepathy-kde 20.04 causes long delay to plasma login
completion
Product: telepathy
Version: 20.04
Platform: Archlinux Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=419991
Bug ID: 419991
Summary: bash shortcut ctrl-B fails for konsole
Product: konsole
Version: 19.12.3
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=391381
Bug ID: 391381
Summary: Plugging in usb drive gives malformed url from device
notifer
Product: plasmashell
Version: 5.12.2
Platform: Archlinux Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=383976
MikeC <mike.cloa...@gmail.com> changed:
What|Removed |Added
CC||mike.cloa...@gma
https://bugs.kde.org/show_bug.cgi?id=357633
--- Comment #4 from MikeC <mike.cloa...@gmail.com> ---
Apologies for the noise
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357633
--- Comment #3 from MikeC <mike.cloa...@gmail.com> ---
Sorry - my last comment related to a network download widget and not a CPU
widget - so please ignore my last comment #2 - your are right that for CPU load
0 to 100 is perfectly sensible.
-
https://bugs.kde.org/show_bug.cgi?id=357633
--- Comment #2 from MikeC <mike.cloa...@gmail.com> ---
If the plot is scaled to the highest point in the current range then 0 to 100
does indeed make sense - but if say there is a period of a few seconds when the
download speed was say
https://bugs.kde.org/show_bug.cgi?id=367822
--- Comment #8 from MikeC <mike.cloa...@gmail.com> ---
I have finally been able to resolve this problem. It turned out that way back
in the history of my machine when I originally set it up, I had used a DVI
monitor, and then a few days later p
https://bugs.kde.org/show_bug.cgi?id=367828
--- Comment #21 from MikeC <mike.cloa...@gmail.com> ---
I have finally been able to resolve this problem. It turned out that way back
in the history of my machine when I originally set it up, I had used a DVI
monitor, and then a few days later p
https://bugs.kde.org/show_bug.cgi?id=367828
--- Comment #20 from MikeC <mike.cloa...@gmail.com> ---
Created attachment 101164
--> https://bugs.kde.org/attachment.cgi?id=101164=edit
kwin support info with the added xorg config to ignore the non-existent eDP1
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=367828
--- Comment #19 from MikeC <mike.cloa...@gmail.com> ---
Created attachment 101163
--> https://bugs.kde.org/attachment.cgi?id=101163=edit
xrandr with the added xorg config to ignore the non-existent eDP1 monitor
--
You are receiving this mai
https://bugs.kde.org/show_bug.cgi?id=367828
--- Comment #18 from MikeC <mike.cloa...@gmail.com> ---
I tried to add in some lines to my xorg config to prevent it detecting the
non-existent eDP1 monitor by using:
Section "Monitor"
Identifier "
https://bugs.kde.org/show_bug.cgi?id=356225
MikeC <mike.cloa...@gmail.com> changed:
What|Removed |Added
CC||mike.cloa...@gma
https://bugs.kde.org/show_bug.cgi?id=367828
--- Comment #17 from MikeC <mike.cloa...@gmail.com> ---
Is there any chance that this issue is connected to bug
https://bugs.kde.org/show_bug.cgi?id=356225 even though I have only a single
monitor and no additional monitor connected?
-
https://bugs.kde.org/show_bug.cgi?id=367828
--- Comment #16 from MikeC <mike.cloa...@gmail.com> ---
Any chance that for some reason plasma is trying to put the panel on the eDP1
display when booted to kernel 4.7.4-1 even though I have only a single HDMI
monitor connected?
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=367828
--- Comment #15 from MikeC <mike.cloa...@gmail.com> ---
Created attachment 101158
--> https://bugs.kde.org/attachment.cgi?id=101158=edit
xrandr output for kernel 4.6.4-1
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=367828
--- Comment #14 from MikeC <mike.cloa...@gmail.com> ---
Created attachment 101157
--> https://bugs.kde.org/attachment.cgi?id=101157=edit
xrandr output for kernel 4.7.4-1
--
You are receiving this mail because:
You are watching all bug changes.
1 - 100 of 129 matches
Mail list logo
