[user-manager] [Bug 371663] New: Saving Avatar as .face is totally broken

[richardlm via KDE Bugzilla]

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

Bug ID: 371663
   Summary: Saving Avatar as .face is totally broken
   Product: user-manager
   Version: 5.8.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: kcontrol module
  Assignee: j...@jriddell.org
  Reporter: richard.l...@gmail.com

I'm referring to the saving of the avatar as .face and .face icon (link to the
former file) for displaying the avatar on the SDDM login screen (which also
doesn't work but I guess this is another issue).

So one can change the avatar of any user as many times as one would like,
however the .face & link file is only created once and never recreated/updated
afterwards.

(The avatar displayed in the user manager is apparently saved somewhere else.)

Reproducible: Always

Steps to Reproduce:
1. Set avatar for new user
2. Notice how .face is created accordingly.
3. Change avatar (or delete .face in home of new user)

Actual Results:  
No new .face and .face.icon is created

Expected Results:  
New .face and .face.icon is created upon change of avatar.

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

[korganizer] [Bug 332441] Remove Lock from Events View and move it to the Calendar Source instead

[richardlm via KDE Bugzilla]

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

richardlm  changed:

   What|Removed |Added

 Status|NEEDSINFO   |UNCONFIRMED
Version|4.12.2  |5.3.0
 Resolution|WAITINGFORINFO  |---

--- Comment #2 from richardlm  ---
When I add http://www.kde.org/releaseschedule.ics to KOrganizer, I don't see
the events at all!
(For example KDE Applications 16.04 Dependency Freeze - 20160316)

So I don't really know.

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

[korganizer] [Bug 332441] Remove Lock from Events View and move it to the Calendar Source instead

[richardlm via KDE Bugzilla]

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

--- Comment #3 from richardlm  ---
PS:
Bumped version accordingly.

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

[systemsettings] [Bug 371636] New: Allow to choose Background Images from Wallpapers / Gallery

[richardlm via KDE Bugzilla]

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

Bug ID: 371636
   Summary: Allow to choose Background Images from Wallpapers /
Gallery
   Product: systemsettings
   Version: 5.8.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: kcm_sddm
  Assignee: k...@davidedmundson.co.uk
  Reporter: richard.l...@gmail.com

Currently when one wants to set a custom background he is only presented with a
file picker. It is not possible to select pictures from the wallpapers gallery.
This is really bad from user perspective, because one can use GHNS to get new
wallpapers, but they are stored somewhere (nobody knows), so one cannot select
them as a background.

Therefore I suggest to present two options upon click on set background image:
- Choose from Gallery... 
- Load from File...
(and Clear)

This is also how it is handled in the select avatar option of the user manager
KCM.

Reproducible: Always

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

[dolphin] [Bug 368010] Paste from Menu and Shortcut (Ctrl+V) is broken on SMB / FTP Shares

[richardlm via KDE Bugzilla]

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

richardlm  changed:

   What|Removed |Added

Summary|Paste and Ctrl+V is broken  |Paste from Menu and
   |on SMB / FTP Shares |Shortcut (Ctrl+V) is broken
   ||on SMB / FTP Shares

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

[kate] [Bug 367713] Improve Search highlighting Scroll-bar Minimap

[richardlm via KDE Bugzilla]

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

--- Comment #3 from richardlm  ---
(In reply to Kåre Särs from comment #2)
> Thanks for the report.
> 
YW!

> 1) Yes black is not the optimal color. Yellow is not so good on light
> themes. The color should probably be configurable/use a theme color.
> 
I would advise against yet another option. Also sane defaults are needed anyway
(to quote the VDG). If the color is good for the text view, why isn't it
sufficient for the minimap?

> 2) Marking only the match is not an option. If you want that you can turn
> off the scrollbar marks and get the yellow from the mini-map highlight
> colors. In large documents you would not be able to distinguish the results
> as they are merged with the surrounding text.
I can't follow your advice, can you explain it in more detail?
If I turn scrollbar marks off, I don't see any marks at all on the scrollbar.

Can the minimap algorithm be tuned so that the match doesn't vanish?

If still using the weird boxes, please place them at least behind (as
background) on the minimap.

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

[marble] [Bug 367717] New: Map Print is not practicable - to low resolution

[richardlm via KDE Bugzilla]

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

Bug ID: 367717
   Summary: Map Print is not practicable - to low resolution
   Product: marble
   Version: 2.0 (KDE Applications 16.08)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: richard.l...@gmail.com

When using the print function, the resolution on the paper is way too low.
Everything is pixelated and NOT readable.
In the options I already set the quality to print quality, however this didn't
changed a thing.

Reproducible: Always

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

[kate] [Bug 367713] Improve Search highlighting Scroll-bar Minimap

[richardlm via KDE Bugzilla]

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

--- Comment #1 from richardlm  ---
Created attachment 100725
  --> https://bugs.kde.org/attachment.cgi?id=100725=edit
Screenshot

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

[kate] [Bug 367713] New: Improve Search highlighting Scroll-bar Minimap

[richardlm via KDE Bugzilla]

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

Bug ID: 367713
   Summary: Improve Search highlighting Scroll-bar Minimap
   Product: kate
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: richard.l...@gmail.com

Please improve the Search highlighting in the Scroll-bar Minimap.
Currently the highlighting is in form black boxes on the minimap (see attached
screenshot).

My Suggestions:
1. The searched string in the text field is highlighted in yellow, so please
use that very same color in the minimap as well. (Black has also poor contrast
on dark theme.)
2. Since this is an actual minimap, please mark only the very exact string
instead of of these big boxes. With the current implementation the minimap
feature is lost (since it is all black) and it is not clear where exactly
(column) the string is.

Thx


Reproducible: Always

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

[kate] [Bug 367710] New: Enable highlighting in Scroll-bar Minimap for (just) Find

[richardlm via KDE Bugzilla]

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

Bug ID: 367710
   Summary: Enable highlighting in Scroll-bar Minimap for (just)
Find
   Product: kate
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: richard.l...@gmail.com

The highlighting of searched strings in the scroll-bar minimap is very cool
feature, however in its current implementation it has very poor ease of access
and poor use.
Why? Because it is only shown when using the "Search & Replace" (S) dialog
but not when using "Find". This is bad for several reasons:
1.  Often (here 99% of the time) one just wants to find text and not replace,
so one wouldn't open S in the first place.
2. Kwrite doesn't has S (or it has also very poor ease of access), hence this
feature isn't there available at all.
3. S is way too complicated for the average (non-developer) user.
4. S takes up way too much space (screen estate) of the window.

-> Therefore I propose to enable the Search highlighting in Scroll-bar Minimap
for Find.

Which really should be a no-brainer and I'm kind of disappointed that one has
to write a bug-report for such an obvious thing. I mean look at chromium, adobe
pdf, etc. everywhere it is enabled on find, why  would you make such a feature
so hidden, really??
/rant

Reproducible: Always

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

[okular] [Bug 367671] "Open in File Manager" in Open Dialog doesn't work

[richardlm via KDE Bugzilla]

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

--- Comment #1 from richardlm  ---
Created attachment 100716
  --> https://bugs.kde.org/attachment.cgi?id=100716=edit
Strange dialog

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

[okular] [Bug 367671] New: "Open in File Manager" in Open Dialog doesn't work

[richardlm via KDE Bugzilla]

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

Bug ID: 367671
   Summary: "Open in File Manager" in Open Dialog doesn't work
   Product: okular
   Version: 0.25.80
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: richard.l...@gmail.com

Sometimes one wants to open the File Manager from the Open dialog.

This works here for kate, kwrite, etc - but not in Okular.

Reproducible: Always

Steps to Reproduce:
1. File -> Open
2. Right click -> Open in File Manager

Actual Results:  
Strange dialog pops up (see attachment).

Expected Results:  
File Manager opens at given location

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

[print-manager] [Bug 365804] Print Dialog doesn't respect Printer Hierarchy / Order

[richardlm via KDE Bugzilla]

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

--- Comment #4 from richardlm  ---
(In reply to Christoph Feck from comment #1)
> Please state which you want fixed: The system settings module, or the print
> dialog.

Sorry, but I don't know - I want them to be in "sync", I don't know where you
would actually fix this.

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

[print-manager] [Bug 365804] Print Dialog doesn't respect Printer Hierarchy / Order

[richardlm via KDE Bugzilla]

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

--- Comment #3 from richardlm  ---
Created attachment 100711
  --> https://bugs.kde.org/attachment.cgi?id=100711=edit
screenshot

Ooops, seems like I forgot the actual screenshot - here you go.

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

[print-manager] [Bug 365804] New: Print Dialog doesn't respect Printer Hierarchy / Order

[richardlm via KDE Bugzilla]

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

Bug ID: 365804
   Summary: Print Dialog doesn't respect Printer Hierarchy / Order
   Product: print-manager
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dantt...@gmail.com
  Reporter: richard.l...@gmail.com

When opening the print dialog from any app, the printer in the printer list are
ordered in an alphabetic order. However in the printer system settings module,
they are not!
See attached screenshot for example.

This creates unnecessary confusion. The printer order should be the same in
both.

Reproducible: Always

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

[print-manager] [Bug 341780] when adding printer error "Failed to group devices"

[richardlm via KDE Bugzilla]

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

richardlm  changed:

   What|Removed |Added

 CC||richard.l...@gmail.com

--- Comment #4 from richardlm  ---
I also get the 
Failed to group devices: 'The name org.fedoraproject.Config.Printing was not
provided by any .service files'
error here (Chakra with latest KF5).

So can someone explain, is this an packaging error or KF5 related?

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

[print-manager] [Bug 337974] wish: support multiple instances of the same printer (with different defaults)

[richardlm via KDE Bugzilla]

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

richardlm  changed:

   What|Removed |Added

 CC||richard.l...@gmail.com

--- Comment #1 from richardlm  ---
Yes, I can confirm this use-case (also for color vs b/w printing) and would
also highly appreciate such a feature!

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

[okular] [Bug 361487] Stream Files instead of creating local copy

[richardlm via KDE Bugzilla]

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

--- Comment #4 from richardlm  ---
Well, IMHO memory is plenty.
And as long as the file is open in okular, isn't it anyways in cache/memory or
does it load from disk for each new page?

Still when using a local copy, would it be possible to:
a) open the file instantaneous (after the first 100kb downloaded) - INSTEAD of
waiting for the whole file to download?
b) Have the whole copy and examinating pop-ups hidden from the user?

Ty

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

[dolphin] [Bug 361490] Opening of files on password protected SMB share fails

[richardlm via KDE Bugzilla]

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

--- Comment #4 from richardlm  ---
Seems to me some sort of "interconnection" issue, because the credentials are
provided in dolphin, but somehow aren't passed to okular.

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

[plasmashell] [Bug 363318] New: Lock / Logout Widget

[richardlm via KDE Bugzilla]

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

Bug ID: 363318
   Summary: Lock / Logout Widget
   Product: plasmashell
   Version: 5.6.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: richard.l...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

The Lock / Logout Widget has several issues:
a) The "Leave" button, has the icon of the "Shutdown" action
b) In the options the "Shutdown" option is missing
c) The symbols are on a non-transparent background

Reproducible: Always

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

[okular] [Bug 362219] Missing Version Tab in About Okular Dialog

[richardlm via KDE Bugzilla]

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

richardlm  changed:

   What|Removed |Added

 Resolution|INVALID |---
 Status|RESOLVED|UNCONFIRMED

--- Comment #3 from richardlm  ---
(In reply to Albert Astals Cid from comment #2)
> You can see the version on the top part, can't you?

> In the About-Dialog I'm missing the "Version" - Tab, which give detailed
> information about Qt & KF-Version and windowing system.


Do you need to code this by hand, isn't there some shared code for this?

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

[okular] [Bug 362219] New: Missing Version Tab in About Okular Dialog

[richardlm via KDE Bugzilla]

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

Bug ID: 362219
   Summary: Missing Version Tab in About Okular Dialog
   Product: okular
   Version: 0.24.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: richard.l...@gmail.com

In the About-Dialog I'm missing the "Version" - Tab, which give detailed
information about Qt & KF-Version and windowing system.

See attached screenshot with Kate example.

Reproducible: Always

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

[okular] [Bug 361490] Opening of files on password protected SMB share fails

[richardlm via KDE Bugzilla]

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

--- Comment #2 from richardlm  ---
(In reply to Albert Astals Cid from comment #1)
> Let me make sure i understand this correct:
>  * if you use okular to open the file, it works
If I use the File - Open dialog in okular it works.

>  * if you dolphin to open the file, it fails
If I click the file in dolphin, okular opens, but with error message.

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

[okular] [Bug 361490] New: Opening of files on password protected SMB share fails

[richardlm via KDE Bugzilla]

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

Bug ID: 361490
   Summary: Opening of files on password protected SMB share fails
   Product: okular
   Version: 0.24.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: richard.l...@gmail.com

I cannot open pdf files with okular on my password protected smb-share

Reproducible: Always

Steps to Reproduce:
1. In dolphin open pdf file on password protected smb share


Actual Results:  
Okular opens with following error message:
"Could not open smb://diskstation/test.pdf. Reason: The file or folder
smb://diskstation/test.pdf does not exist."

Expected Results:  
Okular opens the pdf file

If I do in okular:
1. File -> Open...
2. browse to my smb-share
-> Dialog pop-up and asks for my credentials + password
3. Enter credentials + password
4. continue browsing to file
5. open file
6. file is correctly opened in okular

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

[okular] [Bug 361487] New: Stream Files instead of creating local copy

[richardlm via KDE Bugzilla]

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

Bug ID: 361487
   Summary: Stream Files instead of creating local copy
   Product: okular
   Version: 0.24.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: richard.l...@gmail.com

I have pdf's on a local NAS which I access via smb (or ftp - behavior is the
same) with dolphin.

When I click on a pdf, first of all copy dialog appears and then okular opens
the local copy.
This has several disadvantages:
- Unnecessary slow (one has to wait for the copy of the whole file, instead of
an instant open)
- It is not possible to see changes on the pdf file by reloading (F5)
- Unnecessary local disk usage / fragmentation, etc
- Unnecessary UI clutter/popups/notification (Copy dialog, examination
finished, etc.)

So I propose that okular should "stream" the file from the NAS server, instead
of creating a local copy.

This is the open command for pdfs in my file type properties:
"okular %U %i -caption %c"

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

[partitionmanager] [Bug 360564] Format / recreate File System keep Label

[richardlm via KDE Bugzilla]

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

richardlm  changed:

   What|Removed |Added

   Keywords||usability

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

[partitionmanager] [Bug 360564] New: Format / recreate File System keep Label

[richardlm via KDE Bugzilla]

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

Bug ID: 360564
   Summary: Format / recreate File System keep Label
   Product: partitionmanager
   Version: 2.0.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: richard.l...@gmail.com

Upon recreating a file system from the "Properties" dialog the label is lost,
although one is entered in the properties dialog.

It would be good if the label is kept on formatting, so that one doesn't have
to reset it after formatting.

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

[partitionmanager] [Bug 360556] Change default filesystem suggestion

[richardlm via KDE Bugzilla]

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

richardlm  changed:

   What|Removed |Added

   Keywords||usability

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

[partitionmanager] [Bug 360554] Cache / Save Pending Operations on Error

[richardlm via KDE Bugzilla]

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

richardlm  changed:

   What|Removed |Added

   Keywords||usability

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

[partitionmanager] [Bug 360554] New: Cache / Save Pending Operations on Error

[richardlm via KDE Bugzilla]

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

Bug ID: 360554
   Summary: Cache / Save Pending Operations on Error
   Product: partitionmanager
   Version: 2.0.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: richard.l...@gmail.com

When during the operation an error occures, the whole (pending) operations list
is cleared.

This is annoying and unneeded, because if there is an actual mistake with the
choice of operations it can still be cleared by hand. However when only a small
mistake triggered the error (I had a mount point open), one has to redo all the
steps, although a simple unmount fixes the error.

Therefore I propose to keep the list of pending operations after an error
occured - on a succesfull run the list should still be cleared.

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

[partitionmanager] [Bug 359819] New: Add support for more partition types

[richardlm via KDE Bugzilla]

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

Bug ID: 359819
   Summary: Add support for more partition types
   Product: partitionmanager
   Version: 2.0.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: richard.l...@gmail.com

Due to an installation of linux on BIOS system with GPT partitioning, I noticed
that the "Bios boot" partition type is not supported by KPM. It wrongly lists
the partition as ext4 partition.

I created the "bios boot" partition with fdisk, which also gives a list of
known partition types:
# fdisk /dev/sda

Welcome to fdisk (util-linux 2.27). 
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): l
  1 EFI System C12A7328-F81F-11D2-BA4B-00A0C93EC93B
  2 MBR partition scheme   024DEE41-33E7-11D3-9D69-0008C781F39F
  3 Intel Fast Flash   D3BFE2DE-3DAF-11DF-BA40-E3A556D89593
  4 BIOS boot  21686148-6449-6E6F-744E-656564454649
  5 Sony boot partitionF4019732-066E-4E12-8273-346C5641494F
  6 Lenovo boot partition  BFBFAFE7-A34F-448A-9A5B-6213EB736C22
  7 PowerPC PReP boot  9E1A2D38-C612-4316-AA26-8B49521E5A8B
  8 ONIE boot  7412F7D5-A156-4B13-81DC-867174929325
  9 ONIE configD4E6E2CD-4469-46F3-B5CB-1BFF57AFC149
 10 Microsoft reserved E3C9E316-0B5C-4DB8-817D-F92DF00215AE
 11 Microsoft basic data   EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
 12 Microsoft LDM metadata 5808C8AA-7E8F-42E0-85D2-E1E90434CFB3
 13 Microsoft LDM data AF9B60A0-1431-4F62-BC68-3311714A69AD
 14 Windows recovery environment   DE94BBA4-06D1-4D40-A16A-BFD50179D6AC
 15 IBM General Parallel Fs37AFFC90-EF7D-4E96-91C3-2D7AE055B174
 16 Microsoft Storage Spaces   E75CAF8F-F680-4CEE-AFA3-B001E56EFC2D
 17 HP-UX data 75894C1E-3AEB-11D3-B7C1-7B03A000
 18 HP-UX service  E2A1E728-32E3-11D6-A682-7B03A000
 19 Linux swap 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F
 20 Linux filesystem   0FC63DAF-8483-4772-8E79-3D69D8477DE4
 21 Linux server data  3B8F8425-20E0-4F3B-907F-1A25A76F98E8
 22 Linux root (x86)   44479540-F297-41B2-9AF7-D131D5F0458A
 23 Linux root (ARM)   69DAD710-2CE4-4E3C-B16C-21A1D49ABED3
 24 Linux root (x86-64)4F68BCE3-E8CD-4DB1-96E7-FBCAF984B709
 25 Linux root (ARM-64)B921B045-1DF0-41C3-AF44-4C6F280D3FAE
 26 Linux reserved 8DA63339-0007-60C0-C436-083AC8230908
 27 Linux home 933AC7E1-2EB4-4F13-B844-0E14E2AEF915
 28 Linux RAID A19D880F-05FC-4D3B-A006-743F0F84911E
 29 Linux extended bootBC13C2FF-59E6-4262-A352-B275FD6F7172
 30 Linux LVM  E6D6D379-F507-44C2-A23C-238F2A3DF928
 31 FreeBSD data   516E7CB4-6ECF-11D6-8FF8-00022D09712B
 32 FreeBSD boot   83BD6B9D-7F41-11DC-BE0B-001560B84F0F
 33 FreeBSD swap   516E7CB5-6ECF-11D6-8FF8-00022D09712B
 34 FreeBSD UFS516E7CB6-6ECF-11D6-8FF8-00022D09712B
 35 FreeBSD ZFS516E7CBA-6ECF-11D6-8FF8-00022D09712B
 36 FreeBSD Vinum  516E7CB8-6ECF-11D6-8FF8-00022D09712B
 37 Apple HFS/HFS+ 48465300--11AA-AA11-00306543ECAC
 38 Apple UFS  55465300--11AA-AA11-00306543ECAC
 39 Apple RAID 52414944--11AA-AA11-00306543ECAC
 40 Apple RAID offline 52414944-5F4F-11AA-AA11-00306543ECAC
 41 Apple boot 426F6F74--11AA-AA11-00306543ECAC
 42 Apple label4C616265-6C00-11AA-AA11-00306543ECAC
 43 Apple TV recovery  5265636F-7665-11AA-AA11-00306543ECAC
 44 Apple Core storage 53746F72-6167-11AA-AA11-00306543ECAC
 45 Solaris boot   6A82CB45-1DD2-11B2-99A6-080020736631
 46 Solaris root   6A85CF4D-1DD2-11B2-99A6-080020736631
 47 Solaris /usr & Apple ZFS   6A898CC3-1DD2-11B2-99A6-080020736631
 48 Solaris swap   6A87C46F-1DD2-11B2-99A6-080020736631
 49 Solaris backup 6A8B642B-1DD2-11B2-99A6-080020736631
 50 Solaris /var   6A8EF2E9-1DD2-11B2-99A6-080020736631
 51 Solaris /home  6A90BA39-1DD2-11B2-99A6-080020736631
 52 Solaris alternate sector   6A9283A5-1DD2-11B2-99A6-080020736631
 53 Solaris reserved 1 6A945A3B-1DD2-11B2-99A6-080020736631
 54 Solaris reserved 2 6A9630D1-1DD2-11B2-99A6-080020736631
 55 Solaris reserved 3 6A980767-1DD2-11B2-99A6-080020736631
 56 Solaris reserved 4 6A96237F-1DD2-11B2-99A6-080020736631
 

[konversation] [Bug 359285] New: Join Channel by doubleclick

[richardlm via KDE Bugzilla]

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

Bug ID: 359285
   Summary: Join Channel by doubleclick
   Product: konversation
   Version: 1.6
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: konversation-de...@kde.org
  Reporter: richard.l...@gmail.com

When having the bottom tabs, it would be nice to get a new tab by double
clicking in that same row. E.g. like it is in Dolphin, Kate, others(?)

In the case of Konversation a new tab would (probably) mean "Join a channel",
so the "join Channel" dialog should pop-up on dbl click.

Reproducible: Always

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

[plasmashell] [Bug 359270] Notifications do not pop up from actual widget position

[richardlm via KDE Bugzilla]

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

richardlm  changed:

   What|Removed |Added

 Status|RESOLVED|UNCONFIRMED
 Resolution|INVALID |---

--- Comment #3 from richardlm  ---
> It's not supposed to.
Uh, thats sad... :-/

Can I mark this as an feature request / wishlist then or is this impossible to
add?

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

[plasmashell] [Bug 359268] Pop-up of (single) Notification widget is too small

[richardlm via KDE Bugzilla]

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

--- Comment #4 from richardlm  ---
I see.

>  The notification applet is actually not meant to be used out of the systray 
> popup,
> even though technically possible.
IMHO this technical possibility is a great feature, so it would be nice if the
pop-ups would work just as nice.

Can I just change the component field or do I need to fill a new one?

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

[plasmashell] [Bug 359270] Notifications do not pop up from actual widget position

[richardlm via KDE Bugzilla]

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

--- Comment #1 from richardlm  ---
Created attachment 97149
  --> https://bugs.kde.org/attachment.cgi?id=97149=edit
Example of Issue

PS: This applies both to a moved systray widget, but also for a stand-alone
notification widget.

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

[plasmashell] [Bug 359268] Pop-up of (single) Notification widget is too small

[richardlm via KDE Bugzilla]

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

--- Comment #1 from richardlm  ---
Created attachment 97147
  --> https://bugs.kde.org/attachment.cgi?id=97147=edit
Stand-alone notification widget pop-up

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

[plasmashell] [Bug 359268] Pop-up of (single) Notification widget is too small

[richardlm via KDE Bugzilla]

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

--- Comment #2 from richardlm  ---
Created attachment 97148
  --> https://bugs.kde.org/attachment.cgi?id=97148=edit
Default Notification pop-up

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

[plasmashell] [Bug 359270] New: Notifications do not pop up from actual widget position

[richardlm via KDE Bugzilla]

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

Bug ID: 359270
   Summary: Notifications do not pop up from actual widget
position
   Product: plasmashell
   Version: 5.5.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Notifications
  Assignee: mklape...@kde.org
  Reporter: richard.l...@gmail.com
CC: plasma-b...@kde.org

In my setup I have the panel with notification widget on my right screen edge.
However the notification do not pop up from the widget position, but from the
bottom right.

Reproducible: Always

Steps to Reproduce:
1. Move your default panel to the right screen edge
2. In Terminal enter: kdialog --passivepopup "hello there"


Actual Results:  
Notification pop ups from bottom right

Expected Results:  
Notification pops from the notification widget.

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

[plasmashell] [Bug 359268] New: Pop-up of (single) Notification widget is too small

[richardlm via KDE Bugzilla]

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

Bug ID: 359268
   Summary: Pop-up of (single) Notification widget is too small
   Product: plasmashell
   Version: 5.5.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Notifications
  Assignee: mklape...@kde.org
  Reporter: richard.l...@gmail.com
CC: plasma-b...@kde.org

When using the single notification widget (and not that one which is included
in the systray widget); the pop-up of that widget is considerable smaller and
too small IMHO.

Also I'm missing the headline "Notifications" in the single widget pop-up.

See screenshots for comparison.

Reproducible: Always

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

[plasmashell] [Bug 340729] Two notifications when two default panels on the same screen are present

[richardlm via KDE Bugzilla]

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

richardlm  changed:

   What|Removed |Added

 CC||richard.l...@gmail.com

--- Comment #3 from richardlm  ---
I cannot reproduce this here.

Also I would like to add, that if someone has a desktop spreading across
multiple monitors he might want to have EXACTLY this behavior (a pop-up for
each notification widget, probably on each monitor).

Whereas for the other case (multiple notification widgets on the same monitor)
it is really easy to hide the notification widget from the systray and hence
receiving only one pop-up.

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

[dolphin] [Bug 359230] New: Context Menu: Root Actions is broken

[richardlm via KDE Bugzilla]

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

Bug ID: 359230
   Summary: Context Menu: Root Actions is broken
   Product: dolphin
   Version: 15.12.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: richard.l...@gmail.com

In Configure Dolphin -> Services:
the action:
"Root actions: Open Terminal here"
appears twice.
Further more when trying to disable the  first entry there is a weird behavior,
because it is somehow linked to 2nd entry.

And finally after toggling these entries my context sub menu for root actions
is broken.


Reproducible: Always

Steps to Reproduce:
1. Configure Dolphin -> Services
2. Toggle "Root actions: Open Terminal here"
3. Apply

Actual Results:  
Broken (sub) context menu for root action (see attached screenshot)

Expected Results:  
Corrected root actions sub menu

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

[dolphin] [Bug 359230] Context Menu: Root Actions is broken

[richardlm via KDE Bugzilla]

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

--- Comment #1 from richardlm  ---
Created attachment 97132
  --> https://bugs.kde.org/attachment.cgi?id=97132=edit
Broken root-actions context menu

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

[Breeze] [Bug 343369] Menu in QtQuickControls Combo Box on Breeze Dark Theme Unreadable

[richardlm via KDE Bugzilla]

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

richardlm  changed:

   What|Removed |Added

 CC||richard.l...@gmail.com

--- Comment #19 from richardlm  ---
Same here.

However I was wondering if this actual theme related or by the (combo box)
implementation in the GUI.

For Example:
System Settings -> Multimedia -> Audio Volume -> Configuration
The combo boxes here doesn't follow color sheme, but they also appear rather
random on the screen (see attachment 96556).
Where as in
System Settings -> Multimedia -> Audio and Video -> Audio Hardware Setup
Combo box follows color sheme and is correctly placed.

HTH

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