Bug 333789 - Klipper doesn't generate barcodes for URLs copied from Chromium
Summary: Klipper doesn't generate barcodes for URLs copied from Chromium
Status: RESOLVED DUPLICATE of bug 338769
Alias: None
Product: klipper
Classification: Applications
Component: general (show other bugs)
Version: 0.9.7
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Martin Flöser
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-23 19:34 UTC by Ovidiu D. Niţan
Modified: 2014-10-27 07:18 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ovidiu D. Niţan 2014-04-23 19:34:54 UTC 
When I copy a URL from Chromium's address bar and I want to generate a barcode, I get a blank window named "Mobile Barcode - Klipper" with an OK button. If I paste the URL in a KWrite document and then I copy it again, the barcode is successfully generated, which make me guess that the URLs copied from Chromium's omnibox are some kind of special object?

Reproducible: Always

Steps to Reproduce:
1. Open Chromium
2. Access a webpage
3. Copy the current URL from Chromium's address bar
4. Generate a barcode
Actual Results:  
A blank window is shown

Expected Results:  
A barcode should be generated. Very useful when you want to access a URL from your mobile!
Comment 1 Daniel Eckl 2014-09-13 06:11:19 UTC 
Confirmed, running klipper 0.9.7 with KDE 4.14.0 on Kubuntu Trusty
Comment 2 Jonathan Richards 2014-10-07 10:10:35 UTC 
Confirmed also for URLs copied from Google Chrome.  Please change status from UNCONFIRMED!

Platform and versions:
  Google Chrome: Version 37.0.2062.120 (64-bit)

$ klipper --version
  Qt: 4.8.6
  KDE Development Platform: 4.13.3
  Klipper: 0.9.7

  KDE: Platform Version 4.13.3 (Kubuntu 14.04)

$ uname -a
  Linux Odin 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Comment 3 Christoph Feck 2014-10-25 15:36:43 UTC 
Martin, is this a duplicate of bug 338769, in other words, invalid?
Comment 4 Martin Flöser 2014-10-27 07:18:08 UTC 

*** This bug has been marked as a duplicate of bug 338769 ***