[libqapt] [Bug 370225] New: "QApt worker has either crashed or disappeared" update error from Muon

[skierpage via KDE Bugzilla]

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

Bug ID: 370225
   Summary: "QApt worker has either crashed or disappeared" update
error from Muon
   Product: libqapt
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: sit...@kde.org
  Reporter: skierp...@gmail.com

I booted into my Kubuntu 16.04 system for the first time in a month.
The Plasma Updates widget insisted my system was up to date, but I knew better,
so I ran plasma-discover-updater from the command line. That reported about 30
packages to update, I did so, confirming additional kernel packages and
entering my password. During processing, an alert appeared:
Unexpected Error - Update Manager
It appears that the QApt worker has either crashed or disappeared. Please
report a bug to the QApt maintainers.

I tried `apport --window` to report this bug but that didn't work. By now a
second alert appeared with the same contents.

So here I am. Sadly today's /var/log/dpkg.log and /var/log/apt logs were all
empty.

Reproducible: Couldn't Reproduce




I have libqapt3 Version: 3.0.2-0ubuntu1.1 and
plasma-discover-updater/plasmadiscoverupdater version 5.6.5.

I'm trying to reproduce while strace'ing qaptworker3 and now the update  seems
to be working.

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

[kio] [Bug 369399] New: No "What's this" help in Dolphin > Share > Share with Samba

[skierpage via KDE Bugzilla]

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

Bug ID: 369399
   Summary: No "What's this" help in Dolphin > Share > Share with
Samba
   Product: kio
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kfile
  Assignee: pfeif...@kde.org
  Reporter: skierp...@gmail.com

I'm running Kubuntu 16.04 with the KDE backports: Dolphin 15.12.3, KDE
Frameworks 5.23.0, and Plasma shell 5.6.5; none of these are choices in this
bug's Version field and I don't know how to tell what version of kio I have.

I'm trying to share a folder with a Windows client. In Dolphin, a folder's
Properties > Share has a promising dialog  Share with Samba. But I can't get it
to work, and none of its fields have any help to guide me.

Reproducible: Always

Steps to Reproduce:
1. Start Dolphin
2. Right-click on a directory, choose Properties > Share
3. Click the (?) in the window title bar or click Shift+F1
4. See if you can get any help for any item in the dialog.

Actual Results:  
No help.

Expected Results:  
"When the user activates the question mark button and doesn't get any help
window when clicking on a user interface element, he will get frustrated very
quickly." --
https://techbase.kde.org/Development/Architecture/KDE4/Providing_Online_Help
:-)

I was unable to find *any* documentation anywhere for the Share panel in KDE
Frameworks 5. In KDE Help Center, Dolphin help doesn't mention it and Kioslaves
> smb only documents the smb: protocol to access SMB shares, not to offer a
Samba share. Google coughs up old documentation and an old bug that the Share
panel wasn't present.

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

[Breeze] [Bug 368224] In Dolphin's Compact and Details view, my Documents folder looks like a plain document

[skierpage via KDE Bugzilla]

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

--- Comment #1 from skierpage  ---
Created attachment 100918
  --> https://bugs.kde.org/attachment.cgi?id=100918=edit
My home folder in Dolphin with Breeze

Note how Documents looks like a plain document.

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

[Breeze] [Bug 368224] New: In Dolphin's Compact and Details view, my Documents folder looks like a plain document

[skierpage via KDE Bugzilla]

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

Bug ID: 368224
   Summary: In Dolphin's Compact and Details view, my Documents
folder looks like a plain document
   Product: Breeze
   Version: 5.6.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: skierp...@gmail.com
CC: kain...@gmail.com

In Dolphin using the Breeze default Plasma 5 theme, I stumbled over my
~/Documents folder. I realized the reason I scan past it is in Details view
(and Compact view), its icon is that of a plain document. In Icons views  your
Documents folder is an emblem on top of a folder, but in the Compact and
Details you only see the emblem. This works for other special folders such as
Home, Music, and Pictures because their emblems look distinctive, but not so
well for Documents.

Reproducible: Always

Steps to Reproduce:
1. Set your theme to Breeze
2. Start Dolphin
3. Navigate to ~ (your home directory)
4. Set View > View Mode to Details or Compact

Actual Results:  
The Documents folder icon looks the same as a regular unrecognized file's icon
(foo.bar, foo.doc, etc.)

Expected Results:  
Maybe add an outline ( ⌟ ) to indicate a stack of documents.

The icon for your Documents folder is actually slightly different than a plain
foo.bar file, the document has a darker outline. But it's too subtle.

Fedora F24 KDE spin (with the package breeze-icon-theme 5.25.0.1) has the same
behavior.

FWIW
https://specifications.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html#names
calls for "emblem-documents: The icon used as an emblem for the directory where
a user's documents are stored."

In general Breeze looks great, thanks!

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

[frameworks-baloo] [Bug 364042] balooctl status and balooshow always report "Baloo Index could not be opened"

[skierpage via KDE Bugzilla]

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

--- Comment #2 from skierpage  ---
(In reply to skierpage from comment #1)

> Should I delete my ~/.local/share/baloo/index ?
I ran `balooctl stop`, renamed that file, removed index-lock, ran `balooctl
start` and I get the same "Baloo Index could not be opened" error.

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

[frameworks-baloo] [Bug 364078] baloosearch doesn't explain its -t parameter

[skierpage via KDE Bugzilla]

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

--- Comment #2 from skierpage  ---
(In reply to Stefan Brüns from comment #1)
> Types are from KFileMetadata::Type:
> https://quickgit.kde.org/?p=kfilemetadata.
> git=blob=c1a3a1130184203b7e50b174d4554b19767030f3=ec30b9c7ae739ca1e548
> 2cb6b6288fe497e021d8=src%2Ftypes.h

Thanks, I hope someone can fix the program help to say this.
https://github.com/KDE/baloo/blob/master/docs/user/searching.md also mentions
these types but omits "Folder".

> Valid Types are:
> Archive,
> Audio,
>  Video,
>  Image,
> Document,
>  Spreadsheet,
> Presentation,
> Text,
>  Folder,

Is case significant? Are these translated?
Dolphin's search dialog only supports a subset of these:
Documents, Images, Audio Files, Videos.

Sadly I can't get baloosearch to work at all, it never prints anything but
"Elapsed: 0. msecs" :-(  I'm now on version 5.23.0 on KDE Frameworks 5.23.0
and Qt 5.5.1.

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

[kio] [Bug 325574] Unable to modifying file on Android device using kio-mtp

[skierpage via KDE Bugzilla]

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

skierpage  changed:

   What|Removed |Added

 CC||skierp...@gmail.com

--- Comment #5 from skierpage  ---
Also failing on Kubuntu 16.04 with the backports PPA: 
Dolphin Version 15.12.3
Using:
* KDE Frameworks 5.23.0
* Qt 5.5.1 (built against 5.5.1)
* The xcb windowing system

There are two Device Notifier actions to "Open with File Manager". In the first
if I navigate to Downloads Dolphin's location bar shows
camera:/Motorola%2520Moto%2520X%2520(XT1058)@usb:001,004/store_00010001/Download/
. In the second it shows mtp:/XT1053/Internal storage/Download/

But with either URL I can't copy files to the device. Copying phone files from
Download or DCIM/Camera to a folder on the computer works fine.

I also have KDE Connect installed, maybe it interferes.

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

[kinfocenter] [Bug 355460] Make Information text in "About System" Kcm module selectable

[skierpage via KDE Bugzilla]

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

skierpage  changed:

   What|Removed |Added

 CC||skierp...@gmail.com

--- Comment #3 from skierpage  ---
Yes, having to retype this info is sad. A workaround is to bring up an app with
a Help >About {APP} menu item, e.g. Kate's  Help > About Kate > Version, in
which the text is often copyable.

FWIW, Firefox's about:support page (load that dummy URL in its location field)
has really nice [Copy raw data to clipboard] [Copy text to clipboard] buttons.
Probably overkill here.

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

[Discover] [Bug 362538] Misaligned GUI elements

[skierpage via KDE Bugzilla]

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

--- Comment #14 from skierpage  ---
Created attachment 8
  --> https://bugs.kde.org/attachment.cgi?id=8=edit
again Plasma Discover display glitch of details on top of update list

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

[Discover] [Bug 362538] Misaligned GUI elements

[skierpage via KDE Bugzilla]

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

--- Comment #13 from skierpage  ---
(In reply to Aleix Pol from comment #12)
> Let's assume it was an upstream bug then. If you find the issue again please
> reopen the bug.
Sorry to say, it happened again! I don't have the rights or can't see how to
reopen this bug.

Now I'm running plasma-discover{,-updater} (muondiscover{,updater}) 5.6.5 on
KDE Plasma 5.6.5, KDE Frameworks 5.23.0, Kernel 4.4.0-30-generic 64-bit.

I had several (26) updates, clicked the shield with red [x] badge soon after
booting, clicked the [Update] button in the popup menu, and clicked one of the
package names soon after the window displayed, and got the garbled display of
details on top of updates list (attachment coming). I couldn't activate any of
the buttons to clean up the display. When I tried to reproduce by running
plasma-discover from the command line, after clicking the Update tab and then a
package name I got perfect display with the expected animation sliding into the
package's details.

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

[Discover] [Bug 362538] Misaligned GUI elements

[skierpage via KDE Bugzilla]

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

--- Comment #11 from skierpage  ---
(In reply to Aleix Pol from comment #10)
> Can you guys check what Qt version you're running
In bug 362538 I wrote "I'm running KDE Frameworks 5.22.0 & QT 5.5.1 from the
KDE backport PPA on Kubuntu 16.04. FWIW, I'm now at Plasma 5.6.5 (both
plasma-discover and plasma-discover discover-updated), Frameworks 5.23.0, and
Qt 5.5.1 and I can't garbled the Discover > Updates display with 46 packages to
update.

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

[partitionmanager] [Bug 364476] New: partitionmanager can't identify iso9660 partition

[skierpage via KDE Bugzilla]

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

Bug ID: 364476
   Summary: partitionmanager can't identify iso9660 partition
   Product: partitionmanager
   Version: 1.2.1
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: skierp...@gmail.com

I'm running KDE Frameworks 5.22.0 & QT 5.5.1 from the KDE backport PPA on
Kubuntu 16.04.

I inserted a SanDisk USB flash drive I had partitioned a few years ago in
Ubuntu and mounted its partitions from the plasma panel's Device Notifier,
which showed one as "Ubuntu 14.04 LTS amd64".

Then I ran KDE Partition Manager and clicked on the SanDisk Ultra. It showed up
as /dev/sdg, with /dev/sdg1's type as "unknown"

But /etc/mtab displays the partition as 
   /dev/sdg1 /media/skierpage/Ubuntu\04014.04\040LTS\040amd64 iso9660
ro,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,mode=0400,dmode=0500
0 0

and `df -T` agrees it's an iso9660 file system. This isn't an obscure file
system, so it would be nice if partitionmanager knew about it.

Reproducible: Always

Steps to Reproduce:
1. Create an iso9661 partition on a USB, probably by dd-ing an CD-ROM image
2. Insert the USB flash drive
3. Open it in KDE Partition Manager

Actual Results:  
partitionmanager displays Type as "unknown".

Expected Results:  
/etc/mtab and `df -t`knows it's an iso9661 partition, so should
partitionmanager.

Although partitionmanager doesn't know the type, it can tell that (in my case)
964.00 MiB are Used, so it is using some API to get information about the
partition.

Its Log Output includes
"Using backend plugin: pmlibpartedbackendplugin (1)"
so maybe the problem lies in that. I have libparted2 Version: 3.2-15 installed.

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

[Discover] [Bug 362538] Misaligned GUI elements

[skierpage via KDE Bugzilla]

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

skierpage  changed:

   What|Removed |Added

 CC||skierp...@gmail.com

--- Comment #8 from skierpage  ---
(In reply to Ettore Atalan from comment #1)
> Created attachment 98726 [details]
> Screenshot of KDE Discover

I get similar garbled appearance if I click on a package name in the list of
packages to update, see bug 364436 for more details. It's happened to me on
three separate system updates.

(In reply to Aleix Pol from comment #2)
> I cannot reproduce.
With only one package update available, I can't reproduce. I'm not sure if the
bug occurs with a) more than one package to update, b) lots of packages to
update, or c) when you click on a package soon after the list appears.

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

[Discover] [Bug 363028] Updater shows one update too many

[skierpage via KDE Bugzilla]

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

--- Comment #4 from skierpage  ---
(In reply to Aleix Pol from comment #1)
> I cannot reproduce. Do you know which backends you're using?
> Please tell me the output of: plasma --listbackends

I don't have a `plasma` binary, `/usr/bin/plasma-discover --listbackends`
outputs
Available backends:
 * knscomics-backend
 * knsplasmoids-backend
 * qapt-backend

I notice that I also have a plasma-discover-updater binary with a different
appearance, its -v option outputs "plasmadiscoverupdater 5.6.4".
plasma-discover is the binary that runs when I click [update] in the Plasma
panel's update notification pop-up, its -v option outputs "muondiscover 5.6.4"

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

[Discover] [Bug 363028] Updater shows one update too many

[skierpage via KDE Bugzilla]

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

--- Comment #3 from skierpage  ---
Created attachment 99557
  --> https://bugs.kde.org/attachment.cgi?id=99557=edit
console output running Discover

This is the console output from Discover when I took attachment 99556.
Note the "KNewStuff3" output, is that obsolete?  I've upgraded my Kubuntu
installation in-place 10 times (every release since 9.04).

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

[Discover] [Bug 363028] Updater shows one update too many

[skierpage via KDE Bugzilla]

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

skierpage  changed:

   What|Removed |Added

 CC||skierp...@gmail.com

--- Comment #2 from skierpage  ---
Created attachment 99556
  --> https://bugs.kde.org/attachment.cgi?id=99556=edit
Discover showing Update (2) but only one update.

This happened to me, see screenshot. I'm running Discover 5.6.4 on KDE
Frameworks 5.22.0 & QT 5.5.1 from the KDE backport PPA on Kubuntu 16.04. After
an update I ran `/usr/bin/plasma-discover --mode update` and its header shows
"Update (2)" while there is only one System Update. The pop-up for the plasma
panel also says "1 package to update". I'll attach the output.

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

[Discover] [Bug 364436] garbled Discover display after showing package details

[skierpage via KDE Bugzilla]

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

--- Comment #1 from skierpage  ---
Created attachment 99555
  --> https://bugs.kde.org/attachment.cgi?id=99555=edit
package details appearing on top of Discover's list of packages to update

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

[Discover] [Bug 364436] New: garbled Discover display after showing package details

[skierpage via KDE Bugzilla]

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

Bug ID: 364436
   Summary: garbled Discover display after showing package details
   Product: Discover
   Version: 5.6.4
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: skierp...@gmail.com

I'm running KDE Frameworks 5.22.0 & QT 5.5.1 from the KDE backport PPA on
Kubuntu 16.04.

If I click on a package needing update in Discover, its details display on top
of the list of packages, and thereafter I can't operate the [Update] or other
buttons.

Reproducible: Always

Steps to Reproduce:
1. Wait until the Plasma notification icon's pop-up displays "Updates
available"
2. Click the [Update] button in the pop-up.
3. When Discover opens, as soon as the list of packages to update appears,
click the name of any package with an update.
4. In the header "System Update" > {package name}, click System Update.

Actual Results:  
The details of the package display on top of the list, see attachment.
In the header I can't click System Update to clean up the display.


Expected Results:  
The package details should not appear on top of the list.

This has always happened to me when I seek details about a package update. But
when filing this bug I waited a long time with Discover open, and then when I
clicked I saw an animation of the list going away, replaced by the package's
details. So the key is clicking on a package in the list soon after it draws.

The garbled display looks like attachment 98726 to bug 362538.

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

[Breeze] [Bug 364226] theme should highlight the default action in dialogs

[skierpage via KDE Bugzilla]

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

--- Comment #2 from skierpage  ---
Thanks for responding. `kate -style Fusion` draws a blue line around the
default button in settings and save dialogs, so this is specific to Breeze.

However, the Kate Replace panel (that appears in its window) does not have this
blue highlight. So my attached screenshot is misleading. And looking at Kate's
settings and save dialogs in the Breeze theme, the default action is a slightly
lighter gray.

So I think the bugs here are
* The KDE Breeze theme's indication of the default action in a dialog with a
lighter gray is too subtle.
* The GTK Breeze theme does not indicate the default buttons in dialogs with
this lighter gray, or at all.
* Kate's Replace panel doesn't indicate its default action.

Should I file new bugs or rewrite this one?

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

[plasmashell] [Bug 353998] Wish: When searching for an application via keyboard in kickoff, show on each search result the location where to find it.

[skierpage via KDE Bugzilla]

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

skierpage  changed:

   What|Removed |Added

 CC||skierp...@gmail.com

--- Comment #3 from skierpage  ---
This bothers me too.

(In reply to Thomas Pfeiffer from comment #2)
> How about putting the category in a tooltip instead of showing it
> permanently?

That could work. I would expect to find an application's category by
right-clicking and choosing Properties from the application's context menu. 
Application Launcher/Kickoff has an Edit Application... context menu item,
which is close enough to Properties.  But the "Properties for 
dialog" that this brings up doesn't indicate the application's category, and
also when you search for an application in Kickoff, for some reason its context
menu in search results is different and lacks the Edit Application... menu
item.

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

[plasmashell] [Bug 364227] New: The Super (Windows) key should launch Kickoff, like most other DEs

[skierpage via KDE Bugzilla]

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

Bug ID: 364227
   Summary: The Super (Windows) key should launch Kickoff, like
most other DEs
   Product: plasmashell
   Version: 5.6.4
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: skierp...@gmail.com
CC: plasma-b...@kde.org

I'm running KDE Frameworks 5.22.0 & QT 5.5.1 from the KDE backport PPA on
Kubuntu 16.04.

Switching to KDE after using Gnome, Unity, or Windows is pretty jarring because
the Super (Windows) key does nothing. In all those modern DEs, it opens the
application list/launcher. In KDE to start the Application Launcher (Kickoff) I
have to learn to press Alt+F1.

Reproducible: Always

Steps to Reproduce:
1. Press Super key


Actual Results:  
Nothing happens

Expected Results:  
The Super (Windows) key should open the application launcher as Alt+F1 does.
The Super key seems generally unused in KDE.

I tried the workaround of configuring this, Right-click >  Application Launcher
Settings... > Keyboard shortcuts, but pressing Super just shows Meta+...,
awaiting another key.  I don't want to press a key combination, again I just
want it to work like other desktop environments. Maybe it could be a separate
checkbox:
[ ] Pressing Super (Windows) key activates Application Launcher.

Thanks for all you do.

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

[Breeze] [Bug 364226] New: theme should highlight the default action in dialogs

[skierpage via KDE Bugzilla]

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

Bug ID: 364226
   Summary: theme should highlight the default action in dialogs
   Product: Breeze
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-de...@kde.org
  Reporter: skierp...@gmail.com

Created attachment 99463
  --> https://bugs.kde.org/attachment.cgi?id=99463=edit
In this Kate replace panel, what will happen when I press [Enter]?

I'm running KDE Frameworks 5.22.0 & QT 5.5.1 from the KDE backport PPA on
Kubuntu 16.04.

I noticed in both KDE applications and other applications (Thunderbird, GIMP,
etc.) the default action in a dialog, the one that will take place if you press
the Enter key, is not indicated. This makes it harder to operate KDE from the
keyboard. I'm using the default Breeze theme so I filed this against Breeze,
but I tried switching to Oxygen and the default button was no more apparent.

To reproduce, open some text document in Kate, press Ctrl+R to bring up
replace, and enter "a" in the Find text field and "z" in the Replace text
field. The action buttons all enable (good). At this point I really need to
know what will happen if I press the Enter key on the keyboard, but I can't
tell the buttons apart (bad). Will it do a Replace, Replace All, or Find All?

All dialogs seem to have this problem. Another example: I'm never sure in
settings dialogs whether pressing [Enter] will Apply (and stay visible) or OK
(and go away).

Expected result: the default button has some sort of indication, such as a ring
or pulse or a filled in color, like every other desktop environment I use. To
see some of the visual effects other DEs use, Google "default dialog button on
enter" and click Images.

According to http://doc.qt.io/qt-5/qdialog.html#default , Qt apps have fine
control over what button is default and which dialog items can trigger it on
pressing Enter. But KDE (or Breeze) doesn't indicate this.

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

[Breeze] [Bug 355540] Tooltips color wrong in gtk applications

[skierpage via KDE Bugzilla]

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

skierpage  changed:

   What|Removed |Added

 CC||skierp...@gmail.com

--- Comment #16 from skierpage  ---
(In reply to scionicspectre from comment #13)
> In the meantime, you should untick that checkbox if you're using Breeze.

Excellent! Fixes the problem for me (KDE Frameworks 5.22.0 backports PPA on
Kubuntu 16.04). But people shouldn't have to go to the KDE bugbase to have
legible tooltips in Gimp, Inkscape, Thunderbird, etc.  This essential
workaround should be noted in the KDE/Kubuntu/etc. release notes with something
like:

If you're using the default Breeze theme for KDE, and tooltips in non-KDE
applications such as Gimp and Thunderbird are difficult to read (white text on
gray background), then in System Settings > Color > Options for  the Breeze
theme uncheck "Apply colors to non-QT applications" and click [Apply]. (KDE bug
355540)

(This bugbase does not have a "release notes" or "document" tag.)

(In reply to Wulf from comment #7)
> after then my gtkrc-2.0 only contains: "gtk-alternative-button-order = 1"

Even after unchecking "Apply colors to non-QT applications", my
$HOME/.kde/share/config/gtkrc-2.0 has a line # created by KDE, Fri Apr 17
00:04:50 2015 and that's the modification date of the file. As well as
"gtk-alternative-button-order = 1" it has 50 lines of code, mostly setting a
style "default". Should I remove all that styling?

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

[kdeconnect] [Bug 364081] Can't Ctrl+C within a KDE Connect notification

[skierpage via KDE Bugzilla]

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

--- Comment #2 from skierpage  ---
Perhaps this is a bug in frameworks-knotifications rather than KDE Connect.

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

[kdeconnect] [Bug 364081] Can't Ctrl+C within a KDE Connect notification

[skierpage via KDE Bugzilla]

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

--- Comment #1 from skierpage  ---
Created attachment 99408
  --> https://bugs.kde.org/attachment.cgi?id=99408=edit
KDE desktop Notifications pop-up

I can select in this but Ctrl+C doesn't work.
Notice: the security code here is one-time.

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

[kdeconnect] [Bug 364081] New: Can't Ctrl+C within a KDE Connect notification

[skierpage via KDE Bugzilla]

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

Bug ID: 364081
   Summary: Can't Ctrl+C within a KDE Connect notification
   Product: kdeconnect
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: plasmoid
  Assignee: albertv...@gmail.com
  Reporter: skierp...@gmail.com

I'm using the KDE PPA on Kubuntu 16.04. Despite the instructions on
bugs.kde.org there's no Help | About menu for the KDE Connect application, but
`kdeconnect-cli --version` reports 0.9.

I got a text in Signal on my phone and a KDE Notification popped up with the
contents of it (fantastic!). I could select the text in this notification with
my mouse, but Ctrl+C did not copy it.

Reproducible: Always

Steps to Reproduce:
1. Run KDE Connect on your phone and desktop.
2. Receive a SMS text on your phone. You may have to run Signal rather than the
default Android messaging app.
3. In the KDE desktop "Notifications" window that appears, select some text
from the text message.
4. Press Ctrl+C

Actual Results:  
The text you selected is not copied.

Expected Results:  
Why not let Ctrl+C work? Most of the texts I get on my phone are 2-factor
authentication confirmation codes, so it is very convenient to copy straight
from the notification.

The workaround is to right-click in the Notifications pop-up and choose Copy.

I notice that in KDE Connect's own pop-up window, you can't select text. That
seems a separate bug, and one shared with the Networks pop-up, etc.

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

[frameworks-baloo] [Bug 364078] New: baloosearch doesn't explain its -t parameter

[skierpage via KDE Bugzilla]

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

Bug ID: 364078
   Summary: baloosearch doesn't explain its -t  parameter
   Product: frameworks-baloo
   Version: 5.22.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: skierp...@gmail.com
CC: pinak.ah...@gmail.com

What do you specify in typeStr? `baloosearch -h` doesn't say, and it has no man
page.

Reproducible: Always

Steps to Reproduce:
1. Enter `baloosearch` in a terminal
2. Enter `man baloosearch` in a terminal


Actual Results:  
  -t, --type  Type of data to be searched

  No manual entry for baloosearch

Is typeStr a mime type or file extension? Or is it metadata like search by date
modified, EXIF tag, mp3 title?  Can you enter more than one?

Expected Results:  
A better hint in usage.  Either add a man page or provide a URL in the Usage
string with more explanation.

https://community.kde.org/Baloo/Debugging and other pages don't explain
typeStr.

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

[frameworks-baloo] [Bug 364042] balooctl status and balooshow always report "Baloo Index could not be opened"

[skierpage via KDE Bugzilla]

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

skierpage  changed:

   What|Removed |Added

Summary|balooctl status always  |balooctl status and
   |reports "Baloo Index could  |balooshow always report
   |not be opened"  |"Baloo Index could not be
   ||opened"

--- Comment #1 from skierpage  ---
I added a test file and Dolphin's Find by Content can find it, but`balooshow
~/Documents/baloo_test1.txt` also fails with
   kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties
of Q*Application: no instance (yet) existing.
  The Baloo index could not be opened. Please run "balooctl status" to see if
Baloo is enabled and working.

Under strace this balooshow command likewise makes a failed
  mmap(NULL, 5368709120, PROT_READ, MAP_SHARED, 5, 0) = -1 ENOMEM (Cannot
allocate memory)
system call just before it prints this error.

Should I delete my ~/.local/share/baloo/index ?

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

[frameworks-baloo] [Bug 364042] New: balooctl status always reports "Baloo Index could not be opened"

[skierpage via KDE Bugzilla]

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

Bug ID: 364042
   Summary: balooctl status always reports "Baloo Index could not
be opened"
   Product: frameworks-baloo
   Version: 5.22.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: balooctl
  Assignee: m...@vhanda.in
  Reporter: skierp...@gmail.com
CC: pinak.ah...@gmail.com

I was running Kubuntu 16.04, then set up the Kubuntu Backports PPA to run newer
KDE.

In both, `balooctl status` always reports "Baloo Index could not be opened".

In ~/.local/share/baloo I have a 293 MB index and 8192 index-lock, both
modified recently.

I ran `strace balooctl status` and found that shortly before printing this
error, balooctl attempts
  mmap(NULL, 5368709120, PROT_READ, MAP_SHARED, 12, 0) = -1 ENOMEM (Cannot
allocate memory)
where fd 12 is ~/.local/share/baloo/index. I don't have 5,368,709,120 bytes of
RAM :-)

Reproducible: Always

Steps to Reproduce:
1. balooctl status

Actual Results:  
Baloo Index could not be opened

Expected Results:  
Why can't it open ~/.local/share/baloo/index ?

 "Could not open Baloo Index at " would be a better error message.

Baloo is working somewhat; in Dolphin I can find some files in my home
directory by content.

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