[Bug 1663904] Re: tpm_tis: a TPM error occurred attempting to read a PCR value
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/class/tmp/tpm0/device/temp_deactivated has a value of 1 and tpm_infineon is loaded as a module on top of the tpm_tis compiled into the kernel. I _hope_ _not_ loading tpm_tis would make the chip work with the older tpm_infineon module, but at least (if that doesn't work) loading tpm_tis as a module would allow me to blacklist it and not get the error message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1663904 Title: tpm_tis: a TPM error occurred attempting to read a PCR value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398779] [NEW] scrollkeeper-preinstall / rarian-sk-preinstall broken
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-preinstall.cpp.new
--- rarian-0.8.1/util/rarian-sk-preinstall.cpp 2008-09-01 20:40:21.0
+0200
+++ rarian-0.8.1/util/rarian-sk-preinstall.cpp.new 2009-07-13
15:08:04.0 +0200
@@ -42,8 +42,7 @@
get_attribute (TiXmlElement *elem)
{
TiXmlAttribute* pAttrib=elem->FirstAttribute();
-if (strcmp (pAttrib->Value(), "")) {
-
+if (!strcmp (pAttrib->Value(), "")) {
elem->SetAttribute("url", new_url);
}
}
** Affects: rarian (Ubuntu)
Importance: Undecided
Status: New
--
scrollkeeper-preinstall / rarian-sk-preinstall broken
https://bugs.launchpad.net/bugs/398779
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 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver
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 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 292878] Re: eclipse error when using firefox !
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. -- eclipse error when using firefox ! https://bugs.launchpad.net/bugs/292878 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 290153] Re: Fails to find boot device in Intel D945Gnt
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 machine through various releases. Restricted drivers have long since been upgraded, dkms wouldn't work, etc. Have now manually dl'ed corresponding kernel sources, configured them and can now use dkms. So, I can work for now. -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 290153] Re: Fails to find boot device in Intel D945Gnt
"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-based distro? -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66664] Re: xvidcap crashes while creating a lengthy video
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/185311 -- xvidcap crashes while creating a lengthy video 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 66664] Re: xvidcap crashes while creating a lengthy video
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/.themes/Darker theme/gtk-2.0/gtkrc:50: Clearlooks > configuration option "menuitemstyle" is not supported and will be ignored. > /home/browe/.themes/Darker theme/gtk-2.0/gtkrc:51: Clearlooks > configuration option "listviewitemstyle" is not supported and will be > ignored. > /home/browe/.themes/Darker theme/gtk-2.0/gtkrc:52: Clearlooks > configuration option "progressbarstyle" is not supported and will be > ignored. > [mpeg4 @ 0xb77a46e8]removing common factors from framerate > Locking assertion failure. Backtrace: > #0 /usr/lib/libxcb-xlib.so.0 [0xb6beb767] > #1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_unlock+0x31) [0xb6beb8b1] > #2 /usr/lib/libX11.so.6 [0xb7099421] > #3 /usr/lib/libX11.so.6(XPending+0x43) [0xb70839b3] > #4 /usr/lib/libgdk-x11-2.0.so.0 [0xb7add04d] > #5 /usr/lib/libgdk-x11-2.0.so.0 [0xb7add141] > #6 /usr/lib/libglib-2.0.so.0(g_main_context_prepare+0x18f) [0xb78d257f] > #7 /usr/lib/libglib-2.0.so.0 [0xb78d2d39] > #8 /usr/lib/libglib-2.0.so.0(g_main_loop_run+0x1e7) [0xb78d3467] > #9 /usr/lib/libgtk-x11-2.0.so.0(gtk_main+0xb4) [0xb7d88264] > #10 xvidcap(xvc_ui_run+0xb) [0x805b02b] > #11 xvidcap(main+0x84f) [0x806732f] > #12 /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7165450] > #13 xvidcap [0x8051371] > > -- > xvidcap crashes while creating a lengthy video > https://bugs.launchpad.net/bugs/4 > You received this bug notification because you are a direct subscriber > of the bug. > > -- xvidcap crashes while creating a lengthy video 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 290153] Re: Fails to find boot device in Intel D945Gnt
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.deb linux-image-2.6.28-5-generic_2.6.28-5.15_i386.deb linux-restricted-modules_2.6.28.5.5_i386.deb linux-restricted-modules-2.6.28-5-generic_2.6.28-5.5_i386.deb linux-restricted-modules-generic_2.6.28.5.5_i386.deb For me, the problem persists, only that I now get the COMRESET stuff before the bootsplash. So where previously the order was: 1. bootsplash, 2. message, 3. timeout. 4. busybox, it is now: 1. message, 2. bootsplash, 3. timeout, 4. busybox. -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 290153] Re: Fails to find boot device in Intel D945Gnt
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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 290153] Re: Fails to find boot device in Intel D945Gnt
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.769243] ACPI: Unable to derive IRQ for device :00:11.1 [ 26.769245] ACPI: PCI Interrupt :00:11.1[A]: no GSI [ 26.769258] VP_IDE: chipset revision 6 [ 26.769260] VP_IDE: not 100% native mode: will probe irqs later [ 26.769272] VP_IDE: VIA vt8233a (rev 00) IDE UDMA133 controller on pci:00:11.1 [ 26.769282] ide0: BM-DMA at 0x9400-0x9407, BIOS settings: hda:DMA, hdb:DMA [ 26.769295] ide1: BM-DMA at 0x9408-0x940f, BIOS settings: hdc:DMA, hdd:DMA [ 26.769304] Probing IDE interface ide0... [ 26.793413] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB) [ 26.793458] sd 0:0:0:0: [sda] Write Protect is off [ 26.793461] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 26.793478] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 26.793555] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB) [ 26.793564] sd 0:0:0:0: [sda] Write Protect is off [ 26.793567] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 26.793579] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 26.793585] sda: sda1 [ 26.811244] sd 0:0:0:0: [sda] Attached SCSI disk [ 26.811433] sd 1:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB) [ 26.811448] sd 1:0:0:0: [sdb] Write Protect is off [ 26.811450] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 26.811465] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 26.811507] sd 1:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB) [ 26.811515] sd 1:0:0:0: [sdb] Write Protect is off [ 26.811518] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 26.811531] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 26.811534] sdb: sdb1 [ 26.831648] sd 1:0:0:0: [sdb] Attached SCSI disk [ 26.836660] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 26.836693] sd 1:0:0:0: Attached scsi generic sg1 type 0 ** Attachment added: "lspci.out" http://launchpadlibrarian.net/20077013/lspci.out -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269831] Re: toshset does not support tlsup module (Intrepid)
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 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 290153] Re: Fails to find boot device in Intel D945Gnt
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 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 185311] Re: hardy, locking assertion failure, xorg/libsdl
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185311] Re: hardy, locking assertion failure, xorg/libsdl
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185311] Re: hardy, locking assertion failure, xorg/libsdl
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185311] Re: hardy, locking assertion failure, xorg/libsdl
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 fault, I'd really appreciate some information about what I need to fix around somthing that wasn't even apparently broken with Xlib. I can attach 3 backtraces of various ways xvidcap deadlocks with libxcb (variant 3 resulting in a complete X11 lockup, so I need to ssh into the box and kill xvidcap). The only thing I can see is that in one thread I'm trying to do XShmGetImage on a locked X display while in the other thread GTK does its stuff. Have I been doing this completely wrong for years without noticing? And I've just recorded more than an hour of screencasts without a single hang with your non-xcb libraries. This issue keeps me from upgrading to intrepid because first I'll have to find a way of compiling the required X11 libs without xcb. ** Attachment added: "lock1.txt" http://launchpadlibrarian.net/19120781/lock1.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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 244191] Re: 'BadColor (invalid Colormap parameter)'
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 over a window border or title. If you do this, you will be able to drag the mouse and select an area. But once you have selected the area and release the mouse pointer, the application will crash. This is a long standing issue with xvidcap and compiz because compiz does not return XWindowAttributes of the window when querying for them on the window border. -- 'BadColor (invalid Colormap parameter)' https://bugs.launchpad.net/bugs/244191 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 92700] Re: xvidcap crashed
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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 244204] Re: ppm2mpeg.sh: command not found and other encoding problems
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. Using that, you don't need ppm2mpeg.sh AT ALL. Just do this (as an example on the command line of options you can also select through the preferences): # xvidcap --mf --file /tmp/test.avi --auto ... record smth. # totem /tmp/test.avi You only need ppm2mpeg.sh if you use "single-frame capture". That captures to individual screenshot image files. Those you can encode to a video. The script provided with xvidcap does not work with XWD files. The following should work: # xvidcap --sf --file /tmp/test-%d.png --auto record smth. select "encode" from the xvidcap menu # totem /tmp/output.avi Please read the xvidcap online help for more information and let us know how you fare. -- ppm2mpeg.sh: command not found and other encoding problems https://bugs.launchpad.net/bugs/244204 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 66664] Re: xvidcap
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60708] Re: get libpthread assertion on multicore CPU
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.launchpad.net/bugs/60708 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 248225] Re: cannot capture pcm on intel 82801H (ICH8 Family) rev 03
** 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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 248225] [NEW] cannot capture pcm on intel 82801H (ICH8 Family) rev 03
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. using rhythmbox, no matter what model I select (currently "basic"). It seems the module does not provide a way to feed PCM to the mixer as an input source. You can see my mixer settings in the attachment, but I've tried various permutations. On my gutsy machine with a different soundcard, I have a PCM recording channel for the OSS device, on this machine, the OSS device doesn't even display a "recording" tab, and the alsa device doesn't list PCM as an input source. ** Affects: ubuntu Importance: Undecided Status: New -- 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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 156713] Re: Intel ICH8 Rev 03 ALC8888 Headphone sense does not work
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 either need to reboot or completely restart alsa. If you want to do it without reboot, you should start your computer with a plain xterm session (no artsd, pulseaudio or the like), test, make a change to /etc/modprobe.d/alsa-base, /sbin/alsa unload, verify alsa modules have been unloaded by: lsmod | grep snd (which should show nothing at this time), modprobe snd-hda-intel (check lsmod again), test again, repeat as needed. -- Intel ICH8 Rev 03 ALC Headphone sense does not work https://bugs.launchpad.net/bugs/156713 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 87947] Re: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
"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 for hardy would be to provide both versions of libX11. Make the non-xcb version the default and make apps which need xcb depend on the xcb enabled version placed in a different directory, then compile them with a runtime linker path pointing to that alternative xcb-enabled library. I have just tested Bryce's non-xcb libs by simply extracting the debs to a given directory, unsetting LIBXCB_ALLOW_SLOPPY_LOCK, setting LD_LIBRARY_PATH to the directory with the the non-xcb libX11 and starting an app I was previously having problems with on hardy but none on gutsy. And, of course, everything worked like a charm. -- xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/87947 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 87947] Re: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
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 could give me a hint as to how I can find the right revision, I'll give it a shot. -- xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/87947 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 231039] Re: nvidia driver and blank ttys
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 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 231039] [NEW] nvidia driver and blank ttys
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 (with the xorg.conf you get by running dpkg-reconfigure xserver-xorg) works. Just adding Driver = "nvidia" to the device's section yields the behaviour. This is on hardy. On gutsy, I was seeing a similar issue which could be fixed by making sure fbcon and vesafb were loaded during boot. I've tried removing all vga=* and splash from kernel boot options, vga=normal, and vga=71. I've tried to get older nvidia drivers to work (without success) and the beta 173.08 without betterment. I'm referencing nvidia-glx-new because of reports that using nvidia-glx solves the issue (which I can't seem to be able to do). ** Affects: linux-restricted-modules-2.6.24 (Ubuntu) Importance: Undecided Status: New -- nvidia driver and blank ttys https://bugs.launchpad.net/bugs/231039 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 151828] Re: [gutsy] brightness keys only pop up a slider on a t61p, they don't affect screen brightness
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 there, for me. -- [gutsy] brightness keys only pop up a slider on a t61p, they don't affect screen brightness https://bugs.launchpad.net/bugs/151828 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 183883] Re: hardy toshiba_acpi: Unknown parameter `hotkeys_over_acpi'
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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 183883] Re: hardy toshiba_acpi: Unknown parameter `hotkeys_over_acpi'
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 (will file a separate bug) due to missing kernel support. -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 183969] Re: xserver-xorg-core update breaks java apps
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 for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 137686] Re: [gutsy] [regression] (regression from edgy to feisty and to gutsy) tifm_sd module not working and not producing any message in logs
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.launchpad.net/bugs/137686 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 137686] Re: [gutsy] [regression] (regression from edgy to feisty and to gutsy) tifm_sd module not working and not producing any message in logs
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] (regression from edgy to feisty and to gutsy) tifm_sd module not working and not producing any message in logs https://bugs.launchpad.net/bugs/137686 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 180316] Re: fixed window placement not working
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 fixed viewport works for me, using fixed window dimensions, however, does not. These are the packages I have installed: - [EMAIL PROTECTED]:~$ dpkg --list '*compiz*' - Desired=Unknown/Install/Remove/Purge/Hold - | Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend - |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) - ||/ Name Version Beschreibung - +++-==-==- - ii compiz 1:0.6.2+git20071119-0ubuntu1~gutsy1OpenGL window and compositing manager - un compiz-compcomm-plugins-main (keine Beschreibung vorhanden) - ii compiz-core 1:0.6.2+git20071119-0ubuntu1~gutsy1OpenGL window and compositing manager - un compiz-extra (keine Beschreibung vorhanden) - ii compiz-fusion-plugins-extra0.6.0+git20071121-0ubuntu1~gutsy1 Collection of extra plugins from OpenCompositing for Compiz - ii compiz-fusion-plugins-main 0.5.2+git20070928-0ubuntu2 Collection of plugins from OpenCompositing for Compiz - ii compiz-gnome 1:0.6.2+git20071119-0ubuntu1~gutsy1OpenGL window and compositing manager - GNOME window decorator - un compiz-gtk (keine Beschreibung vorhanden) - ii compiz-plugins 1:0.6.2+git20071119-0ubuntu1~gutsy1OpenGL window and compositing manager - plugins - ii compizconfig-settings-manager 0.5.2+git20070912-0ubuntu1 Compiz configuration settings manager - ii libcompizconfig-backend-gconf 0.5.2+git20071010-0ubuntu1 Settings library for plugins - OpenCompositing Project - ii libcompizconfig0 0.5.2+git20070919-0ubuntu3 Settings library for plugins - OpenCompositing Project - ii python-compizconfig0.5.2+git20070912-0ubuntu1 Compiz configuration system bindings + compiz 1:0.6.2+git20071119-0ubuntu1~gutsy1 + compiz-core 1:0.6.2+git20071119-0ubuntu1~gutsy1 + compiz-fusion-plugins-extra 0.6.0+git20071121-0ubuntu1~gutsy1 + compiz-fusion-plugins-main 0.5.2+git20070928-0ubuntu2 + compiz-gnome 1:0.6.2+git20071119-0ubuntu1~gutsy1 + compiz-plugins 1:0.6.2+git20071119-0ubuntu1~gutsy1 + compizconfig-settings-manager 0.5.2+git20070912-0ubuntu1 + libcompizconfig-backend-gconf 0.5.2+git20071010-0ubuntu1 + libcompizconfig0 0.5.2+git20070919-0ubuntu3 + python-compizconfig 0.5.2+git20070912-0ubuntu1 I'll attach my compiz config next. -- fixed window placement not working https://bugs.launchpad.net/bugs/180316 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 180316] fixed window placement not working
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: compiz 1:0.6.2+git20071119-0ubuntu1~gutsy1 compiz-core 1:0.6.2+git20071119-0ubuntu1~gutsy1 compiz-fusion-plugins-extra 0.6.0+git20071121-0ubuntu1~gutsy1 compiz-fusion-plugins-main 0.5.2+git20070928-0ubuntu2 compiz-gnome 1:0.6.2+git20071119-0ubuntu1~gutsy1 compiz-plugins 1:0.6.2+git20071119-0ubuntu1~gutsy1 compizconfig-settings-manager 0.5.2+git20070912-0ubuntu1 libcompizconfig-backend-gconf 0.5.2+git20071010-0ubuntu1 libcompizconfig0 0.5.2+git20070919-0ubuntu3 python-compizconfig 0.5.2+git20070912-0ubuntu1 I'll attach my compiz config next. ** Affects: compiz (Ubuntu) Importance: Undecided Status: New -- fixed window placement not working https://bugs.launchpad.net/bugs/180316 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 156421] Re: Compiz-Fusion "Show-Desktop" screen edge binding not working
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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 156421] Re: Compiz-Fusion "Show-Desktop" screen edge binding not working
++ 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-manager do not show anything. gconf-editor still shows the values, but they have no effect. Just opening and closing the list editor for the list values of the edge binding (without changing or adding a value) reactivates them for the current session. -- 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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120003] Re: xvidcap 1.1.6 is out (on cvs...) + debian fixes
++ 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60708] Re: get libpthread assertion on multicore CPU
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. After spending hours on getting glibc compiled from the source debs, I spent another few hours making my system boot again. So, if anybody here with more xp tinkering with glibc could help out here, trying to narrow this down, that would be much appreciated. -- 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
[Bug 60708] Re: get libpthread assertion on multicore CPU
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 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
[Bug 60708] Re: get libpthread assertion on multicore CPU
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.cgi?id=29415 That in turn suggests that an addition to gcc after 4.1.1. introduces a bug. And edgy has some gcc additions after 4.1.1: gcc version 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5) On the other hand, that would not explain why I was seeing this on dapper. Looking at the backtrace of the crash, it strikes me that it always happens in the same spot (where the application uses a number of mutex locks): Core was generated by `/home/kb87850/xvidcap/bin/xvidcap --file test-%d.avi --fps 10 --continue yes --'. Program terminated with signal 6, Aborted. #0 0xe410 in __kernel_vsyscall () (gdb) bt #0 0xe410 in __kernel_vsyscall () #1 0xb7544770 in raise () from /lib/tls/i686/cmov/libc.so.6 #2 0xb7545ef3 in abort () from /lib/tls/i686/cmov/libc.so.6 #3 0xb753ddbb in __assert_fail () from /lib/tls/i686/cmov/libc.so.6 #4 0xb7725591 in pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0 #5 0xb775e517 in g_source_attach () from /usr/lib/libglib-2.0.so.0 #6 0xb775e67c in g_idle_add_full () from /usr/lib/libglib-2.0.so.0 #7 0xb775e6e8 in g_idle_add () from /usr/lib/libglib-2.0.so.0 #8 0x08060cf2 in commonCapture (xtp=0xb77c21e4, capfunc=1) at capture.c:721 #9 0x08060f9c in TCbCaptureSHM (xtp=0x0) at capture.c:808 #10 0x080641b6 in do_record_thread (job=0x87178b0) at gnome_ui.c:974 #11 0xb7723504 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #12 0xb75e851e in clone () from /lib/tls/i686/cmov/libc.so.6 (gdb) I'm ALWAYS seeing the crash after a call to g_idle_add which would point at glib ... But perhaps that's just because it or glibc were compiled with gcc 4.1.1+ If the binaries for glib or glibc are broken, I'd call that bad. Karl. -- 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
[Bug 60708] Re: get libpthread assertion on multicore CPU
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 compatability are those that POSIX offers." all I'm doing to manipulate threads is done through these functions (on more than those instances, though): g_thread_init(NULL); pthread_attr_init(&recording_thread_attr); pthread_attr_setdetachstate(&recording_thread_attr, PTHREAD_CREATE_JOINABLE); pthread_cond_init(&recording_condition_unpaused, NULL); pthread_cond_wait(&recording_condition_unpaused, &recording_mutex); pthread_create(&recording_thread, &recording_thread_attr, (void *) do_record_thread, (void *) job); pthread_exit(NULL); pthread_join(recording_thread, NULL /* (void **) &status*/ ); pthread_mutex_init(&recording_mutex, NULL); pthread_mutex_lock(&recording_mutex); pthread_mutex_unlock(&recording_mutex); XInitThreads(); pthread_mutex_trylock(&mp) pthread_kill(tid, SIGUSR1); those don't constitue relying on opaque structures, do they?!? Also, wouldn't that break on a single CPU, too? -- 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
[Bug 60711] Re: library ABI-tags not the same for 64bit and 32bit AMD
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. -- 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/listinfo/ubuntu-bugs
[Bug 60711] Re: library ABI-tags not the same for 64bit and 32bit AMD
"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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60708] Re: get libpthread assertion on multicore CPU
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: AMD32 (Athlon XP) : works like a charm P4 3GHz (HT enabled with SMP kernel) : chrashes every so often (~1-2 times out of ten) AMD64 (Multicore CPU with SMP kernel : crashes (next to) every time My guess is that this is somehow related to higher CPU speeds and/or more fine-grained timings increasing the probability of this happening. Also, LinuxThreads or non-SMP seem to avoid this problem. I've read of a somewhat similar case (ages ago, though) where the error is due to individual threads !on different CPUs! getting a mutex at the same time. Dunno if this is the same here, too, though. Thanks for your help, Karl. -- 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
[Bug 60708] Re: get libpthread assertion on multicore CPU
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
[Bug 60708] Re: get libpthread assertion on multicore CPU
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
[Bug 60711] Re: library ABI-tags not the same for 64bit and 32bit AMD
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60711] Re: library ABI-tags not the same for 64bit and 32bit AMD
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/listinfo/ubuntu-bugs
[Bug 60708] Re: get libpthread assertion on multicore CPU
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
[Bug 60711] library ABI-tags not the same for 64bit and 32bit AMD
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 GNU. 0210 0200 0600 However, in a 32 bit environment you have: [EMAIL PROTECTED]:~$ LC_ALL=C objdump -s -j .note.ABI-tag /lib/tls/i686/cmov/libm.so.6 /lib/tls/i686/cmov/libm.so.6: file format elf32-i386 Contents of section .note.ABI-tag: 0114 0400 1000 0100 474e5500 GNU. 0124 0200 0600 [EMAIL PROTECTED]:~$ LC_ALL=C objdump -s -j .note.ABI-tag /lib/tls/libm.so.6 /lib/tls/libm.so.6: file format elf32-i386 Contents of section .note.ABI-tag: 0114 0400 1000 0100 474e5500 GNU. 0124 0200 0600 [EMAIL PROTECTED]:~$ LC_ALL=C objdump -s -j .note.ABI-tag /lib/libm.so.6 /lib/libm.so.6: file format elf32-i386 Contents of section .note.ABI-tag: 0114 0400 1000 0100 474e5500 GNU. 0124 0200 0200 This effectively makes LD_ASSUME_KERNEL (and thus LinuxThreads as an alternative to NPTL) unusable. Shouldn't this be transparent? ** Affects: glibc (Ubuntu) Importance: Untriaged Status: Unconfirmed -- 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/listinfo/ubuntu-bugs
[Bug 60708] get libpthread assertion on multicore CPU
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) everything is fine. If the program is run on a multi-core CPU or a e.g. a P4 with HT enabled, I frequently get this: xvidcap: pthread_mutex_lock.c:108: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed. Aborted On the platforms where the error occurs, setting LD_ASSUME_KERNEL=2.4.19 makes the problem go away (if the libraries present allow the use of LD_ASSUME_KERNEL which is not always the case, but I'll file a separate bug for that). This effectively disables NPTL. All this stuff should be transparent to the application, though. The application just uses libpthread. If the application works with LinuxThreads it should work with NPTL. If the application works with NPTL on a single core, it should work on an SMP box (that's the SMP paradigm after all) ** Affects: glibc (Ubuntu) Importance: Untriaged Status: Unconfirmed -- 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
