[plasmashell] [Bug 347825] qt-recordMyDesktop does not show a systray icon and recording cannot be stopped

2016-10-21 Thread Sasha Unspecified via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=347825

Sasha Unspecified  changed:

   What|Removed |Added

 CC||sasha2...@gmail.com

--- Comment #4 from Sasha Unspecified  ---
FYI:
KUbuntu 16.04.1, gtk-recordmydesktop 0.3.8-4.1ubuntu1 — systray button exists,
but has no icon; i.e. looks like a gap between other systray buttons (Keyboard
Layout and Audio Volume), so not easy to guess that it belongs to
recordmydesktop.

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

[gwenview] [Bug 358322] New: Pressing Enter during crop causes going 1 level up instead of confirming the crop

2016-01-21 Thread Sasha Unspecified via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358322

Bug ID: 358322
   Summary: Pressing Enter during crop causes going 1 level up
instead of confirming the crop
   Product: gwenview
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: sasha2...@gmail.com
CC: myr...@kde.org

See subj.

Reproducible: Always

Steps to Reproduce:
1. Open some image in gwenview.
2. Press the "Crop" button within the "Image Operations" panel.
3. (Optionally) Specify crop region with mouse.
4. Press Enter.

Actual Results:  
Gwenview goes one level up, now showing all images within directory of the
original image.

Expected Results:  
I expected the crop to be done.
The "Crop" button at the bottom of the windows looks like the default button
(see attach).
Even if it looked the same as the "Cancel" button, I'd anyway expected it to be
default.

Version 15.08.2
Using:
- KDE Frameworks 5.15.0
- Qt 5.5.1 (built against 5.4.2)
- The xcb windowing system
(This happened in prev versions too.)

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


[gwenview] [Bug 358322] Pressing Enter during crop causes going 1 level up instead of confirming the crop

2016-01-21 Thread Sasha Unspecified via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358322

--- Comment #2 from Sasha Unspecified  ---
Created attachment 96772
  --> https://bugs.kde.org/attachment.cgi?id=96772=edit
Buttons with gtk+ style

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


[gwenview] [Bug 358322] Pressing Enter during crop causes going 1 level up instead of confirming the crop

2016-01-21 Thread Sasha Unspecified via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358322

--- Comment #1 from Sasha Unspecified  ---
Created attachment 96771
  --> https://bugs.kde.org/attachment.cgi?id=96771=edit
Buttons with breeze style

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


[plasmashell] [Bug 356409] Plasma fails to start when using old video driver

2015-12-09 Thread Sasha Unspecified via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356409

Sasha Unspecified  changed:

   What|Removed |Added

 Resolution|WONTFIX |---
 Status|RESOLVED|UNCONFIRMED

--- Comment #2 from Sasha Unspecified  ---
1. Well... Could you please tell me what QT_XCB_FORCE_SOFTWARE_OPENGL is? I
mean: is it environment variable, or value in some config file, or what?

2. Shouldn't be this a default behavior? I mean, if not OpenGL support
available, then use simpler graphics API/software emulation. Cause a user
who've installed new (buggy) video driver/uses old graphic card/connects with
VNC to monitor-less server/whatsoever will certainly prefer to see his plasma
running, then displaying such useless message at start-up. Graphic wow-effects
on desktop are not so important to prevent the whole X-server be started in
case when video-driver configuration is not ideal.

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


[plasmashell] [Bug 356409] New: Plasma fails to start when using old video driver

2015-12-08 Thread Sasha Unspecified via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356409

Bug ID: 356409
   Summary: Plasma fails to start when using old video driver
   Product: plasmashell
   Version: 5.4.2
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: sasha2...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Plasma fails to start when using old video driver (e.g. vesa).
The same happens when X server is using dummy driver (e.g. I want to allow PC
be properly booted even when no monitor is attached, to make it accessible with
VNC).

On start plasma displays the following message:
"Plasma is unable to start as it couldn't correctly use OpenGL 2.
Please check that your graphic drivers are set up correctly."

The biggest disappointment is that plasma displays this message in nice graphic
window. I could understand if that message would appear in stderr/log file --
that would mean that the driver is really unusable.

Desktop effects are turned off, of course.

Reproducible: Always

Steps to Reproduce:
There are to proposed ways to reproduce that:
A -- by downgrading your graphics driver to vesa. Determine which graphics
drivers are currently in use, and then disable them (either by blacklisting or
by uninstalling correspondent packages). For example, I reach this state when I
uninstall the persistently hanging xserver-xorg-video-nouveau package (but
binary NVIDIA packages aren't yet installed).
B -- by forcing your X server to run without monitor and then connecting with
VNC:
1. Install and turn on the dummy driver on server (as per
http://ubuntuforums.org/showthread.php?t=1452600=7=11419677#post11419677).
2. Connect with SSH to the server, install x11vnc package and launch x11vnc.
3. Connect to the server with xtightvncviewer.

Actual Results:  
The "Plasma is unable to start as it couldn't correctly use OpenGL 2.
Please check that your graphic drivers are set up correctly." message in the
graphic window.

Expected Results:  
I expect plasma to be working. Maybe slowly, maybe with glitches. But somehow
working.
Is kwin is able to display windows, then plasma should be able to display
widgets.

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