Bug 7297 - No Genome Terminal in product section of Linux 6.1
Summary: No Genome Terminal in product section of Linux 6.1
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 2.1r
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-11-24 17:43 UTC by georgel
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1999-11-24 18:17:40 UTC


Attachments (Terms of Use)

Description georgel 1999-11-24 17:43:49 UTC
I tried to copy to clipboard from a Genome Terminal and paste into a
bugzilla bug report.

I tried to copy to clipboard from a Genome Terminal and paste into a
bugzilla bug report.
I tried to copy to clipboard from a Genome Terminal and paste into a
bugzilla bug report.
Here I copied the above two lines to the clipboard using the Edit Copy
then I went to a Genome Terminal and copied some other selected text to the
clipboard by highlighting the text and releasing the mouse button.
I returned to this window and pasted using alt-V.

Conclusion Genome-Terminal doesn't copy to clip board.

Sorry about sticking this stuff in a bugzilla bug report but I couldn't
find how to report it as a Genome Terminal bug.

Comment 1 georgel 1999-11-24 17:50:59 UTC
I tried to copy to clipboard from a Genome Terminal and paste into a bugzilla
bug report.

I was able to paste to another Genome Terminal. I opened up a new Genome
Terminal and Edit-paste  did put the clipboard stuff to the new terminal.

This means that bugzilla and genome terminal are not sharing the same clipboard.

Comment 2 David Lawrence 1999-11-24 18:17:59 UTC
Gnome-terminal belongs to the gnome-core component under Red Hat 6.1. Please
re-enter this bug report with Red Hat 6.1 as the product and the component set
to gnome-core so the right developer will be able to look at it.


Note You need to log in before you can comment on or make changes to this bug.