[Crow Translate] [Bug 494043] Target Language Code invalid for Persian

2024-10-06 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=494043

Gena  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Gena  ---
Thanks, fixed in the latest master.

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

[Crow Translate] [Bug 493455] Duplicate shortcuts

2024-09-22 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=493455

--- Comment #3 from Gena  ---
Shift is usually for in-app shortcuts. Alt is for global... Maybe change
letters?..

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

[Crow Translate] [Bug 493455] Duplicate shortcuts

2024-09-21 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=493455

--- Comment #1 from Gena  ---
Thanks for the report! I will change the default shortcuts. What shortcuts
would you suggest?
In the meanwhile, you can just remove these shortcuts from Crow in the system
settings.

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

[Crow Translate] [Bug 491011] Language autodetection after switching to the Mozhi

2024-09-12 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=491011

--- Comment #8 from Gena  ---
Fixed, already available in https://mozhi.aryak.me instance.

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

[Crow Translate] [Bug 491011] Language autodetection after switching to the Mozhi

2024-09-09 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=491011

--- Comment #7 from Gena  ---
Sure :)

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

[Crow Translate] [Bug 491011] Language autodetection after switching to the Mozhi

2024-09-09 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=491011

Gena  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|REOPENED|RESOLVED

--- Comment #5 from Gena  ---
Ah, I see, so the response parsed correctly and the problem is in quotes. But I
escape them on the app side, this is why I suspected that the bug was in
parsing.

I tried using Mozhi web interface and it have the same issue. I reported it
here: https://codeberg.org/aryak/libmozhi/issues/6, it's a bug on their side.
They added autodetection for Yandex, BTW.

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

[Crow Translate] [Bug 491011] Language autodetection after switching to the Mozhi

2024-09-09 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=491011

--- Comment #3 from Gena  ---
The text is escaped properly, the issue is response parsing.
Could you send me the output of the translation using CLI with `--json`?

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

[extra-cmake-modules] [Bug 492753] New: KDE_INSTALL_DATAROOTDIR points to share on Windows

2024-09-07 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=492753

Bug ID: 492753
   Summary: KDE_INSTALL_DATAROOTDIR points to share on Windows
Classification: Frameworks and Libraries
   Product: extra-cmake-modules
   Version: 6.5.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ecm-bugs-n...@kde.org
  Reporter: genalo...@gmail.com
  Target Milestone: ---

SUMMARY

In KDEInstallDirs `DATAROOTDIR` points to `share` on Windows. But it should be
`/data`. This is where Qt will look on Windows (See
`GenericDataLocation` in https://doc.qt.io/qt-6/qstandardpaths.html). Docs
(https://api.kde.org/ecm/kde-module/KDEInstallDirs5.html) also say that
`DATAROOTDIR` on Windows points to `/data`.

The code also looks like it should also use `/data`:
https://invent.kde.org/frameworks/extra-cmake-modules/-/blob/master/kde-modules/KDEInstallDirsCommon.cmake#L271

But the `_define_relative` tries to take this variable from GNUInstallDirs
module if `KDE_INSTALL_DIRS_NO_CMAKE_VARIABLES` is not set (by default):
https://invent.kde.org/frameworks/extra-cmake-modules/-/blob/master/kde-modules/KDEInstallDirsCommon.cmake#L93
But In GNUInstallDirs the `DATAROOTDIR` is defined as `share` which leads to
the bug.

STEPS TO REPRODUCE
1. `include(KDEInstallDirs)`
2. `message(${KDE_INSTALL_DATAROOTDIR})

OBSERVED RESULT

Prints `share`.

EXPECTED RESULT

Prints `bin/data`.

SOFTWARE/OS VERSIONS
Windows: 10

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

[Crow Translate] [Bug 491011] Language autodetection after switching to the Mozhi

2024-07-30 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=491011

Gena  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG

--- Comment #1 from Gena  ---
> But, it's not 100% clear if the Mozhi (by the way, it sounds symbolically on 
> the Russian: "brain" ;) ) in turn gather what I send via it to the Google or 
> any other translator.

The name pronounced as "moli" :) But Mozhi is much more secure. Instead of
sending your data to an engine from your IP, it receives the IP of the
instance. Consider it's as a proxy. You can even create your own instance if
you worry about the instance being compromised.

> The second issue is in that the new approach works noticeably slower.

Try to choose an instance that is close to you. For me it depends on the
instance.

But the main migration reason was maintainability, security and more engines
support. Online engines often breaks and there is literally zero documentation
of how to use API for free. We usually reverse-engineer the API by inspecting
what browser do with web version. We decided easier to delegate it to the Mozhi
team.

> Yandex translator. 

That's unfortunate, yes. Should be fixed on Mozhi side:
https://codeberg.org/aryak/libmozhi/issues/3
I just don't know Go, so I can't contribute.
Regardless autodetection in google, I can't reproduce it. Works for me just
fine.

> Finally, IMHO, the main engine switching in the software is a significant 
> cause to change its version. 

It will be 3.0, I didn't draft a new release.
Ah, you probably installed it from
https://flathub.org/apps/org.kde.CrowTranslate which is based on unpublished
version. I submitted Flatpak manifest to prepare for the upcoming release, I
didn't expect it to be published. I will contact the team about it.

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

[Breeze] [Bug 489984] Add symlinks for Crow Translate

2024-07-23 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=489984

--- Comment #2 from Gena  ---
Ah, correct, I do have `crow-translate-tray-dark.svg` and
`crow-translate-tray-light.svg` in my application to let user choose which icon
to use for tray explicitly.

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

[Breeze] [Bug 489984] Add symlinks for Crow Translate

2024-07-09 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=489984

Gena  changed:

   What|Removed |Added

Summary|Add symlink for Crow|Add symlinks for Crow
   |Translate   |Translate

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

[Breeze] [Bug 489984] New: Add symlink for Crow Translate

2024-07-09 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=489984

Bug ID: 489984
   Summary: Add symlink for Crow Translate
Classification: Plasma
   Product: Breeze
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: genalo...@gmail.com
CC: kain...@gmail.com, m...@nueljl.in
  Target Milestone: ---

SUMMARY

The application was recently incubated
(https://invent.kde.org/office/crow-translate) and changed its appid to
`org.kde.CrowTranslate`. And in the upcoming release we changed icon names to
follow this convention:
* `crow-translate-tray-dark.svg` -> `org.kde.CrowTranslate-tray-dark.svg`
* `crow-translate-tray-light.svg` -> `org.kde.CrowTranslate-tray-light.svg`
* `crow-translate-tray.svg` -> `org.kde.CrowTranslate-tray.svg`
* `crow-translate.svg` -> `org.kde.CrowTranslate.svg`

Could add symlinks for these icons?

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

[systemsettings] [Bug 484093] Added applications doesn't persist after reboot

2024-03-31 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=484093

--- Comment #1 from Gena  ---
Can't reproduce anymore after 6.0.3.

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

[systemsettings] [Bug 484093] Added applications doesn't persist after reboot

2024-03-31 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=484093

Gena  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

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

[systemsettings] [Bug 484093] New: Added applications doesn't persist after reboot

2024-03-20 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=484093

Bug ID: 484093
   Summary: Added applications doesn't persist after reboot
Classification: Applications
   Product: systemsettings
   Version: 6.0.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_keys
  Assignee: plasma-b...@kde.org
  Reporter: genalo...@gmail.com
CC: k...@david-redondo.de
  Target Milestone: ---

SUMMARY

If you add a `.desktop` file for a non-KDE application in global shortcuts, it
doesn't persists after reboot.

STEPS TO REPRODUCE
1. Create the following desktop file:

```
[Desktop Entry]
Actions=TurnOffScreen;
Type=Application
Name=KScreen Doctor
Comment=Allows to change the screen setup
Exec=kscreen-doctor
Categories=ConsoleOnly;System;
Icon=preferences-system-power-management
StartupNotify=false

[Desktop Action TurnOffScreen]
Exec=kscreen-doctor --dpms off
Name=Turn off screen
X-KDE-Shortcuts=Power off
```

2. Add the added .desktop file to the list of global shortcuts.
3. Reboot.

OBSERVED RESULT

The added .desktop file no longer present in global shortcuts.

EXPECTED RESULT

The added .desktop file still present in global shortcuts.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: ArchLinux
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

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

[plasma-mobile] [Bug 474296] New: Ability to display navigation panel in fullscreen apps.

2023-09-08 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=474296

Bug ID: 474296
   Summary: Ability to display navigation panel in fullscreen
apps.
Classification: Plasma
   Product: plasma-mobile
   Version: unspecified
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Shell
  Assignee: plasma-mobile-bugs-n...@kde.org
  Reporter: genalo...@gmail.com
CC: c...@carlschwan.eu
  Target Milestone: ---

Currently in order to show navigation panel in fullscreen mode I have to change
volume sound. After sound bar appears it also displays navigation panel. But it
would be great to be able to swap from side as you do on Android devices.

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

[Plasma Mobile Dialer] [Bug 474014] No ringing tone

2023-09-01 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=474014

--- Comment #1 from Gena  ---
> Looks like the phone stays muted until the recipient answers.

I meant that looks like audio is not being turned on until the call is
established.

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

[Plasma Mobile Dialer] [Bug 474014] New: No ringing tone

2023-09-01 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=474014

Bug ID: 474014
   Summary: No ringing tone
Classification: Applications
   Product: Plasma Mobile Dialer
   Version: unspecified
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: aa...@ya.ru
  Reporter: genalo...@gmail.com
  Target Milestone: ---

When I call someone, I don't hear [ringing
tone](https://en.wikipedia.org/wiki/Ringing_tone). The tones are generated
either from the modem or the network (depending on what user select).


STEPS TO REPRODUCE
1. Call someone.

OBSERVED RESULT

Silence until recipient picks up.  Looks like the phone stays muted until the
recipient answers.

EXPECTED RESULT

I would expect to see a ringing tone.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 23.08
Qt Version: 5.15.10+kde+r152

ADDITIONAL INFORMATION

This functionality works for me on the same distro in Phosh, so I assume that
the problem is not in my configuration.

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

[Powerdevil] [Bug 473480] Incorrect charging status with Pine keyboard

2023-08-17 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=473480

--- Comment #1 from Gena  ---
Created attachment 161025
  --> https://bugs.kde.org/attachment.cgi?id=161025&action=edit
Settings menu, system thinks that the phone is charging, while it's actually
not

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

[Powerdevil] [Bug 473480] New: Incorrect charging status with Pine keyboard

2023-08-17 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=473480

Bug ID: 473480
   Summary: Incorrect charging status with Pine keyboard
Classification: Plasma
   Product: Powerdevil
   Version: 5.27.7
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: genalo...@gmail.com
CC: m...@ratijas.tk, natalie_clar...@yahoo.de
  Target Milestone: ---

I use Plasma on my PinePhone Pro with the Pine keyboard (that includes
additional battery).
Powerdevil detects that the phone is charging, while it actually not.
Sysfs reports that both batteries discharging:
```
shatur@pinephone-pro ~> cat /sys/class/power_supply/rk818-battery/status
Discharging
shatur@pinephone-pro ~> cat /sys/class/power_supply/ip5xxx-battery/status
Discharging
```

Here is the output from `upower -d`: https://pastebin.com/YaiQGqAx
Everything is discharging.

But powerdevil thinks that the phone is charging for some reason. I would
expect it to detect charging only when at least one battery is charging.

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

[KClock] [Bug 471064] Alarm doesn't work if the sound is muted

2023-06-15 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=471064

--- Comment #2 from Gena  ---
Yes, I think a separate audio channel would be preferred.
But as a temporary solution mute / unmute should do the job.
Alternatively we could create a separate audio profile for kclock as we have
for phone calls.

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

[KClock] [Bug 471064] New: Alarm doesn't work if the sound is muted

2023-06-15 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=471064

Bug ID: 471064
   Summary: Alarm doesn't work if the sound is muted
Classification: Applications
   Product: KClock
   Version: 23.04.1
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: espi...@gmail.com
  Reporter: genalo...@gmail.com
CC: hanyo...@protonmail.com
  Target Milestone: ---

STEPS TO REPRODUCE
1. Mute the audio
2. Set an alarm
3. Wait for the alarm

OBSERVED RESULT

Alarm is triggered, but silently, there is no sound.

EXPECTED RESULT

Alarm is triggered with sound. The phone is temporary unmuted.

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

[xdg-desktop-portal-kde] [Bug 435781] Allow screenshots to be taken without pop-up dialog.

2021-05-01 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=435781

Gena  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/plas
   ||ma/xdg-desktop-portal-kde/c
   ||ommit/72cd34252c3954a9f6ae7
   ||7b23bfc9a752d312f22
 Status|CONFIRMED   |RESOLVED

--- Comment #1 from Gena  ---
Git commit 72cd34252c3954a9f6ae77b23bfc9a752d312f22 by Hennadii Chernyshchyk.
Committed on 01/05/2021 at 18:44.
Pushed by meven into branch 'master'.

Do not display screenshot dialog if interactive is set to false

M  +4-2src/screenshot.cpp
M  +40   -19   src/screenshotdialog.cpp
M  +6-2src/screenshotdialog.h

https://invent.kde.org/plasma/xdg-desktop-portal-kde/commit/72cd34252c3954a9f6ae77b23bfc9a752d312f22

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

[xdg-desktop-portal-kde] [Bug 435781] New: Allow screenshots to be taken without pop-up dialog.

2021-04-15 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=435781

Bug ID: 435781
   Summary: Allow screenshots to be taken without pop-up dialog.
   Product: xdg-desktop-portal-kde
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: genalo...@gmail.com
  Target Milestone: ---

SUMMARY

At the moment, when creating a screenshot via `xdg-desktop-portal`, a
confirmation dialog appears. If you specify `interactive = false` (default),
then the dialog will still appear with confirmation of saving the captured
screenshot.


SUGGESTION

It would be nice not to display this dialog with the `interactive = false`
option, as GNOME does.
For example, in my application, the user needs to select a screen area from
which to recognize the text. With the current behavior, the user, after
activating the recognition, needs to click the "Save" button in the dialog that
appears before displaying the selection of the area. This behavior is not very
obvious to the user.

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

[kwin] [Bug 435696] Validate relative paths in desktop files for X-KDE-DBUS-Restricted-Interfaces

2021-04-14 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=435696

--- Comment #6 from Gena  ---
(In reply to David Edmundson from comment #5)
> Then you break everyone's dev setups, and you have snaps and flatpaks in
> your path, which breaks real sandboxes which is a major no-no.

You probably misunderstood me. I suggested adding support for executables from
PATH, but additionally validating paths that obtained from PATH. For example,
check if the received application location from PATH is `/usr/bin/share` (or
any other folder owned by root). This approach shouldn't break anything, and
full paths will work as before (e.g. without additonal check).

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

[kwin] [Bug 435696] Validate relative paths in desktop files for X-KDE-DBUS-Restricted-Interfaces

2021-04-14 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=435696

--- Comment #4 from Gena  ---
(In reply to David Edmundson from comment #3)

> It is. Otherwise the security aspect is just pointless, anyone can call
> their app spectacle and take as many screenshots as they want.

I agree, this is why I suggested to just check the folder owner if the
application executable was taken from PATH. What do you think about this?

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

[kwin] [Bug 435696] Validate relative paths in desktop files for X-KDE-DBUS-Restricted-Interfaces

2021-04-14 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=435696

--- Comment #2 from Gena  ---
(In reply to David Redondo from comment #1)
> I think absolute paths are intentional. If you want to ship your app in some
> packaged format you might want to look into the cross-desktop screenshot
> portal.

On KDE Plasma, the portal first shows a pop-up window with a preview in which
the user has to click "Save", after which I can display a selection of the
rectangular recognition area. I already support this, but it is not very
obvious to the user, so I would like to use the native API on KDE.
If security is so important, can we check the resulting path from $PATH and
allow taking a screenshot if the application folder is owned by root?

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

[kwin] [Bug 435696] New: Validate relative paths in desktop files for X-KDE-DBUS-Restricted-Interfaces

2021-04-13 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=435696

Bug ID: 435696
   Summary: Validate relative paths in desktop files for
X-KDE-DBUS-Restricted-Interfaces
   Product: kwin
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: platform-wayland
  Assignee: kwin-bugs-n...@kde.org
  Reporter: genalo...@gmail.com
  Target Milestone: ---

SUMMARY

At the moment, to take a screenshot on Walyand, the
`X-KDE-DBUS-Restricted-Interfaces = org.kde.kwin.Screenshot` parameter must be
specified in the .desktop file. But this only works for absolute paths
specified in `Exec=`. Meven suggested to handle relative paths in this comment:
https://phabricator.kde.org/D29407#inline-171509, it has not been resolved.

ADDITIONAL INFORMATION

My application (https://github.com/crow-translate/crow-translate) uses text
recognition from the screen and in order to be able to capture the screen on
Walyand I need to hardcoded the full path in the .desktop file. This creates
some inconvenience, for example, for creating an AppImage.

The standard allows the use of relative paths:
https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html#exec-variables

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

[lattedock] [Bug 410386] latte-dock dependency on pulseaudio

2019-07-30 Thread gena
https://bugs.kde.org/show_bug.cgi?id=410386

--- Comment #2 from gena  ---
Hm.. But in Debian plasma-desktop doesn't depend on pulseaudio. OK, I should
ask them about that. Thanks!

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

[lattedock] [Bug 410386] latte-dock dependency on pulseaudio

2019-07-30 Thread gena
https://bugs.kde.org/show_bug.cgi?id=410386

gena  changed:

   What|Removed |Added

 CC||gena...@inbox.ru

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

[lattedock] [Bug 410386] New: latte-dock dependency on pulseaudio

2019-07-30 Thread gena
https://bugs.kde.org/show_bug.cgi?id=410386

Bug ID: 410386
   Summary: latte-dock dependency on pulseaudio
   Product: lattedock
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: gena...@inbox.ru
  Target Milestone: ---

SUMMARY
Why is it depend on pulseaudio? Is it really necessary or is it some debian
specifics?

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[Breeze] [Bug 396124] New: Icon Request: Crow Translate

2018-07-03 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=396124

Bug ID: 396124
   Summary: Icon Request: Crow Translate
   Product: Breeze
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: genalo...@gmail.com
CC: kain...@gmail.com
  Target Milestone: ---

Application name: Crow Translate
Description: A simple and lightweight translator that allows to translate and
say selected text using the Google Translate API and much more.
Desktop file name: crow-translate.desktop
Icon names: `crow-translate` for app, `crow-translate-tray` for default system
tray icon, `crow-translate-tray-light` and `crow-translate-tray-dark` -
monochrome icons for the system tray, which can be selected in the settings
(like in QBittorrent).
Program GitHub repository: https://github.com/Shatur95/crow-translate

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

[dolphin] [Bug 279614] The Dolphin shell panel (opend by F4) does not source .bashrc

2018-05-07 Thread gena
https://bugs.kde.org/show_bug.cgi?id=279614

gena  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---
 Ever confirmed|0   |1

--- Comment #32 from gena  ---
Hi!

I've tested dolphin 18.04.0 (KF 5.44.0, Qt 5.10.1) on debian testing amd64 and
sometimes (not always!) after reboot I see that dolphin doesn't source my
bashrc. I think it's somehow connected with the option "Restore previous
session" on login.

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

[systemsettings] [Bug 388574] Application Launcher keyboard shortcuts can launch only certain applications.

2018-01-05 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=388574

--- Comment #2 from Gena  ---
Here are the screenshots that describe the problem:
http://storage6.static.itmages.ru/i/18/0105/h_1515179827_6093518_366c7ab21f.png
http://storage6.static.itmages.ru/i/18/0105/h_1515179827_7819723_9ee3b171ba.png

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

[systemsettings] [Bug 388574] Application Launcher keyboard shortcuts can launch only certain applications.

2018-01-05 Thread Gena
https://bugs.kde.org/show_bug.cgi?id=388574

Gena  changed:

   What|Removed |Added

 CC||genalo...@gmail.com

--- Comment #1 from Gena  ---
I have the same bug too.

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