[kwin] [Bug 478048] New: Cannot configure Win as a modifier to change keyboard layout in X applications running in XWayland
https://bugs.kde.org/show_bug.cgi?id=478048 Bug ID: 478048 Summary: Cannot configure Win as a modifier to change keyboard layout in X applications running in XWayland Classification: Plasma Product: kwin Version: 5.27.9 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: eric.bru...@lps.ens.fr Target Milestone: --- I am using KDE+Wayland on a fully uptodate Fedora 39 laptop. My `.config/kxkbrc` file looks like this: ``` [$Version] update_info=kxkb.upd:remove-empty-lists,kxkb.upd:add-back-resetoptions,kxkb_variants.upd:split-variants [Layout] DisplayNames=, LayoutList=fr,gr Options=grp:win_switch,compose:rctrl,terminate:ctrl_alt_bksp ResetOldOptions=true Use=true VariantList=oss,polytonic ``` With the `grp:win_switch` setting, while I press the "Windows" key of my laptop, the keyboard layout is changed to greek. (So that `Win+d` gives `δ`, for instance.) This works very well, except in X applications running under XWayland. Then, this specific shortcut does not work. Hitting `Win+d` only gives `d`. I have tried xterm and thunderbird. (Nota: I don't care about xterm, but I'd like to have thunderbird for X working. I cannot, unfortunately, use thunderbird for wayland as I have an extension which only works with the X version.) Note that other shortcuts are working fine. For instance, as can be seen in my `.kxkbrc`, I configured the right Ctrl key to work as Compose, and this works perfectly in wayland and X applications. I have many personal shortcuts defined in a .XCompose file which work perfectly well. (As a workaround, I tried to add the option `grp:lctrl_lwin_toggle` to my `.kxkbrc`, but then I hit another bug, see bug 478046.) To summarize, I think that keyboard should behave in the same way under native wayland applications and X applications. It is nearly the case but, unfortunately, some options such as `grp:win_switch` do not work in X applications under XWayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478046] New: Cannot configure two ways to switch layout
https://bugs.kde.org/show_bug.cgi?id=478046 Bug ID: 478046 Summary: Cannot configure two ways to switch layout Classification: Plasma Product: kwin Version: 5.27.9 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: eric.bru...@lps.ens.fr Target Milestone: --- Flags: Wayland+ I am using KDE+Wayland on a fully uptodate Fedora 39 laptop. I am using a french keyboard, but I also want to enter greek letters and so I have configured my keyboard with these two layouts, and I have set the Windows key as a modifier to change layout while pressed. My `.config/kxkbrc` file looks like this: ``` [$Version] update_info=kxkb.upd:remove-empty-lists,kxkb.upd:add-back-resetoptions,kxkb_variants.upd:split-variants [Layout] DisplayNames=, LayoutList=fr,gr Options=grp:win_switch,compose:rctrl,terminate:ctrl_alt_bksp ResetOldOptions=true Use=true VariantList=oss,polytonic ``` With the `grp:win_switch` setting, while I press the "Windows" key of my laptop, the keyboard layout is changed to greek. (So that `Win+d` gives `δ`, for instance.) Recall that without this option, the "Windows" key is interpreted as "Menu" if I press and release it, or as "Meta" if I press it with another key (so that `Win + d`, interpreted as `Meta + d`, shows the desktop without any window as per the standard kwin shortcuts). I tried to add another shortcut to toggle keyboard layouts (using the graphical interface), so that my `.kxkbrc` looks like ``` [$Version] update_info=kxkb.upd:remove-empty-lists,kxkb.upd:add-back-resetoptions,kxkb_variants.upd:split-variants [Layout] DisplayNames=, LayoutList=fr,gr Options=grp:win_switch,compose:rctrl,terminate:ctrl_alt_bksp,grp:lctrl_lwin_toggle ResetOldOptions=true Use=true VariantList=oss,polytonic `` With the option `grp:lctrl_lwin_toggle`, hitting `Left Ctrl + Left Win` switches the keyboard between my two layouts, french and greek. This toggle shortcut works well, but then the first option `grp:win_switch` is ignored: the "Windows" key used alone is seen as a "Menu" key, and `Win + key` is interpreted as `Meta + key`; in particular, `Win + d` shows the desktop. The system config interface lets me select several ways to switch layouts, and there is nothing logically incompatible between the two options I tried to set at the same time. They should both work together. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 468852] New: Akonadi flashes unreadable error windows
https://bugs.kde.org/show_bug.cgi?id=468852 Bug ID: 468852 Summary: Akonadi flashes unreadable error windows Classification: Frameworks and Libraries Product: Akonadi Version: 5.22.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: eric.bru...@lps.ens.fr Target Milestone: --- Created attachment 158348 --> https://bugs.kde.org/attachment.cgi?id=158348=edit videoshot of the screen When one of the imap servers I am using has an error, the akonadi server shows every couple of minutes an error message in a flashing window: it appears and immediately disappears. The window flashes too quickly to be readable; I had to make a movie with my phone, and watch it frame by frame, to be able to read the message. I am attaching a 1 sec video demonstrating the problem. There are several issues here: *) the window flashing going every minute or so is annoying *) it is very hard to see the window reports a problem with akonadi *) even once the message has been read, there is no easy way to stop the error windows flashing. Here is a small wishlist: == fix the flashing issue (obviously...) == add a Pause/Unpause button in the "account configuration window" of kmail == add an option to entirely disable such error windows. There could be other ways to notify that a resource is down The message is in french, basically it says: Title: authentification impossible --- [$Imap_resource_name] The server from the account "$Imap_resource_name" has refused the username and the password. Do you want to open the configuration window, try connecting again, or do nothing Connection error: The server replied A04 NO AUTHENTICATE failed Buttons: [Account configuration] [Try again] [Cancel] Now the strange part: I have another configured Imap resource. If I enter the wrong password in that resource, then the same error window (for that other account) appears and works as expected: it appears, and wait for me to click one of the buttons. What can I do to debug this ? I have an up-to-date fedora 38 linux, running with Wayland and kde kf5-akonadi-server-mysql-22.12.3-1.fc38.x86_64 kwin-5.27.4.1-1.fc38.x86_64 libwayland-server-1.22.0-1.fc38.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[phonon-backend-vlc] [Bug 307364] video stream does not cover full size of VideoWidget
https://bugs.kde.org/show_bug.cgi?id=307364 --- Comment #12 from Éric Brunet --- Sorry: phonon-qt5-4.11.1-11.fc38.x86_64 phonon-qt5-backend-vlc-0.11.3-3.fc37.x86_64 vlc-3.0.19-0.3.fc38.1.x86_64 poppler-23.02.0-1.fc38.x86_64 okular-22.12.3-1.fc38.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[phonon-backend-vlc] [Bug 307364] video stream does not cover full size of VideoWidget
https://bugs.kde.org/show_bug.cgi?id=307364 Éric Brunet changed: What|Removed |Added CC||eric.bru...@lps.ens.fr --- Comment #11 from Éric Brunet --- Created attachment 158162 --> https://bugs.kde.org/attachment.cgi?id=158162=edit pdf with movie demonstrating the problem Hi, This is an old bug. I have an issue with vlc-phonon backend which might be the same issue, but I am not sure. I am trying to build pdf with embedded movie; I am using latex with the beamer/multimedia package. The idea is that a rectangle on the pdf is defined, and when the user clicks on it (using a compatible pdf reader; I am using okular), the video is played tight on top the rectangle, as if it was embedded in the pdf itself. Internally, okular uses the poppler library which calls phonon which uses vlc. I am using a video with a 2:1 aspect ratio, and I define a rectangle with the same aspect ratio. My problem is that the video occupies the full height of the rectangle, but not its full width: it has been squeezed horizontally, and black bands appear on both sides. In order for the video to fill the whole rectangle, it seems that the rectangle must have an aspect ratio of 7:4. Now here's the catch: the problem seems to appear only using Wayland. It seems to be working as expected with X11. I am using an uptodate fedora38 beta. I have attached a pdf file embedding twice the same movie: once onto a rectangle with a 2:1 aspect ratio, and once onto a rectangle with a 7:4 aspect ratio. The video should fit the first rectangle, and horizontal black band should appear in the second rectangle. this works as expected under X1. Under wayland, the video is squeezd and fits the second rectangle. On the first rectangle, vertical black bands appear. For documentation, I have also included the latex file. Is this the same bug? Should I open a new one? Is there a workaround? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 453877] If fingerprint authentication is enabled, unable to unlock screen with password until after 3 failed fingerprint auth attempts
https://bugs.kde.org/show_bug.cgi?id=453877 --- Comment #4 from Éric Brunet --- I agree it should be PAM's job, but they don't seem to think so. From the manpage for pam_fprintd: The PAM stack is by design a serialised authentication, so it is not possible for pam_fprintd to allow authentication through passwords and fingerprints at the same time. It is up to the application using the PAM services to implement separate PAM processes and run separate authentication stacks separately. This is the way multiple authentication methods are made available to users of gdm for example. So maybe it is up to kscreenlocker to do the work, after all. There must be some code in gdm that could be adapted in kscreenlocker and in sddm. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 453877] If fingerprint authentication is enabled, unable to unlock screen with password until after 3 failed fingerprint auth attempts
https://bugs.kde.org/show_bug.cgi?id=453877 Éric Brunet changed: What|Removed |Added CC||eric.bru...@lps.ens.fr --- Comment #2 from Éric Brunet --- I have the same issue on a fedora 38 beta. After failing three times the fingerprint, I can indeed type my password to unlock It works the other way around: I can type my password, hit enter (nothing happens), and then fail three times the fingerprint; the computer unlocks. The problem might not be on kde side, as it is also present with other programs. For instance, if I use sudo, I need to fail three times the fingerprint before being offered a keyboard prompt. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 357606] All the mails from one of my contacts cannot be displayed
https://bugs.kde.org/show_bug.cgi?id=357606 Éric Brunet changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Éric Brunet --- Yes, I confirm the bug is still present. Six () years later, I saved my own attachment as a .mbox file, I configured kmail to treat this .mbox file as a new "Receiving Account", i could see the subject and date of the e-mail, but the content displayed as N��Ʀ�[b�,j+��, with no attachment. As before, mutt was able to read the e-mail, and save the pdf file. I also found the original e-mail in my 2016 archive, and the problem is still there. What about you? Can't you reproduce the issue? I am really curious. That being said, i no longer exchange e-mails with that specific contact, so I am no longer impacted. Éric Brunet -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455228] focus follows mouse thwarted by libreoffice
https://bugs.kde.org/show_bug.cgi?id=455228 --- Comment #1 from Éric Brunet --- Today, I managed to reproduce this bug on a different computer also running XOrg. I also tried to reproduce it on that same computer but with wayland, but I couldn't. So, the bug only happens with XOrg. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455228] New: focus follows mouse thwarted by libreoffice
https://bugs.kde.org/show_bug.cgi?id=455228 Bug ID: 455228 Summary: focus follows mouse thwarted by libreoffice Product: kwin Version: 5.24.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: eric.bru...@lps.ens.fr Target Milestone: --- Created attachment 149671 --> https://bugs.kde.org/attachment.cgi?id=149671=edit A simple LibreOffice Calc demonstrating the problem I am running an uptodate fedora 35, with KDE and Xorg. kwin is configured with "focus follows mouse", and it usually works. However, a certain manipulation with libreoffice Calc can lock the focus on libreoffice Calc's window. In detail, one can specify a list of valid values for some cells in LibreOffice Calc. In the attached file BugFocus.ods file, the only valid valued for cell A1 are "emacs" and "vim". When clicking on cell A1, a down arrow appears on the right of the cell. When clicking on the arrow, a drop-down menu appears to choose one of these values. If one chooses a value (and don't click anywhere else), then the focus is locked to LibreOffice Calc. In particular, even after moving the cursor out of LibreOffice's windows, mouse scroll events and keyboard events are directed to LibreOffice. A mouse click event is first sent to LibreOffice, but breaks the lock and gives the focus to the window under the cursor. I tried all the possible settings for kwin's focus policy (in particular I tried "extreme focus stealing prevention"), but it doesn't help. I don't know what horrible thing LibreOffice is doing, but focus stealing prevention is kwin's job. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356446] [Meta] Enable Qt scaling on X11
https://bugs.kde.org/show_bug.cgi?id=356446 --- Comment #77 from Éric Brunet --- Hi, I am the reporter of bug 451193, which has just been marked as a duplicate of this bug. I have read all the comments of this bug, and I don't think this addresses the main message of 451193, which is: plasma is behaving differently under Xorg depending on the low-level graphics driver (Intel or modesetting, in my case) I think changing the low-level driver can change performance and/or stability, but not the overall look of the Desktop. In particular, I am very happy with the look of plasma using the Intel driver and PLASMA_USE_QT_SCALING=1, and I wish that it would look as good with the modesetting driver, but unfortunately PLASMA_USE_QT_SCALING has no effect for me with the modesetting driver. Should I reopen 451193 ? BTW, I can't hide I had hoped a solution would be found for Xorg, but of course there is a limited amount of time available, and I wanted to thank you for all the work done. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451193] HiDPI: wrong sizes for several UI element
https://bugs.kde.org/show_bug.cgi?id=451193 --- Comment #4 from Éric Brunet --- Created attachment 147325 --> https://bugs.kde.org/attachment.cgi?id=147325=edit kmail with modesetting driver Nota: it is not plasma only, but the whole of KDE which behaves differently with Intel and Modesetting driver. I have attached, as an illustration, two screenshot of kmail's editor with both drivers. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451193] HiDPI: wrong sizes for several UI element
https://bugs.kde.org/show_bug.cgi?id=451193 --- Comment #3 from Éric Brunet --- Created attachment 147324 --> https://bugs.kde.org/attachment.cgi?id=147324=edit kmail with Intel driver -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451193] HiDPI: wrong sizes for several UI element
https://bugs.kde.org/show_bug.cgi?id=451193 --- Comment #2 from Éric Brunet --- Created attachment 147323 --> https://bugs.kde.org/attachment.cgi?id=147323=edit With Modesetting driver -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451193] HiDPI: wrong sizes for several UI element
https://bugs.kde.org/show_bug.cgi?id=451193 --- Comment #1 from Éric Brunet --- Created attachment 147322 --> https://bugs.kde.org/attachment.cgi?id=147322=edit With Intel driver and PLASMA_USE_QT_SCALING unset -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451193] New: HiDPI: wrong sizes for several UI element
https://bugs.kde.org/show_bug.cgi?id=451193 Bug ID: 451193 Summary: HiDPI: wrong sizes for several UI element Product: plasmashell Version: 5.24.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: eric.bru...@lps.ens.fr CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 147321 --> https://bugs.kde.org/attachment.cgi?id=147321=edit With Intel driver and PLASMA_USE_QT_SCALING=1 I have a XPS 13 Dell laptop with 3840x2160 resolution, and its hidpi screen brings some issues: UI elements such as icons in front of menu items and checkboxes in dialog boxes are sometimes too small, and there does not seem any easy way to fix it. I am running an uptodate fedora 35 linux, with XOrg (not wayland!) and plasma kde, but the problem has been present for several revision. The global scale on the display configuration box is set to 250%, and I am forcing 240dpi in the fonts settings. * When I set PLASMA_USE_QT_SCALING=1 and run the intel driver for XOrg, sizes are pretty good both for contextual menu icons and checkboxes. * When I don't set PLASMA_USE_QT_SCALING and run the intel driver, sizes are wrong for contextual menu icons, but good for checkboxes. * When I run the modesetting driver for Xorg, PLASMA_USE_QT_SCALING seems to have no effect, and sizes for contextual menu icons and checkboxes are wrong. Please see the attached screenshots. Notice the icons in front of the menu items in the bottom right contextual menu. Notice the checkboxes in the dialog box. Notice also that the small icons (battery, volume, etc...) in the taskbar: depending on the display driver, they fit in one or two columns. Notice also the size of the configuration windows: in each time, I made it as small as possible. This minimal size is nice and fit for the Modesetting driver, and way too large for the Intel driver. I believe that the behaviour of plasma should not depend on the low level hardware driver of Xorg I believe that I shouldn't have to set (or not) environment variables such as PLASMA_USE_QT_SCALING to get things right or not. I suspect that there is a bug around PLASMA_USE_QT_SCALING, since it has an effect for one Xorg driver and not for the other. I believe there should be an easy way to change the size of UI elements such as contextual menu icons and checkboxes, in case the automatic scaling fails. Nota: I used to live happily using th eIntel driver, but I am now experiencing an independant bug with Intel which forces me back to modesetting... -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433828] Bug with annotations on jpg or png when display scaling is enabled.
https://bugs.kde.org/show_bug.cgi?id=433828 --- Comment #3 from Éric Brunet --- I have upgraded my fedora to version 34, I now have okular-20.12.2-2.fc34.x86_64, and the problem is indeed fixed. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 147995] javascript error prevents watching movie trailers on www.allocine.fr
https://bugs.kde.org/show_bug.cgi?id=147995 --- Comment #8 from Éric Brunet --- Well, I am no longer using konqueror, but I just restarted it to try. (I have an uptodate fedora 33). I still seem to be having some issues, but it is complicated: what I see depends on the web rendering engine (should I choose khtml, webkit, webengine?) I nearly add success with webengine: when I run on youtube.com, the page loads but there are grey squares instead of the video posters. When I click on one of them, the video plays (after the ads). On allocine.fr, sometimes I can see the ad, sometimes not. I didn't manage to get an actual trailer. Well. There might be some old and unusual configuration choices on my computer, but this did not give me the impulse to go back to konqueror. Anyway, you can close this bug if you want. I am no longer concerned, and the problem I see might have some other cause. And if there is still some problems, it is certainly for a different reason as 10 years ago... -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433828] Bug with annotations on jpg or png when display scaling is enabled.
https://bugs.kde.org/show_bug.cgi?id=433828 --- Comment #2 from Éric Brunet --- Ah, yes, thanks: from the description of the commit, this looks likely. The commit is in okular-20-12, hopefully fedora will ship it at some time. When this happens, I'll confirm here whether the bug is fixed or not. (There is a okular-20-12 in fedora rawhide, but this requires to upgrade also the glibc, and I'd rather not take any chance...) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433828] New: Bug with annotations on jpg or png when display scaling is enabled.
https://bugs.kde.org/show_bug.cgi?id=433828 Bug ID: 433828 Summary: Bug with annotations on jpg or png when display scaling is enabled. Product: okular Version: 1.11.1 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: eric.bru...@lps.ens.fr Target Milestone: --- Created attachment 136303 --> https://bugs.kde.org/attachment.cgi?id=136303=edit Video of the bug in action I have an uptodate fedora 33 computer, with okular-20.08.1-1.fc33.x86_64.rpm (reporting as okular 1.11.1). I have an issue which 1) occurs with .jpg and .png files, but not with .pdf files 2) occurs only when System Settings->Display Configuration->Global scale is not set to 100%. (Specifically: I have it set at 200%). The bug is the following: when trying to use the "Freehand line" annotation tool, everything works correctly while I draw. But when the drawing ends (when I release the mouse button, or when I remove my finger from the touchscreen), the whole drawing gets dilated by a factor of 2 from the upper-left corner: all the coordinates are multiplied by 2. I am attaching a small video to illustrate the problem. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 33 KDE Plasma Version: plasma-desktop-5.20.5-1.fc33.x86_64 KDE Frameworks Version: kf5-kparts-5.79.0-2.fc33.x86_64 Qt Version: qt5-qtbase-5.15.2-2.fc33.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421822] 'Scroll Page Up'/'Scroll Page Down' actions do not scroll by pages
https://bugs.kde.org/show_bug.cgi?id=421822 Éric Brunet changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED --- Comment #25 from Éric Brunet --- [Sorry, I seem to have sent my comment prematurly. I am finishing it now] 4) I go back into the settings and ask for the scrollbars to be hidden 5) The space key is still working properly. 6) I quit okular and start again 7) The bug is is back: the space key scrolls by one line of text. Extra information: I have a HiDPI display, and I might have some non-standard configuration options. For instance, my plasma desktop is scaled by a factor 2 and the server X is started with -dpi 192. I don't know whether this is relevant or not. So the bug is still present in okular 20.12, but depends on some configuration options. In my case, to observe it, okular must be started without any scrollbar. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421822] 'Scroll Page Up'/'Scroll Page Down' actions do not scroll by pages
https://bugs.kde.org/show_bug.cgi?id=421822 Éric Brunet changed: What|Removed |Added CC||eric.bru...@lps.ens.fr --- Comment #24 from Éric Brunet --- I think there's been a mix up between two different issues a) the fact that Scroll Up/Scroll Down or Space moved the document by about one line of text instead of nearly the full displayed height b) the issues about smooth scrolling The original description of the bug was about problem a), but in the comments it drifted to problem b), and eventually the bug was marked as resolved and duplicate of bug 422050. But this is for problem b)! Problem a) is not fixed, and I am reopening this bug. My okular was working correctly in Fedora 32 (Version 19.something of okular, I didn't make note of exact version). I upgraded to Fedora 33 (Version 20.08) and ran into the problem described here. I then upgraded the okular package from fedora rawhide (or 34) in the hope the problem was already fixed: okular-20.12.2-2.fc34.x86_64 But it is not. The bug seem related to scrollbars. I have set up okular so that scrollbars are not set. Then: 1) I run okular on some pdf file. No scrollbar, of course, and the bug is present: pressing the space key moves me down by about one line of text. 2) I go into the settings and I ask for the scrollbars to be displayed 3) The bug no longer shows! Pressing Space scrolls me down by nearly one height of the displayed text. 4) I go back into the settings -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 429858] New: Problem with creating mbox files
https://bugs.kde.org/show_bug.cgi?id=429858 Bug ID: 429858 Summary: Problem with creating mbox files Product: kmail2 Version: 5.15.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: eric.bru...@lps.ens.fr Target Milestone: --- I tried to make kmail create some mbox files in order to archive some e-mails in a portable and readable way. However, I cannot get the name of the resource to be displayed properly, and it doesn't work immediately without applying an extra step which should be unnecessary. STEPS TO REPRODUCE 1. In the "configure kmail"->"Accounts"->"Receiving"->"Add...Custom account" dialog, I choose "Mbox". A dialog window opens and, before I fill any field, an account named "akonadi_mbox_resource_[some number]" appears in the list of accounts in the "configure/accounts/receiving" window, but not in the list of folders in the main window. 2. In the filename field of the configuration dialog, I enter "foobar.mbox" and click "Ok". the name "akonadi_mbox_resource_[some number]" appears in the folder list of the main window. It is still present under that name in the "configure/accounts/receiving" window. No file "foobar.mbox" is created. 3. In the "configure/accounts/receiving" window, I select the "akonadi_mbox_resource_[some number]" account and click "Restart". Three things happen at the same time: *) a notification message appears, reading "The resource akonadi_mbox_resource_[some number] is not working. No file specified." *) in the "configure/accounts/receiving", the account "akonadi_mbox_resource_[some number]" is renamed "foobar.mbox" *) the empty file "foobar.mbox" is created However, in the folder list of the main window, the resource is still named "akonadi_mbox_resource_[some number]", and I can find no way to change its name to foobar.mbox or anything else. The resource seems however to be working: I can move messages to it, and the appear in the foobar.mbox file. So, I guess I have three related issues; from most important to less: *) In the folder list of the main window, the proper name "foobar.mbox", or whatever I choose in the configuration dialog, should be used, rather than "akonadi_mbox_resource_[some number]". *) When creating the Mbox account, I should not be required to "restart the resource" before it starts working. *) As a user, I should never see an internal name such as "akonadi_mbox_resource_[some number]", even temporarily. In particular, nothing should appear in the "configure/accounts/receiving" window before I enter a filename. This is on an uptodate fedora 32, with kmail-19.12.2-1.fc32.x86_64, plasma-workspace-5.18.5-2.fc32.x86_64, kf5-akonadi-server-19.12.2-2.fc32.x86_64, qt5-qtbase-5.14.2-8.fc33.x86_64. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407998] Okular scales down pages when printing
https://bugs.kde.org/show_bug.cgi?id=407998 Éric Brunet changed: What|Removed |Added CC||eric.bru...@lps.ens.fr --- Comment #15 from Éric Brunet --- (In reply to Michael Weghorn from comment #11) > This is https://phabricator.kde.org/D10974 and I quickly verified that > current development version of Okular actually offers either "Fit to > printable area" or "Fit to full page" when opening a TIFF file. This is very good indeed, but it seems to me a third option is needed: Keep the actual image size and do no scaling at all At the moment, if I load a pdf of size 15cm x 8cm, I do not know how to print it to have a 15cm x 8cm picture in the middle of an empty A4 sheet of paper. Or did I miss an option somewhere ? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #29 from Éric Brunet --- Created attachment 121110 --> https://bugs.kde.org/attachment.cgi?id=121110=edit patch to reenable numbers, v19.04 Updated version of the patch to re-enable numbers in systray for kmail. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 390971] Delayed content rendering during scrolling on a hidpi screen
https://bugs.kde.org/show_bug.cgi?id=390971 Éric Brunet changed: What|Removed |Added CC||eric.bru...@lps.ens.fr --- Comment #7 from Éric Brunet --- I have, I think, the same problem on my new computer (Dell XPS 13, Fedora 30, okular 18.12.2, poppler 0.73.0) The computer has a resolution 3840x2160 and Screen Scale is set at 2.5. Like Eugene, I notice that it mostly happen with large windows. Okular even seems to give up at some points and doesn't render parts of the page till I move again. I have also put a file on (this is the file pgfmanual.pdf in package texlive-pgf-doc) look how rendering is flickering and how page 7 doesn't appear till I go up and down again. The computer is brand new, everything is going very smoothly with evince, so I don't think the problem is a lack of CPU or RAM. It works much better with Screen Scale set at 1. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #26 from Éric Brunet --- Created attachment 118961 --> https://bugs.kde.org/attachment.cgi?id=118961=edit patch to reenable numbers, v18.12 Sorry, I was slow with updating this patch. The method horizontalAdvance seems to replace nicely the method width. Probably that they changed it because "width" was so difficult to remember... -- You are receiving this mail because: You are watching all bug changes.
[kturtle] [Bug 329488] A typo in the "repeat" command gives surprising results.
https://bugs.kde.org/show_bug.cgi?id=329488 Éric Brunet changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Éric Brunet --- 5 years later, I am no longer using kturtle, but the bug is still there. kturtle v 0.8.1 beta KDE 5.52.0 Qt 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #23 from Éric Brunet --- Created attachment 114942 --> https://bugs.kde.org/attachment.cgi?id=114942=edit patch to reenable numbers, v18.04.3 This is an updated version of my patch to re-enable numbers in the tray icon for kmail. It is for kmail version 5.8.3 shipped with kde 18.04.3, as found in fedora 28. As I have already said, if this is rolled back into kmail, I am willing to answer bug reports regarding this feature. I think it should be rolled back; kmail must be the only graphical mail reader without this feature... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #21 from Éric Brunet <eric.bru...@lps.ens.fr> --- The patch for 17.12.0 also applies to 17.12.2 which has just been shiped by fedora. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 309808] Remember view mode for documents
https://bugs.kde.org/show_bug.cgi?id=309808 Éric Brunet <eric.bru...@lps.ens.fr> changed: What|Removed |Added CC||eric.bru...@lps.ens.fr --- Comment #1 from Éric Brunet <eric.bru...@lps.ens.fr> --- Yes please! I was about to open a new bug/wish with this issue when I saw this 5 year old bug. For books and journal papers, one wants the view mode to be continuous. For presentation (slides), one wants the view mode to be non-continuous. okular should remember, for each document, the view mode that the user chose. For documents never opened before, I suggest the following heuristic: set the view mode to continuous if the document is portrait and to non-continuous if it is landscape. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #12 from Éric Brunet <eric.bru...@lps.ens.fr> --- The patch for 17.12.0 also applies to 17.12.1 witho no modification, the version that appeared this week in fedora 27. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #11 from Éric Brunet <eric.bru...@lps.ens.fr> --- Created attachment 109722 --> https://bugs.kde.org/attachment.cgi?id=109722=edit patch to reenable numbers, v17.12.0 Hi Kamil, I am happy this is useful to someone. I'll post updated patches in a more timely way. Here is the patch to re-enable numbers for kmail 5.7.0, as found in kde 17.12.0, as shipped by the latest fedora 27 updates -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #9 from Éric Brunet <eric.bru...@lps.ens.fr> --- Created attachment 109488 --> https://bugs.kde.org/attachment.cgi?id=109488=edit patch to reenable numbers, v17.08.3 This is an updated version of my patch to re-enable numbers in the tray icon for kmail. It is for kmail version 5.6.3 shipped with kde 17.08.3, as found in fedora 27. I have also a version for the kmail that shipped with fedora 26 that I forgot to post here. Contact me if anyone needs it. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #8 from Éric Brunet <eric.bru...@lps.ens.fr> --- This is the patch I have been using for two weeks to re-enable nulbers in systray. It works fine. It is against kmail 16.12.3, which is the version shipped by fedora 25. It is not a simple revert of the feature removal: the displayed was small and ugly. The reason is that kmail sends a pixmap of size 32x32 which is scaled down by systray to 22x22 (in standard theme). I am not sure how to ask the theme what the correct icon size should be. I think the problem is also present in the unpatched kmail. Please? You could put me in the loop and I would answer bug reports about this? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #7 from Éric Brunet <eric.bru...@lps.ens.fr> --- Created attachment 105670 --> https://bugs.kde.org/attachment.cgi?id=105670=edit patch to reenable numbers patch against kmail 16.12.3 to re-enable showing number of unread emails in systray -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 Éric Brunet <eric.bru...@lps.ens.fr> changed: What|Removed |Added CC||eric.bru...@lps.ens.fr --- Comment #6 from Éric Brunet <eric.bru...@lps.ens.fr> --- Please, would you reconsider your decision ? I have just upgraded my fedora 23 into a fedora 25, and had the bad surprise to see that the number of unread emails was gone in the system tray icon. Having this number of emails displayed was a useful feature. I thought it was a configuration bug and I spent a long time trying to re-enable it, and then I have seen this bug. (I thought of a configuration bug because the icon when there are no unread mail is the simple breeze envelope outline, while the icon when there are unread mails is a solid white envelope with shading and a yellow star. I understand the yellow star, but why does the envelope changes ?) People choose kde over gnome for its flexibility and configurability. Your users are not afraid of an extra config option! Thanks anyway for all the work. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378007] Cannot display attached files for some weird content-type
https://bugs.kde.org/show_bug.cgi?id=378007 Éric Brunet <eric.bru...@lps.ens.fr> changed: What|Removed |Added Version|4.14.10 |5.4.3 Summary|Cannot display attached |Cannot display attached |files for some weir |files for some weird |content-type|content-type --- Comment #1 from Éric Brunet <eric.bru...@lps.ens.fr> --- I have just checked on a more uptodate computer. The bug is still present in kmail 5.4.2 and kmail 5.4.3. I am updating the version, and removing the typo in the title -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378007] New: Cannot display attached files for some weir content-type
https://bugs.kde.org/show_bug.cgi?id=378007 Bug ID: 378007 Summary: Cannot display attached files for some weir content-type Product: kmail2 Version: 4.14.10 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: eric.bru...@lps.ens.fr Target Milestone: --- I am reading some email with a pdf file attached. If I save the pdf in my home dir, I can open it without problem If I click on the attachment to open it from kmail, I have some display bugs. In fact, the temporary pdf file in /tmp/kde-*/kmail2*/ is corrupted; it is shorter than it should be. In fact, after a more careful look, every sequence of CRLF (0x0d 0x0a) has been replaced by LF (0x0a) in the binary pdf file, as though dos2unix -f had been run on it. In the email, I have the following contents-line for the attachment: --050809070702050207010502 Content-Type: =?windows-1252?q?application/pdf; name="XXX.pdf" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="XXX.pdf" Notice the windows-1252. For another mail where the Content-Type is Content-Type: application/x-pdf; then everything works perfectly. I am not familiar with mime rules, and possibly the email I was sent is faulty. But kmail should know enough to not run filters designed for text files on binary files. When googling the problem, I see that thunderbird had the same problem six years ago; see https://bugzilla.mozilla.org/show_bug.cgi?id=659355 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370975] device notifier pretends it cannot mount usb device while actually mounting it
https://bugs.kde.org/show_bug.cgi?id=370975 --- Comment #3 from Éric Brunet <eric.bru...@lps.ens.fr> --- (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
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
https://bugs.kde.org/show_bug.cgi?id=357726 --- Comment #5 from Éric Brunet <eric.bru...@lps.ens.fr> --- 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
https://bugs.kde.org/show_bug.cgi?id=354384 Éric Brunet <eric.bru...@lps.ens.fr> changed: What|Removed |Added CC||eric.bru...@lps.ens.fr --- Comment #1 from Éric Brunet <eric.bru...@lps.ens.fr> --- 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
https://bugs.kde.org/show_bug.cgi?id=359893 --- Comment #4 from Éric Brunet <eric.bru...@lps.ens.fr> --- 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
https://bugs.kde.org/show_bug.cgi?id=359893 --- Comment #1 from Éric Brunet <eric.bru...@lps.ens.fr> --- 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
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
https://bugs.kde.org/show_bug.cgi?id=356662 Éric Brunet <eric.bru...@lps.ens.fr> changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #6 from Éric Brunet <eric.bru...@lps.ens.fr> --- 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
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
https://bugs.kde.org/show_bug.cgi?id=358603 Éric Brunet <eric.bru...@lps.ens.fr> changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Éric Brunet <eric.bru...@lps.ens.fr> --- 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
https://bugs.kde.org/show_bug.cgi?id=358603 --- Comment #2 from Éric Brunet <eric.bru...@lps.ens.fr> --- 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
https://bugs.kde.org/show_bug.cgi?id=358603 --- Comment #1 from Éric Brunet <eric.bru...@lps.ens.fr> --- 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
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
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
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
https://bugs.kde.org/show_bug.cgi?id=357606 --- Comment #1 from Éric Brunet <eric.bru...@lps.ens.fr> --- 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
https://bugs.kde.org/show_bug.cgi?id=357606 --- Comment #2 from Éric Brunet <eric.bru...@lps.ens.fr> --- 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%
https://bugs.kde.org/show_bug.cgi?id=351438 Éric Brunet <eric.bru...@lps.ens.fr> 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
https://bugs.kde.org/show_bug.cgi?id=356662 --- Comment #4 from Éric Brunet <eric.bru...@lps.ens.fr> --- 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
https://bugs.kde.org/show_bug.cgi?id=356662 --- Comment #3 from Éric Brunet <eric.bru...@lps.ens.fr> --- 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
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.
