[okteta] [Bug 336607] cursor is blinking (flashing) at insane rate

[Arek Guzinski via KDE Bugzilla]

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

--- Comment #8 from Arek Guzinski  ---
Bump!

2 Years later and still not fixed :(
While there is still no way to easily turn off blinking in qt5 on linux (shame
on that!), it can be done with qt5noblink
(https://github.com/igogo/qt5noblink).
While this works for other applications, okteta (0.17.0 here) still blinks
insanely.

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

[plasmashell] [Bug 355528] Multiple monitor support is erratic

[Arek Guzinski via KDE Bugzilla]

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

--- Comment #18 from Arek Guzinski  ---
Created attachment 97232
  --> https://bugs.kde.org/attachment.cgi?id=97232=edit
logfiles for the three cases

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

[plasmashell] [Bug 355528] Multiple monitor support is erratic

[Arek Guzinski via KDE Bugzilla]

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

Arek Guzinski  changed:

   What|Removed |Added

 CC||ker...@ag.de1.cc

--- Comment #17 from Arek Guzinski  ---
I also have issues with multi-monitor support, however this is on a desktop
system, where both screens are always connected.

The setup is (as taken from xrandr output)
DFP1 connected primary 1920x1200+1024+0
DFP2 connected 1024x1280+0+0 (rotated to the) right
The panel *should* appear on DFP1, but even if i change the config, it lasts at
most for one start of plasma and appears on DFP2 the next time.

when plasmashell is started, randomly one of 3 things happen:
1. (sometimes on login, mostly on manual restart) Everything except the panel
beeing on the wrong screen is fine
2. (sometimes on login, maybe 30% of the time on manual restart) Background is
visible, but no panel or other widgets
3. (most likely on login) Plasma is pretty messed up, meaning:
the Plasma root window on DFP2 has the dimensions, as if the screen was not
rotated, leaving black space at the bottom and overflowing to DFP1. if i click
the root of DFP1, its root goes to front, hiding that part of DFP2's plasma.
https://bugs.kde.org/show_bug.cgi?id=337590 is probably related to this.
When i maximize windows, instead of the screens height, their height is set to
1074 pixels (on both screens). Width is ok.

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

[Skanlite] [Bug 359351] New: skanlite should display a progress bar when uploading firmware (Usability bug)

[Arek Guzinski via KDE Bugzilla]

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

Bug ID: 359351
   Summary: skanlite should display a progress bar when uploading
firmware (Usability bug)
   Product: Skanlite
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kare.s...@iki.fi
  Reporter: ker...@ag.de1.cc

I have an Epson Perfection 660 scanner, which needs its firmware uploaded every
time before scanning.
When i start skanlite, a window pops up for maybe 0.5 seconds, then vanishes.
After that nothing visible happens for a minute or two. Then the Skanlite
window appears and everything works.

Now i know, the firware is being uploaded and i just need to wait a bit, but a
new user would think that the application crashed.

Reproducible: Always

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

[Skanlite] [Bug 359351] skanlite should display a progress bar when uploading firmware (Usability bug)

[Arek Guzinski via KDE Bugzilla]

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

--- Comment #2 from Arek Guzinski  ---
Well, lets see...

xsane: same as skanlite :/

what i didn't notice before is that all three applications print the following
2 lines to stderr (which also answers the question how scanimage handles this): 
[snapscan] Scanner warming up - waiting 31 seconds.
[snapscan] Scanner warming up - waiting 31 seconds.

well, maybe i was wrong after all and the firmware isn't the reason - does not
change the UI-issue though.

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

[frameworks-kdelibs4support] [Bug 359320] New: formatDateTime(..., KLocale::FancyShortDate, ... ) should take LC_TIME into account

[Arek Guzinski via KDE Bugzilla]

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

Bug ID: 359320
   Summary: formatDateTime(..., KLocale::FancyShortDate, ... )
should take LC_TIME into account
   Product: frameworks-kdelibs4support
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: ker...@ag.de1.cc

This is related to my bugreport for akregator 
https://bugs.kde.org/show_bug.cgi?id=359191 (theres a screenshot too), which
turned out to belong to a frameworks component. I hope this is the correct
component (probably not...), but after trying to find out which component
exactly this belongs to for about 40 minutes, i had enough and took my best
guess

with the following env...
LANGUAGE=en_US:de
LC_TIME=de_DE.UTF-8

akregator shows the time as "MM/DD/ hh:mm AM/PM", as opposed to "DD.MM.
hh:mm", which is what i would expect with LC_TIME=de_DE.UTF-8.

What i would expect , vs what i get is (examples)
Expected   | What i get
Yesterday 14:35 |  Yesterday 02:35 PM
29.01.2016 19:20  |   01/29/2016 07:20  PM

so in my opinion the function should translate the words based on LANGUAGE (as
it does), but the numeric part based on LC_TIME, as this would be consistent
with the Interface language being english and the date/time format being german

as a workaround, LANGUAGE=en_GB:de makes things a bit better for me

Reproducible: Always

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

[bugs.kde.org] [Bug 340420] Make it easier to file issue reports

[Arek Guzinski via KDE Bugzilla]

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

Arek Guzinski  changed:

   What|Removed |Added

 CC||ker...@ag.de1.cc

--- Comment #9 from Arek Guzinski  ---
While i agree that finding the product works well for a specific application,
it does not for bugs that appear in multiple applications (aka bugs in the
frameworks). This is made even worse by having kde 4&5 stuff mixed together.

I propose the following changes:

add a checkbox "show deprecated products"
and/or
add columns to the table, which show in which version of kde it is used

add the Line "If you are unsure, choose kde" at the bottom of the table. This
way it will be visible, after trying to find the right product, but not
encourage people to use it every time.
I remember that i did not file at least one bug in the past, because i could
not find the right product and did not see the "kde" category.

If you click the "search" link from
https://bugs.kde.org/enter_bug.cgi?product=productname , the product should be
preselected.

sometimes i knew which api call causes a problem (through debug output, stack
trace, alook into the applications source code, etc..). However, finding to
which part of frameworks it belongs, is not that easy. it would be great if you
could search for an api call. Or simply find the product name in the api
reference.

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

[akregator] [Bug 359191] aKregator does not honor LC_TIME / date and time in wrong format

[Arek Guzinski via KDE Bugzilla]

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

--- Comment #4 from Arek Guzinski  ---
ok, i see the problem now...

> I saw in your screenshot that all is in english so it's the problem.
yes, it is. and it should be, because, for several reasons, i prefer english as
my interface language. However, i really really hate the US/UK date format,
which is why i set my time to de_DE (btw: yes, i live in germany)

i had a quick look at the dolphin source code, where QLocale is used, which
displays the date the way i want it (dd.mm.). But QLocale does not support
anything like KLocale::FancyShortDate.
As FancyShortDate uses words, it seems to get its locale settings from the
LANGUAGE variable, instead of LC_TIME.

i think the correct way to handle this would be to use LANGUAGE for the words
and LC_TIME for the rest (as, i believe, it was in kde 4) which is, of course,
an issue for the kf5 libraries and not a bug in akregator. I'll file a report
there.

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

[akregator] [Bug 359191] New: aKregator does not honor LC_TIME / date and time in wrong format

[Arek Guzinski via KDE Bugzilla]

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

Bug ID: 359191
   Summary: aKregator does not honor LC_TIME / date and time in
wrong format
   Product: akregator
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: ker...@ag.de1.cc

Version: 5.0.3

the date and time are displayed in US format (mm/dd/yy hh:mm AM/PM) instead of
german format (dd.mm.yy HH:mm).

output of $ env | ack-grep '^L[AC]' | sort

LANG=en_US.UTF-8
LANGUAGE=en_US.UTF-8
LC_ADDRESS=de_DE.UTF-8
LC_IDENTIFICATION=de_DE.UTF-8
LC_MEASUREMENT=de_DE.UTF-8
LC_MONETARY=de_DE.UTF-8
LC_NAME=de_DE.UTF-8
LC_NUMERIC=C
LC_PAPER=de_DE.UTF-8
LC_TELEPHONE=de_DE.UTF-8
LC_TIME=de_DE.UTF-8



Reproducible: Always




date and time are correctly displayed in other applications ( tested with
dolphin(15.08.03), konqueror (4.14.13), kmail(5.0.3) )

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

[akregator] [Bug 335748] Information in date columns unclear, no controls to clarify

[Arek Guzinski via KDE Bugzilla]

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

Arek Guzinski  changed:

   What|Removed |Added

 CC||ker...@ag.de1.cc

--- Comment #2 from Arek Guzinski  ---
Created attachment 97110
  --> https://bugs.kde.org/attachment.cgi?id=97110=edit
Screenshot

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

[akregator] [Bug 335748] Information in date columns unclear, no controls to clarify

[Arek Guzinski via KDE Bugzilla]

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

--- Comment #3 from Arek Guzinski  ---
Damn it - sorry, the screenshot should go to another bugreport - can someone
delete it?

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

[akregator] [Bug 359191] aKregator does not honor LC_TIME / date and time in wrong format

[Arek Guzinski via KDE Bugzilla]

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

--- Comment #2 from Arek Guzinski  ---
Created attachment 97111
  --> https://bugs.kde.org/attachment.cgi?id=97111=edit
Screenshot

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

[systemsettings] [Bug 358547] New: Some Shortcuts get assigned to wrong keys (mixup between current and us layout)

[Arek Guzinski via KDE Bugzilla]

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

Bug ID: 358547
   Summary: Some Shortcuts get assigned to wrong keys (mixup
between current and us layout)
   Product: systemsettings
   Version: 5.4.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_keys
  Assignee: k...@michael-jansen.biz
  Reporter: ker...@ag.de1.cc

I am on KUbuntu 15.10, using a slightly modified Version of the programmer
dvorak layout. Escape is swapped with CapsLock.

here are my examples (best viewed with monospace fonts):
Action  |   Keys Pressed and Displayed  |   Actual Keys
Performing the Action
Log out |   Meta + CapsLock |   Meta + Escape
Log out |   Meta + Escape   |   Meta + CapsLock
Window to Next Screen   |   Meta + Shift + Q|   Meta + Shift + ; 
Window to Next Screen   |   Meta + :|   ??? 

So in order to map something to "Meta + Shift + ;" (';' is where 'q' is on us
layout), i have to press "Meta + Shift + q" ('q' is where 'x' is on us).

i am sure more examples could be found...


Reproducible: Always

Steps to Reproduce:
1. Set Programmer Dvorak as your Main Keyboard Layout
2. Open Systemsettings -> Shortcuts -> Global Keyboard Shortcuts
3. Assign (e.g.) KWin -> Window to Next Screen to "Meta + Shift + ;"
4. Assign (e.g.) KWin -> Window to Desktop 1 to "Meta + Shift + q"

Actual Results:  
pressing Meta + Shift + ; moves the Window to Desktop 1

Expected Results:  
pressing Meta + Shift + ; should move the Window to the other Screen

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

[systemsettings] [Bug 338361] After swapping Esc and Caps Lock and assigning new action to shortcut which includes Esc, it doesn't work.

[Arek Guzinski via KDE Bugzilla]

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

Arek Guzinski  changed:

   What|Removed |Added

 CC||ker...@ag.de1.cc

--- Comment #2 from Arek Guzinski  ---
Bump!

This still happens with KUbuntu 15.10 and Plasma 5.4.3 :(
also with every other KUbuntu/Kf5 version before that.

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

[ksmserver] [Bug 357942] New: Session does not reliably restore all Applications

[Arek Guzinski via KDE Bugzilla]

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

Bug ID: 357942
   Summary: Session does not reliably restore all Applications
   Product: ksmserver
   Version: 5.4.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: l.lu...@kde.org
  Reporter: ker...@ag.de1.cc

Since Kf5 Sessions are not properly restored.

previously applications that were restored, were all on the same desktop, but
that seems to be partialy fixed in 5.4.3.

See "Actual Results"

Reproducible: Always

Steps to Reproduce:
1. Open a few applications
2. Log out
3. Log in

Actual Results:  
With my user account (after deleting old ksmserverrc and session/* in kde 4&5
dirs): 
Restored: Yakuake, SMPlayer, Kile
Not restored: Kate, Konsole, Opera

With brand new User:
same as above, except: on first try kate and konsole were also restored, but on
wrong desktop. after that, same as above.

Expected Results:  
After login all application windows are restored and on the same virtual
desktop as at logout.

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