Actually, bug number is #6236 "some errors on copy paste function "
sorry, my mistake. -andyj
--
gedit 2.22.3 random pasting location
https://bugs.launchpad.net/bugs/255638
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/16609076/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/16609077/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/16609078/ProcStatus.txt
--
gedit
Public bug reported:
Binary package hint: gedit
Similar to bug #34629 "Copy-paste with mouse wheel fails", but this
appears to have been closed.
Using gedit 2.22.3 on Hardy Heron with all updates applied.
For context: I'm using gedit to edit python, bash, html and plain text
files, with multipl
*** This bug is a duplicate of bug 234911 ***
https://bugs.launchpad.net/bugs/234911
No, this is NOT a duplicate of this bug - the mouse-wheel is not
involved. Please note that I misquoted the similar bug initially.
-andyj
*** This bug is a duplicate of bug 234911 ***
https://bugs.launch
*** This bug is a duplicate of bug 234911 ***
https://bugs.launchpad.net/bugs/234911
Ah, Ok - but it doesn't say that in the bug report or any of the
responses to it. It's also closed; does that mean it's not being looked
at anymore?
regards,
-andyj
*** This bug is a duplicate of bug 234911
Sorry I had completely forgotten about this bug report. The issue turned
out to be a faulty SCSI lead, though I still can't understand why DSL
could read the archive but Ubuntu couldn't. Maybe DSL drives the SCSI
channel at a lower speed or uses different SCSI chatter - DSL, at that
time at least,
Public bug reported:
Binary package hint: tar
GNU tar reports "This does not appear to be a tar archive" when
attempting to list or restore (tar tvf or tar xvf) from a tape archive
created by the same version of tar. Verification with tar cvWf works
correcty however.
An older version of tar (on
eth1 (my cisco wireless card) is up after boot, but no ip address is
assigned; running "/etc/init.d/networks restart" solves the problem.
I had no such hassle under dapper - could this be related?
--
Wireless network interface (ipw2200) does not have IP address after boot
https://launchpad.net/b
