[Bug 1845214] Re: Keyboard NumLock indicator turns off on connecting another keyboard
I've noticed the same thing… both on Ubuntu, and lately on Gentoo as well, so I'm thinking maybe something in udev / kernel has changed? I use FVWM2 as my desktop on both OSes. My desktop runs Ubuntu 20.04 (AMD64). On my laptop (Panasonic CF-53, which runs Gentoo) it's particularly insidious, plugging in the YubiKey (mine's a 5C which I use with a USB- A-C adaptor) causes NumLock to be turned on, and if your PIN code uses letters over the right-side of the keyboard, guess what? You're unwittingly typing numbers now! Cue confusion when the YubiKey rejects the PIN you just entered. I've locked myself out of the YubiKey once because of that -- had to go in with the PUK and unlock it. My desktop doesn't seem to secretly turn NumLock on; the state is retained, just the LED turns off. If we can figure out what mechanism is doing it in Ubuntu, I'll chase up what's doing it Gentoo-side. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845214 Title: Keyboard NumLock indicator turns off on connecting another keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1845214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857407] Re: mplayer broken Theora codec: libmpcodecs/vf.c:287: vf_get_image: Assertion `h == -1 || h >= vf->h' failed.
Right, so the situation is this: bit rot. mplayer is no longer maintained apparently, the suggested alternative being `mpv`, which *can* be used with `xscreensaver` (see Debian bug#958865 link). Guess we can close this now, time to migrate over to `mpv`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857407 Title: mplayer broken Theora codec: libmpcodecs/vf.c:287: vf_get_image: Assertion `h == -1 || h >= vf->h' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mplayer/+bug/1857407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857407] Re: mplayer broken Theora codec: libmpcodecs/vf.c:287: vf_get_image: Assertion `h == -1 || h >= vf->h' failed.
So this issue has been known of in Debian for a while now. I reported the issue today there: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958865 but there was this earlier report from nearly a year ago: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920485 ** Bug watch added: Debian Bug tracker #958865 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958865 ** Bug watch added: Debian Bug tracker #920485 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920485 ** Bug watch added: Debian Bug tracker #920485 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920485 ** Changed in: mplayer (Debian) Importance: Undecided => Unknown ** Changed in: mplayer (Debian) Status: New => Unknown ** Changed in: mplayer (Debian) Remote watch: None => Debian Bug tracker #920485 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857407 Title: mplayer broken Theora codec: libmpcodecs/vf.c:287: vf_get_image: Assertion `h == -1 || h >= vf->h' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mplayer/+bug/1857407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857407] Re: mplayer broken Theora codec: libmpcodecs/vf.c:287: vf_get_image: Assertion `h == -1 || h >= vf->h' failed.
Reproduced the same crash on Debian 10. ** Also affects: mplayer (Debian) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857407 Title: mplayer broken Theora codec: libmpcodecs/vf.c:287: vf_get_image: Assertion `h == -1 || h >= vf->h' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mplayer/+bug/1857407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857407] [NEW] mplayer broken Theora codec: libmpcodecs/vf.c:287: vf_get_image: Assertion `h == -1 || h >= vf->h' failed.
Public bug reported:
Hi,
I'm using 'mplayer' alongside 'xscreensaver' to play a few videos as
screen savers. To save space, I've dropped the frame size of the videos
(and they play without sound).
On some videos, which I have converted from other media (the example I
will give here is a truncated version of a public-domain video from
archive.org to demonstrate the issue), mplayer on Ubuntu 18.04 crashes:
$ mplayer /tmp/test.ogv
MPlayer 1.3.0 (Debian), built with gcc-7 (C) 2000-2016 MPlayer Team
do_connect: could not connect to socket
connect: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.
Playing /tmp/test.ogv.
libavformat version 57.83.100 (external)
libavformat file format detected.
[lavf] stream 0: video (theora), -vid 0
[lavf] stream 1: audio (vorbis), -aid 0, -alang eng
VIDEO: [theo] 240x180 0bpp 29.970 fps0.0 kbps ( 0.0 kbyte/s)
==
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
libavcodec version 57.107.100 (external)
Selected video codec: [fftheora] vfm: ffmpeg (FFmpeg Theora)
==
Load subtitles in /tmp/
==
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 32000 Hz, 1 ch, floatle, 128.0 kbit/12.50% (ratio: 16000->128000)
Selected audio codec: [ffvorbis] afm: ffmpeg (FFmpeg Vorbis)
==
AO: [pulse] 32000Hz 1ch floatle (4 bytes per sample)
Starting playback...
Movie-Aspect is 1.33:1 - prescaling to correct movie aspect.
VO: [vdpau] 240x180 => 240x180 Planar YV12
Movie-Aspect is 1.33:1 - prescaling to correct movie aspect.
VO: [vdpau] 240x180 => 240x180 Planar YV12
Dropping frame with size not matching configured size (240x180 vs 240x168 vs
240x180)
Dropping frame with size not matching configured size (240x180 vs 240x168 vs
240x180)
[VD_FFMPEG] DRI failure.
mplayer: libmpcodecs/vf.c:287: vf_get_image: Assertion `h == -1 || h >= vf->h'
failed.
MPlayer interrupted by signal 6 in module: decode video
[ This binary of MPlayer in Debian is currently compiled with
'--enable-debug'; the debugging symbols are in the package
'mplayer-dbgsym'.]
The same videos play just fine with mplayer on Gentoo. (The video was
produced using the command: ffmpeg -i ${INPUT} -s 240x180 -ar 32000 -ac
1 -b:a 128000 -b:v 25 -t 10 ${OUTPUT}). I have tried other CODECs
and container formats, it seems to be related to Theora which I chose
because it's a good free-software CODEC for video.
stuartl@vk4msl-ws:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename: bionic
stuartl@vk4msl-ws:~$ uname -a
Linux vk4msl-ws 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
stuartl@vk4msl-ws:~$ dpkg -l mplayer
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 mplayer 2:1.3.0-7build2 amd64
movie player for Unix-like systems
** Affects: mplayer (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Video that causes the crash."
https://bugs.launchpad.net/bugs/1857407/+attachment/5314961/+files/test.ogv
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857407
Title:
mplayer broken Theora codec: libmpcodecs/vf.c:287: vf_get_image:
Assertion `h == -1 || h >= vf->h' failed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mplayer/+bug/1857407/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730947] Re: package fails to build with glibc-2.26
I hit the same bug on Gentoo with glibc-2.29-r2 and alsa-lib-1.1.8.
Looking at the code, I see they do something similar to the suggestion
made in https://stackoverflow.com/a/32672476.
It would appear this kludge no longer works. Down later the suggestion
was to tweak the -std=XXX flag passed to gcc. After unsuccessfully
trying to set this in CFLAGS, I got things compiling with this:
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 639fdc711..2d1c744f2 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -13,7 +13,7 @@ include
("${CMAKE_CURRENT_SOURCE_DIR}/cmake_modules/GNUInstallDirs.cmake")
project ("cairo-dock-plugins")
set (VERSION "3.4.1")
-add_definitions (-std=c99 -Wall -Werror-implicit-function-declaration) #
-Wextra -Wwrite-strings -Wuninitialized -Werror-implicit-function-declaration
-Wstrict-prototypes -Wreturn-type -Wparentheses -Warray-bounds)
+add_definitions (-std=gnu99 -Wall -Werror-implicit-function-declaration) #
-Wextra -Wwrite-strings -Wuninitialized -Werror-implicit-function-declaration
-Wstrict-prototypes -Wreturn-type -Wparentheses -Warray-bounds)
if (NOT DEFINED CMAKE_BUILD_TYPE)
add_definitions (-O3)
endif()
cairo-dock-plug-ins now build. I'm just trying them out to see if there
are any ill effects from doing the above hack.
** Also affects: cairo-dock-plug-ins (Gentoo Linux)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730947
Title:
package fails to build with glibc-2.26
To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo-dock-plug-ins/+bug/1730947/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815978] Re: sa-compile broken on 16.04 LTS AMD64
ypemap "/usr/share/perl/5.22/ExtUtils/typemap" body_0.xs > body_0.xsc && mv body_0.xsc body_0.c x86_64-linux-gnu-gcc -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -DVERSION=\"1.0\" -DXS_VERSION=\"1.0\" -fPIC "-I/usr/lib/x86_64-linux-gnu/perl/5.22/CORE" body_0.c x86_64-linux-gnu-gcc -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -DVERSION=\"1.0\" -DXS_VERSION=\"1.0\" -fPIC "-I/usr/lib/x86_64-linux-gnu/perl/5.22/CORE" scanner1.c x86_64-linux-gnu-gcc -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -DVERSION=\"1.0\" -DXS_VERSION=\"1.0\" -fPIC "-I/usr/lib/x86_64-linux-gnu/perl/5.22/CORE" scanner2.c x86_64-linux-gnu-gcc -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -DVERSION=\"1.0\" -DXS_VERSION=\"1.0\" -fPIC "-I/usr/lib/x86_64-linux-gnu/perl/5.22/CORE" scanner3.c x86_64-linux-gnu-gcc -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -DVERSION=\"1.0\" -DXS_VERSION=\"1.0\" -fPIC "-I/usr/lib/x86_64-linux-gnu/perl/5.22/CORE" scanner4.c x86_64-linux-gnu-gcc -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -DVERSION=\"1.0\" -DXS_VERSION=\"1.0\" -fPIC "-I/usr/lib/x86_64-linux-gnu/perl/5.22/CORE" scanner5.c x86_64-linux-gnu-gcc -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -DVERSION=\"1.0\" -DXS_VERSION=\"1.0\" -fPIC "-I/usr/lib/x86_64-linux-gnu/perl/5.22/CORE" scanner6.c rm -f blib/arch/auto/Mail/SpamAssassin/CompiledRegexps/body_0/body_0.so x86_64-linux-gnu-gcc -shared -L/usr/local/lib -fstack-protector-strong body_0.o scanner1.o scanner2.o scanner3.o scanner4.o scanner5.o scanner6.o -o blib/arch/auto/Mail/SpamAssassin/CompiledRegexps/body_0/body_0.so \ \ chmod 755 blib/arch/auto/Mail/SpamAssassin/CompiledRegexps/body_0/body_0.so "/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- body_0.bs blib/arch/auto/Mail/SpamAssassin/CompiledRegexps/body_0/body_0.bs 644 Manifying 1 pod document make install PREFIX=/tmp/.spamassassin28456guVjwjtmp/ignored INSTALLSITEARCH=/var/lib/spamassassin/compiled/5.022/3.004002 Running Mkbootstrap for Mail::SpamAssassin::CompiledRegexps::body_0 () chmod 644 "body_0.bs" Manifying 1 pod document Files found in blib/arch: installing files in blib/lib into architecture dependent library tree Installing /var/lib/spamassassin/compiled/5.022/3.004002/auto/Mail/SpamAssassin/CompiledRegexps/body_0/body_0.so Installing /tmp/.spamassassin28456guVjwjtmp/ignored/man/man3/Mail::SpamAssassin::CompiledRegexps::body_0.3pm Appending installation info to /var/lib/spamassassin/compiled/5.022/3.004002/perllocal.pod cp /tmp/.spamassassin28456guVjwjtmp/bases_body_0.pl /var/lib/spamassassin/compiled/5.022/3.004002/bases_body_0.pl cd / rm -rf /tmp/.spamassassin28456guVjwjtmp root@bnesecrf0:~# echo $? 0 root@bnesecrf0:~# I must admit the idea of "i386" headers and "amd64" headers is completely foreign to me. They're plain-text C code files, with no concept of processor architecture or bit width whatsoever. Normally for the C library, i386 and AMD64 binaries are built from the same C source (and headers), and are installed *together* so there shouldn't be a need to introduce this fragile complexity of having architecture-dependent C compiler include paths. It certainly was this way on Gentoo/MIPS where we had to contend with not two, but three ABIs (o32, n32 and n64), having a single "include" header tree with multiple ABIs continues to work just fine there. I think Ubuntu in having "i386" and "AMD64" headers are trying to solve a non-existent problem, and creating others (like this one) in the process. I believe this policy may need a re-think. Anyway, it looks like `sa- compile` is working once again. Regards, Stuart Longland -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815978 Title: sa-compile broken on 16.04 LTS AMD64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1815978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815978] Re: sa-compile broken on 16.04 LTS AMD64
Okay, well firstly, we're not planning on moving up to 18.04 LTS for a while… so everything here is as per the Ubuntu 16.04 LTS distribution. > - the current libperl in 18.04 should be libperl5.26:amd64 - could you upgrade that and all other packges and retry? root@bnesecrf0:~# apt-cache search libperl libperl-dev - Perl library: development files libperl5.22 - shared Perl library perl-modules-5.22 - Core Perl modules libperl4-corelibs-perl - libraries historically supplied with Perl 4 … It would appear libperl5.22:amd64 is the equivalent on 16.04. root@bnesecrf0:~# apt-get install -y libperl5.22 Reading package lists... Done Building dependency tree Reading state information... Done libperl5.22 is already the newest version (5.22.1-9ubuntu0.6). 0 to upgrade, 0 to newly install, 0 to remove and 79 not to upgrade. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up sa-compile (3.4.2-0ubuntu0.16.04.1) ... Running sa-compile (may take a long time) bayes: locker: safe_lock: cannot create tmp lockfile /var/lib/spamd/bayes.lock.bnesecrf0.vrt.int.10269 for /var/lib/spamd/bayes.lock: Permission denied bayes: expire_old_tokens: locker: safe_lock: cannot create tmp lockfile /var/lib/spamd/bayes.lock.bnesecrf0.vrt.int.10269 for /var/lib/spamd/bayes.lock: Permission denied In file included from body_0.xs:2:0: /usr/lib/x86_64-linux-gnu/perl/5.22/CORE/perl.h:701:23: fatal error: sys/types.h: No such file or directory compilation terminated. make: *** [body_0.o] Error 1 command 'make PREFIX=/tmp/.spamassassin10269alKcE2tmp/ignored INSTALLSITEARCH=/var/lib/spamassassin/compiled/5.022/3.004002 >>/tmp/.spamassassin10269alKcE2tmp/log' failed: exit 2 dpkg: error processing package sa-compile (--configure): subprocess installed post-installation script returned error exit status 25 Errors were encountered while processing: sa-compile E: Sub-process /usr/bin/dpkg returned an error code (1) > - verify that the content is correct > $ dpkg --verify sa-compile spamassassin root@bnesecrf0:~# dpkg --verify sa-compile spamassassin ??5?? c /etc/default/spamassassin ??5?? c /etc/spamassassin/local.cf I'm afraid ??5?? means nothing to me. Those are both configuration files meant to be modified. /etc/default/spamassassin has: # /etc/default/spamassassin # Duncan Findlay # WARNING: please read README.spamd before using. # There may be security risks. # Change to one to enable spamd ENABLED=1 # Options # See man spamd for possible options. The -d option is automatically added. # SpamAssassin uses a preforking model, so be careful! You need to # make sure --max-children is not set to anything higher than 5, # unless you know what you're doing. OPTIONS="--create-prefs --max-children 5 --helper-home-dir -u mail --allow-tell" # Pid file # Where should spamd write its PID to file? If you use the -u or # --username option above, this needs to be writable by that user. # Otherwise, the init script will not be able to shut spamd down. PIDFILE="/var/run/spamd.pid" # Set nice level of spamd #NICE="--nicelevel 15" # Cronjob # Set to anything but 0 to enable the cron job to automatically update # spamassassin's rules on a nightly basis CRON=1 and /etc/spamassassin/local.cf has (skipping actual comments for brevity): rewrite_header Subject *SPAM* trusted_networks xx.xx # OUR INTERNAL NETWORK SUBNET HERE required_score 5.0 use_bayes 1 bayes_auto_learn 1 bayes_path /var/lib/spamd/bayes bayes_file_mode 0666 bayes_ignore_header X-Bogosity bayes_ignore_header X-Spam-Flag bayes_ignore_header X-Spam-Status # I believe the above are mostly defaults, these would be customisations: score RCVD_IN_SORBS_DUL 2 score SPF_SOFTFAIL 3 score SPF_FAIL 4 header CHESTERFIELDLOCALS Return-Path =~ /chesterfieldlocals.info/ describe CHESTERFIELDLOCALS Memory loss spammer (I remember you, so clearly don't meed your product) score CHESTERFIELDLOCALS 20 body SEO_MOREENQUIRIES /www.moreenquiries.com.au/i describe SEO_MOREENQUIRIES The liars from moreenquiries.com.au have their NO score SEO_MOREENQUIRIES 20 body SEO_PAYONRESULTS /pay-on-results/i describe SEO_PAYONRESULTS SEO rubbish score SEO_PAYONRESULTS 20 body SEO_PAGEOFGOOGLE /page *\d* of google/i describe SEO_PAGEOFGOOGLE SEO claiming we can be page 1 of Google (Google and Google alone is page one of https://google.com) score SEO_PAGEOFGOOGLE 20 body FROM_RUSSIA_IN_USA /I'?m from Russia.*I live in the USA/i describe FROM_RUSSIA_IN_USA Supposedly from Russia, as if we care score FROM_RUSSIA_IN_USA 20 score URIBL_BLACK 10.0 score URIBL_ABUSE_SURBL 10.0 ifplugin Mail::SpamAssassin::Plugin::Shortcircuit shortcircuit USER_IN_WHITELIST on shortcircuit USER_IN_DEF_WHITELIST on shortcircuit USER_IN_ALL_SPAM_TO on shortcircuit SUBJECT_IN_WHITELISTon shortcircuit USER_IN_BLACKLIST on shortcircuit USER_IN_BLACKLIST_TOon shortcircuit
[Bug 1815978] [NEW] sa-compile broken on 16.04 LTS AMD64
Public bug reported: This could be a bug in the underlying toolchain or Perl libraries. The host in question has been updated from Ubuntu 12.04 LTS → 14.04 LTS → 16.04 LTS. root@bnesecrf0:~# sa-compile Feb 15 08:52:01.090 [1364] info: generic: base extraction starting. this can take a while... Feb 15 08:52:01.090 [1364] info: generic: extracting from rules of type body_0 100% [===] 9213.60 rules/sec 00m00s DONE 100% [===] 1166.48 bases/sec 00m02s DONE Feb 15 08:52:03.255 [1364] info: body_0: 1168 base strings extracted in 2 seconds cd /tmp/.spamassassin1364iPK7zxtmp reading bases_body_0.in cd Mail-SpamAssassin-CompiledRegexps-body_0 re2c -i -b -o scanner1.c scanner1.re re2c -i -b -o scanner2.c scanner2.re re2c -i -b -o scanner3.c scanner3.re re2c -i -b -o scanner4.c scanner4.re re2c -i -b -o scanner5.c scanner5.re re2c -i -b -o scanner6.c scanner6.re /usr/bin/perl Makefile.PL PREFIX=/tmp/.spamassassin1364iPK7zxtmp/ignored INSTALLSITEARCH=/var/lib/spamassassin/compiled/5.022/3.004002 Generating a Unix-style Makefile Writing Makefile for Mail::SpamAssassin::CompiledRegexps::body_0 Writing MYMETA.yml and MYMETA.json make PREFIX=/tmp/.spamassassin1364iPK7zxtmp/ignored INSTALLSITEARCH=/var/lib/spamassassin/compiled/5.022/3.004002 cp body_0.pm blib/lib/Mail/SpamAssassin/CompiledRegexps/body_0.pm Running Mkbootstrap for Mail::SpamAssassin::CompiledRegexps::body_0 () chmod 644 "body_0.bs" "/usr/bin/perl" "/usr/share/perl/5.22/ExtUtils/xsubpp" -typemap "/usr/share/perl/5.22/ExtUtils/typemap" body_0.xs > body_0.xsc && mv body_0.xsc body_0.c x86_64-linux-gnu-gcc -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -DVERSION=\"1.0\" -DXS_VERSION=\"1.0\" -fPIC "-I/usr/lib/x86_64-linux-gnu/perl/5.22/CORE" body_0.c In file included from body_0.xs:2:0: /usr/lib/x86_64-linux-gnu/perl/5.22/CORE/perl.h:701:23: fatal error: sys/types.h: No such file or directory compilation terminated. Makefile:345: recipe for target 'body_0.o' failed make: *** [body_0.o] Error 1 command failed: exit 2 root@bnesecrf0:~# dpkg -S /usr/include/sys/types.h libc6-dev-i386: /usr/include/sys/types.h root@bnesecrf0:~# dpkg -S /usr/lib/x86_64-linux-gnu/perl/5.22 libperl5.22:amd64: /usr/lib/x86_64-linux-gnu/perl/5.22 root@bnesecrf0:~# dpkg -l libc6-dev-i386 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) ||/ NameVersionArchitecture Description +++-===-==-==-=== ii libc6-dev-i386 2.23-0ubuntu10 amd64 GNU C Library: 32-bit development libraries for AMD64 root@bnesecrf0:~# dpkg -l libperl5.22:amd64 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) ||/ NameVersionArchitecture Description +++-===-==-==-=== ii libperl5.22:amd64 5.22.1-9ubuntu0.6 amd64 shared Perl library root@bnesecrf0:~# dpkg -l sa-compile 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) ||/ NameVersionArchitecture Description +++-===-==-==-=== iF sa-compile 3.4.2-0ubuntu0.16. allTools for compiling SpamAssassin rules into C The F in dpkg output here is because dpkg-configure fails to successfully run `sa-compile` for the same reason. Something, it would seem, is wrong with the C preprocessor include path at the time when ExtUtils::xsubpp invokes gcc. To the best of my knowledge, there are no locally installed Perl modules on this server (a scan of /usr/local shows no perl modules there). ** Affects: spamassassin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815978 Title: sa-compile broken on 16.04 LTS AMD64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1815978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
Re: [Bug 1313497] Re: USB keyboard unresponsive on fresh install
On 29/04/14 18:35, Stefan Bader wrote: Hi Stuart, On 29.04.2014 05:23, Stuart Longland wrote: Did the linux-3.13.0-24-generic package miss out a few files or are they in a separate package the installer forgot to install? That could be and depends on you seed. For bare-metal you should have seleced linux-server for d-i base-installer/kernel/image. In general the linux-image should not be picked directly as we indeed split up the modules into the minimum for virtual machines and a rest. linux-server, linux-generic, and linux-virtual are all meta-package which will install the right set of packages and also make sure you see kernel updates. server and generic nowadays is actually the same. So you could have installed without those and now miss the linux-image-extra package. Ahh, I have in my preseed: # The kernel image (meta) package to be installed; none can be used if no # is to be installed. d-i base-installer/kernel/image string linux-image-virtual Perhaps I mis-interpreted the intent of virtual. Is there a document that describes the image options in detail that one could refer to? Perhaps mention of it should be made in the preseed examples? It's easy to miss the bit about it being for virtual instances in the dpkg -l output, which is how I installed the image: root@host:~# dpkg -l linux-image-virtual 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) ||/ NameVersion Architecture Description +++-===--- ii linux-image-virtual 3.13.0.24.29 amd64This package will always depend on the latest minima I shall amend my preseed scripts and perhaps we can work on the documentation (which either is lacking or I missed seeing it). Regards, -- Stuart Longland Systems Engineer _ ___ \ /|_) | T: +61 7 3535 9619 \/ | \ | 38b Douglas StreetF: +61 7 3535 9699 SYSTEMSMilton QLD 4064 http://www.vrt.com.au -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313497 Title: USB keyboard unresponsive on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1313513] Re: mountall does not honour _netdev
On 29/04/14 10:32, Steve Langasek wrote: While the mount(8) manpage says that _netdev causes the mount to be deferred until the network is up, this manpage was written in a bygone era when network up was a discrete event, which it hasn't been for a long time. Ahh, so out of date documentation strikes again. Ahh well, we should perhaps amend that documentation. Or an equivalent feature re-instated, as I believe there are valid use cases for the old _netdev behaviour. The current behavior is that _netdev devices will be tried immediately on boot, and tried again each time a network interface comes up. If this doesn't give the desired results, I think this is a bug in the ceph driver - not in mountall, which has been tested with _netdev (and network filesystems) repeatedly and shown to work correctly. The trouble is it hangs waiting for a /dev/rbd device to appear, which won't happen until the 'rbdmap' service is started. Once 'rbdmap' has done its duty, mount works as expected (and thus, mountall should also work). As seen from the attached snapshot, it doesn't bother to wait, and blindly tries to mount the RBD before connecting to Ceph: this will never work. If there is a specific connection that needs to be made before running the mount command, then I don't think that's something mountall can be expected to handle. Something else on the system would need to intercept the request for a ceph mount, and block it until ceph is available. How about not blocking the entire system boot so the machine remains unresponsive and impossible to connect to remotely? Some of the machines we look after are stuck in military bases or underground in mines: it's not like we can just stroll up to the console and press a button. Had the 'mountall' not stalled the entire boot sequence, but allowed the boot to proceed minus the /var/lib/one whilst continuing to retry, it might've found the device it needed would appear in time. I can understand the let's wait it out and see if it appears, but not the let's halt everything until the device magically appears. The latter is dangerous for any system for which local console access is difficult or unavailable. (As is my case here, with the buggered keyboard.) Regards, -- Stuart Longland Systems Engineer _ ___ \ /|_) | T: +61 7 3535 9619 \/ | \ | 38b Douglas StreetF: +61 7 3535 9699 SYSTEMSMilton QLD 4064 http://www.vrt.com.au -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313513 Title: mountall does not honour _netdev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1313513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1313497] Re: USB keyboard unresponsive on fresh install
/3.13.0-24-generic/kernel/crypto/crc32.ko /lib/modules/3.13.0-24-generic/kernel/crypto/deflate.ko /lib/modules/3.13.0-24-generic/kernel/crypto/rmd160.ko /lib/modules/3.13.0-24-generic/kernel/crypto/crypto_user.ko /lib/modules/3.13.0-24-generic/kernel/crypto/authenc.ko /lib/modules/3.13.0-24-generic/kernel/crypto/vmac.ko /lib/modules/3.13.0-24-generic/kernel/crypto/pcrypt.ko /lib/modules/3.13.0-24-generic/kernel/crypto/md4.ko /lib/modules/3.13.0-24-generic/kernel/crypto/ansi_cprng.ko /lib/modules/3.13.0-24-generic/kernel/crypto/des_generic.ko /lib/modules/3.13.0-24-generic/kernel/crypto/lrw.ko /lib/modules/3.13.0-24-generic/kernel/crypto/af_alg.ko /lib/modules/3.13.0-24-generic/kernel/crypto/cast6_generic.ko /lib/modules/3.13.0-24-generic/kernel/crypto/cts.ko /lib/modules/3.13.0-24-generic/kernel/crypto/serpent_generic.ko /lib/modules/3.13.0-24-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko /lib/modules/3.13.0-24-generic/kernel/sound/core/seq/snd-seq.ko /lib/modules/3.13.0-24-generic/kernel/sound/core/seq/snd-seq-midi-event.ko /lib/modules/3.13.0-24-generic/kernel/sound/core/seq/snd-seq-midi.ko /lib/modules/3.13.0-24-generic/kernel/sound/core/seq/snd-seq-virmidi.ko /lib/modules/3.13.0-24-generic/kernel/sound/core/seq/snd-seq-device.ko /lib/modules/3.13.0-24-generic/kernel/sound/core/seq/snd-seq-dummy.ko /lib/modules/3.13.0-24-generic/kernel/sound/core/seq/snd-seq-midi-emul.ko /lib/modules/3.13.0-24-generic/kernel/sound/core/snd-compress.ko /lib/modules/3.13.0-24-generic/kernel/sound/core/snd-pcm.ko /lib/modules/3.13.0-24-generic/kernel/sound/core/snd.ko /lib/modules/3.13.0-24-generic/kernel/sound/core/snd-hrtimer.ko /lib/modules/3.13.0-24-generic/kernel/sound/core/snd-hwdep.ko /lib/modules/3.13.0-24-generic/kernel/sound/core/snd-page-alloc.ko /lib/modules/3.13.0-24-generic/kernel/sound/core/snd-timer.ko /lib/modules/3.13.0-24-generic/kernel/sound/core/snd-rawmidi.ko /lib/modules/3.13.0-24-generic/kernel/sound/pci/snd-ens1370.ko /lib/modules/3.13.0-24-generic/kernel/sound/soundcore.ko Did the linux-3.13.0-24-generic package miss out a few files or are they in a separate package the installer forgot to install? Regards, -- Stuart Longland Systems Engineer _ ___ \ /|_) | T: +61 7 3535 9619 \/ | \ | 38b Douglas StreetF: +61 7 3535 9699 SYSTEMSMilton QLD 4064 http://www.vrt.com.au -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313497 Title: USB keyboard unresponsive on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313513] Re: mountall does not honour _netdev
As a point of interest, this is an `rbdmount` script I use with upstart as a work-around to the mountall issue. It assumes that the devices listed in /etc/ceph/rbdmap are intended to be mounted locally, and so calls mount on each listed device that appears. Very much a hack: it'd be more elegant for mountall to not block the boot process. ** Attachment added: rbdmount.conf upstart script workaround https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1313513/+attachment/417/+files/rbdmount.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313513 Title: mountall does not honour _netdev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1313513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313513] [NEW] mountall does not honour _netdev
Public bug reported: Hi, This is a fresh install of Ubuntu 14.04 LTS AMD64. I tried configuring a Ceph Rados Block Device (rbd) to be mounted during boot on /var/lib/one, containing my OpenNebula configuration and database. The idea being that should the machine go belly up, I'll have an up-to- date snapshot of the OpenNebula data on Ceph to mount on the new frontend machine. /etc/ceph/rbdmap is configured, I set up /etc/fstab with an entry: /dev/rbd/pool/rbdname /var/lib/one xfs defaults,_netdev 0 1 then rebooted. According to mount(8), _netdev is supposed to tell mountall to skip mounting this device until the network is up. As seen from the attached snapshot, it doesn't bother to wait, and blindly tries to mount the RBD before connecting to Ceph: this will never work. mountall seems to rely on *knowing* a list of network file systems: this means when someone comes up with a new network file system, or uses a conventional disk file system with a remote block device, mountall's heuristic falls flat on its face as has been demonstrated here. The problem would also exist for iSCSI, AoE, FibreChannel, nbd and drbd devices. Due to bug 1313497, the keyboard is non-functional. Recovery is useless as the keyboard is broken there too, and now the machine is waiting for a keypress it will never see due to that bug. A headless system would similarly have this problem. Two suggestions I would have: 1. mountall should honour _netdev to decide whether to mount a device or not: this gives the user the means to manually tell mountall that the device needs network access to operate even if the filesystem looks to be local. I'd wager that if the user specified _netdev, they probably meant it and likely know better than mountall. 2. mountall should time out after a predefined period and NEVER wait indefinitely: even if the disk is local. If a disk goes missing, then it is better the machine tries to boot in its degraded state so it can be remotely managed and raise an alarm, than to wait for someone to notice the machine being down. Unfortunately since the machine is now effectively bricked, I can only grep proxy server logs to see what packages got installed. mountall_2.53_amd64.deb seems to be the culprit. ** Affects: mountall (Ubuntu) Importance: Undecided Status: New ** Attachment added: The end result: since the keyboard driver is stuffed, this is where it hangs. https://bugs.launchpad.net/bugs/1313513/+attachment/4099117/+files/IMG_20140428_154151.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313513 Title: mountall does not honour _netdev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1313513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313497] [NEW] USB keyboard unresponsive on fresh install
to perform this installation was downloaded this morning, and has the following checksums: 01f16ef8b1f11b29bd0ce940b0aad8ea950f5346 trusty/amd64/linux fbb74f8e7d0c1e2ce4b027fc4a0e1aca54cf0fe5 trusty/amd64/initrd.gz If there's any additional information that would be useful, please let me know. Regards, Stuart Longland ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: dmesg output https://bugs.launchpad.net/bugs/1313497/+attachment/4098999/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313497 Title: USB keyboard unresponsive on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313497] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1313497/+attachment/4099042/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313497 Title: USB keyboard unresponsive on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313497] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1313497/+attachment/4099041/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313497 Title: USB keyboard unresponsive on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313497] Re: USB keyboard unresponsive on fresh install
- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32 (3000ns min, 6000ns max), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 10 Region 0: Memory at f7c0 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- I've had to do a rebuild already because of this bug (no console access then loosing network access pretty much means game over), so I can confirm 100% repeatability thus far. For interests' sake, the netboot image I used to perform this installation was downloaded this morning, and has the following checksums: 01f16ef8b1f11b29bd0ce940b0aad8ea950f5346 trusty/amd64/linux fbb74f8e7d0c1e2ce4b027fc4a0e1aca54cf0fe5 trusty/amd64/initrd.gz If there's any additional information that would be useful, please let me know. Regards, Stuart Longland + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Apr 28 14:35 seq + crw-rw 1 root audio 116, 33 Apr 28 14:35 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.14.1-0ubuntu3 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: Error: [Errno 2] No such file or directory + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME=UUID=c087705d-cbe4-4546-bfcd-436edfe047c8 + IwConfig: Error: [Errno 2] No such file or directory + Package: linux (not installed) + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=8c972a72-4f98-4043-b9a1-d409f02d6dbc ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 + RelatedPackageVersions: + linux-restricted-modules-3.13.0-24-generic N/A + linux-backports-modules-3.13.0-24-generic N/A + linux-firmware N/A + RfKill: Error: [Errno 2] No such file or directory + Tags: trusty + Uname: Linux 3.13.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 11/20/2012 + dmi.bios.vendor: Intel Corp. + dmi.bios.version: MKQ7710H.86A.0054.2012.1120.1444 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: DQ77MK + dmi.board.vendor: Intel Corporation + dmi.board.version: AAG39642-500 + dmi.chassis.type: 3 + dmi.modalias: dmi:bvnIntelCorp.:bvrMKQ7710H.86A.0054.2012.1120.1444:bd11/20/2012:svn:pn:pvr:rvnIntelCorporation:rnDQ77MK:rvrAAG39642-500:cvn:ct3:cvr: ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1313497/+attachment/4099039/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313497 Title: USB keyboard unresponsive on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313497] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1313497/+attachment/4099040/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313497 Title: USB keyboard unresponsive on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313497] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1313497/+attachment/4099044/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313497 Title: USB keyboard unresponsive on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313497] PciMultimedia.txt
apport information ** Attachment added: PciMultimedia.txt https://bugs.launchpad.net/bugs/1313497/+attachment/4099043/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313497 Title: USB keyboard unresponsive on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313497] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1313497/+attachment/4099045/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313497 Title: USB keyboard unresponsive on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313497] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1313497/+attachment/4099048/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313497 Title: USB keyboard unresponsive on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313497] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1313497/+attachment/4099047/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313497 Title: USB keyboard unresponsive on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313497] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1313497/+attachment/4099049/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313497 Title: USB keyboard unresponsive on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313497] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1313497/+attachment/4099050/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313497 Title: USB keyboard unresponsive on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313497] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1313497/+attachment/4099046/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313497 Title: USB keyboard unresponsive on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1313497] Missing required logs.
Hi Brad, On 28/04/14 14:30, Brad Figg wrote: This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1313497 and then change the status of the bug to 'Confirmed'. I have just done this, you should see the attachments now. Due to being the reporter of the problem I am unable to mark the bug as confirmed. Regards, -- Stuart Longland Systems Engineer _ ___ \ /|_) | T: +61 7 3535 9619 \/ | \ | 38b Douglas StreetF: +61 7 3535 9699 SYSTEMSMilton QLD 4064 http://www.vrt.com.au -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313497 Title: USB keyboard unresponsive on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289318] Re: Samba dumps core if you try to export keytab in trusty
For the record, my initial report of problems was here: https://lists.samba.org/archive/samba/2014-March/179844.html -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1289318 Title: Samba dumps core if you try to export keytab in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1289318/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1289318] Re: Samba dumps core if you try to export keytab in trusty
For the record, my initial report of problems was here: https://lists.samba.org/archive/samba/2014-March/179844.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289318 Title: Samba dumps core if you try to export keytab in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1289318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1246732] Re: Access denied to web frontend resources
Actually, rather than commenting out stanzas, one should just fix the directives to use the correct statement in the sogo.conf: Directory /usr/lib/GNUstep/SOGo Require all granted # Explicitly allow caching of static content to avoid browser specific behavior. # A resource's URL MUST change in order to have the client load the new version. IfModule expires_module ExpiresActive On ExpiresDefault access plus 1 year /IfModule /Directory This seems to work the way the distributed file did, but with Apache 2.4. The file does need customisation by the end user, but it would be a nice courtesy to drop a copy in /etc/apache/confs-available so the user doesn't have to go hunting far for the file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1246732 Title: Access denied to web frontend resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sogo/+bug/1246732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384347] Re: _netdev not working
Just discovered this gem trying to mount a Ceph RBD device on boot. To add insult to injury, this is on a normally headless server, which is in a difficult spot to get a keyboard and monitor to. A server that requires me to be physically present to press a S key (and also as a side-effect, *doesn't* mount volumes that it needs) is completely useless to me. I need this server to boot automatically, without intervention. If it's going to need hand-holding, save yourselves the effort and make the next release of Ubuntu symlink /sbin/init to /bin/bash and we'll do it ourselves! Okay… rant over, I needed to get that out of my system. The system in question is running Ubuntu 12.04 LTS AMD64, installed yesterday via PXE. According to /etc/lsb-release, it's release 12.04.4. I have in my /etc/fstab: /dev/rbd/pool-name/name-of-rbd /local/mountpoint xfs defaults,_netdev 0 0 rbdmap service is configured and set to start at boot. Indeed, when the machine does boot up, `mount -a` successfully mounts the RBD. However, I need to do this *before* starting services. Doing so after logging in is shutting the stable doors long after the horse has bolted. I need it to do this the moment networking is up. I see I'm not the only one a bit miffed by this situation: http://ubuntuforums.org/showthread.php?t=2131380 http://ubuntuforums.org/showthread.php?t=2135891 The former of those threads mentions a kludge. An ugly kludge at that. Has someone got any ideas as to where to look it fix this problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/384347 Title: _netdev not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/384347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067934] Re: spends 10+ minutes deduplicating Package lists
Hi, Apologies for the delay. I've been on other projects and only just got back to this one. We're using the files from http://au.archive.ubuntu.com/pub/ubuntu/archive/dists/precise- proposed/main/installer-amd64/current/images/netboot/netboot.tar.gz I'm downloading the latest copy of that now, and will give it another shot. I'll let you know if this fixes the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067934 Title: spends 10+ minutes deduplicating Package lists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-retriever/+bug/1067934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067934] Re: spends 10+ minutes deduplicating Package lists
That seems to have fixed it at long last. We've got a rather complicated boot menu system so out of those netboot tarballs, I just grab initrd.gz and linux files, and place them in a common directory tree so we can deploy various i686 and AMD64 distributions by picking them from a menu. The broken files had the checksums: 59fcdc4f29fdc3ff08d24b96ef28151f3988a9ff initrd.gz fba53798707c7278334a5402453586bed216de20 linux The working ones had the checksums: 54c80dd94b0f22f4a51df70502bcfff7c29d42b4 initrd.gz 76a613634ff1c595b2e279af99bd88bff4a46404 linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067934 Title: spends 10+ minutes deduplicating Package lists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-retriever/+bug/1067934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067934] Re: spends 10+ minutes deduplicating Package lists
Silly question, has this fix made it into the current netboot images for Ubuntu 12.04 on AMD64 and i686? I just downloaded the latest netboot images, even tried the ones in the -proposed directory, and I'm still getting a long pause from my netboot images. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067934 Title: spends 10+ minutes deduplicating Package lists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-retriever/+bug/1067934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1012629] Re: grub-installer ignores bootdev setting in preseed file
I've got the following in my preseed file: d-i partman-auto/disk string /dev/sdc d-i grub-installer/only_debian boolean false d-i grub-installer/bootdev string /dev/sdc We've got two machines intended as Ceph OSD nodes, they've got two 3TB HDDs on the two high-speed SATA ports and a 60GB SSD on a second. Since the SSD is mostly for the OS with the HDDs providing the bulk of the I/O, this is meant the HDDs wound up as sda and sdb with the SSD being called sdc. The BIOS is set to boot sdc first, and the other two disks will be initially unpartitioned so it's important that the boot-loader winds up on sdc. The above seems to do the trick. I rather suspect the docs are a little ambiguous, particularly with regards to the syntax used to specify bootdev which looks like a relic of GRUB-legacy days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1012629 Title: grub-installer ignores bootdev setting in preseed file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1012629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 989396] Re: Package keyboard-configuration post-installation script. Hang on /bin/setupcon --force --save for 10 min then killed
Well, I've been battling this for the past 8 hours. I'm trying to configure some virtual machines. My intention is to provision some real machines for use in an Ceph/OpenStack cluster. Since it'll probably take a few attempts, I want to automate as much as possible. As a test, I am doing the deployment with a stack of VMs running under libvirtd/kvm on Gentoo. The actual machines will be headless 99% of the time (the remaining 1% will be for maintenance), so I couldn't give two hoots what keyboard layout it picks — we may even be setting up a serial device server and using serial console in the real deployment. Sadly, I don't see a way to skip this. The set-up is a TFTP dishing out the netboot images and pxelinux configuration scripts. HTTP dishing out preseed files; one per host. I have tried with Ubuntu 13.10, 13.04 and 12.04, all AMD64 architecture. I have tried specifying the keyboard settings in the pre-seed file, and on the kernel command line, I've also tried leaving it out and answering on the console. No dice. Maybe one attempt in 20 works and I get a working installation, but most of the time, install hangs at the Configuring keyboard-configuration step. There seems to be no rhyme or reason why it suddenly works, then doesn't. The libvirt-manager CPU monitor seems to indicate activity consistent with a system that's waiting for input. But what? Where? How? It doesn't ask. It doesn't make it clear what it's wanting, or how I'm to provide it. It's not a matter of time either; I left VMs installing earlier this morning about 1AM … 6-7 hours later, I wake up, check on them, they're stuck at this very point. What do I do? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/989396 Title: Package keyboard-configuration post-installation script. Hang on /bin/setupcon --force --save for 10 min then killed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/989396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1053217] Re: gdm leaking filehandles, causing too many open files
Hi, Is there any possibility of this patch being reviewed and included in the Ubuntu 10.04 series? We just had the customer at this site ring up complaining that they couldn't log in today. Turns out something reverted our patched gdm package back to the original Ubuntu one. Think: big industrial system, and when this problem occurs we have to boot everyone off to restart gdm. It was good until the old package got instated then the service restarted, causing the old problem to occur once more. This is our problem, but you could help us a little if you put out an updated gdm binary. Or, as a work around: maybe tell us a way we can stop the update manager from messing with the one we have now. The original patch is linked in the original post, my revised patch is supplied, and I've given detail on how to reproduce the problem and how to check if the problem is fixed. Is there anything else I need to supply in order to get this bug resolved? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1053217 Title: gdm leaking filehandles, causing too many open files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1053217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666828] Re: task jbd2/cciss!c0d0:258 blocked for more than 120 seconds
Fair enough, I think I found some related files on the HP site, been reading through those. What I don't understand is this: why is it suddenly a firmware issue now on Ubuntu 12.04, when it wasn't an issue on VMWare ESX? The hardware has not changed. If there's a firmware bug, fine, but why was it handled before and not now? I managed to get an oops out of the current running kernel (3.2.0-40-generic): [69240.280022] INFO: task rs:main Q:Reg:405 blocked for more than 120 seconds. [69240.280037] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [69240.280050] rs:main Q:Reg D 0001 0 405 1 0x [69240.280057] 880036fbb9d8 0082 0001 0010 [69240.280065] 880036fbbfd8 880036fbbfd8 880036fbbfd8 000137c0 [69240.280073] 8800785a1700 88007a904500 880036fbb9b8 88007fc54080 [69240.280081] Call Trace: [69240.280093] [81118630] ? __lock_page+0x70/0x70 [69240.280102] [8165c58f] schedule+0x3f/0x60 [69240.280107] [8165c63f] io_schedule+0x8f/0xd0 [69240.280113] [8111863e] sleep_on_page+0xe/0x20 [69240.280118] [8165ce5f] __wait_on_bit+0x5f/0x90 [69240.280122] [811187a8] wait_on_page_bit+0x78/0x80 [69240.280129] [8108bf00] ? autoremove_wake_function+0x40/0x40 [69240.280134] [811194b2] grab_cache_page_write_begin+0x92/0xe0 [69240.280140] [81078098] ? lock_timer_base.isra.29+0x38/0x70 [69240.280176] [a00b81e0] ? xfs_get_blocks_direct+0x20/0x20 [xfs] [69240.280183] [811ad4a8] block_write_begin+0x38/0xa0 [69240.280201] [a00b82a3] xfs_vm_write_begin+0x43/0x70 [xfs] [69240.280207] [81118a7a] generic_perform_write+0xca/0x210 [69240.280213] [81118c1d] generic_file_buffered_write+0x5d/0x90 [69240.280232] [a00be19c] xfs_file_buffered_aio_write+0xfc/0x1c0 [xfs] [69240.280238] [8165d736] ? down_write+0x16/0x40 [69240.280257] [a00be3dc] xfs_file_aio_write+0x17c/0x2a0 [xfs] [69240.280263] [8109ead2] ? unqueue_me+0x52/0x80 [69240.280267] [8109fc48] ? futex_wait+0x108/0x210 [69240.280273] [8117900a] do_sync_write+0xda/0x120 [69240.280279] [812d9c28] ? apparmor_file_permission+0x18/0x20 [69240.280285] [8129f3bc] ? security_file_permission+0x2c/0xb0 [69240.280289] [811795b1] ? rw_verify_area+0x61/0xf0 [69240.280294] [81179913] vfs_write+0xb3/0x180 [69240.280298] [81179c3a] sys_write+0x4a/0x90 [69240.280303] [81666a82] system_call_fastpath+0x16/0x1b -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666828 Title: task jbd2/cciss!c0d0:258 blocked for more than 120 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/666828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666828] Re: task jbd2/cciss!c0d0:258 blocked for more than 120 seconds
Not sure what the official status is, but I'm getting this problem with a HP ProLiant box here running Ubuntu 12.04 LTS and linux- image-3.5.0-25-generic as well as the 3.2-series kernels. For me the machine will run fine for about a day, then everything locks up. If I'm lucky, I can SSH in, but then `dmesg` hangs. `fold -w 80 /dev/vcs1` dumps the following output: message. [158400.224328] INFO: task oned:3106 blocked for more than 120 seconds. [158400.224337] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [158400.224491] INFO: task mm_sched:3116 blocked for more than 120 seconds. [158400.224501] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [158520.224030] INFO: task rs:main Q:Reg:888 blocked for more than 120 seconds. [158520.224046] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [158520.224327] INFO: task oned:3106 blocked for more than 120 seconds. [158520.224336] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [158520.224503] INFO: task mm_sched:3116 blocked for more than 120 seconds. [158520.224524] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [158640.224028] INFO: task rs:main Q:Reg:888 blocked for more than 120 seconds. [158640.224056] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [158640.224362] INFO: task oned:3106 blocked for more than 120 seconds. [158640.224382] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. The box previously worked reliably running VMWare ESXi. The link to the Red Hat bug database seems to require a log in to see the bug, so at time of writing, the bug is inaccessible to me and I'm unable to follow any advice there. (I get an error message You are not authorized to access bug #615543.) I'm trying a complete reload (I install using a PXE boot image) to see if a newer kernel has been released that fixes the issue -- also to clean up the last vestiges of an OpenNebula installation that's no longer in use. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666828 Title: task jbd2/cciss!c0d0:258 blocked for more than 120 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/666828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666828] Re: task jbd2/cciss!c0d0:258 blocked for more than 120 seconds
Just re-loaded, lspci reports the affected controller as being the following: 07:01.0 RAID bus controller: Compaq Computer Corporation Smart Array 64xx (rev 01) Subsystem: Compaq Computer Corporation Smart Array 642 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 18 Memory at fdff (64-bit, non-prefetchable) [size=8K] I/O ports at 5000 [size=256] Memory at fdf8 (64-bit, non-prefetchable) [size=256K] [virtual] Expansion ROM at 8030 [disabled] [size=256K] Capabilities: [d0] Power Management version 2 Capabilities: [dc] PCI-X non-bridge device Capabilities: [f0] Vital Product Data Kernel driver in use: cciss Kernel modules: cciss During boot, I see in `dmesg`: [1.097409] HP CISS Driver (v 3.6.26) [1.098444] cciss :07:01.0: PCI IRQ 50 - rerouted to legacy IRQ 18 [1.098524] cciss :07:01.0: PCI INT A - GSI 18 (level, low) - IRQ 18 [1.098694] cciss :07:01.0: Controller reports max supported commands of 0, an obvious lie. Using 16. Ensure that firmware is up to date. [1.216111] cciss :07:01.0: cciss0: 0x46 at PCI :07:01.0 IRQ 18 using DAC I'm not sure what the firmware update procedure is on these things. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666828 Title: task jbd2/cciss!c0d0:258 blocked for more than 120 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/666828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 970234] Re: Selecting spice and qxl mode results in blank screen
I've noticed this myself. For what it's worth, a lot of people here are experiencing it with Windows VMs. I tried booting a Zentyal system with a qxl emulated card and got the same result. root@bneprdcn0:/var/lib/libvirt/images# dpkg -l qemu-kvm* 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 VersionDescription +++-==-==- ii qemu-kvm 1.0+noroms-0ubuntu14.7 Full virtualization on i386 and amd64 hardware ii qemu-kvm-extras1.0.50-2012.03-0ubuntu QEMU system and user mode emulation (transitional package) ii qemu-kvm-spice 1.0.50-2012.03-0ubuntu Full virtualization on amd64 hardware This is on a Ubuntu 12.04 AMD64 server, installed via PXEboot. The workaround for the first VM was to just use VNC, since it's only Zentyal and I'll only be using the console for getting networking going (something I have done; simple as blasting away the udev network naming rules). For the second VM on that host, it'll be Windows Server 2008r2, where the graphical console is much more important. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/970234 Title: Selecting spice and qxl mode results in blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm-spice/+bug/970234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1053217] [NEW] gdm leaking filehandles, causing too many open files
Public bug reported: At a client's site (a large mining company here in Queensland) we have a Ubuntu 10.04 virtual machine running MacroView SCADA in a dr:bd high availability cluster. Workstations connect to the server via XDMCP for control of the local plant. In the past they ran two discrete Ubuntu servers, which used to run reliably for months at a time. Since the switch to the high availability cluster, they now find gdm will refuse to accept new logins after about 6 weeks of operation until the gdm service is restarted. The restart of gdm has the effect of booting off everyone currently logged in -- so for a few seconds, everyone loses control of the processing plant while people re-connect, every 6 weeks. The logs show the following: Sep 20 08:23:38 cgmv1 gdm-binary[31050]: CRITICAL: could not add display to access file: Too many open files Sep 20 08:23:38 cgmv1 gdm-binary[31050]: WARNING: Unable to set up access control for display 1691 Sep 20 08:23:38 cgmv1 gdm-binary[31050]: WARNING: GdmDisplay: display lasted 0.010690 seconds Doing a search, it would appear this is a file-handle leaking bug reported to Red Hat back in February 2010: https://bugzilla.redhat.com/show_bug.cgi?id=562143 Comment #2 of that bug has a patch that allegedly fixes the problem. I have hand-applied the patch against the latest stable source package of gdm (2.30.2.is.2.30.0), which I have attached here and am in the process of testing. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1053217 Title: gdm leaking filehandles, causing too many open files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1053217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1053217] Re: gdm leaking filehandles, causing too many open files
** Patch added: The aforementioned patch for gdm https://bugs.launchpad.net/bugs/1053217/+attachment/3324446/+files/gdm-2.30.2.is.2.30.0-filehandle-fix.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1053217 Title: gdm leaking filehandles, causing too many open files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1053217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1053217] Re: gdm leaking filehandles, causing too many open files
Okay, I can confirm this would appear to fix the problem. Test procedure: 1. Log in remotely to the affected machine using ssh, run the following command: $ sudo watch ls -l /proc/$( pidof gdm-binary )/fd 2. Start a remote X session with that host (through Xnest, plain X, whatever)... observe that new files are opened. 3. Close the X session, observe that the files are not removed from the list. In my case, this looked like this: Vanilla Ubuntu gdm build. After initial start-up. total 0 lrwx-- 1 root root 64 2012-09-20 14:34 0 - /dev/null lrwx-- 1 root root 64 2012-09-20 14:34 1 - /dev/null lrwx-- 1 root root 64 2012-09-20 14:34 2 - /dev/null lrwx-- 1 root root 64 2012-09-20 14:34 3 - socket:[78942] lr-x-- 1 root root 64 2012-09-20 14:34 4 - pipe:[78945] l-wx-- 1 root root 64 2012-09-20 14:34 5 - pipe:[78945] lr-x-- 1 root root 64 2012-09-20 14:34 6 - inotify lr-x-- 1 root root 64 2012-09-20 14:34 7 - pipe:[78952] l-wx-- 1 root root 64 2012-09-20 14:34 8 - pipe:[78952] lrwx-- 1 root root 64 2012-09-20 14:34 9 - /var/run/gdm/auth-for-gdm-omI8J6/database lr-x-- 1 root root 64 2012-09-20 14:34 10 - pipe:[78971] l-wx-- 1 root root 64 2012-09-20 14:34 11 - pipe:[78971] lr-x-- 1 root root 64 2012-09-20 14:34 12 - pipe:[78937] lrwx-- 1 root root 64 2012-09-20 14:34 13 - socket:[78973] lrwx-- 1 root root 64 2012-09-20 14:34 14 - socket:[78974] After a few logins... total 0 lrwx-- 1 root root 64 2012-09-20 14:38 0 - /dev/null lrwx-- 1 root root 64 2012-09-20 14:38 1 - /dev/null lrwx-- 1 root root 64 2012-09-20 14:38 2 - /dev/null lrwx-- 1 root root 64 2012-09-20 14:38 3 - socket:[78942] lr-x-- 1 root root 64 2012-09-20 14:38 4 - pipe:[78945] l-wx-- 1 root root 64 2012-09-20 14:38 5 - pipe:[78945] lr-x-- 1 root root 64 2012-09-20 14:38 6 - inotify lr-x-- 1 root root 64 2012-09-20 14:38 7 - pipe:[78952] l-wx-- 1 root root 64 2012-09-20 14:38 8 - pipe:[78952] lrwx-- 1 root root 64 2012-09-20 14:38 9 - /var/run/gdm/auth-for-gdm-omI8J6/database lr-x-- 1 root root 64 2012-09-20 14:38 10 - pipe:[78971] l-wx-- 1 root root 64 2012-09-20 14:38 11 - pipe:[78971] lr-x-- 1 root root 64 2012-09-20 14:38 12 - pipe:[78937] lrwx-- 1 root root 64 2012-09-20 14:38 13 - socket:[78973] lrwx-- 1 root root 64 2012-09-20 14:38 14 - socket:[78974] lrwx-- 1 root root 64 2012-09-20 14:38 15 - /var/run/gdm/auth-for-gdm-bqKAEb/database lrwx-- 1 root root 64 2012-09-20 14:38 16 - /var/run/gdm/auth-for-gdm-QC37Jk/database lrwx-- 1 root root 64 2012-09-20 14:38 17 - /var/run/gdm/auth-for-vrtadmin-4oPw6L/database lrwx-- 1 root root 64 2012-09-20 14:38 18 - /var/run/gdm/auth-for-gdm-ePg83T/database lrwx-- 1 root root 64 2012-09-20 14:38 19 - /var/run/gdm/auth-for-vrtadmin-YMcsem/database Now, build gdm with the given patch here, re-start gdm, and try again with the same procedure. In my case, I see: Patched gdm build. After initial start-up. total 0 lrwx-- 1 root root 64 2012-09-20 14:49 0 - /dev/null lrwx-- 1 root root 64 2012-09-20 14:49 1 - /dev/null lrwx-- 1 root root 64 2012-09-20 14:49 2 - /dev/null lrwx-- 1 root root 64 2012-09-20 14:49 3 - socket:[102450] lr-x-- 1 root root 64 2012-09-20 14:49 4 - pipe:[102453] l-wx-- 1 root root 64 2012-09-20 14:49 5 - pipe:[102453] lr-x-- 1 root root 64 2012-09-20 14:49 6 - inotify lr-x-- 1 root root 64 2012-09-20 14:49 7 - pipe:[102460] l-wx-- 1 root root 64 2012-09-20 14:49 8 - pipe:[102460] lrwx-- 1 root root 64 2012-09-20 14:49 9 - /var/run/gdm/auth-for-gdm-kjZfwe/database lr-x-- 1 root root 64 2012-09-20 14:49 10 - pipe:[102479] l-wx-- 1 root root 64 2012-09-20 14:49 11 - pipe:[102479] lr-x-- 1 root root 64 2012-09-20 14:49 12 - pipe:[102445] lrwx-- 1 root root 64 2012-09-20 14:49 13 - socket:[102481] lrwx-- 1 root root 64 2012-09-20 14:49 14 - socket:[102482] During a remote X session total 0 lrwx-- 1 root root 64 2012-09-20 14:51 0 - /dev/null lrwx-- 1 root root 64 2012-09-20 14:51 1 - /dev/null lrwx-- 1 root root 64 2012-09-20 14:51 2 - /dev/null lrwx-- 1 root root 64 2012-09-20 14:51 3 - socket:[102450] lr-x-- 1 root root 64 2012-09-20 14:51 4 - pipe:[102453] l-wx-- 1 root root 64 2012-09-20 14:51 5 - pipe:[102453] lr-x-- 1 root root 64 2012-09-20 14:51 6 - inotify lr-x-- 1 root root 64 2012-09-20 14:51 7 - pipe:[102460] l-wx-- 1 root root 64 2012-09-20 14:51 8 - pipe:[102460] lrwx-- 1 root root 64 2012-09-20 14:51 9 - /var/run/gdm/auth-for-gdm-kjZfwe/database lr-x-- 1 root root 64 2012-09-20 14:51 10 - pipe:[102479] l-wx-- 1 root root 64 2012-09-20 14:51 11 - pipe:[102479] lr-x-- 1 root root 64 2012-09-20 14:51 12 - pipe:[102445] lrwx-- 1 root root 64 2012-09-20 14:51 13 - socket:[102481] lrwx-- 1 root root 64 2012-09-20 14:51 14 - socket:[102482] lrwx-- 1 root root 64 2012-09-20 14:51 15 -
[Bug 259139] Re: Ncurses package does not contain libtinfo
Hate to bump an old bug... but it seems silly to create another one for essentially the same issue. I am currently packaging a proprietary application as an Ubuntu package (the MacroView SCADA system, as it so happens). Host platform is Ubuntu 10.04 LTS i386. In previous releases, the upstream software package linked against libncurses.so.5. Now it links against libtinfo.so.5, and thus I now have an issue getting dpkg-buildpackage to co-operate. I tried making a dummy package to install the necessary symlink... this might fool a runtime application, but it does not fool dpkg-shlibdeps, which complains loudly: dpkg-shlibdeps: warning: /lib/libtinfo.so.5 has an unexpected SONAME (libncurses.so.5) dpkg-shlibdeps: error: no dependency information found for /lib/libtinfo.so.5 (used by debian/macroview/usr/lib/macro/imgstat64). Now, all very well to argue that the build scripts should take care of this; however in my situation, the build scripts are taking a tarball containing precompiled binaries and copying them into the appropriate directories for packaging -- I do not control the linking process. So the solution in comment #8 will not work for this use case. Is it possible that this issue could be addressed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/259139 Title: Ncurses package does not contain libtinfo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/259139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
