Public bug reported:
The following sequence of calls ends up failing in step 4 with EBUSY:
1) pthread_mutex_init(mtx, NULL);
2) pthread_mutex_trylock(mtx);
3) pthread_mutex_unlock(mtx);
4) pthread_mutex_destroy(mtx);
I've attached a self-contained example that fails on 14.10 and passes on
I agree 100% that it is the programmer's responsibility to check for
null pointers and found this bug through testing of my own code.
I also played around with it last night and confirm as well that my
original guess at the cause of this behavior was incorrect.
The only reason I reported this
Public bug reported:
Binary package hint: libc6
This happens both on AMD 64 and i386 of Ubuntu 7.10.
The following c code will segfault:
printf(%s\n, NULL);
The following code will just output (null):
printf(%s \n, NULL);
The distinction is the space between the %s and the \n.
I believe
Small correction: vfprintf.c not vprintf.c. Sorry for the typo.
--
Printf inconsistency when handed null string
https://bugs.launchpad.net/bugs/193795
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I fixed my issue with this by running sudo dpkg-reconfigure -phigh
xserver-xorg. This replaced my xorg.conf with a less inflated version
that fixed the issue. As a side effect it also strips out the bullet-
proof x config info (so only run this if you're comfortable with the
command line and
I can confirm this bug is in the gnome release of gusty as well. I did
not have this problem in feisty, and it only started in gusty.
--
no shutdown option with nvidia driver
https://bugs.launchpad.net/bugs/154668
You received this bug notification because you are a member of Ubuntu
Bugs, which
I'm not sure what did it, but I did a fresh install off the beta CD, and
install all updates through today, and the problem is gone. I did not
need to modify my /etc/fstab or any other file to fix it.
Does this work on anyone else's machine?
--
[feisty] cdrom double entries
I'm not familiar with gnome-vfs or what it does, but the problem was
fixed by changing /dev/hda to /dev/dvd. No further action was necessary
after a reboot. Could this be a problem with the installer not
configuring the devices correctly?
--
[feisty] cdrom double entries
I confirm the same issue on a fresh install of Herd 5 with all the
latest updates.
I get:
Unable to mount the selected volume.
mount: special device /dev/hda does not exist
No /dev/hda exists, but /dev/dvd and /dev/dvdrw both exist.
I attached my /etc/fstab and my lshal -t.
** Attachment
