Adding to the hue and cry.
Encountered this after a reboot of 8.10.
$ uname -a
Linux bigstory 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:20 UTC 2008 i686
GNU/Linux
$ apt-cache policy network-manager-gnome
network-manager-gnome:
Installed: 0.7~~svn20081020t000444-0ubuntu1
Candidate: 0.7~~svn200
Public bug reported:
Binary package hint: gnome-terminal
gnome-terminal is drawing to X very badly. I think screenshots would be
describe this.
** Affects: gnome-terminal (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
--
gnome-terminal X misbehaviour
https://launchpad.net/bug
--
gnome-terminal X misbehaviour
https://launchpad.net/bugs/56922
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The problem "goes away" when I refresh the g-t window, make it redraw,
but returns if I move the g-t window, or resize it.
It also draws parts of over other windows. Cannot capture a shot of this
-- doing so makes the artifacts disappear.
--
gnome-terminal X misbehaviour
https://launchpad.net/bu
In the above shot, "gnome-terminal misbehaving with mutt", the part of
the image that shows a gnome-terminal (running 'top') is interesting: I
had closed that terminal, yet the instance of g-t running mutt was still
drawing it.
--
gnome-terminal X misbehaviour
https://launchpad.net/bugs/56922
--
g-t has crashed twice on starting it on a desktop with other windows.
Here is the stacktrace.
Debugging Information:
Backtrace was generated from '/usr/bin/gnome-terminal'
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols f
I ran started g-t with strace and it obliged me by crashing. The strace
output is attached. Does that suffice?
--
gnome-terminal X misbehaviour
https://launchpad.net/bugs/56922
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Description changed:
Binary package hint: gnome-terminal
- gnome-terminal is drawing to X very badly. I think screenshots would be
- describe this.
+ gnome-terminal is drawing to X very badly. I think screenshots would
+ best describe this.
--
gnome-terminal X misbehaviour
https://launch
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=6.06
DISTRIB_CODENAME=dapper
DISTRIB_DESCRIPTION="Ubuntu 6.06.1 LTS"
uname -srvm
Linux 2.6.15-26-386 #1 PREEMPT Thu Aug 3 02:52:00 UTC 2006 i686
$ gnome-terminal --version
Gnome gnome-terminal 2.14.2
Using the fglrx driver for X, on an ATI
It's a constant problem now, so I can reproduce it simply by running as
g-terminal.
This problem first appeared a few days ago, I believe after g-terminal
being updated.
--
gnome-terminal X misbehaviour
https://launchpad.net/bugs/56922
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
The output of dpkg --status gnome-terminal | grep Version:
Version: 2.14.2-0ubuntu3
--
gnome-terminal X misbehaviour
https://launchpad.net/bugs/56922
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Dennis Kaarsemaker was right: it was a quinn packages, not Ubuntu ones
causing the trouble. libvte4 particularly.
Shouldn't QuinnStorm call her packages *quinn* rather than *ubuntu*?
That caused much confusion.
--
gnome-terminal X misbehaviour
https://launchpad.net/bugs/56922
--
ubuntu-bugs ma
This is resolved. It was caused by $LD_LIBRARY_PATH being set to
/home/me/.local/lib by autopackage, in a file left over from my prior
installs: ~/.config/autopackage/paths-bash which was getting sourced by
~/.bash_profile.
--
library misbehaviour in terminals
https://bugs.launchpad.net/bugs/1125
This really is urgent: Wordpress users on Ubuntu need all the security
they can get. Wordpress 2.3 "Dexter" is now out.
Announcement:
http://wordpress.org/development/2007/09/wordpress-23/
Fixed bugs:
http://trac.wordpress.org/query?status=closed&milestone=2.3
The newer features would also be
So what happens now?
Do you need me to pass on more information?
Just not sure if I now wait to be contacted or if I need to do something else?
I guess those reports take a hell of time to go through, and you guys are
doing this for free.
One of my prime uses of Linux involves sound, so I have t
Sorry to be thick, but can you tell me how I go about doing that?
Cheers.
Dave.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
Daniel T Chen
Sent: 24 April 2007 15:25
To: [EMAIL PROTECTED]
Subject: [Bug 107863] Re: no sound: Audigy card, SigmaTel STAC9721 mi
Hey, ignore my last email...
I found the switch for "Analog/Digital Output Jack" unselected it, and hey
presto I now have sound!
Thank you so much you guys.
You do a great Job, keep up the good work.
Namasté
Dave.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behal
Public bug reported:
Binary package hint: rhythmbox
Don't know how to report an error for the whole system, but since
upgrading to feisty fawn 7.04 I now have no sound at all.
ProblemType: Bug
Architecture: i386
Date: Fri Apr 20 01:01:23 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/r
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/7356091/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://librarian.launchpad.net/7356092/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://librarian.launchpad.net/7356093/ProcStatus.txt
--
No Sou
Public bug reported:
Since upgrade to Feisty Fawn 7.04 I now have no sound at all.
The card seems to be there & installed in the device manager, the sound options
show my card, but none of the tests produce any sounds.
Still works fine with Windows & with Edgy 6.10
** Affects: Ubuntu
Import
Sorry...
I'm new to Linux.
I've attempted to make a file with the requested output.
Hope it's OK.
Cheers.
Dave.
** Attachment added: "Bug Reports"
http://librarian.launchpad.net/7362865/G%3A%5Cnosoundop
--
No Sound
https://bugs.launchpad.net/bugs/107863
You received this bug notification beca
Public bug reported:
Strange one. I'll use points for the sake of brevity.
- upgraded Dapper -> Edgy -> Feisty
- Dapper -> Edgy via network
- Edgy -> Feisty reinstall with desktop CD
- in Edgy -> Feisty reinstall, I preserved my home partition and data
- most everything is fine, *except
Public bug reported:
Binary package hint: wordpress
The wordpress package available in Dapper should be updated, as the
upstream version has had at least 2 critical security updates.
In Dapper (universe), the latest was 2.0.2-2. wordpress.org's upstream
version is 2.1.3.
** Affects: wordpress
I meant to add that I downloaded and installed that deb by hand (after
backing up my wordpress stuff to be on the safe side) and it installed
without complaint; and my blog is behaving without issue.
--
wordpressPackage Needs Updating
https://bugs.launchpad.net/bugs/107104
You received this bug n
N.B: 2.1.3-1ubuntu1 is in Feisty.
--
wordpressPackage Needs Updating
https://bugs.launchpad.net/bugs/107104
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
25 matches
Mail list logo
