[Bug 850649] Re: gnome-terminal extremely slow and display buggy
I made a video showcasing the bug: http://www.youtube.com/watch?v=oOms1TzIKCM -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850649 Title: gnome-terminal extremely slow and display buggy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/850649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850649] Re: gnome-terminal extremely slow and display buggy
Not only is displaying (very!) slow, but the content of the terminal gets borked as well, meaning contents of the terminal are vanishing! I find myself pressing ctrl-l (refresh display) repeatedly in vim to display my file correctly. This is a pretty serious bug for me, serious enough to consider switching to Fedora, so if I can do anything to help o tdebug this, please step forward and tell. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850649 Title: gnome-terminal extremely slow and display buggy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/850649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 366621] Re: guake package does not install gconfig schema
I can confirm this bug in oneiric. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/366621 Title: guake package does not install gconfig schema To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/guake/+bug/366621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152950] Re: please backport collectd to dapper
No longer needed. Please close. ** Changed in: dapper-backports Status: New => Opinion ** Changed in: edgy-backports Status: Invalid => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/152950 Title: please backport collectd to dapper To manage notifications about this bug go to: https://bugs.launchpad.net/dapper-backports/+bug/152950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645023] Re: libwv2 release package compiled with DEBUG flag
** Changed in: wv2 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/645023 Title: libwv2 release package compiled with DEBUG flag To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wv2/+bug/645023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 845483] [NEW] Setting up of tex-common fails because /usr/bin/omega is missing in package
Public bug reported: Neither the package texlive-binaries, nor the package texlive-omega has /usr/bin/omega but it is required by fmtutil. This is what "fmtutil --all" produces: fmtutil: running `omega -ini -jobname=omega -progname=omega omega.ini' ... /usr/bin/fmtutil: 1: omega: not found Error: `omega -ini -jobname=omega -progname=omega omega.ini' failed mv: cannot stat `omega.log': No such file or directory fmtutil: running `omega -ini -jobname=lambda -progname=lambda lambda.ini' ... /usr/bin/fmtutil: 1: omega: not found Error: `omega -ini -jobname=lambda -progname=lambda lambda.ini' failed mv: cannot stat `lambda.log': No such file or directory This is a summary of all `failed' messages: `omega -ini -jobname=omega -progname=omega omega.ini' failed `omega -ini -jobname=lambda -progname=lambda lambda.ini' failed (END) ** Affects: texlive-bin (Ubuntu) Importance: Undecided Status: New ** Tags: binary package packaging tex ** Summary changed: - Setting up of tex-common failes because /usr/bin/omega is missing + Setting up of tex-common fails because /usr/bin/omega is missing ** Summary changed: - Setting up of tex-common fails because /usr/bin/omega is missing + Setting up of tex-common fails because /usr/bin/omega is missing in package -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/845483 Title: Setting up of tex-common fails because /usr/bin/omega is missing in package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/845483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645023] Re: libwv2 release package compiled with DEBUG flag
It's been almost a year since I first reported this bug, a fix is available and nothing is done. What does it take to release a new libwv2 Package with this patch? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/645023 Title: libwv2 release package compiled with DEBUG flag To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wv2/+bug/645023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645023] Re: libwv2 release package compiled with DEBUG flag
** Changed in: wv2 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: wv2 (Ubuntu) Status: Fix Released => Triaged ** Changed in: wv2 (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/645023 Title: libwv2 release package compiled with DEBUG flag To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wv2/+bug/645023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645023] [NEW] libwv2 release package compiled with DEBUG flag
Public bug reported: When using the library in DEBUG mode it emits lots of "Got a sprm" messages. This seriously degrades performance. Upon compiling it new without DEBUG, everything is fine. ** Affects: wv2 (Ubuntu) Importance: Undecided Status: New -- libwv2 release package compiled with DEBUG flag https://bugs.launchpad.net/bugs/645023 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 403957] [NEW] Variable mismatch in /etc/init.d/pdns-recursor
Public bug reported: Binary package hint: pdns-recursor PowerDNS Recursor can be started, but not stopped via the initscript. Cause: Line 32 is currently: PIDFILE=$SOCKETDIR/$NAME.pid but should be: PIDFILE=$PIDDIR/$NAME.pid ** Affects: pdns-recursor (Ubuntu) Importance: Undecided Status: New ** Tags: startupscript -- Variable mismatch in /etc/init.d/pdns-recursor https://bugs.launchpad.net/bugs/403957 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152950] Backport to edgy and dapper?
Public bug reported: Binary package hint: collectd Is it possible to backport this package to edgy and dapper? ** Affects: collectd (Ubuntu) Importance: Undecided Status: New -- Backport to edgy and dapper? https://bugs.launchpad.net/bugs/152950 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 137718] Excessive CPU usage of /usr/lib/xscreensaver/ifs
Public bug reported:
Binary package hint: gnome-screensaver
Symptom:
The screensaver module IFS does (to my information) not use 3D
acceleration, yet on my old 500MHz machine it ran faster than today on
my 2GHz machine. I see that new features (changing colors) were added,
but that can not account for a >80% CPU usage in window mode (rather
small window).
Something has gone wrong, I think.
More information:
I did an strace, but do not know if this is normal as I never had the
incentive to do one before.
This block repeats:
--snip--
write(3, "[EMAIL PROTECTED]"..., 7328) = 7328
ioctl(3, FIONREAD, [32])= 0
read(3, "\16\213=\212\1\0\300\3\0\0>\0\254\3\0\t`1\37\10\2\0\0\300"..., 32) = 32
ioctl(3, FIONREAD, [0]) = 0
ioctl(3, FIONREAD, [0]) = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0
ioctl(3, FIONREAD, [0]) = 0
select(0, NULL, NULL, NULL, {0, 1}) = 0 (Timeout)
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 16384) = 16384
write(3, "[EMAIL PROTECTED]"..., 7328) = 7328
--snap--
** Affects: gnome-screensaver (Ubuntu)
Importance: Undecided
Status: New
--
Excessive CPU usage of /usr/lib/xscreensaver/ifs
https://bugs.launchpad.net/bugs/137718
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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 137307] Re: Xgl very slow, even when running only metacity (Intel i810)
** Changed in: xserver-xgl (Ubuntu) Status: New => Confirmed -- Xgl very slow, even when running only metacity (Intel i810) https://bugs.launchpad.net/bugs/137307 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 137307] Re: Xgl very slow, even when running only metacity (Intel i810)
I tried it with both drivers and had the exact same outcome. -- Xgl very slow, even when running only metacity (Intel i810) https://bugs.launchpad.net/bugs/137307 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 137307] Xgl very slow, even when running only metacity (Intel i810)
Public bug reported: Binary package hint: xserver-xgl symptoms: after upgrading today (2007-09-04) I noticed very strange behaviour of X. The screen got drawn very slowly in triangles which divide the screen diagonally. When dragging windows it felt like 2D acceleration was disabled completely. The login screen did not suffer this symptoms, they only startet after logging in. Looking at the processes I saw Xgl starting. solution (obviously not the right one): After adding "intel" to XGL_BLACKLIST in /etc/X11/Xsession.d/00xserver- xgl_start-server and thus disabling Xgl all problems went away (including the mangled keyboard as mentioned in bug #32857 related packages: xserver-xgl1:1.1.99.1~git20070727-0ubuntu1 xserver-xorg-core 2:1.3.0.0.dfsg-12ubuntu2 and either: xserver-xorg-video-i8102:1.7.4-0ubuntu5 or xserver-xorg-video-intel 2:2.1.1-0ubuntu2 ** Affects: xserver-xgl (Ubuntu) Importance: Undecided Status: New -- Xgl very slow, even when running only metacity (Intel i810) https://bugs.launchpad.net/bugs/137307 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112927] Thread support not compiled in
Public bug reported: Binary package hint: xaos Xaos has an option to compile it with threads. This is not done thus limiting its performance on modern multi-core processors. ** Affects: xaos (Ubuntu) Importance: Undecided Status: Unconfirmed -- Thread support not compiled in https://bugs.launchpad.net/bugs/112927 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72992] Re: Kernel panic when starting domU
Started domain trac01 [0.00] Linux version 2.6.17-6-generic-xen0 ([EMAIL PROTECTED]) (gcc version 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)) #3 SMP Mon Oct 16 06:15:23 UTC 2006 (ubuntu-xen) [...] [ 423.868395] Using IPI No-Shortcut mode [ 423.868830] Registering block device major 8 At this poinit the host system gone into a reboot. ** Changed in: xen-source-2.6.17 (Ubuntu) Status: Unconfirmed => Confirmed ** Changed in: xen-source-2.6.17 (Ubuntu) Status: Confirmed => Unconfirmed -- Kernel panic when starting domU https://bugs.launchpad.net/bugs/72992 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 106028] Re: Kvm not installable in feisty
Question: is a new kernel release still possible? If not, the kvm package has to be changed before release to allow installation. An incompatibility is less severe than not being able to install it at all. -- Kvm not installable in feisty https://bugs.launchpad.net/bugs/106028 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83025] Re: initramfs-tools script doesn't wait for device initialization, preventing mdadm to assemble md arrays
I solved my problem by adding "auto=yes" to the device section in mdadm.conf and afterwards rerunning update-initramfs -u -k all The system boots now, a pristine Feisty installation although would not boot. -- initramfs-tools script doesn't wait for device initialization, preventing mdadm to assemble md arrays https://bugs.launchpad.net/bugs/83025 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83025] Re: initramfs-tools script doesn't wait for device initialization, preventing mdadm to assemble md arrays
I get the same effect (mdadm does not start arrays), similar setup as Dominik (ata_piix, raid1), but apparently a different cause for the problem. According to ps udevd is not started at all when mdadm bails out. If I start the udev start script manually the device nodes appear and the mdadm script can initialize the arrays. ** Changed in: initramfs-tools (Ubuntu) Status: Unconfirmed => Confirmed -- initramfs-tools script doesn't wait for device initialization, preventing mdadm to assemble md arrays https://bugs.launchpad.net/bugs/83025 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 38007] Re: pvmove coredumps
never mind... might just be that hard drive dying below my feet without me noticing. :-( ** Changed in: lvm2 (Ubuntu) Status: Confirmed => Fix Released -- pvmove coredumps https://launchpad.net/bugs/38007 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 38007] pvmove STILL coredumps.
[EMAIL PROTECTED]:~# dpkg -l|grep devmapper1.02
ii libdevmapper1.02 1.02.05-1ubuntu1[...]
[EMAIL PROTECTED]:~# pvmove
Segmentation fault
[EMAIL PROTECTED]:~# strace pvmove
[...]
stat64("/dev/fibre/dspam01-root", {st_mode=S_IFBLK|0600, st_rdev=makedev(253,
28), ...}) = 0
stat64("/dev/fibre/dspam01-root", {st_mode=S_IFBLK|0600, st_rdev=makedev(253,
28), ...}) = 0
open("/dev/fibre/dspam01-root", O_RDONLY|O_DIRECT|O_LARGEFILE|O_NOATIME) = 3
fstat64(3, {st_mode=S_IFBLK|0600, st_rdev=makedev(253, 28), ...}) = 0
ioctl(3, BLKBSZGET, 0x80eafb8) = 0
_llseek(3, 0, [0], SEEK_SET)= 0
read(3,
+++ killed by SIGSEGV +++
** Changed in: lvm2 (Ubuntu)
Status: Fix Released => Confirmed
--
pvmove coredumps
https://launchpad.net/bugs/38007
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 85766] Re: mouse doesn't work in War§o w any more
setting it to confirmed. ** Changed in: gnome-screensaver (Ubuntu) Status: Needs Info => Confirmed ** Summary changed: - mouse doesn't work in War§ow any more + running gnome-screensaver prevents War§sow from accessing mouse -- running gnome-screensaver prevents War§sow from accessing mouse https://launchpad.net/bugs/85766 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 85766] Re: mouse doesn't work in War§o w any more
I correct me. After looking at src/gs-watcher-x11.c I think beagle looks for the mouse and key-events itself. Suspected some d-bus trickery. So is this a problem in gnome-screensaver after all? Or is it a problem in x11? -- mouse doesn't work in War§ow any more https://launchpad.net/bugs/85766 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 85766] I can still confirm this bug.
I suspected this had something to do with the fact that beagle uses all my CPU if I refrain from mouse moving for too long. If I move my mouse beagle stops instantaneous. Somehow beagle must get notified of mouse movements. I suspected that control of the mouse is not given off to newly launched applications. So I killed several processes until I got the culprit. It's gnome-screensaver. If I kill it mouse works again in Warsow. If I start it again, mouse isn't working anymore. Pretty obvious I think. :) In retrospect it's obvious that gnome-screensaver should stop beagle from beagling as it has to look for mouse movement anyway. So I'm pretty sure this is a bug. :) ** Changed in: control-center (Ubuntu) Sourcepackagename: control-center => gnome-screensaver -- mouse doesn't work in War§ow any more https://launchpad.net/bugs/85766 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59357] Re: mod_auth_ldap confused by server side references
** Changed in: apache2 (Ubuntu) Status: Unconfirmed => Rejected -- mod_auth_ldap confused by server side references https://launchpad.net/bugs/59357 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88078] Backport this to edgy, dapper?
Public bug reported: Binary package hint: python-flup Would be neat if it was possible to have this package included in dapper-backports and edgy-backports. ** Affects: flup (Ubuntu) Importance: Undecided Status: Unconfirmed -- Backport this to edgy, dapper? https://launchpad.net/bugs/88078 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
