Bug 4583

Summary: Middle mouse button paste stalls chromium-browser for 120 seconds (with synergy)
Product: Mageia Reporter: Herbert Poetzl <herbert>
Component: RPM PackagesAssignee: Nicolas Lécureuil <mageia>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: Normal CC: marja11, nic
Version: CauldronKeywords: UPSTREAM
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
URL: http://code.google.com/p/chromium/issues/detail?id=12150
Whiteboard:
Source RPM: chromium-browser CVE:
Status comment:

Description Herbert Poetzl 2012-02-19 08:24:54 CET
Description of problem:
selecting some text (on a different screen) then pasting it with the middle mouse button into chromium browser (e.g. into a text field) results in chromium becoming unresponsive (scrollers don't work, pages cannot be updated) for 120 seconds

Version-Release number of selected component (if applicable):
synergy-1.4.6-1.mga2.x86_64
chromium-browser-stable-16.0.912.77-1.mga2.x86_64

How reproducible:
always

Steps to Reproduce:
1. select text (e.g. from terminal) on one screen
2. move to the other screen (running chromium-browser)
3. paste with middle mouse button
Comment 1 Manuel Hiebel 2012-02-19 14:45:28 CET
seems this bug: http://code.google.com/p/chromium/issues/detail?id=12150

URL: (none) => http://code.google.com/p/chromium/issues/detail?id=12150
Summary: Middle mouse button paste stalls chromium-browser for 120 seconds => Middle mouse button paste stalls chromium-browser for 120 seconds (with synergy)
Source RPM: synergy-1.4.6-1.mga2.src.rpm => chromium-browser

Manuel Hiebel 2012-03-08 16:41:43 CET

Keywords: (none) => UPSTREAM

Comment 2 Marja Van Waes 2012-05-26 13:09:26 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Manuel Hiebel 2012-06-12 21:01:51 CEST

Keywords: NEEDINFO => (none)

Comment 3 Nic Baxter 2015-02-11 09:15:57 CET
Checked  http://code.google.com/p/chromium/issues/detail?id=12150. Bug still not fixed. Discussion still active upstream

CC: (none) => nic

Samuel Verschelde 2016-10-11 22:37:17 CEST

Assignee: bugsquad => mageia

Comment 4 sturmvogel 2022-03-12 12:44:14 CET
Is this after 8 years still a problem or could this bug be closed?
Comment 5 Marja Van Waes 2022-03-12 17:42:56 CET
(In reply to Nic Baxter from comment #3)
> Checked  http://code.google.com/p/chromium/issues/detail?id=12150. Bug still
> not fixed. Discussion still active upstream

That bug was closed as duplicate/merged with https://bugs.chromium.org/p/chromium/issues/detail?id=131863 which was closed FIXED in 2016

We have recent chromium-browser-99.0.4844.51 in cauldron now, so closing as FIXED

CC: (none) => marja11
Resolution: (none) => FIXED
Status: NEW => RESOLVED