Hi Christopher,
this is no longer a bug.
Thank you
-Angelo Borsotti
On 9 January 2014 03:40, Christopher M. Penalver
christopher.m.penal...@gmail.com wrote:
Angelo Borsotti, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering
Hi Joseph
it is a bit sad to spend time to isolate a bug, file it, provide all
the additional data asked, see it confirmed and then see that it has
been dropped because bug fixing has taken so much time as to make the
OS release obsolete.
Anyway, knowing that bugs that are not resolved in one
Hi Michael.
the correct text should be:
EINTR The call was interrupted by a signal handler before any of the
requested events occurred; see signal(7).
The issue is that EINTR is not returned when the timeout expires, but only
when one of the events occur.
-Angelo
--
You
I have logged in as guest, and the missing icon is shown. In my home
directory
there is no .profile.
The contents of my xsession error file is quite similar to that of the
guest user.
What could then the cause of the missing icon?
-Angelo
--
You received this bug notification because you are a
The installation is a fresh one, with the default theme. If you need I can
take
a photograph of the screen and send it to you.
-Angelo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/888485
Title:
Public bug reported:
I have upgraded from 11.04 to 11.10, and having a computer with a Nvidia card I
have installed the
latest Nvidia driver thru the Ubuntu software center. On the desktop, on the
top bar, the last
icon I see is the one with my username account. However, there should be one
Public bug reported:
I have upgraded from 11.04 to 11.10. 11.10 comes with a default video driver
that does not work
on a computer that has a Nvidia video card. The desktop freezes to that there
is no way out
except by switching off the computer. I then installed the proprietary Nvidia
driver
Hi Fabio,
yes, the same problem occurs in lucid. I have tested it right now and have
seen that
inotify does not work as expected.
-Angelo
--
inotify does not watch /proc
https://bugs.launchpad.net/bugs/454722
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Tags added: apport-collected
** Description changed:
Compile the following program (inotifyerr.c)
#include stdlib.h
#include stdio.h
#include sys/inotify.h
int main(int argc, char* argv[]){
int fd = inotify_init();
if (fd == -1){
apport information
** Attachment added: AplayDevices.txt
https://bugs.edge.launchpad.net/bugs/454722/+attachment/1513677/+files/AplayDevices.txt
--
inotify does not watch /proc
https://bugs.launchpad.net/bugs/454722
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: ArecordDevices.txt
https://bugs.edge.launchpad.net/bugs/454722/+attachment/1513678/+files/ArecordDevices.txt
--
inotify does not watch /proc
https://bugs.launchpad.net/bugs/454722
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: Card0.Amixer.values.txt
https://bugs.edge.launchpad.net/bugs/454722/+attachment/1513680/+files/Card0.Amixer.values.txt
--
inotify does not watch /proc
https://bugs.launchpad.net/bugs/454722
You received this bug notification because you are a member
apport information
** Attachment added: BootDmesg.txt
https://bugs.edge.launchpad.net/bugs/454722/+attachment/1513679/+files/BootDmesg.txt
--
inotify does not watch /proc
https://bugs.launchpad.net/bugs/454722
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: Card0.Codecs.codec.0.txt
https://bugs.edge.launchpad.net/bugs/454722/+attachment/1513681/+files/Card0.Codecs.codec.0.txt
--
inotify does not watch /proc
https://bugs.launchpad.net/bugs/454722
You received this bug notification because you are a member
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.edge.launchpad.net/bugs/454722/+attachment/1513682/+files/CurrentDmesg.txt
--
inotify does not watch /proc
https://bugs.launchpad.net/bugs/454722
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: IwConfig.txt
https://bugs.edge.launchpad.net/bugs/454722/+attachment/1513683/+files/IwConfig.txt
--
inotify does not watch /proc
https://bugs.launchpad.net/bugs/454722
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: Lspci.txt
https://bugs.edge.launchpad.net/bugs/454722/+attachment/1513684/+files/Lspci.txt
--
inotify does not watch /proc
https://bugs.launchpad.net/bugs/454722
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.edge.launchpad.net/bugs/454722/+attachment/1513686/+files/ProcCpuinfo.txt
--
inotify does not watch /proc
https://bugs.launchpad.net/bugs/454722
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: ProcModules.txt
https://bugs.edge.launchpad.net/bugs/454722/+attachment/1513688/+files/ProcModules.txt
--
inotify does not watch /proc
https://bugs.launchpad.net/bugs/454722
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: PciMultimedia.txt
https://bugs.edge.launchpad.net/bugs/454722/+attachment/1513685/+files/PciMultimedia.txt
--
inotify does not watch /proc
https://bugs.launchpad.net/bugs/454722
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.edge.launchpad.net/bugs/454722/+attachment/1513687/+files/ProcInterrupts.txt
--
inotify does not watch /proc
https://bugs.launchpad.net/bugs/454722
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: UdevDb.txt
https://bugs.edge.launchpad.net/bugs/454722/+attachment/1513689/+files/UdevDb.txt
--
inotify does not watch /proc
https://bugs.launchpad.net/bugs/454722
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: WifiSyslog.txt
https://bugs.edge.launchpad.net/bugs/454722/+attachment/1513691/+files/WifiSyslog.txt
--
inotify does not watch /proc
https://bugs.launchpad.net/bugs/454722
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: UdevLog.txt
https://bugs.edge.launchpad.net/bugs/454722/+attachment/1513690/+files/UdevLog.txt
--
inotify does not watch /proc
https://bugs.launchpad.net/bugs/454722
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hello Fabio,
the error that I have reported in the man page of pthread_cancel has been
corrected. That man page has been updated both in 9.04 and in the releases
after it.
You can then close the bug.
Thank you
-Angelo Borsotti
--
POSIX cancallation points not supported
https
Hello,
I have tested again the hibernation in Ubuntu 10.04, and have seen that the
problem has been solved.
You can then close the bug.
Thank you
-Angelo Borsotti
--
hibernate does not work
https://bugs.launchpad.net/bugs/369757
You received this bug notification because you are a member
is that of a thread, not that of a
process.
The url above instead mentions explicitly that the stack is that of the
current thread.
To remove the bug, the man page file for sigaltstack must be changed to make
it consistent with the url above.
Thank you
-Angelo Borsotti
--
sigaltstack man page error
provide?
Thank you
-Angelo Borsotti
--
timer_delete does not cancel the thread to run the function
https://bugs.launchpad.net/bugs/489497
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
Hi Fabio,
I am on vacation at the moment and have no way to test the bug with lucid,
but I will do it
as soon as I will come back.
Thank you
-Angelo
--
POSIX cancallation points not supported
https://bugs.launchpad.net/bugs/370853
You received this bug notification because you are a member of
Philippe,
then the man page must be changed because it is telling something that is
not
true.
-Angelo
--
raise(3) produces SI_TKILL in siginfo_t
https://bugs.launchpad.net/bugs/370967
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
apport information
** Tags added: apport-collected
** Description changed:
timer_create(), when told to run a function at time expiration, creates
immediately an ancillary thread
(it could have created it when armed, or even better, when expired). When the
timer is deleted, the
apport information
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/48567207/AplayDevices.txt
--
timer_delete does not cancel the thread to run the function
https://bugs.launchpad.net/bugs/489497
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/48567208/ArecordDevices.txt
--
timer_delete does not cancel the thread to run the function
https://bugs.launchpad.net/bugs/489497
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/48567212/BootDmesg.txt
--
timer_delete does not cancel the thread to run the function
https://bugs.launchpad.net/bugs/489497
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: Card0.Amixer.values.txt
http://launchpadlibrarian.net/48567214/Card0.Amixer.values.txt
--
timer_delete does not cancel the thread to run the function
https://bugs.launchpad.net/bugs/489497
You received this bug notification because you are a member of
apport information
** Attachment added: Card0.Codecs.codec.0.txt
http://launchpadlibrarian.net/48567216/Card0.Codecs.codec.0.txt
--
timer_delete does not cancel the thread to run the function
https://bugs.launchpad.net/bugs/489497
You received this bug notification because you are a member
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/48567218/CurrentDmesg.txt
--
timer_delete does not cancel the thread to run the function
https://bugs.launchpad.net/bugs/489497
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: IwConfig.txt
http://launchpadlibrarian.net/48567227/IwConfig.txt
--
timer_delete does not cancel the thread to run the function
https://bugs.launchpad.net/bugs/489497
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/48567243/Lspci.txt
--
timer_delete does not cancel the thread to run the function
https://bugs.launchpad.net/bugs/489497
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: PciMultimedia.txt
http://launchpadlibrarian.net/48567245/PciMultimedia.txt
--
timer_delete does not cancel the thread to run the function
https://bugs.launchpad.net/bugs/489497
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/48567247/ProcCpuinfo.txt
--
timer_delete does not cancel the thread to run the function
https://bugs.launchpad.net/bugs/489497
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/48567249/ProcModules.txt
--
timer_delete does not cancel the thread to run the function
https://bugs.launchpad.net/bugs/489497
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/48567248/ProcInterrupts.txt
--
timer_delete does not cancel the thread to run the function
https://bugs.launchpad.net/bugs/489497
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/48567250/UdevDb.txt
--
timer_delete does not cancel the thread to run the function
https://bugs.launchpad.net/bugs/489497
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/48567251/UdevLog.txt
--
timer_delete does not cancel the thread to run the function
https://bugs.launchpad.net/bugs/489497
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Jeremy,
I have tested the issue with 10.04: it is still there.
I have used apport to collect data and send them.
-Angelo
--
timer_delete does not cancel the thread to run the function
https://bugs.launchpad.net/bugs/489497
You received this bug notification because you are a member of
apport information
** Attachment added: WifiSyslog.txt
http://launchpadlibrarian.net/48567255/WifiSyslog.txt
--
timer_delete does not cancel the thread to run the function
https://bugs.launchpad.net/bugs/489497
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi Jeremy,
I have tested in with Ubuntu 10.04. The problem is still there.
I did not collect data with apport because the problem is just a
documentation
error in a man page.
-Angelo
--
sigaltstack man page error
https://bugs.launchpad.net/bugs/488691
You received this bug notification because
Public bug reported:
timer_create(), when told to run a function at time expiration, creates
immediately an ancillary thread
(it could have created it when armed, or even better, when expired). When the
timer is deleted, the
ancillary thread does not get cancelled. Not even if it was created as
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/36194119/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/36194120/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/36194121/ArecordDevices.txt
Public bug reported:
man sigaltstack
.
sigaltstack() allows a process to define a new alternate signal stack ...
This is not correct: sigaltstack allows a thread to define a new alternate
signal stack
for signals handlers for signals delivered to it (as reported in the IEEE Std
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/36108344/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/36108345/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/36108346/ArecordDevices.txt
Public bug reported:
man epoll_wait states:
EINTR The call was interrupted by a signal handler before any of the
requested events occurred or the timeout expired; see signal(7).
However, epoll_wait does not return EINTR when the timeout expires, it
simply returns 0 as number of
:
https://help.ubuntu.com/9.04/installation-guide/i386/install-overview.html
Thank you
-Angelo Borsotti
--
support for reinstallation
https://bugs.launchpad.net/bugs/460958
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
want the installer to install the system
creating whatever root file system it needs.
I ask you then not to close the bug, unless there is a way to overcome
this problem and succeed to install the system on an existing partition.
Thank you
-Angelo Borsotti
--
support for reinstallation
https
Public bug reported:
The current installer does not support reinstallation. However, the need to
reinstall the system
occurs. For example, I have now upgraded from 9.04 to 9.10RC, but the upgrade
process
corrupted the system, to the point that it cannot even bootstrapped.
To overcome the
Public bug reported:
Compile the following program (inotifyerr.c)
#include stdlib.h
#include stdio.h
#include sys/inotify.h
int main(int argc, char* argv[]){
int fd = inotify_init();
if (fd == -1){
perror(inotify_init);
}
char path[256];
Hi,
I have found the problem after havind updated Ubuntu. This means that the
colors used by ls have changed.
Of course, the programmer that has the task to develop ls cannot know what
background colors the user is using.
By the same token the user cannot foretell what changes will be made to
Hello,
it seems it is a combination of an ls and a terminal coloring issue.
I did the tests you suggests: changing the terminal background and
using a TTY (which has a back background), the names that were
invisible before become visible.
I am a heavy command-line user too, and I did not notice
Public bug reported:
Binary package hint: gnome-terminal
ls -la does not show directory names.
However, it shows them if run using script, e.g. script -c ls-la, or if
its output is redirected to a file, lile, e.g. ls -la tmp, or if run
from superuser, i.e. sudo ls -la.
The problem occurs only
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/32901918/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/32901919/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/32901920/ProcStatus.txt
--
ls -la
** Attachment added: ls -la output
http://launchpadlibrarian.net/32902195/Screenshot.png
--
ls -la fails to print directory names
https://bugs.launchpad.net/bugs/441142
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Hi Dave,
thank you very much for your prompt reply. It is perfectly understandable
that
a sigset_t must be initialized before calling one such function. However, I
have called sigpending() before calling sigisemptyset(). Now sigpending()
returns the set of signals that are pending By this, I
ignore (to refuse
to take notice of -Merrian-Webster dictionary) in the man pages, which
would not otherwise
be the case stating that the program takes notice of something it is not
told to do.
Thank you
-Angelo Borsotti
--
sigwait() resumed by ignored signal
https://bugs.launchpad.net/bugs
Hi,
I know, sigwait() does not change the disposition set by sigaction(), but
from the user's point takes precedence over it. Override means
prevail over. Isn't it the correct word to explain what it does?
-Angelo
--
sigwait() resumed by ignored signal
https://bugs.launchpad.net/bugs/431813
Public bug reported:
Compile and run the following program file (sigpending.c):
#include signal.h
#include stdio.h
int main(int argc, char* argv[]){
sigset_t sigpend;
sigpending(sigpend);
printf(empty? %d\n,sigisemptyset(sigpend));
int i;
for (i = 1; i SIGRTMAX; i++){
Public bug reported:
A program that sets the disposition of a signal to ignore (SIG_IGN) should not
be affected by the ignored signals. However, this is not the case when it calls
sigwait().
Compile and run this program file (sigwait.c):
#include stdio.h
#include signal.h
int main(int argc,
Hello,
this bug is still marked incomplete, but it has been reported roughly two
months ago, and all the
requested data provided. I have updated today the software, but the bug is
still there.
--
hibernate does not work
https://bugs.launchpad.net/bugs/369757
You received this bug notification
Public bug reported:
Binary package hint: network-manager
Periodically, I see bursts of process creation and cancellations from
hal-acl-tool. E.g.
15:0:1.111506635 fork pid 27484 parent: 27454 /usr/lib/hal/hal-acl-tool
15:0:1.112480222 exec pid 27484
Hello,
this bug is still marked incomplete, but I have provided all the information
I was
requested to. Is there any other data that can shed some light on it?
This bug is very annoying because it forces the user to shut down the computer
every day (in order to save power during the night)
Why this bug is marked incomplete? Is any information missing?
--
pthread_kill ESRCH
https://bugs.launchpad.net/bugs/374769
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
Charlie,
I have isolated the bug that occurred in a large application into a small
file, that I have included in my problem report.
In case you have not received it, here is the file again. Copy it into a
text editor window, save it as errkill.c, compile and run it: you will
see that the program
Public bug reported:
Man page of pthread_kill:
...
The pthread_kill function returns the following error codes on error:
EINVAL signo is not a valid signal number
ESRCH the thread thread does not exist (e.g. it has already
terminated)
Hello
here is is:
$ aptitude search restricted
p kubuntu-restricted-extras - Commonly used restricted packages
p linux-restricted-modules- Generic Linux restricted modules.
i linux-restricted-modules-2.6.28 - Non-free Linux kernel modules for version
p
Hello,
today, I have booted Ubuntu, and let the Update Manager install the available
updates.
After that, I tried Hibernate (in the hope the problem had been resolved).
The problem has become even worse: after displaying the unlock window
(as before), the mouse cursor becomes the waiting wheel,
Hello,
first, something that might be important: hibernate works properly in Ubuntu 8.
I attach then the output of lspci, and those of hardinfo, biosdecode
and dmidecode,
which sould provide all the data you asked. Let me know if some are
not provided.
kernel version:
Linux angelo-desktop
Hello,
I have tried to do what you requested. This time, however, Hybernate behaves
differently from a couple of days ago, when I reported the problem: when I hit
Hybernate, the screen becomes black, and a few seconds later, a window
appears, with my username as title, an input field requesting
Public bug reported:
I have a dual boot configuration, with Ubuntu and Vista. From within Ubuntu I
can access the
Vista NTFS partitions.
However, if after login I open a terminal window, I cannot change the current
directory to a
NTFS partition (cd /media/Volume). See Screenshot1.
If I hit
Public bug reported:
I hit the top-right switch user or shut down button and then selected
hyberhate.
The screen becomes almost black, and nothing else happens. The computer does
not switch off, or even set to the low power consumption mode.
Moreover, there is no way to resume normal operation
79 matches
Mail list logo
