[plasmashell] [Bug 370975] device notifier pretends it cannot mount usb device while actually mounting it

[Éric Brunet via KDE Bugzilla]

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

--- Comment #3 from Éric Brunet  ---
(In reply to Marco Martin from comment #1)
> do the two computers use the same distribution/plasma version/distribution
> version?

Both computers are fedora 23. One is up to date (plasma 5.7.5), the other not
quite (plasma 5.7.3).

But I have been experiencing this bug for a long time: it has been present for
several version of fedora and of plasma. Unfortunately, I cannot say since
when. Several times, I have simply waited for the next update, and was in the
impression that the next update did fix it.  (And maybe it has been fixed for
some period of time?) But at some point the bug would reappear. As it doesn't
occur every time, and as I don't use so often an external drive, it is hard for
me to be precise.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 370975] New: device notifier pretends it cannot mount usb device while actually mounting it

[Éric Brunet via KDE Bugzilla]

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

Bug ID: 370975
   Summary: device notifier pretends it cannot mount usb device
while actually mounting it
   Product: plasmashell
   Version: 5.7.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Device Notifier
  Assignee: plasma-b...@kde.org
  Reporter: eric.bru...@lps.ens.fr

I plug a USB key. Device notifier pops up, and I click "open in file manager"

Instead of dolphin appearing, I have an error box titled "Error KIO Client"
with the text
"malformed URL" and an "Ok" button. This error box seems to be from kde-open5
launched with a single argument which is an empty string, as in:  kde-open5 ''

Dolphin did not appear, but my usb key is now mounted: I can even see the bar
in the device notifier telling me how full it is.

If I click again on "Open in file Manager" in the device notifier, I no longer
have the "malformed url" error, but I have instead  two error messages:
1) one inside the device notifier popup: "You are not authorized to mount this
device"
2) one in a new Plasma popup: "Devices notifications".  "Could not mount the
following device:" 

I can click as many times as I want "Open in file manager", I have always the
same answer.

Again, the device is mounted from the first click in the device notifier. I can
launch dolphin manually and browse it with no difficulty. The device-notifier
knows it is mounted, because it displays the small bar. And I can unmount with
no difficulty the usb key from the device notifier itself by clicking the small
underlined triangle on the right. But device notifier makes an error instead of
running dolphin.

When this bug starts to happen it never disappears without a reboot.

After a fresh boot, the bug is sometimes there from the start, and sometimes it
is not: the device-notifier works perfectly! But at some point (I don't know
what causes the problem) the bug appears again.

I see this on two computers, with several different usb devices (keys and hard
drives).

Reproducible: Sometimes

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 357726] volume indicator and wifi quality are too hard to read

[Éric Brunet via KDE Bugzilla]

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

--- Comment #5 from Éric Brunet  ---
Ah, much better!

Thank you!

-- 
You are receiving this mail because:
You are watching all bug changes.

[telepathy] [Bug 354384] No visible way to add/configure link-local XMPP account

[Éric Brunet via KDE Bugzilla]

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

Éric Brunet  changed:

   What|Removed |Added

 CC||eric.bru...@lps.ens.fr

--- Comment #1 from Éric Brunet  ---
Yes, this is annoying. I just want to chat on the local network, but I cannot
make it work.

I managed to create an account from the command line with

mc-tool add salut/local-xmpp "Personnes à proximité" string:first-name="Éric"
string:last-name="Brunet"

and then

mc-tool enable salut/local_xmpp/account0

I did this on two computers on the same local network (both fedora 23 linux).
We could see each other on the contact list, but were unable to chat. When
clicking on the other contact, a chat window appears, I can type some text, but
it doesn't reach the other person.

A funny point is that the computer still manage to exchange a little bit of
information: when the chat window is opened, if the other contact changes its
status, it is reported back in the chat window.

So the question is: did I create correctly the Salut accounts ? Why is it not
working ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 359893] There is a phantom entry in systray

[Éric Brunet via KDE Bugzilla]

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

--- Comment #4 from Éric Brunet  ---
Thanks for the update. I confirm that killing xembedsniproxy removes the blank
entry.
However, I don't have fcitx on my system, and I have no idea what program might
be responsible for the entry.

Anyway, I'll wait for Plasma 5.6

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 359893] There is a phantom entry in systray

[Éric Brunet via KDE Bugzilla]

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

--- Comment #1 from Éric Brunet  ---
Created attachment 97594
  --> https://bugs.kde.org/attachment.cgi?id=97594=edit
systray with blank item and parameters window with blank entry

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 359893] New: There is a phantom entry in systray

[Éric Brunet via KDE Bugzilla]

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

Bug ID: 359893
   Summary: There is a phantom entry in systray
   Product: plasmashell
   Version: 5.5.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: eric.bru...@lps.ens.fr

Each time I log on, there is a blank space in my system tray. It cannot be
clicked. If I open the system tray menu to change the parameters, there is an
entry with no icon nor label with a visibility set on "Auto". I can set it on
"Hidden" and the blank space disappears. But it will be set on "Auto" on the
next login.

I have no idea what this entry might be.  I have plasma-desktop-5.5.4-1 and I
have just installed qt5 5.5.1-12 (but the bug was present with qt5 5.5.1-11).
This last qt update was supposed to fix
bug 352055 which is maybe related to this one, but it didn't help in my case. 

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[kio] [Bug 356662] dolphin 15.08 does not know the camera protocol

[Éric Brunet via KDE Bugzilla]

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

Éric Brunet  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Éric Brunet  ---
I confirm that kamera-15.12 allows dolphin to browse the camera. I am marking
this bug as resolved(fixed).

I have opened bug 359714 to cover the second issue, the fact that clicking on a
file from the camera from dolphin fails to open okular on that file, even
though okular by itself is able to open it.


(In reply to Marcus Meissner from comment #5)
> The second issue is unrelated to the first, for such please open new bugs.
> I think the second one is caused by the fact that only 1 process can access
> the camera. the kioslave in dolphin/konqueror is still open, but the one for
> okular tries to access the camera, getting blocked.
> as the kioslave will autoclose the camera after some seconds, you will be
> getting success if you reload after some seconds

-- 
You are receiving this mail because:
You are watching all bug changes.

[kio] [Bug 359714] New: bad interaction over kio_kamera between kde4 and kde5 applications

[Éric Brunet via KDE Bugzilla]

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

Bug ID: 359714
   Summary: bad interaction over kio_kamera between kde4 and kde5
applications
   Product: kio
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kamera
  Assignee: mar...@jet.franken.de
  Reporter: eric.bru...@lps.ens.fr

I have an uptodate fedora 23 with the latest kamera package, which includes the
kamera kio
both for kde4 and kde5 applications. This means that dolphin (kde5) can browse
without any problem my camera, and okular (kde4) can also open files on the
camera from its open menu.

However, when browsing files with dolphin on the camera, and clicking on one
file, kde tries to launch okular on this file and fails: after about 15 second
a error window appears:
Could not open
camera:/Fuji%2520FinePix%2520X10@usb:001,005/store_1001/DCIM/111_FUJI/DSCF1369.JPG.
Reason: Unknown error
Impossible de communiquer avec le périphérique USB

If, however, I try to right-click on the file and welect "open
with..."->"okular", I manage most of the time to open the file. Also, as
already said, opening directly from okular's open menu works fine.

Note: this is a follow-up of bug 356662.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-solid] [Bug 358603] unlocking luks encrypted drive gives an error

[Éric Brunet via KDE Bugzilla]

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

Éric Brunet  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Éric Brunet  ---
After the latest series of upgrades, my fedora 23 features now plasma 5.5.4 and
kf5 5.19, and this bug appears to be fixed: my encrypted drive is working fine.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-solid] [Bug 358603] unlocking luks encrypted drive gives an error

[Éric Brunet via KDE Bugzilla]

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

--- Comment #2 from Éric Brunet  ---
The bug keeps being very annoying. Is there anything I can do to help debugging
it ? I tried to run
dbus-monitor while trying my encrypted drive, but I cannot say I understand
much.

So, just in case, while the drive is successfully mounted, when I click on
"Open in the file manager" in the device notifier window, I don't get a dolphin
window but an error message "Could not mount the following device:".
Here is what happens on dbus during that time. Does it help ?

==
method call time=1455042915.689297 sender=:1.18 -> destination=org.kde.kded5
serial=2777 path=/modules/soliduiserver; interface=org.kde.SolidUiServer;
member=showActionsDialog
   string "/org/freedesktop/UDisks2/block_devices/sdb1"
   array [
  string "test-predicate-openinwindow.desktop"
   ]

signal time=1455042915.692089 sender=:1.5 -> destination=(null destination)
serial=5374
path=/org/kde/solid/Device__2Forg_2Ffreedesktop_2FUDisks2_2Fblock_5Fdevices_2Fsdb1;
interface=org.kde.Solid.Device; member=setupRequested

method return time=1455042915.694461 sender=:1.5 -> destination=:1.18
serial=5375 reply_serial=2777
signal time=1455042915.696512 sender=:1.5 -> destination=(null destination)
serial=5376
path=/org/kde/solid/Device__2Forg_2Ffreedesktop_2FUDisks2_2Fblock_5Fdevices_2Fsdb1;
interface=org.kde.Solid.Device; member=setupDone
   int32 1
   string "Le périphérique est déjà monté: Device /dev/dm-5 is already mounted
at `/run/media/eric/backup'.
"

method call time=1455042915.698572 sender=:1.75 ->
destination=org.freedesktop.Notifications serial=329
path=/org/freedesktop/Notifications; interface=org.freedesktop.Notifications;
member=Notify
   string "Hardware notifications"
   uint32 0
   string "emblem-mounted"
   string "Devices notification"
   string "Could not mount the following device: 149,0 GiB Encrypted Drive"
   array [
   ]
   array [
  dict entry(
 string "x-kde-appname"
 variant string "hardwarenotifications"
  )
   ]
   int32 -1

method return time=1455042915.711033 sender=:1.18 -> destination=:1.75
serial=2778 reply_serial=329
   uint32 22
signal time=1455042921.045219 sender=:1.18 -> destination=(null destination)
serial=2779 path=/org/freedesktop/Notifications;
interface=org.freedesktop.Notifications; member=NotificationClosed
   uint32 22
   uint32 1
signal time=1455042921.045856 sender=:1.75 -> destination=(null destination)
serial=330 path=/Notify; interface=org.kde.KNotify; member=notificationClosed
   int32 268

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-solid] [Bug 358603] unlocking luks encrypted drive gives an error

[Éric Brunet via KDE Bugzilla]

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

--- Comment #1 from Éric Brunet  ---
I forgot to mention that everything used to work fine on my fedora 21 system
(with kde 4), so this is a regression.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-solid] [Bug 358603] New: unlocking luks encrypted drive gives an error

[Éric Brunet via KDE Bugzilla]

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

Bug ID: 358603
   Summary: unlocking luks encrypted drive gives an error
   Product: frameworks-solid
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: lu...@kde.org
  Reporter: eric.bru...@lps.ens.fr
CC: kdelibs-b...@kde.org

I have a USB drive with a luks encrypted partition. When I plug the drive, the
device notifier pops up, suggesting to open the volume in the file manager. So
far, so good.
I click as suggested to open the volume, a window pops up to ask for the
password. I enter the password and then it gets weird:
1) An error message appears with
   "Could not mount the following device: .."
2) dolphin is not launched.

However, the password was accepted and the device ***is in fact mounted***
despite what the error message says. Even the device notifier is aware that the
device is mounted, because now there is the "unmount" icon on the right (and
the icon works as expected) and there is a line representing how full the
filesystem is appearing under its name.  While the volume is mounted, I can
click on its name in the device notifier: it still fails to launch dolphin and
pops the same error message instead: "Could not mount the following
device:"

So, to summarize, the device notifier works almost: the drive is mounted when
the user asks, but the file manager is not launched and a false error message
pops up.

Remark that I can bypass entirely the device notifier: plugging the drive,
ignoring the device notifier, launching dolphin and clicking on the drive from
within dolphin works perfectly: my password is asked for, and the drive mounts
without an error.

I am running an uptodate fedora 23. I am not sure which packages are involved.
I have
plasma 5.5.3, kf5 5.18, dolphin 15.12, cryptsetup 1.6.8


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 357726] New: volume indicator and wifi quality are too hard to read

[Éric Brunet via KDE Bugzilla]

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

Bug ID: 357726
   Summary: volume indicator and wifi quality are too hard to read
   Product: Breeze
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: uri_herr...@nitrux.in
  Reporter: eric.bru...@lps.ens.fr
CC: kain...@gmail.com

I have upgraded from fedora 21 (with plasma 4 and oxygen icon theme) to fedora
23 with (plasma 5 and breeze icon theme) recently, and even after allowing for
some time to get used to the new icons, I still cannot read easily what is the
reception level of my wifi or the set volume of the speakers at a glance: the
volume has two bars and the wifi has three, and each bar can be either black or
grey, but the black and grey are so close that it is impossible to tell them
apart without squirting at the screen.

This is a big regression after coming from the oxygen icons, where an unset bar
was hollowed and a set bar was painted in white: reading the levels was
immediate. The breeze icons for the volume and wifi reception need more
contrast, either by changing the grey level of the unset bars, or making them
dash lines, or making bolder the set bars.

Note that this is not a criticism about the breeze design; it is a bug about
how two icons which should convey easily important information fail to convey
that information. To take an exemple, I find that the battery indicator does a
great job (better than the oxygen icon) to tell me at glance the battery level.

It is important that the breeze icon set be flawless because there is no
alternative. I tried, because of the current issue, to use the oxygen icons but
it is impossible because some icons are missing (such that, for instance, the
wifi killswitch and airport mode icons in the pop-up menu).

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 357606] New: All the mails from one of my contacts cannot be displayed

[Éric Brunet via KDE Bugzilla]

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

Bug ID: 357606
   Summary: All the mails from one of my contacts cannot be
displayed
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: eric.bru...@lps.ens.fr

I am using kmail 4.14.10 on an up-to-date fedora 23 linux machine.

One of my contacts are sending some mails (usually with attachments) which I am
enable to read. When I try to open their message in kmail, the headers are
correct (From:, To:, Date:) but the body of the message is replaced by the
following gibberish:
   N¬Æ¦º[b¥ªíë,j¢Âú+«
Furthermore, the message is marked as "No HTML" (it is actually HTML+Text) and
it doesn't see any attachment (there is one).

*) If I open the message on the web interface of my provider, everything works.
*) I can save the message locally from kmail with File->Save As into a .mbox
file. Then, I can
read the email and the attachment from the .mbox file with mutt
*) If I try to open the .mbox file from kmail, it still doesn't work.

It is very annoying and make kmail unusable for this particular contact.

I am attaching one of their emails to demonstrate the problem. What I actually
did was:
  1) I saved one of their email into bugreport.mbox 
  2) I edited bugreport.mbox to replace all the names/addresses/Tel/etc with
X. I tried
  not to change the number of characters.
  3) similarly, IP addresses and numeric IDs have been replaced by strings of
1.
  4) I removed the attached .pdf (encoded in base64) and replaced it by another
dummy pdf
  5) I tried to recompute the values of the headers "Content-Length:" and
"Lines:" to account
  for the modified .pdf

This way, bugreport.mbox should not contain any sensitive information. I
checked that the resulting file could be viewed with mutt (including the
attachment) but not with kmail.


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 357606] All the mails from one of my contacts cannot be displayed

[Éric Brunet via KDE Bugzilla]

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

--- Comment #1 from Éric Brunet  ---
Created attachment 96478
  --> https://bugs.kde.org/attachment.cgi?id=96478=edit
One message that kmail cannot read but that mutt can read

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 357606] All the mails from one of my contacts cannot be displayed

[Éric Brunet via KDE Bugzilla]

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

--- Comment #2 from Éric Brunet  ---
Sorry, on the first line, please read that I am "unable" to read the messages,
not "enable"...

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-pa] [Bug 351438] scale max volume value to more than 100%

[Éric Brunet via KDE Bugzilla]

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

Éric Brunet  changed:

   What|Removed |Added

 CC||eric.bru...@lps.ens.fr

-- 
You are receiving this mail because:
You are watching all bug changes.

[kio] [Bug 356662] dolphin 15.08 does not know the camera protocol

[Éric Brunet via KDE Bugzilla]

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

--- Comment #4 from Éric Brunet  ---
So, on my uptodate fedora 23, I downloaded the file
http://mirror.rit.edu/archlinux/testing/os/x86_64/kamera-15.12.0-1-x86_64.pkg.tar.xz
from the archlinux distribution and manually put the files kcm_kamera.so and
kio_kamera.so
into /usr/lib64/qt5/plugins, and the files camera.protocol and kamera.desktop
into /usr/share/kservices5, and the file solid_camera.desktop into
/usr/share/solid/actions. In logged out of my kde session, logged in again and
tried my camera.

1) on plugging my camera, a notification happens, and I can click on the
"devices" icon to look at my possible actions. Good.
2) it proposes to open my camera in the file manager. Good.
3) clicking on the action, dolphin opens. I can browse my camera, display
previews and copy files from my camera to the computer file system. Good.
4) HOWEVER, if I click on a photo to open it, it fires up okular which fails to
open the photo: okular's window appears empty, and after about fifteen seconds
an error window appears with the message:

Could not open
camera:/Fuji%2520FinePix%2520X10@usb:001,006/store_1001/DCIM/111_FUJI/DSCF1377.JPG.
 
Reason: Unknown error
Impossible de communiquer avec le périphérique USB

(the last sentence being "impossible to communicate with the USB device")

After closing the error message in okular, I can go to the File->Open Recent
dialog. The URL of the photo I tried to open is there and if I attempt to open
it from here, it works AFTER A COUPLE OF TRIES. (On the first tries it usually
fails with the same error message, but without the fifteen second wait. After a
couple of atttempts it works, and once it worked, all the subsequent tries work
also)

>From okular, I can also go to the File->Open dialog, and type camera:/ and
access my files without any problem.

And now, for the very weird stuff: from dolphin, if I right-click a file to
open the contextual menu, select  "open with" and then "okular", it works most
of the time: the file opens. Sometimes, it opens after a very small wait (1
second), sometimes one has to wait about 10 seconds, sometimes it fails after
15 seconds.

I cannot make sense of this!
So, okular is not a kf5 application

-- 
You are receiving this mail because:
You are watching all bug changes.

[kio] [Bug 356662] dolphin 15.08 does not know the camera protocol

[Éric Brunet via KDE Bugzilla]

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

--- Comment #3 from Éric Brunet  ---
Excellent news. 15.12 does not seem to be released yet, I'll wait a few days in
the hope that I'll find some already compiled packages and I'll report back.

Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kio] [Bug 356662] New: dolphin 15.08 does not know the camera protocol

[Éric Brunet via KDE Bugzilla]

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

Bug ID: 356662
   Summary: dolphin 15.08 does not know the camera protocol
   Product: kio
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kioslave
  Assignee: konq-b...@kde.org
  Reporter: eric.bru...@lps.ens.fr

When plugging my fujifilm X10 camera, which uses the PTP protocol, in a fedora
23 with kde, nothing happens. When I plug the same camera in a fedora 21, the
device notifier pops up and gives me some options. The fact that nothing
happens on the fedora 23 is an annoying bug by itself, but it is not really the
bug I want to report now.

On the fedora 21 machine, I can browse and modify the files on the camera from
within dolphin by entering the url "camera:/". On fedora 23, entering
"camera:/" gives me an "invalid protocol" error message.

Of course, fedora 21 uses dolphin 15.04.0 based on kde 4.14.11, while fedora 23
uses dolphin 15.08.1 based on kde frameworks 5.16.0. I presume that the camera
ioslave was not ported to kde 5.

As a matter of fact, if I fire good old konqueror on the fedora 23 computer, I
can access the filesystem on the camera by entering the "camera:/" url.
konqueror is still a kde 4 application.

This is a very serious regression. In 2015, one expects to have a window
popping up when plugging a camera and having no trouble browsing the files on
it. Is there any way to make dolphin5 use the kde4 kioslave ? Is there a plan
porting the kioslave to kde5 ?

For information, the relevant output from "solid-hardware5 list details" when
the camera is plugged:

udi =
'/org/kde/solid/udev/sys/devices/pci:00/:00:1d.0/usb1/1-1/1-1.3/1-1.3.2'
  parent = '/org/kde/solid/udev'  (string)
  vendor = '04cb'  (string)
  product = 'USB PTP Camera'  (string)
  description = 'Appareil photo'  (string)
  Block.major = 189  (0xbd)  (int)
  Block.minor = 8  (0x8)  (int)
  Block.device = '/dev/bus/usb/001/009'  (string)
  Camera.supportedProtocols = {'ptp'}  (string list)
  Camera.supportedDrivers = {'gphoto'}  (string list)



Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.