I'm getting this on an admittedly old Toshiba Tecra M9 which supposedly
_does_ have an infineon TPM chip. And although tpm_version shows a chip
of vendor id IFX to be present and there's a device, trousers or the
tpm-tools always claim the device is disabled (after log entries as per
OP). /sys/clas
Public bug reported:
Binary package hint: rarian-compat
srollkeeper-preinstall / rarian-sk-preinstall don't update the url field on
jaunty.
The following fixes it. Note: strcmp returns 0 == false on a match.
$ diff -Naurs rarian-0.8.1/util/rarian-sk-preinstall.cpp
rarian-0.8.1/util/rarian-sk-p
Judging from the suggested workaround, I wouldn't at all be surprised, if this
was caused by this:
http://lists.freedesktop.org/archives/compiz/2008-May/003125.html
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver
https://bugs.launchpad.net/bugs/353126
Yo
Look here:
http://bearfruit.org/blog/2008/06/10/fixing-eclipse-after-the-firefox-3-rc1-update-in-ubuntu-8-04
and if you already have xulrunner-1.9, you might want to look here:
http://www.mail-archive.com/udig-de...@lists.refractions.net/msg09462.html
Installing 1.8.1.16 solved the issue for me.
OK, have calmed down a bit since yesterday, when I had multiple X crashes with
the vesa driver.
The connection with nvidia drivers was that the only way I can boot this
machine atm. is using a way old kernel image I only still have out of pure
coincidence and because I've been upgrading this mac
"I'm really excited about some of the things in Jaunty..."
I for my part am really excited of not being able to run nvidia drivers
on this box for four months. I'm quite loth to use nvidia packaged
drivers. Anybody affected here, knows whether machines affected by this
work with any other Debian-b
Locking assertion sounds a lot like one of the multitude of libxcb issues.
Look for:
"xvidcap hangs on starting a capture session. What can I do about it?"
here:
http://xvidcap.wiki.sourceforge.net/faq#usage
Or for one of the libxcb issues, e. g. here:
https://bugs.launchpad.net/xorg-server/+bug/1
On Fri, January 30, 2009 4:05 am, browe wrote:
> xvidcap crashes with every use for me in 8.04.
> I'm using mpeg 4 - divx and no audio in preferences.
> Ran from terminal so you can see the messages. probably lasted closer to
> 50 secs this time. That was a long one.
>
> :~$ xvidcap
> /home/browe/
Since the links to the jaunty kernels above are dead, I dl'ed the kernel
2.6.28-5 from packages.ubuntu.com. I installed the following packages:
linux-backports-modules-2.6.28-5-generic_2.6.28-5.2_i386.deb
linux-headers-2.6.28-5_2.6.28-5.15_all.deb
linux-headers-2.6.28-5-generic_2.6.28-5.15_i386.de
Btw., since I cannot boot AT ALL with the new kernel, the output above
was taken from my old 2.6.22-14-generic
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
The issue persists for me, too. Please find my lspci output attached.
For me, the boot drives are hooked up to a VT8233 based SATA controller.
dmesg has this to say: The two drivers sda and sdb are used in a lvm
volume group.
[ 26.769215] VP_IDE: IDE controller at PCI slot :00:11.1
[ 26.76
compiled the kernel myself for just that reason and put the result here:
http://www.jarre-de-the.net/computing/
The three linux-*deb files there should be all you need for DKMS on an i386
platform.
--
toshset does not support tlsup module (Intrepid)
https://bugs.launchpad.net/bugs/269831
You rec
Or is there a way to dl the binaries resulting from the following build for
testing?
https://launchpad.net/ubuntu/+source/linux/2.6.27-10.20/+build/793011
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a mem
Alex,
can you make an intrepid non-xcb libX11 available somewhere?
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
xvidcap deadlock backtrace 3
** Attachment added: "lock3.txt"
http://launchpadlibrarian.net/19121100/lock3.txt
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
xvidcap deadlock backtrace 2
** Attachment added: "lock2.txt"
http://launchpadlibrarian.net/19121081/lock2.txt
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Bryce,
as far as fixing the applications are concerned, I don't quite follow
why applications that used to work need to be fixed because libxcb
apparently one way or another changes an API contract that it has no
business of changing.
That being said, if somebody claims its the application's faul
Are you using compiz a.k.a. Desktop Effects?
If so, please try to make sure you don't start your selection of the capture
area on a window border. For example, if you click on the select button and
move the mouse to where you want to select an area, dont press the mouse button
with the pointer o
The original stack trace shows a version 1.1.5, so not related to 1.1.6, no?
Is this otherwise a duplicate of #207406 ?
--
xvidcap crashed
https://bugs.launchpad.net/bugs/92700
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
two things here:
1.) The ubuntu package apparently does not put the ppm2mpeg.sh script to a
location where it will be found automatically. Your workaround seems good.
2.) I very much suspect a usage problem here. xvidcap has a concept of
"multi-frame capture" which records to a video directly. Us
Is the issue of crashing xvidcap when closing windows reproducible? Does
it occur with Xdamage and without?
--
xvidcap
https://bugs.launchpad.net/bugs/4
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
Since this is no longer a glibc task, the whole purpose of this bug has
gone. After finding the exact conditions in glib to cause this, xvidcap
has avoided the problem for ages and not displayed this anymore. Should
be safe to close.
--
get libpthread assertion on multicore CPU
https://bugs.launc
** Attachment added: "information gathered by alsa-info.sh"
http://launchpadlibrarian.net/15999683/alsa-info.txt
--
cannot capture pcm on intel 82801H (ICH8 Family) rev 03
https://bugs.launchpad.net/bugs/248225
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
On a Toshiba M9 laptop with an Intel ICH8 chipset for audio, I can play
audio by adding a module=XXX option to /etc/modprobe.d/alsa-base. I can
even record from the microphone. I cannot, however, record from the PCM
channel, i. e. sound I'm playing back on the laptop e. g. usi
With the snd-hda-intel driver, chances are you need to tune the module options.
Look here:
zless /usr/share/doc/alsa-base/driver/ALSA-Configuration.txt.gz
Then search for hda-intel and look at the "model" options. You may need
to try a few. Start with "model=basic". Between making a change you
ei
"Why can't we just remove the XCB infection/bridge layer from libX11 and
revert it to the stock libX11 module? Let old libX11 programs use that,
and new ones use XCB."
Far as I understand the issue, it is because some apps (e. g. compiz) don't
work without.
I think the ideal short term solution f
Jamey, I would be more than willing to test the socket handoff patches,
but I cannot get the patches to apply well. If I checkout current git
and do git-apply --check --summary, only the first patch does not yield
any problems. I suppose I need to check out a specific revision of
libxcb? If you cou
Ah, btw. to state this clearer: in contrast to the older gutsy problem,
the ttys look fine during boot. Only when X starts, they are gone and
don't return when X is stopped.
--
nvidia driver and blank ttys
https://bugs.launchpad.net/bugs/231039
You received this bug notification because you are a
Public bug reported:
Binary package hint: nvidia-glx-new
On a Toshiba Tecra M9 with an Nvidia Quadro NVM130M, when I use the
restricted drivers all ttys go completely black without blinking cursor
or anything. The ttys are still responsive, but don't show anything.
Using the open source driver (w
I have the same problem on my Toshiba Tecra M9. It works fine with the nv
driver. With the nvidia driver it only works on tty, not for X11.
ref.: http://www.nvnews.net/vbulletin/showthread.php?t=100494&page=3
Tested this with hardy live cd (which has the latest nvidia driver) and it is
not fixed
the missing-kernel-config-for-toshset bug is already there: #181374
--
hardy toshiba_acpi: Unknown parameter `hotkeys_over_acpi'
https://bugs.launchpad.net/bugs/183883
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
interestingly enough, when booting my Toshiba Tecra M9 off the current hardy
live cd most hotkeys do smth.
Audio mute works, brightness up/down works (when not using nvidia drivers).
Bluetooth e. g. does not work where it did ootb on gutsy.
FnFx might work, but I doubt it as toshset does not (wi
Netbeans working but not azureus here supports the assumption that this
is between the xorg update and libswt.
--
xserver-xorg-core update breaks java apps
https://bugs.launchpad.net/bugs/183969
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact f
Dunno about the regression bit because I have just tested on this rather
new laptop with an edgy live cd and it did NOT work for me, either.
--
[gutsy] [regression] (regression from edgy to feisty and to gutsy) tifm_sd
module not working and not producing any message in logs
https://bugs.launchp
Tested with the live CD and still does not work.
The live CD defaults to use of sdhci which does nothing with no output in
/var/log/messages.
Manually unloading sdhci and loading tifm_core, tifm_sd, tifm_7xx1 yields the
same both with card inserted or not while loading.
--
[gutsy] [regression]
my compiz config
** Attachment added: "Default.ini"
http://launchpadlibrarian.net/11147940/Default.ini
** Description changed:
Binary package hint: compiz
I'm trying to get windows positionied explicitly through the "Windows
Placement" plugin in compiz.
Opening a new window on a fix
Public bug reported:
Binary package hint: compiz
I'm trying to get windows positionied explicitly through the "Windows
Placement" plugin in compiz.
Opening a new window on a fixed viewport works for me, using fixed window
dimensions, however, does not.
These are the packages I have installed:
seems to be related to the gconf backend, because switching to file
based backend solves the issue for me.
--
Compiz-Fusion "Show-Desktop" screen edge binding not working
https://bugs.launchpad.net/bugs/156421
You received this bug notification because you are a member of Ubuntu
Bugs, which is th
++
this is also the case for arbitrary commands. I have configured commands
for command 10 and 11 and bound "BottomLeft" and "BottomRight" to those.
compiz-settings-manager didn't let me do it. gconf-editor let me do it
and it works once. Logging out and back in makes it not work, compiz-
settings
++
any progress here?
--
xvidcap 1.1.6 is out (on cvs...) + debian fixes
https://bugs.launchpad.net/bugs/120003
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
before taking this to the gnome folks I was trying rule out a connection
between glibc and the above mentioned gcc bug by recompiling glibc with gcc 3.4
(because __generic_mutex_lock DOES use some inline asm code and could match the
gcc bug).
However, that seems to be beyond my current skills. A
recompiling libglib2.0-0 with gcc 3.4 does not solve the issue and the crashes
keep coming up in g_idle_add().
Dunno if http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29415 means that this is a
question of what compiler glibc was compiled with?
Maybe it is a libglib thing?
--
get libpthread assert
get the same error on edgy and here it's more dramatic because LinuxThreads
support appears to be gone.
Some more research brings up glibc bug # 3328
http://sources.redhat.com/bugzilla/show_bug.cgi?id=3328
that one was rejected and points to gcc bug # 29415
http://gcc.gnu.org/bugzilla/show_bug.cg
since you were saying in bug # 60711:
"where they're assuming some behaviour of LinuxThreads rather than relying on
POSIX semantics. The design of NPTL is radically different: All the internal
opaque structures are different, it uses Thread Local Storage, etc. The only
guarantees for compatabili
alright then, thanks for the detailed answer.
I understand the rationale and will readily agree that (provided the issue LT
has been used to workaround is not in the application) it should be fixed
rather than LT ported to AMD64 to workaround it ;S
Therefore I wouldn't mind closing this one.
--
"We don't offer" as in it's not included in Ubuntu vs. a
general/theoretical availability in Linux, or is this smth. that cannot
exist with AMD64?
--
library ABI-tags not the same for 64bit and 32bit AMD
https://launchpad.net/bugs/60711
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
Hello Jeff,
you don't need any special equipment for xvidcap. You might want to try current
svn trunk, though, and do the usual "./autogen.sh && debian/rules binary"
As for the platforms I've been talking about: Well, since the effect seemed
different on various platforms we've tested some:
AMD3
ref.
http://sourceforge.net/tracker/index.php?func=detail&aid=1551015&group_id=81535&atid=563254
--
get libpthread assertion on multicore CPU
https://launchpad.net/bugs/60708
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
oh and I forgot to mention that this is on dapper
--
get libpthread assertion on multicore CPU
https://launchpad.net/bugs/60708
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
ack ... and that is in the 64 bit environment, of course. In the 32 bit
environment it will work because /lib/libm.so.6 publishes 2.2 as the
minimum kernel version where the 64 bit library publishes 2.6
--
library ABI-tags not the same for 64bit and 32bit AMD
https://launchpad.net/bugs/60711
--
This effectively makes . unusable, IF the application in question is
linked to libm (haven't check others)
--
library ABI-tags not the same for 64bit and 32bit AMD
https://launchpad.net/bugs/60711
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/list
issue # 60711 prevents the use of LD_ASSUME_KERNEL in a 64 bit
environment on AMD64
--
get libpthread assertion on multicore CPU
https://launchpad.net/bugs/60708
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
On a dapper drake AMD64 machine in a 64 bit environment, you have:
[EMAIL PROTECTED]:~$ LC_ALL=C objdump -s -j .note.ABI-tag
/lib/libm.so.6
/lib/libm.so.6: file format elf64-x86-64
Contents of section .note.ABI-tag:
0200 0400 1000 0100 474e5500
Public bug reported:
Binary package hint: libc6
This occurs when running xvidcap current svn trunk
(http://www.sourceforge.net/projects/xvidcap).
The program is multi-threaded and uses a number of mutex locks.
If the program is compiled and run on a non-SMP machine (no HT enabled,
no mulit-core
54 matches
Mail list logo
