Bug#906158: intel-microcode: Update intel-microcode to 20180807
Hello. Do you have confirmation that they will change the license? Should we contact (pester) them or do you think this is not more necessary now? Hey! Thanks a lot for the great work and service you are doing with this updates! Very appreciated! Have a great day. -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ Freelance C++/PHP programmer and GNU/Linux systems administrator. The sky is not the limit!
Bug#886367: partial fix uploaded
It's the same level of protection.
HTH.
Bye!
El 15/01/18 a las 07:33, Andreas
Heinlein escribió:
On Thu, 4 Jan 2018 23:18:49 -0200 Henrique de Moraes Holschuh
wrote:
> Intel has released several updates already, but not all of
them AFAIK.
>
> These microcode updates are of little impact until the
kernel changes to
> activate the new MSRs are deployed. But they do mess with
conditional
> jumps and LFENCE.
>
> Anyway, uploading a partial, unofficial set of updates to
unstable to
> close the bug. Several processors are still missing. I
expect an
> official release from Intel soon, hopefully with updates
for everything.
>
> Everyone should look for firmware updates, the usual good
vendors
> already have them out, or will have them out by the end of
the next
> week.
Sorry for the question, this is not exactly the right place but
I know of no better one:
Do microcode updates delivered by this package have the same
effect as BIOS/Firmware updates? Or do they complement each
other?
At our organization, we unfortunately have a large number of
different machines from different vendors, and updating the BIOS
on all of them will be a very time consuming task. So I'd like
to ask whether we can expect the same protection from updated
microcode and kernel packages.
Thanks,
Andreas
--
Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/
Freelance C++/PHP programmer and GNU/Linux systems administrator.
The sky is not the limit!
Bug#762700: systemd: journald fails to forward some messages to syslog
Hello.
Sorry if what I ask is very silly, but I feel I need to ask anyway...
If sysvinit started syslog and waited for it and then started
everything else, why can't we do the same with systemd?
I mean, don't create the socket and then start syslog, but just
start syslog and make everything that logs wait for it like in sysvinit.
Is this just a performance optimization or is there another reason?
BTW, my system says "systemd-journal[153]: Forwarding to syslog
missed 293 messages.".
Another thing I don't understand is why after startup, in normal
operation, things like NetworkManager or some other daemons can lose
messages to syslog? Does that happen with sysvinit too or is it a
systemd specific thing?
RHEL7 has the same issue? Maybe they have solved it or do something
differently, but it could be useful to look...
Thanks and sorry for being dumb!
Have a great day!
--
Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/
From Montevideo, Uruguay, at the south of South America.
Freelance programmer and GNU/Linux system administrator, hire me!
Alternatives: iba...@codigolibre.net - http://go.to/ibaldo
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#779825: no port attached to webserver
Hello.
Maybe you don't have IPv6 at all configured, not even in the "lo"
interface?
Whats the output of "ip -6 addr"?
Thanks!
--
Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/
From Montevideo, Uruguay, at the south of South America.
Freelance programmer and GNU/Linux system administrator, hire me!
Alternatives: iba...@codigolibre.net - http://go.to/ibaldo
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#779825: no port attached to webserver
Hello Shirish! Good news, thats it, you don't have IPv6 at all configured, not even for the loopback interface, which is a pretty non standard setup nowadays so be careful, other services could act badly. I don't know what the Policy document says about this situation, but shouldn't the install succeed even if Nginx couldn't be started? For example, suppose that I want to remove all IPv6 support from a server, I think the package should install correctly anyway and let me fix the configuration later myself to avoid listening on IPv6 and listen only in IPv4. Or what happens if I have something else listening on port 80 (a reverse proxy for example) and I want to install Nginx and then change it to listen on port 81 instead? This is not a bug on _installation_ but on _startup_, there's a difference. Of course this is my own personal opinion and haven't read the Policy document in years... Thanks all, have a great day everybody! El 09/03/15 a las 09:59, shirish शिरीष escibió: Hi Ivan, The output is :- $ ip -6 addr $ On 3/9/15, Ivan Baldo wrote: Hello. Maybe you don't have IPv6 at all configured, not even in the "lo" interface? Whats the output of "ip -6 addr"? Thanks! -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: iba...@codigolibre.net - http://go.to/ibaldo -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: iba...@codigolibre.net - http://go.to/ibaldo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#779825: no port attached to webserver
Ok, decided to check current Debian Policy Manual and there isn't a
specific mention of what to do when starting a service after dpkg's
configuration phase and that service fails.
So I guess is up to maintainers of this package to decide.
For what is worth, I vote for just continuing anyway and let the
sysadmin fix it later, since it surely will see that the webserver isn't
starting...
Thanks for your consideration!
El 09/03/15 a las 10:14, Ivan Baldo escibió:
Hello Shirish!
Good news, thats it, you don't have IPv6 at all configured, not
even for the loopback interface, which is a pretty non standard setup
nowadays so be careful, other services could act badly.
I don't know what the Policy document says about this situation,
but shouldn't the install succeed even if Nginx couldn't be started?
For example, suppose that I want to remove all IPv6 support from a
server, I think the package should install correctly anyway and let me
fix the configuration later myself to avoid listening on IPv6 and
listen only in IPv4.
Or what happens if I have something else listening on port 80 (a
reverse proxy for example) and I want to install Nginx and then change
it to listen on port 81 instead?
This is not a bug on _installation_ but on _startup_, there's a
difference.
Of course this is my own personal opinion and haven't read the
Policy document in years...
Thanks all, have a great day everybody!
El 09/03/15 a las 09:59, shirish शिरीष escibió:
Hi Ivan,
The output is :-
$ ip -6 addr
$
On 3/9/15, Ivan Baldo wrote:
Hello.
Maybe you don't have IPv6 at all configured, not even in the "lo"
interface?
Whats the output of "ip -6 addr"?
Thanks!
--
Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/
From Montevideo, Uruguay, at the south of South America.
Freelance programmer and GNU/Linux system administrator, hire me!
Alternatives: iba...@codigolibre.net - http://go.to/ibaldo
--
Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/
From Montevideo, Uruguay, at the south of South America.
Freelance programmer and GNU/Linux system administrator, hire me!
Alternatives: iba...@codigolibre.net - http://go.to/ibaldo
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#779825: no port attached to webserver
Shirish, doesn't matter if your ISP doesn't have IPv6, thats no reason to disable it system wide and not using it, loopback connections will use it, as well maybe LAN connections. Nginx will listen on both IPv4 and IPv6. You are using a non standard setup so problems like this will happen. Regarding dh_installinit, I disagree thats the best behavior, for me it would be best that it complains but continues the configuration ignoring the error anyway; the init file is correctly installed, it just failed to start it, thats not an installation problem, there is nothing wrong with the installation... though that probably should be discussed in another wishlist report or a mailing list... This bug should be closed then, thanks very much to everyone! El 10/03/15 a las 13:08, shirish शिरीष escibió: at bottom :- On 3/10/15, Christos Trochalakis wrote: This is definitely the problem, nginx cannot bind an ipv6 socket so it fails to start. The package stays in unconfigured state when nginx could not be started, this is standard behaviour: dh_installinit by default adds a stanga in the postinst script that runs `invoke-rc.d start || exit $?`. So when the service fails the script exits with a non-zero exit status. Please let me know what do you want to do so I know what action I need to take my end - a. Wait for you to package a patched version. b. Think of how I can get IPv6 only on the loopback interface 'lo' . This is how I had done it https://wiki.debian.org/DebianIPv6#How_to_turn_off_IPv6 basically ~$ cat /etc/default/grub | grep ipv6 GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1 init=/lib/systemd/systemd" You can delete the `listen` ipv6 line from your nginx config (probably /etc/nginx/sites-enabled/default) and run an `apt-get install` to reconfigure the package. That should fix the issue for you. -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8 Hi Christos, Thank you for taking time off and helping. I don't see IPv6 mentioned anywhere in the file explicitly but I am guessing you are saying to delete line 18 from the file. listen [::]:80 default_server; If my understanding is correct then the ::: are for IPv6 as the addresses are pretty large. It's a good thing that the sites-available/default file is from nginx-common package $ dpkg -L nginx-common | grep default /etc/default /etc/default/nginx /etc/nginx/sites-available/default So I deleted that line and then reinstalled the package. ~$ sudo aptitude install nginx-full The following partially installed packages will be configured: nginx-full No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 4 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. D01: ensure_diversions: new, (re)loading D01: process queue pkg nginx-full:amd64 queue.len 0 progress 1, try 1 Setting up nginx-full (1.6.2-5) ... D01: ensure_diversions: same, skipping D01: cmpversions a='0:1.17.24' b='0:1.16' r=1 D01: cmpversions a='0:1.17.24' b='0:1.16' r=1 D01: ensure_diversions: new, (re)loading D01: cmpversions a='0:1.17.24' b='0:1.16' r=1 D01: cmpversions a='0:1.17.24' b='0:1.16' r=1 For some reason I like aptitude more than apt-get, does the same thing, as can be seen it reconfigures the package and doesn't complain anymore. Then ran the test :- $ sudo /usr/sbin/nginx -t nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful Made sure that dpkg says it is installed just fine :- $ dpkg -l nginx-full Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii nginx-full 1.6.2-5 amd64 nginx web/proxy server (standard version) So, essentially the work-around works. Now the standard behavior "should be" that if IPv6 fails, it should fall-back to IPv4 but for some reason that isn't happening. Just as a caveat also saw this http://www.ipv6-test.com/stats/country/IN, so it seems it will take a few more years for Ipv6 to become dominant at least here in India. -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux
Bug#657097: Please close this bug.
Please close this bug, thanks! -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: iba...@codigolibre.net - http://go.to/ibaldo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#445959: icedove - FTBFS: error: 'asm' operand has impossible constraints
Hello. Any news regarding this? The last message from Bastian Blank dated 27 Oct 2007 contained a patch but nobody answered and the package hasn't been uploaded since then, it is still stuck on unstable. I am not demanding anything, just doing a ping :-). Thanks!!! -- Ivan Baldo - [EMAIL PROTECTED] - http://ibaldo.codigolibre.net/ ICQ 10215364 - Phone/FAX (598) (2) 613 3223. Caldas 1781, Malvin, Montevideo, Uruguay, South America. We believe that we are free, but in reality we are not! Are we? Alternatives: [EMAIL PROTECTED] - http://go.to/ibaldo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#427406: No more mouse/keyboard-input possible after closing crashed application
I suggest two things: 1 - forwarding the bug upstream: because maybe they want to look into this to make the application or library more robust. 2 - see what makes GTK+ 2.11 refuse to create the icon cache and backport it to GTK+ 2.10, then close this bug: so Metacity transitions to testing without this problem. Otherwise, if those things are much work, then just wait till GTK+ 2.12 gets done and uploaded to testing and then close this bug. Its just an opinion... Thanks for all your great work guys!!! -- Ivan Baldo - [EMAIL PROTECTED] - http://ibaldo.codigolibre.net/ ICQ 10215364 - Phone/FAX (598) (2) 613 3223. Caldas 1781, Malvin, Montevideo, Uruguay, South America. We believe that we are free, but in reality we are not! Are we? Alternatives: [EMAIL PROTECTED] - http://go.to/ibaldo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#502447: Cannot reproduce neither.
Package: audacity Followup-For: Bug #502447 I can't reproduce this bug neither, I have been using this program yesterday. The original submitter has a strange version of libwxbase2.6-0 and libwxgtk2.6-0 2.6.4.0-2rpd that I cannot find in Debian, maybe thats the problem? HTH. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26.3 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=es_UY.UTF-8, LC_CTYPE=es_UY.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages audacity depends on: ii libasound21.0.16-2 ALSA library ii libc6 2.7-14 GNU C Library: Shared libraries ii libexpat1 2.0.1-4XML parsing C library - runtime li ii libflac++61.2.1-1.2 Free Lossless Audio Codec - C++ ru ii libflac8 1.2.1-1.2 Free Lossless Audio Codec - runtim ii libgcc1 1:4.3.2-1 GCC support library ii libglib2.0-0 2.16.6-1 The GLib library of C routines ii libgtk2.0-0 2.12.11-3 The GTK+ graphical user interface ii libid3tag00.15.1b-10 ID3 tag reading library from the M ii libjack0 0.109.2-3 JACK Audio Connection Kit (librari ii libmad0 0.15.1b-3 MPEG audio decoder library ii libogg0 1.1.3-4Ogg Bitstream Library ii libsndfile1 1.0.17-4 Library for reading/writing audio ii libsoundtouch1c2 1.3.1-2sound stretching library ii libstdc++64.3.2-1The GNU Standard C++ Library v3 ii libvorbis0a 1.2.0.dfsg-3.1 The Vorbis General Audio Compressi ii libvorbisenc2 1.2.0.dfsg-3.1 The Vorbis General Audio Compressi ii libvorbisfile31.2.0.dfsg-3.1 The Vorbis General Audio Compressi ii libwxbase2.6-02.6.3.2.2-3wxBase library (runtime) - non-GUI ii libwxgtk2.6-0 2.6.3.2.2-3wxWidgets Cross-platform C++ GUI t audacity recommends no packages. Versions of packages audacity suggests: pn ladspa-plugin (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#497789: Does it still happens?
Hello. I didn't understand anything of what you said, I am not a security expert anyway, and I am not a maintainer of this packages. But anyway, the problem exists in the new Etch version 2.0.0.17-0etch1? And does it exist in Lenny 3.0.3-2? Thanks for your help. Bye. -- Ivan Baldo - [EMAIL PROTECTED] - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: [EMAIL PROTECTED] - http://go.to/ibaldo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#486354: Some possibly strange things in that strace log.
Hello.
I looked in the strace and found this couple of files that seem strange:
12613 open("/usr/lib/iceweasel/components/xpti.dat.tmp",
O_WRONLY|O_CREAT|O_TRUNC, 0666) = -1 EACCES (Permission denied)
12613 open("/usr/lib/iceweasel/components/xpti.dat.tmp",
O_WRONLY|O_CREAT|O_TRUNC, 0666) = -1 EACCES (Permission denied)
and
12613 open("/usr/lib/iceweasel/components/compreg.dat.tmp",
O_WRONLY|O_CREAT|O_TRUNC, 0664) = -1 EACCES (Permission denied)
I couldn't find those lines in my strace!
Also, try to remove temporarily the plugins in
/usr/lib/iceweasel/plugins/ to see if they cause the problems.
I don't know, maybe try to reinstal iceweasel or xulrunner, etc.
Hope this helps, bye.
--
Ivan Baldo - [EMAIL PROTECTED] - http://ibaldo.codigolibre.net/
From Montevideo, Uruguay, at the south of South America.
Freelance programmer and GNU/Linux system administrator, hire me!
Alternatives: [EMAIL PROTECTED] - http://go.to/ibaldo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#508476: Has it been reported upstream?
Hello. Has this problem been reported upstream? Thanks. -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: iba...@codigolibre.net - http://go.to/ibaldo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#517768: Ping - Any news?
Hello. Any news about this? This is a blocker for the new Nautilus, while the new Nautilus doesn't enter Testing, Testing will remain without automounting services. There is some problem with the local mime database of the user (look at the other reports merged with this one), who is responsible for keeping that file up-to-date? Thanks!!! -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: iba...@codigolibre.net - http://go.to/ibaldo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
