Bug 323100

Summary:	paste.kde.org input field is broken for regular large workstation displays
Product:	[Unmaintained] paste.kde.org	Reporter:	Laszlo Papp <lpapp>
Component:	general	Assignee:	Sayak Banerjee <sayakb>
Status:	RESOLVED NOT A BUG
Severity:	grave	CC:	imalchow, sayakb
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	screenshot: paste.kde.org

Description Laszlo Papp 2013-08-02 09:35:06 UTC

Archlinux, Chromium 28.0.1500.71-1, 64 bit. The output of "xrandr -q" is the following:

Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 480mm x 268mm
   1920x1080      60.0*+
   1680x1050      59.9  
   1280x1024      75.0     60.0  
   1440x900       75.0     59.9  
   1024x768       75.1     60.0  
   800x600        75.0     60.3  
   640x480        72.8     75.0     66.7     60.0  
   720x400        70.1  
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)

Note, it may not be a bug, but I have been told in the #kde-www support channel on freenode, KDE www people prefer user supports via bugzilla.

Reproducible: Always

Comment 1 Laszlo Papp 2013-08-02 09:36:39 UTC

Created attachment 81526 [details]
screenshot: paste.kde.org

Can be dismissed by F5, but I have not figured that out on my own for days, and by the time I did, I already switched away from the service.

Perhaps, we should not lose more KDE users due to this issue.

Comment 2 Sayak Banerjee 2013-08-02 10:19:39 UTC

Thanks for reporting the issue. What I see is that you have attached the same screenshot you showed us on IRC. I read in your comment that it now works after you refreshed the screen. What is it that you want us to take a look at here?

Comment 3 Laszlo Papp 2013-08-02 10:22:37 UTC

Well, it should work off-hand for the people still having the issue on a machine or more.

i.e. refresh should not be necessary. Even a relaunch, or worst case, reboot should fix it.

Comment 4 Sayak Banerjee 2013-08-02 10:27:53 UTC

What happened with your workstation has nothing to do with the application itself, or for that matter any application. Chrome heavily caches static resources and we will not adjust our sites to flush user side caches as it adds unnecessary server load.

Closing the issue as it already works for you.

Comment 5 Laszlo Papp 2013-08-02 10:30:16 UTC

I do not understand why I have been told to report this by you, guys.