[Bug 2063143] Re: sddm/simpledrm race conditions leads to frequent black display on bootup
Same here using NVidia GTX1050 Ti with Kubuntu 24.04. adding nomodeset fixes the problem as does removing both splash and quiet instead as a less performance impacting change. (Didnt try just one of spash and quiet to see which was the real culprit as its a production machine so try to avoid reboots - sorry!) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063143 Title: sddm/simpledrm race conditions leads to frequent black display on bootup To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/2063143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064815] Re: Always black screen on first reboot after fresh install 24.04, Intel and AMD GPU
*** This bug is a duplicate of bug 2063143 *** https://bugs.launchpad.net/bugs/2063143 Same here using NVidia GTX1050 Ti with Kubuntu 24.04. adding nomodeset fixes the problem as does removing both splash and quiet instead as a less performance impacting change. (Didnt try just one of spash and quiet to see which was the real culprit as its a production machine so try to avoid reboots - sorry!) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064815 Title: Always black screen on first reboot after fresh install 24.04, Intel and AMD GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947783] Re: home page fails after upgrade to ubuntu 21.10
Also PHP Fatal error: Uncaught ArgumentCountError: Attribute::__construct() expects at most 1 argument, 4 given in /usr/share/phpldapadmin/lib/AttributeFactory.php:136\nStack trace:\n#0 /usr/share/phpldapadmin/lib/AttributeFactory.php(136) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947783 Title: home page fails after upgrade to ubuntu 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpldapadmin/+bug/1947783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947783] Re: home page fails after upgrade to ubuntu 21.10
Also Fatal error: Uncaught Error: Call to undefined function each() in /usr/share/phpldapadmin/lib/functions.php:85 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947783 Title: home page fails after upgrade to ubuntu 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpldapadmin/+bug/1947783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947783] Re: home page fails after upgrade to ubuntu 21.10
If that Fatal is fixed with [] then it fails with
Deprecated: Required parameter $data follows optional parameter $subitem
in /usr/share/phpldapadmin/lib/functions.php on line 904
Deprecated: Required parameter $index follows optional parameter
$attr_name in /usr/share/phpldapadmin/lib/functions.php on line 2028
Fatal error: Uncaught Error: Call to undefined function
get_magic_quotes_gpc() in /usr/share/phpldapadmin/lib/common.php:299
Stack trace: #0 /usr/share/phpldapadmin/htdocs/common.php(13):
require_once() #1 /usr/share/phpldapadmin/htdocs/cmd.php(13):
require_once('...') #2 /usr/share/phpldapadmin/htdocs/index.php(151):
include('...') #3 {main} thrown in
/usr/share/phpldapadmin/lib/common.php on line 299
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947783
Title:
home page fails after upgrade to ubuntu 21.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/phpldapadmin/+bug/1947783/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947783] [NEW] home page fails after upgrade to ubuntu 21.10
Public bug reported: Deprecated: Required parameter $data follows optional parameter $subitem in /usr/share/phpldapadmin/lib/functions.php on line 904 Fatal error: Array and string offset access syntax with curly braces is no longer supported in /usr/share/phpldapadmin/lib/functions.php on line 1614 (debian package installed 1.2.2-6.3) ** Affects: phpldapadmin (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/1947783 Title: home page fails after upgrade to ubuntu 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpldapadmin/+bug/1947783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767314] Re: Ubuntu Bionic vi/vim not working correctly
Setting regexpengine=1 drops this back down to 1.4 seconds. So either this is the root cause of this particular slowdown (i.e. when syntax highlighting gitolite format files) or at least compensates for whatever is the root cause. According to https://stackoverflow.com/posts/38521226 the default regexp engine changed with Vim 7.4. This was the version shipped with Trusty onwards so in theory was already in use on 14.04 and 16.04 ubuntu so something doesnt quite tie up -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767314 Title: Ubuntu Bionic vi/vim not working correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1767314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767314] Re: Ubuntu Bionic vi/vim not working correctly
Just by way of more info I was editing a gitolite conf file of 4096 lines with
the following stats to render the syntax with the cursor at the end of the file
The total time taken was 5 seconds. By default redrawtime is set to 2 seconds
so the 5 srconds taken represents a considetable drop off in performance. It
is true that 18.04 feels sluggish. Maybe Spectre malware fix slowdowns?
TOTAL COUNT MATCH SLOWEST AVERAGE NAME PATTERN
1.580522 4214 96 0.0028750.000375 gitoliteRefex
\(^\s*\(-\|R\|RW+\?C\?D\?\)\s\+\)\@<=\S.\{-}\(\s*=
1.542289 4068 27120.0060480.000379 gitoliteConfigKey
\(\(config\|option\)\s\+\)\@<=[^ =]*
0.986339 1426 0 0.0327780.000692 gitoliteCreateRule
\(^\s*C\s.*=\s*\)\@<=\S[^#]*[^# ]
0.777079 4068 40680.0008700.000191 gitoliteConfigVal
\(=\s*\)\@<=\S.*
0.652198 1502 95 0.040.000434 gitoliteDenyRule
\(^\s*-\s.*=\s*\)\@<=\S[^#]*[^# ]
0.059132 2852 14260.0001000.21 gitoliteRule
\(^\s*\)\@<=\(-\|C\|R\|RW+\?C\?D\?\)\s\@=
0.033258 4118 13560.490.08 gitoliteConfigLine
^\s*\(config\|option\|include\|subconf\)\s[^#]*
0.024610 4142 14260.350.06 gitoliteRuleLine
^\s*\(-\|C\|R\|RW+\?C\?D\?\)\s[^#]*
0.016784 6026 32580.130.03 gitoliteGroup @\S\+
0.014909 4142 13950.130.04 gitoliteRepoError
^\s*\S\+\s*=
0.014868 4118 657 0.450.04 gitoliteRepoLine
^\s*repo\s\+[^=]*$
0.013410 4118 0 0.440.03 gitoliteRepoError ^\s*repo.*=
0.010654 4400 574 0.450.02 gitoliteComment#.*
0.004946 4118 1 0.140.01 gitoliteGroupLine
^\s*@\S\+\s*=\s*\S.*$
0.003386 4118 0 0.090.01 gitoliteTemplateLine ^=begin
template-data$
0.001547 4118 0 0.020.00 gitoliteSpecialRefex /USER/
0.001208 4118 0 0.010.00 gitoliteSpecialRefex NAME/
5.737139 65666
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767314
Title:
Ubuntu Bionic vi/vim not working correctly
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1767314/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767314] Re: Ubuntu Bionic vi/vim not working correctly
Further investigation with a recompiled version more recent than that shipped with 18.04 yields that syntax highlighting failure is caused by redrawtime being exceeded - often triggered after using G to move to the end of the file. It is not possible to set "syntax on" manually at that point as it immediatetly gets disabled again unless you move to the start of the file with g. This explains the "persistence" due to the "jump to the previously edited line in the file" setting being set - but forgetting it upon deletion of .viminfo as this is where this Info is stored. Without it vi opens with the cursor at line 1. In my case this problem has occurred following an upgrade and has never happened before on the same hardware running the same applications for many years with lots of files being edited multiple times every day - day in day out. Ie something in the timing dynamics when running vi has changed wirh 18.04 See https://github.com/vim/vim/issues/2790 for further discussion and possible workarounds. ** Bug watch added: github.com/vim/vim/issues #2790 https://github.com/vim/vim/issues/2790 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767314 Title: Ubuntu Bionic vi/vim not working correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1767314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767314] Re: Ubuntu Bionic vi/vim not working correctly
The mis-interpretation of PC cursor keys when accessed vi ssh (as described in the discussion link above) is very remeniscent of trying to use vim.tiny not vim.basic (which server install defaults to). Maybe this along with my above post will help characterise the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767314 Title: Ubuntu Bionic vi/vim not working correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1767314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767314] Re: Ubuntu Bionic vi/vim not working correctly
The "set nocompatible" fix doesn't work on 18.04.1 LTS server. The trigger condition appears to be a random operation and not repeatable. Symptoms include loss of tab completion and syntax highlighting. It is persistent through a re-edit of the same file. The fault can be cleared by removing .viminfo until the next random occurence. Given the use of vi on a server instance with no GUU is very high I would request the importance of this bug is set to high as it significantly damages productivity when used in a professional context. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767314 Title: Ubuntu Bionic vi/vim not working correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1767314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314729] Re: dahdi-dkms 1:2.5.0.1+dfsg-1ubuntu2: dahdi kernel module failed to build [error: implicit declaration of function ‘PDE’]
Identical bug when compiling on debian wheezy dahdi-source_2.6.1+dfsg2-1_all.deb on kernel 3.14.12 /usr/src/modules/dahdi/drivers/dahdi/dahdi-base.c: In function 'dahdi_proc_open': /usr/src/modules/dahdi/drivers/dahdi/dahdi-base.c:902:2: error: implicit declaration of function 'PDE' [-Werror=implicit-function-declaration -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314729 Title: dahdi-dkms 1:2.5.0.1+dfsg-1ubuntu2: dahdi kernel module failed to build [error: implicit declaration of function ‘PDE’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1314729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 918896] Re: returns no data from SQL server
Thanks Alfonso - you saved me a lot of work. Pity they couldn't default the last parameter to being '' or None to retain the old behaviour and thus not break existing code. Anyway I can confirm your results on 12.04 LTS Here are my precise component versions. Server: Ubuntu12.04.2 LTS x86_64 python: 2.7.3-0ubuntu2.2 python-pymssql: 1.0.2+dfsg-1build1 freetds-common: 0.91-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/918896 Title: returns no data from SQL server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pymssql/+bug/918896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 676391] Re: do_lrm_control: Failed to sign on to the LRM after upgrade to Maverick
cluster-glue containing upstart support (1.0.6-1ubuntu1.1) may be buggy atm in that it doesnt initialise the threading system that upstart support requires when accessing d-bus. See http://www.gossamer- threads.com/lists/linuxha/dev/68379?search_string=possible%20deadlock%20in%20lrmd;#68379 for further discussions. It does, however, include Senko Rasic's patch mentioned in that thread. -- do_lrm_control: Failed to sign on to the LRM after upgrade to Maverick https://bugs.launchpad.net/bugs/676391 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 676391] Re: do_lrm_control: Failed to sign on to the LRM after upgrade to Maverick
hb_report added just after corosync started for what it is worth. ** Attachment added: report_node1.tar.bz2 https://bugs.launchpad.net/ubuntu/+source/cluster-glue/+bug/676391/+attachment/1738641/+files/report_node1.tar.bz2 -- do_lrm_control: Failed to sign on to the LRM after upgrade to Maverick https://bugs.launchpad.net/bugs/676391 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 676391] [NEW] do_lrm_control: Failed to sign on to the LRM after upgrade to Maverick
Public bug reported: Binary package hint: cluster-glue Since upgrading to Maverick and installing cluster-glue 1.0.6-1ubuntu1.1 for upstart support I am getting repeats of crmd: WARN: lrm_signon: can not initiate connection crmd: [4963]: WARN: do_lrm_control: Failed to sign on to the LRM 29 (30 max) time on a system that previously was working fine on lucid netstat -anp shows unix 2 [ ] DGRAM 22204 4546/lrmd which implies at least part of lrmd is running. I dont know what this implies but I cannot find any unix sockets in the filing system ps auxf shows: root 4539 0.0 0.0 0 0 ? Z 00:04 0:00 \_ [lrmd] defunct root 4546 0.0 0.0 36424 1344 ? S 00:04 0:00 \_ /usr/lib/heartbeat/lrmd crm_mon -1 shows Last updated: Wed Nov 17 00:13:25 2010 Stack: openais Current DC: NONE 2 Nodes configured, 2 expected votes 2 Resources configured. OFFLINE: [ node1 node2 ] Clearly the Current DC:NONE is the symptom that results from lrmd not being communicative. I've tried downgrading to cluster-glue 1.0.6-1ubuntu1 and this is showing the same symptom. I've also tried removing and reinstalling all relevant components (pacemaker, corosync etc) without success. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: cluster-glue 1.0.6-1ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.35-22.35-server 2.6.35.4 Uname: Linux 2.6.35-22-server x86_64 Architecture: amd64 Date: Wed Nov 17 07:41:09 2010 ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: cluster-glue ** Affects: cluster-glue (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- do_lrm_control: Failed to sign on to the LRM after upgrade to Maverick https://bugs.launchpad.net/bugs/676391 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 676391] Re: do_lrm_control: Failed to sign on to the LRM after upgrade to Maverick
-- do_lrm_control: Failed to sign on to the LRM after upgrade to Maverick https://bugs.launchpad.net/bugs/676391 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 676391] Re: do_lrm_control: Failed to sign on to the LRM after upgrade to Maverick
For clarirification I am running a 2 node failover (master slave) clustered ftp server using drbd to duplicate the filesystem. I'm using corosync/pacemaker for my HA stack. I can post the configuration but dont think that important as the system fails before really using that. -- do_lrm_control: Failed to sign on to the LRM after upgrade to Maverick https://bugs.launchpad.net/bugs/676391 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 676391] Re: do_lrm_control: Failed to sign on to the LRM after upgrade to Maverick
Versions of these other packages pacemaker 1.0.9.1-2ubuntu4 corosync 1.2.1-1ubuntu1 cluster-agents 1:1.0.3-3 The only other thing I noticed during the upgrade was heartbeat-common had no candidate on 1 of the 2 servers I upgraded. I Put this down to the fact I had previously had the old heartbeat HA working on that box. -- do_lrm_control: Failed to sign on to the LRM after upgrade to Maverick https://bugs.launchpad.net/bugs/676391 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 676391] Re: do_lrm_control: Failed to sign on to the LRM after upgrade to Maverick
Further investigation (not yet correlated) suggests that it might possibly be a
permissions or a timing issue.
I can see from straces crmd creating the lrm sockets
[pid 4433] unlink(/var/run/heartbeat/lrm_cmd_sock) = -1 ENOENT (No such file
or directory)
[pid 4433] bind(4, {sa_family=AF_FILE,
path=/var/run/heartbeat/lrm_cmd_sock}, 110) = 0
[pid 4433] chmod(/var/run/heartbeat/lrm_cmd_sock, 0777) = 0
[pid 4433] listen(4, 10) = 0
[pid 4433] fcntl(4, F_GETFL) = 0x2 (flags O_RDWR)
[pid 4433] fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK) = 0
[pid 4433] socket(PF_FILE, SOCK_STREAM, 0) = 7
[pid 4433] unlink(/var/run/heartbeat/lrm_callback_sock) = -1 ENOENT (No such
file or directory)
[pid 4433] bind(7, {sa_family=AF_FILE,
path=/var/run/heartbeat/lrm_callback_sock}, 110) = 0
[pid 4433] chmod(/var/run/heartbeat/lrm_callback_sock, 0777) = 0
and then shortly afterwards delete them again
[pid 4433] unlink(/var/run/heartbeat/lrm_cmd_sock unfinished ...
[pid 4436] ... mprotect resumed )= 0
[pid 4433] ... unlink resumed ) = 0
[pid 4425] futex(0x7f33c929b0c4, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7f33c929b0c0,
{FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1} unfinished ...
[pid 4433] close(7 unfinished ...
[pid 4426] ... futex resumed ) = 0
[pid 4433] ... close resumed ) = 0
[pid 4426] futex(0x7f33c929b100, FUTEX_WAIT_PRIVATE, 2, NULL unfinished ...
[pid 4433] unlink(/var/run/heartbeat/lrm_callback_sock unfinished ...
On one of the two nodes I did manage to make some progress in that I stopped
corosync, waited for a few minutes then started it again and now I get the
sockets (Doing /etc/init.d/corosync restarts or machine reboots wasnt ever
successful.
r...@node1:/var/run/heartbeat# ls -l
total 0
srwxrwxrwx 1 root root 0 2010-11-17 01:22 lrm_callback_sock
srwxrwxrwx 1 root root 0 2010-11-17 01:22 lrm_cmd_sock
drwxr-xr-x 2 root root 40 2010-11-17 01:22 rsctmp
srwxrwxrwx 1 root root 0 2010-11-17 01:22 stonithd
srwxrwxrwx 1 root root 0 2010-11-17 01:22 stonithd_callback
but I cant repeat this on the second node.
I havent tried it on the first node again (at least I can compare things with
the 2nd node).
After
--
do_lrm_control: Failed to sign on to the LRM after upgrade to Maverick
https://bugs.launchpad.net/bugs/676391
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 676391] Re: do_lrm_control: Failed to sign on to the LRM after upgrade to Maverick
Yes Andres, I'm Dave! To answer your questions: /etc/default/corosync - YES start at boot /etc/corosync/corosync.conf identical between nodes, looks OK/intact and is dated1 month ago. authkeys md5sum identical and dated 1 month ago 400 root.root perms Both nodes are reporting same with crm_mon so no reason to think comms is a problem (e.g. auth or multicast bad) Last few lines of log from node2 as crmd died: ... Nov 17 10:55:26 node2 crmd: [22808]: info: crm_timer_popped: Wait Timer (I_NULL) just popped! Nov 17 10:55:26 node2 crmd: [22808]: WARN: lrm_signon: can not initiate connection Nov 17 10:55:26 node2 crmd: [22808]: ERROR: do_lrm_control: Failed to sign on to the LRM 30 (max) times Nov 17 10:55:26 node2 crmd: [22808]: ERROR: do_log: FSA: Input I_ERROR from do_lrm_control() received in state S_STARTING Nov 17 10:55:26 node2 crmd: [22808]: info: do_state_transition: State transition S_STARTING - S_RECOVERY [ input=I_ERROR cause=C_FSA_INTERNAL origin=do_lrm_control ] Nov 17 10:55:26 node2 crmd: [22808]: ERROR: do_recover: Action A_RECOVER (0100) not supported Nov 17 10:55:26 node2 crmd: [22808]: ERROR: do_started: Start cancelled... S_RECOVERY Nov 17 10:55:26 node2 crmd: [22808]: ERROR: do_log: FSA: Input I_TERMINATE from do_recover() received in state S_RECOVERY Nov 17 10:55:26 node2 crmd: [22808]: info: do_state_transition: State transition S_RECOVERY - S_TERMINATE [ input=I_TERMINATE cause=C_FSA_INTERNAL origin=do_recover ] Nov 17 10:55:26 node2 crmd: [22808]: info: do_ha_control: Disconnected from OpenAIS Nov 17 10:55:26 node2 crmd: [22808]: info: do_cib_control: Disconnecting CIB Nov 17 10:55:26 node2 crmd: [22808]: info: crmd_cib_connection_destroy: Connection to the CIB terminated... Nov 17 10:55:26 node2 crmd: [22808]: info: do_exit: Performing A_EXIT_0 - gracefully exiting the CRMd Nov 17 10:55:26 node2 crmd: [22808]: ERROR: do_exit: Could not recover from internal error Nov 17 10:55:26 node2 crmd: [22808]: info: free_mem: Dropping I_TERMINATE: [ state=S_TERMINATE cause=C_FSA_INTERNAL origin=do_stop ] Nov 17 10:55:26 node2 cib: [20601]: WARN: send_ipc_message: IPC Channel to 22808 is not connected Nov 17 10:55:26 node2 cib: [20601]: WARN: send_via_callback_channel: Delivery of reply to client 22808/3210be2d-0165-4c05-8c43-8945feea0692 failed Nov 17 10:55:26 node2 crmd: [22808]: info: do_exit: [crmd] stopped (2) Nov 17 10:55:26 node2 cib: [20601]: WARN: do_local_notify: A-Sync reply to crmd failed: reply failed Nov 17 10:55:26 node2 corosync[20586]: [pcmk ] info: pcmk_ipc_exit: Client crmd (conn=0x1d98d00, async-conn=0x1d98d00) left Nov 17 10:55:27 node2 corosync[20586]: [pcmk ] ERROR: pcmk_wait_dispatch: Child process crmd exited (pid=22808, rc=2) Nov 17 10:55:27 node2 corosync[20586]: [pcmk ] pcmk_wait_dispatch: Call to wait4(crmd) failed: (10) No child processes Nov 17 10:55:27 node2 corosync[20586]: [pcmk ] ERROR: pcmk_wait_dispatch: Child respawn count exceeded by crmd Nov 17 10:55:27 node2 corosync[20586]: [pcmk ] info: update_member: Node node2 now has process list: 0002 (69906) -- do_lrm_control: Failed to sign on to the LRM after upgrade to Maverick https://bugs.launchpad.net/bugs/676391 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 676391] Re: do_lrm_control: Failed to sign on to the LRM after upgrade to Maverick
Also on node 1 (where I think lrmd is running) I have crm_mon[26251]: 2010/11/17_21:00:32 info: determine_online_status: Node node1 is standby crm_mon[26251]: 2010/11/17_21:00:32 debug: unpack_rsc_op: failover-ip_monitor_0 on node1 returned 0 (ok) instead of the expected value: 7 (not running) crm_mon[26251]: 2010/11/17_21:00:32 notice: unpack_rsc_op: Operation failover-ip_monitor_0 found resource failover-ip active on node1 crm_mon[26251]: 2010/11/17_21:00:32 debug: unpack_rsc_op: drbd_disk:0_monitor_0 on node1 returned 8 (master) instead of the expected value: 7 (not running) crm_mon[26251]: 2010/11/17_21:00:32 notice: unpack_rsc_op: Operation drbd_disk:0_monitor_0 found resource drbd_disk:0 active in master mode on node1 crm_mon[26251]: 2010/11/17_21:00:32 debug: unpack_rsc_op: fs_drbd_monitor_0 on node1 returned 0 (ok) instead of the expected value: 7 (not running) crm_mon[26251]: 2010/11/17_21:00:32 notice: unpack_rsc_op: Operation fs_drbd_monitor_0 found resource fs_drbd active on node1 crm_mon[26251]: 2010/11/17_21:00:32 debug: unpack_rsc_op: vsftpd_monitor_0 on node1 returned 0 (ok) instead of the expected value: 7 (not running) crm_mon[26251]: 2010/11/17_21:00:32 notice: unpack_rsc_op: Operation vsftpd_monitor_0 found resource vsftpd active on node1 which suggests that the ra's arent reporting correctly -- do_lrm_control: Failed to sign on to the LRM after upgrade to Maverick https://bugs.launchpad.net/bugs/676391 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659510] Re: Upstart Resource Agent Plugin is not installed
Since upgrading to Maverick and installing cluster-glue 1.0.6-1ubuntu1.1 I am getting repeats of crmd: WARN: lrm_signon: can not initiate connection crmd: [4963]: WARN: do_lrm_control: Failed to sign on to the LRM 29 (30 max) time on a system that previously was working on lucid (except for upstart which is why I upgraded) netstat -anp shows unix 2 [ ] DGRAM222044546/lrmd ps auxf shows: root 4539 0.0 0.0 0 0 ?Z00:04 0:00 \_ [lrmd] defunct root 4546 0.0 0.0 36424 1344 ?S00:04 0:00 \_ /usr/lib/heartbeat/lrmd Anyone seen this or know how best to debug this? A rapid response would be helpful as I have a production HA cluster down! -- Upstart Resource Agent Plugin is not installed https://bugs.launchpad.net/bugs/659510 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659510] Re: Upstart Resource Agent Plugin is not installed
crm_mon -1 shows Last updated: Wed Nov 17 00:13:25 2010 Stack: openais Current DC: NONE 2 Nodes configured, 2 expected votes 2 Resources configured. OFFLINE: [ node1 node2 ] -- Upstart Resource Agent Plugin is not installed https://bugs.launchpad.net/bugs/659510 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659510] Re: Upstart Resource Agent Plugin is not installed
I've just tried downgrading to cluster-glue 1.0.6-1ubuntu1 and this is showing the same symptom. Dont want to mis-post so should I raise separate ticket for this. It maybe something wrong with the upgrade although I have tried removing and reinstalling all the associated packages corosync, pacemaker etc and lrmd is in cluster-glue! -- Upstart Resource Agent Plugin is not installed https://bugs.launchpad.net/bugs/659510 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 654784] [NEW] eucalyptus-common 2.0+bzr1241-0ubuntu4 warning during postinst
Public bug reported: Binary package hint: eucalyptus-common Split out from bug 652815 when the postinstall script runs for eucalyptus-common the warning start: Unknown parameter: IFACE is generated. The install completes OK. This is on a maverick ubuntu 10.10 beta amd64 system previously installed fresh from CD. The line that generates this appears to be line 8 of the upstart job /etc/init/eucalyptus-network.conf which has the string instance $IFACE ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: eucalyptus-common (not installed) ProcVersionSignature: Ubuntu 2.6.35-22.32-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Mon Oct 4 20:28:54 2010 ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: eucalyptus ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- eucalyptus-common 2.0+bzr1241-0ubuntu4 warning during postinst https://bugs.launchpad.net/bugs/654784 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- 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 654784] [NEW] eucalyptus-common 2.0+bzr1241-0ubuntu4 warning during postinst
Public bug reported: Binary package hint: eucalyptus-common Split out from bug 652815 when the postinstall script runs for eucalyptus-common the warning start: Unknown parameter: IFACE is generated. The install completes OK. This is on a maverick ubuntu 10.10 beta amd64 system previously installed fresh from CD. The line that generates this appears to be line 8 of the upstart job /etc/init/eucalyptus-network.conf which has the string instance $IFACE ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: eucalyptus-common (not installed) ProcVersionSignature: Ubuntu 2.6.35-22.32-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Mon Oct 4 20:28:54 2010 ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: eucalyptus ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- eucalyptus-common 2.0+bzr1241-0ubuntu4 warning during postinst https://bugs.launchpad.net/bugs/654784 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 639712] Re: PCI Pass Through via libvirt cannot remap IRQ's
Yes. That aspect has been noted already in Bug #552311. Depending on how we deal with the various components of this issue it might be sensible to track the config changes under that reference. -- PCI Pass Through via libvirt cannot remap IRQ's https://bugs.launchpad.net/bugs/639712 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 639712] Re: PCI Pass Through via libvirt cannot remap IRQ's
Yes. That aspect has been noted already in Bug #552311. Depending on how we deal with the various components of this issue it might be sensible to track the config changes under that reference. -- PCI Pass Through via libvirt cannot remap IRQ's https://bugs.launchpad.net/bugs/639712 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 552311] Re: CONFIG_DMAR is not set
Beyond DMAR there are other changes that I found were required to make Vt-d virtualisation work. I have reported these in Bug #639712 -- CONFIG_DMAR is not set https://bugs.launchpad.net/bugs/552311 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 453653] Re: [karmic] libvirt fails to list node devices
To answer janusz comments - To reassign IRQ's etc you need: (Recompiled) Kernel with CONFIG_DMAR=y CONFIG_DMAR_DEFAULT_ON=y To check your available kernels: grep DMAR /boot.config* If you look at other launchpad entries you will see there has been discussion on this so it might have been resolved already. Sadly Maverick Beta does not have it set. Apparmor set up as follows: /etc/apparmor.d/abstractions/libvirt-qemu needs to contain # required for IRQ remapping with PCI Pass Through capability sys_rawio, # For hostdev access /sys/devices/ r, /sys/devices/** r, Dave -- [karmic] libvirt fails to list node devices https://bugs.launchpad.net/bugs/453653 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 639712] [NEW] PCI Pass Through via libvirt cannot remap IRQ's
Public bug reported: Trying to allocate a hardware device (telecoms card) using virt-manager results in errors - most frequently (but not exclusively) a) Errors claiming IOMMU cannot be found even though the hardware is VT-x and VT-d capable and BIOS has it enabled b) Failed to assign irq for hostdev0: Operation not permitted Perhaps you are assigning a device that shares an IRQ with another device? and c) PCI region 0 at address 0xe520 has size 0x100, which is not a multiple of 4K Tried with versions of Lucid and Maverick. Currently using 0.8.3-1ubuntu9 Investigation showed that i) The kernel does not have DMAR enabled even on Maverick Server. ii) apparmor profile does not have the right settings iii) Updates in qemu-kvm git repository which handle small I/O windows havent yet been incorporated in a release Investigation showed there to be several problems (which perhaps could gave been documented somewhere) To fix this successfully it was necessary for me to undertake the following: a) recompiled the kernel with CONFIG_DMAR=y CONFIG_DMAR_DEFAULT_ON=y CONFIG_GART_IOMMU=y b) recompiled qemu-kvm from git source c) Added the following to /etc/apparmor.d/abstractions/libvirt-qemu # required for pci passthru capability sys_rawio, # For hostdev access. /sys/devices/ r, /sys/devices/** r, You could argue that the small PCI Memory problem was very card specific but given that Ubuntu claims the Server version is ready for virtualisation under KVM and that technology supports VT-d and PCI Pass Through there should be a suitable kernel version and apparmor profile that supports it available. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: libvirt-bin 0.8.3-1ubuntu9 [modified: usr/bin/virsh usr/sbin/libvirtd usr/share/libvirt/schemas/domain.rng usr/share/libvirt/schemas/storagepool.rng] ProcVersionSignature: Ubuntu 2.6.35-19.28-dmar 2.6.35.3 Uname: Linux 2.6.35-19-dmar x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Sep 15 16:49:55 2010 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Alpha amd64 (20100803.1) ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: libvirt ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- PCI Pass Through via libvirt cannot remap IRQ's https://bugs.launchpad.net/bugs/639712 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 639712] Re: PCI Pass Through via libvirt cannot remap IRQ's
** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/639712/+attachment/1589223/+files/Dependencies.txt -- PCI Pass Through via libvirt cannot remap IRQ's https://bugs.launchpad.net/bugs/639712 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 44676] Re: cannot allocate memory
I will have to check on a different machine. The server I am using it on at present is still running karmic. -- cannot allocate memory https://bugs.launchpad.net/bugs/44676 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 453653] Re: [karmic] libvirt fails to list node devices
To answer janusz comments - To reassign IRQ's etc you need: (Recompiled) Kernel with CONFIG_DMAR=y CONFIG_DMAR_DEFAULT_ON=y To check your available kernels: grep DMAR /boot.config* If you look at other launchpad entries you will see there has been discussion on this so it might have been resolved already. Sadly Maverick Beta does not have it set. Apparmor set up as follows: /etc/apparmor.d/abstractions/libvirt-qemu needs to contain # required for IRQ remapping with PCI Pass Through capability sys_rawio, # For hostdev access /sys/devices/ r, /sys/devices/** r, Dave -- [karmic] libvirt fails to list node devices https://bugs.launchpad.net/bugs/453653 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 639712] [NEW] PCI Pass Through via libvirt cannot remap IRQ's
Public bug reported: Trying to allocate a hardware device (telecoms card) using virt-manager results in errors - most frequently (but not exclusively) a) Errors claiming IOMMU cannot be found even though the hardware is VT-x and VT-d capable and BIOS has it enabled b) Failed to assign irq for hostdev0: Operation not permitted Perhaps you are assigning a device that shares an IRQ with another device? and c) PCI region 0 at address 0xe520 has size 0x100, which is not a multiple of 4K Tried with versions of Lucid and Maverick. Currently using 0.8.3-1ubuntu9 Investigation showed that i) The kernel does not have DMAR enabled even on Maverick Server. ii) apparmor profile does not have the right settings iii) Updates in qemu-kvm git repository which handle small I/O windows havent yet been incorporated in a release Investigation showed there to be several problems (which perhaps could gave been documented somewhere) To fix this successfully it was necessary for me to undertake the following: a) recompiled the kernel with CONFIG_DMAR=y CONFIG_DMAR_DEFAULT_ON=y CONFIG_GART_IOMMU=y b) recompiled qemu-kvm from git source c) Added the following to /etc/apparmor.d/abstractions/libvirt-qemu # required for pci passthru capability sys_rawio, # For hostdev access. /sys/devices/ r, /sys/devices/** r, You could argue that the small PCI Memory problem was very card specific but given that Ubuntu claims the Server version is ready for virtualisation under KVM and that technology supports VT-d and PCI Pass Through there should be a suitable kernel version and apparmor profile that supports it available. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: libvirt-bin 0.8.3-1ubuntu9 [modified: usr/bin/virsh usr/sbin/libvirtd usr/share/libvirt/schemas/domain.rng usr/share/libvirt/schemas/storagepool.rng] ProcVersionSignature: Ubuntu 2.6.35-19.28-dmar 2.6.35.3 Uname: Linux 2.6.35-19-dmar x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Sep 15 16:49:55 2010 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Alpha amd64 (20100803.1) ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: libvirt ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- PCI Pass Through via libvirt cannot remap IRQ's https://bugs.launchpad.net/bugs/639712 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 639712] Re: PCI Pass Through via libvirt cannot remap IRQ's
** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/639712/+attachment/1589223/+files/Dependencies.txt -- PCI Pass Through via libvirt cannot remap IRQ's https://bugs.launchpad.net/bugs/639712 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576071] Re: After upgrade to Lucid /dev/disk/by-uuid missing when booting with initramfs
Upgrade to 10.04.1 server from 10.04 reinstates the broken behaviour. Again the fix to references to blkid in /lib/udev/rules.d and remaking the initramfs as decribed above fixes it for me, -- After upgrade to Lucid /dev/disk/by-uuid missing when booting with initramfs https://bugs.launchpad.net/bugs/576071 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 619129] Re: kernel upgrade does not adjust grub2 default parameter when it is non-zero
Thanks for your response. The technique works fine! (Note for careless users - no errors are reported if the string is wrong when upgrade-grub is run) -- kernel upgrade does not adjust grub2 default parameter when it is non-zero https://bugs.launchpad.net/bugs/619129 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 619129] [NEW] kernel upgrade does not adjust grub2 default parameter when it is non-zero
Public bug reported: I was running a tweaked command line version of 2.6.35-12 to get over bugs in nouveau as a new grub entry. This required me to set GRUB_DEFAULT=6 in my /etc/defaultgrub On upgrade to 2.6.35-14 as part of Maverick updates the new kernel was inserted and results (either by update-grub or by grub-pc itself during boot) with the entries (normal and recovery versions) being the first in the list. GRUB_DEFAULT should have been set to 8 to compensate for the new entries but it remained at 6 resulting in the system booting the wrong image upon restart. (It booted memtest86 as it happens!). Obviously the workaround to get the system working is to interrupt grub with shift key, select the right kernel and once booted manually update the default to the required entry (in my case editing the entry to point to the new kernel). It is not reasonable to cope with all possible manual alterations to grub settings but this one should have been dealt with automatically as it is 100% deterministic and the consequence of the kernel upgrade scriplet. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: linux-generic 2.6.35.15.16 Regression: No Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.35-14.20-generic 2.6.35 Uname: Linux 2.6.35-14-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. AplayDevices: List of PLAYBACK Hardware Devices card 0: I82801BAICH2 [Intel 82801BA-ICH2], device 0: Intel ICH [Intel 82801BA-ICH2] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dwilliams 1318 F xfce4-volumed dwilliams 1326 F pulseaudio dwilliams 1369 F xfce4-mixer-plu CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'I82801BAICH2'/'Intel 82801BA-ICH2 with AD1885 at irq 17' Mixer name : 'Analog Devices AD1885' Components : 'AC97a:41445360' Controls : 38 Simple ctrls : 27 Date: Tue Aug 17 09:58:54 2010 HibernationDevice: RESUME=UUID=fbce8d08-8d33-4e5f-b2f3-346a1028a9b2 InstallationMedia: Xubuntu 10.10 Maverick Meerkat - Alpha i386 (20100803) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hewlett-Packard HP Vectra ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-14-generic root=UUID=053be657-1f44-4636-89c5-2cc550a839ef ro nouveau.modeset=0 ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.38 RfKill: SourcePackage: linux dmi.bios.date: 07/19/2001 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: JA.01.03US dmi.board.name: HP System Board dmi.board.vendor: Hewlett-Packard dmi.board.version: A06 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Version 1.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJA.01.03US:bd07/19/2001:svnHewlett-Packard:pnHPVectra:pvrVL420:rvnHewlett-Packard:rnHPSystemBoard:rvrA06:cvnHewlett-Packard:ct3:cvrVersion1.00: dmi.product.name: HP Vectra dmi.product.version: VL420 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 kconfig maverick needs-upstream-testing -- kernel upgrade does not adjust grub2 default parameter when it is non-zero https://bugs.launchpad.net/bugs/619129 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 619129] Re: kernel upgrade does not adjust grub2 default parameter when it is non-zero
** Attachment added: AcpiTables.txt https://bugs.launchpad.net/bugs/619129/+attachment/1494897/+files/AcpiTables.txt ** Attachment added: AlsaDevices.txt https://bugs.launchpad.net/bugs/619129/+attachment/1494898/+files/AlsaDevices.txt ** Attachment added: ArecordDevices.txt https://bugs.launchpad.net/bugs/619129/+attachment/1494899/+files/ArecordDevices.txt ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/619129/+attachment/1494900/+files/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt https://bugs.launchpad.net/bugs/619129/+attachment/1494901/+files/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.txt https://bugs.launchpad.net/bugs/619129/+attachment/1494902/+files/Card0.Codecs.codec97.0.ac97.0.0.txt ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.regs.txt https://bugs.launchpad.net/bugs/619129/+attachment/1494903/+files/Card0.Codecs.codec97.0.ac97.0.0.regs.txt ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/619129/+attachment/1494904/+files/CurrentDmesg.txt ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/619129/+attachment/1494905/+files/Dependencies.txt ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/619129/+attachment/1494906/+files/Lspci.txt ** Attachment added: PciMultimedia.txt https://bugs.launchpad.net/bugs/619129/+attachment/1494907/+files/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/619129/+attachment/1494908/+files/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/619129/+attachment/1494909/+files/ProcInterrupts.txt ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/619129/+attachment/1494910/+files/ProcModules.txt ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/619129/+attachment/1494911/+files/UdevDb.txt ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/619129/+attachment/1494912/+files/UdevLog.txt ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/619129/+attachment/1494913/+files/WifiSyslog.txt -- kernel upgrade does not adjust grub2 default parameter when it is non-zero https://bugs.launchpad.net/bugs/619129 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581549] Re: nouveau driver hangs system
I have a series of HP machines all using the Vidia Corporation NV6 [Vanta/Vanta LT] (rev 15) as the video controller These all hang X after a random period of time after start up whether or not X is being used actively but if you do something that manipulates the screen then it is more likely to happen within a few seconds. If you dont log in or use console VTX (ctrl-alt-f2 etc) then the PC stays running. In some instances you can ssh into the machine after X has locked up. syslog shows many repeats (several per second) of nouveau :01:00.0: PFIFO_DMA_PUSHER - Ch 1 These machines were fine on Karmic but fail on fails on Lucid and Maverick Alpha2 (when nouveau is the default) and is worse when using XFCE. It is irrespective of upgrade or fresh install. It is marginally more reliable if using Gnome (These are low spec machines so xubuntu/xfce is my prime choice for these machines. Dropping back to VESA (setting nouveau.modeset=0) (Not sure why it didnt drop to nv instead but thats a different issue) the machines are stable. -- nouveau driver hangs system https://bugs.launchpad.net/bugs/581549 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559482] Re: flickering on external screen
I have the same flickering problem on external monitor at 1280x1024 on an HP 6400 with an X1300 chipset running kernel 2.6.35-14-generic from Maverick (Alpha 2). It only shows when you move the mouse. It is OK at lower resolutions. -- flickering on external screen https://bugs.launchpad.net/bugs/559482 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 586175] Re: Windows XP/2003 doesn't boot
I am struggling with the same problem with a WIndows 2003 install under virt-manager/virsh The byte at 7e1c was already set to 3F. hexediting the byte at offset 7e1a to FF allowed the system to boot OK. -- Windows XP/2003 doesn't boot https://bugs.launchpad.net/bugs/586175 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- 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 586175] Re: Windows XP/2003 doesn't boot
I am struggling with the same problem with a WIndows 2003 install under virt-manager/virsh The byte at 7e1c was already set to 3F. hexediting the byte at offset 7e1a to FF allowed the system to boot OK. -- Windows XP/2003 doesn't boot https://bugs.launchpad.net/bugs/586175 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576071] Re: After upgrade to Lucid /dev/disk/by-uuid missing when booting with initramfs
I have just done an upgrade on a completely different server machine and run into the same problem. As an additional thought - these machines were previously running versions as early as feisty and have been incrementally updated since. -- After upgrade to Lucid /dev/disk/by-uuid missing when booting with initramfs https://bugs.launchpad.net/bugs/576071 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581805] Re: libsrp1-dev srtp-utils srtp-docs missing from lucid
The tone of your comment suggests you aren't quite sure. Can you provide more details of what version you are looking at and the changelog entry that resolved the issue reported? Latest version on the mirrors still appears to be 1.4.4~dfsg-2, the upstream source (sourcefroge.net) hasnt got any significant changes and keyserver.ubuntu.com isnt responding so I cant look at the PPA. Thanks Dave -- libsrp1-dev srtp-utils srtp-docs missing from lucid https://bugs.launchpad.net/bugs/581805 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581805] Re: libsrp1-dev srtp-utils srtp-docs missing from lucid
This may be because building the packages from source fails (on my 64 bit system) within test/rtpw_test.sh. I had to make the following changes to get it to succeed. a) Added a sleep 1 to prevent killall killing the receiver process immediately after it was created (even though this was done on a subsequent script line) b) Added ax flags to the ps command as under fakeroot the receiver and sender tasks werent reported by ps on its own. c) Added a -q in the killall to tidy up the output. a) and b) were both rather strange faults. Anway this is the patch: --- srtp_1.4.4~dfsg.orig/test/rtpw_test.sh 2006-06-13 16:17:57.0 +0100 +++ srtp_1.4.4~dfsg-3/test/rtpw_test.sh 2010-05-18 15:22:10.0 +0100 @@ -6,3 +6,3 @@ -RTPW=rtpw +RTPW=./rtpw DEST_PORT= @@ -20,3 +20,4 @@ -killall rtpw 2/dev/null +killall -q rtpw 2/dev/null +sleep 1 @@ -35,3 +36,3 @@ # verify that the background job is running -ps | grep -q $receiver_pid +ps ax | grep -q $receiver_pid retval=$? @@ -50,5 +51,4 @@ echo $0 : sender PID = $sender_pid - # verify that the background job is running -ps | grep -q $sender_pid +ps ax | grep -q $sender_pid retval=$? -- libsrp1-dev srtp-utils srtp-docs missing from lucid https://bugs.launchpad.net/bugs/581805 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581805] [NEW] libsrp1-dev srtp-utils srtp-docs missing from lucid
Public bug reported: These packages existed in karmic and an entry exists in http://packages.ubuntu.com/source/lucid/srtp implying it is supposed to be there still. ** Affects: srtp (Ubuntu) Importance: Undecided Status: New -- libsrp1-dev srtp-utils srtp-docs missing from lucid https://bugs.launchpad.net/bugs/581805 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577601] [NEW] package seamonkey-browser 1.1.17 nobinonly-0ubuntu1 [modified: usr/share/seamonkey/chrome/installed-chrome.txt] failed to install/upgrade:
Public bug reported: Binary package hint: dpkg Reported during routine upgrade from karmic to lucid ProblemType: Package DistroRelease: Ubuntu 10.04 Package: seamonkey-browser 1.1.17+nobinonly-0ubuntu1 [modified: usr/share/seamonkey/chrome/installed-chrome.txt] ProcVersionSignature: Ubuntu 2.6.31-20.58-generic Uname: Linux 2.6.31-20-generic i686 Architecture: i386 Date: Sat May 8 20:37:53 2010 ErrorMessage: ErrorMessage: package seamonkey-browser is already installed and configured SourcePackage: dpkg Title: package seamonkey-browser 1.1.17+nobinonly-0ubuntu1 [modified: usr/share/seamonkey/chrome/installed-chrome.txt] failed to install/upgrade: ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- package seamonkey-browser 1.1.17 nobinonly-0ubuntu1 [modified: usr/share/seamonkey/chrome/installed-chrome.txt] failed to install/upgrade: https://bugs.launchpad.net/bugs/577601 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577601] Re: package seamonkey-browser 1.1.17 nobinonly-0ubuntu1 [modified: usr/share/seamonkey/chrome/installed-chrome.txt] failed to install/upgrade:
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/48085875/Dependencies.txt ** Attachment added: VarLogDistupgradeAptlog.gz http://launchpadlibrarian.net/48085876/VarLogDistupgradeAptlog.gz ** Attachment added: VarLogDistupgradeApttermlog.gz http://launchpadlibrarian.net/48085877/VarLogDistupgradeApttermlog.gz ** Attachment added: VarLogDistupgradeLspcitxt.gz http://launchpadlibrarian.net/48085878/VarLogDistupgradeLspcitxt.gz ** Attachment added: VarLogDistupgradeMainlog.gz http://launchpadlibrarian.net/48085879/VarLogDistupgradeMainlog.gz ** Attachment added: VarLogDistupgradeSystemstatetargz.gz http://launchpadlibrarian.net/48085880/VarLogDistupgradeSystemstatetargz.gz ** Attachment added: VarLogDistupgradeTermlog.gz http://launchpadlibrarian.net/48085881/VarLogDistupgradeTermlog.gz -- package seamonkey-browser 1.1.17 nobinonly-0ubuntu1 [modified: usr/share/seamonkey/chrome/installed-chrome.txt] failed to install/upgrade: https://bugs.launchpad.net/bugs/577601 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577601] Re: package seamonkey-browser 1.1.17 nobinonly-0ubuntu1 [modified: usr/share/seamonkey/chrome/installed-chrome.txt] failed to install/upgrade:
Further investigation suggests some problem occurred with the download of the deb. Removing the cached version and redownloading fixed the problem. ** Changed in: dpkg (Ubuntu) Status: New = Invalid -- package seamonkey-browser 1.1.17 nobinonly-0ubuntu1 [modified: usr/share/seamonkey/chrome/installed-chrome.txt] failed to install/upgrade: https://bugs.launchpad.net/bugs/577601 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539350] Re: X does not behave properly with the -16 kernel in Lucid
I am also seeing it on my NC6400 as reported in #6 above. Running kernel -22 -- X does not behave properly with the -16 kernel in Lucid https://bugs.launchpad.net/bugs/539350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562138] Re: radeon KMS causes corrupt VGA output on X1400
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539350 reports similar issues -- radeon KMS causes corrupt VGA output on X1400 https://bugs.launchpad.net/bugs/562138 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539350] Re: X does not behave properly with the -16 kernel in Lucid
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/562138 reports similar issues -- X does not behave properly with the -16 kernel in Lucid https://bugs.launchpad.net/bugs/539350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576071] [NEW] After upgrade to Lucid /dev/disk/by-uuid missing when booting with initramfs
Public bug reported:
Upgraded from Karmic to Lucid with root=UUID= set in grub and using UUID in
/etc/fstab.
System fails to boot because the root device cannot be found.
From busybox shell determined /dev/disk/by-uuid missing.
Note behaviour is identical with grub and grub2
Further investigation suggests problem is with udev and initramfs interaction.
udev's 60-persistent-storage.rules amongst others contains the line
KERNEL!=sr*, IMPORT{program}=/sbin/blkid -o udev -p $tempnode
with an explicit path for blkid
This is used to populate udev's db which the rule
ENV{ID_FS_USAGE}==filesystem|other|crypto, ENV{ID_FS_UUID_ENC}==?*,
SYMLINK+=disk/by-uuid/$env{ID_FS_UUID_ENC}
uses to create the /dev/disk/by-uuid links,
However initramfs (in the file /usr/share/initramfs-tools/hooks/udev) copies
/sbin/blkid from the host system to /lib/udev in the initramfs image. The net
result is that it appears (at least from the busybox environment) that blkid
cannot be found and hence does not run.
Several other posts (ubuntu forums) suggest various workarounds (e.g.
going back to /dev/sda1 type root= lines in grub) but this is purely
masking the problem not solving it.
All other program references in udev (eg.ata_id usb_id and I guess the
old vol_id that preceded blkid) did not have an explicit path. Replacing
the references to /sbin/blkid to simple blkid in udev rules and
recreating initramfs via update-initramfs -u appears to fix the problem
and the system boots OK. However I am concerned that there may be other
reasons why the /sbin reference was included and hence if this was
introduced as a patch may break some other aspect I am unaware of.
Current environment:
udev 151-12
kernel 2.6.32-22-generic
initramfs-tools 0.93.2~bpo50+2
initramfs-tools-bin 0.92bubuntu78
distro Ubuntu 10.04 LTS
grub-pc 1.98-1ubuntu6
** Affects: ubuntu
Importance: Undecided
Status: New
--
After upgrade to Lucid /dev/disk/by-uuid missing when booting with initramfs
https://bugs.launchpad.net/bugs/576071
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388221] Re: python-rrdtool is almost empty
I have been looking at this too the last couple of days. What environment was that tested with? I have tried your patch with a vanilla karmic but with the same result - i.e. the bindings are not built. The problem is that parseversions doesnt exist in /usr/share/python- support/private/ so PY_VERS computes to a null string. The issue has been fixed in the upstream Debian version 1.38 already using. PY_VERS := $(shell pyversions -vr) However their version still has dependencies on python 2.6 (which Karmic installs). There is another Debian bug fix (sorry I dont have the # to hand) which addresses this aspect but I have yet to try incorporating that. -- python-rrdtool is almost empty https://bugs.launchpad.net/bugs/388221 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 361991] Re: Sent items are not getting created / Outbox not flushed
I have done a bit more work on this and it appears that the To: field in the email is left blank because a call to exhange_mapi_util_modify_recpients fails returning with MAPI_E_CALL_FAILED(0x80004005) and submitting the message ecInvalidRecips(0x467). This appears to be only a problem for recipients within the email domain - not external recipients. That seems to work. I have tried describing the local recipients email in different ways (fully qualified, local name, excluding the domain suffix etc) but with no success. I havent been able to get my Global Address List working (setting the correct source appears to do nothing) so this may have some influence on the problem. Perhaps you can check if you are seeing the same symptoms. -- Sent items are not getting created / Outbox not flushed https://bugs.launchpad.net/bugs/361991 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 361991] Re: Sent items are not getting created / Outbox not flushed
Not sure if this is the same bug but I'm seeing the Outbox not getting flushed and then ANY future attempts to read mail (e.g. deleting or retrieving mail content from the server) using evolution fail. However it does appear that the mail is sent to the recipient. Launching MS's outlook client shows the mail still being stuck in the Outbox on the exchange server. All attempts to clear it fail - the only recourse being to delete it using MS Outlook. Attempts to restart evolution (unless you leave it for a period of time - 20 mins or so - leave you with the same problem. Currently it renders the plugin useless for production use. I have the debug version 0.26.01 installed so could grab logs if that helps. -- Sent items are not getting created / Outbox not flushed https://bugs.launchpad.net/bugs/361991 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 44676] Re: cannot allocate memory
Its not a compiler issue - the duplicate errors come from confdefs.h Explicit tests are done earlier in configure and these add #define uint32_t unsigned #define uint16_t unsigned short #define uint8_t unsigned char but not sure why they were added in preference to #including stdint.h in the appropriate place(s) Resolving this aspect is the correct way to fix the problem -- cannot allocate memory https://bugs.launchpad.net/bugs/44676 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 44676] Re: cannot allocate memory
Further investigation shows it is an out of date (well inappropriate for the current Ubuntu) configure script. Although the configure.in is present with the source code the build system isnt recreating configure but using the existing one instead. In passing I note that configure.in is using deprecated macros -e.g AC_CHECK_TYPE(uint8_t, unsigned char) rather than AC_TYPE_UINT8_T (See http://www.delorie.com/gnu/docs/autoconf/autoconf_154.html) For Ubuntu you can get round these problems by rebuilding configure and then recreating the package. There may be a way you can force this with apt automatically but the steps to rebuild configure manually are: download the source and dependencies using apt-get build-dep afbackup apt-get source afbackup Unpack the source and cd into the directory and delete configure (and config.cache and config.setup if present). run autoconf Autoconf spots the old macros and either replaces them (or uses them as is) but at least generates a better code fragment. You can then rebuild the package. The steps are: from the parent directory apt-get -b source afbackup (or if you prefer dpkg-buildpackage -rfakeroot -uc -b from within the directory) Then install it with dpkg -i afbackup_3.5.1pl2-3_amd64.deb I will pass these observations upstream to the authors of afbackup as they may wish to re-publish configure or change the macros. Equally they may wish to change the way the code handles the error condition that gave the out of memory error. Dave -- cannot allocate memory https://bugs.launchpad.net/bugs/44676 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 44676] Re: cannot allocate memory
Ive not tried building on 8.10 (I might try it as I have a server
already built with Intrepid on)
Having said that the problem is caused at run time by a failure in
get_hostnamestr() in inetutils.c which is meant to return a string.
There is a section in the definition starting #ifdef HAVE_IP6 which is missing
from the compiled code because HAVE_IP6 is not defined properly on some
platforms (see next para).
The net result an else clause gets executed resulting in the function returning
NULL.
This is used in server.c main() around line 4060 where there is function call :
EM__(remotehost = get_connected_peername(commrfd))
which indirectly calls get_hostnamestr()
The EM__ macro mis-interprets the remotehost=NULL response and misleadingly
reports an Out of Memory error.
This should be improved - the macro shouldnt be used in this context.
Having said that the issue is actually triggered by the HAVE_IP6.
On my 64 bit Hardy system strace shows that the getpeername() library call is
as follows:
getpeername(sa_family=AF_INET6, sin6_port=htons(55263), inet_pton(AF_INET6,
:::127.0.1.1, sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, [28]) = 0
As you can see it is using AF_INET6 family. This is what the missing piece of
code mentioned above is meant to deal with.
Why is HAVE_IP6 not defined?
Because when built configure fails to detect ipv6 running. It fails with
configure:5450: cc -o conftest -g -O2 -g -Wall -O2 -Wl,-Bsymbolic-functions
conftest.c -lpthread 15
configure: In function 'sigh':
configure:5441: warning: implicit declaration of function 'exit'
configure:5441: warning: incompatible implicit declaration of built-in function
'exit'
configure: In function 'main':
configure:5446: warning: implicit declaration of function 'getmntent'
configure:5532: checking for IPv6 implementation
configure:5546: cc -o conftest -g -O2 -g -Wall -O2 -Wl,-Bsymbolic-functions
conftest.c -lpthread 15
In file included from /usr/include/netinet/in.h:24,
from configure:5539:
/usr/include/stdint.h:49: error: duplicate 'unsigned'
/usr/include/stdint.h:49: error: two or more data types in declaration
specifiers
/usr/include/stdint.h:50: error: duplicate 'unsigned'
/usr/include/stdint.h:50: error: duplicate 'short'
/usr/include/stdint.h:52: error: duplicate 'unsigned'
configure: In function 'main':
configure:5542: warning: unused variable 'sock6'
configure:5542: warning: unused variable 'in6'
configure: failed program was:
#line 5537 configure
#include confdefs.h
#include netinet/in.h
int main() {
struct in6_addr in6; struct sockaddr_in6 sock6;
; return 0; }
This has nothing to do with the ipv6 test being performed but due (my guess) to
a compiler issue (It is using gcc 4.2.3)
Strangely compiling the same code outside configure on the command line DOESNT
generate the same error.
I'm not sure how we fix it properly. Maybe someone else knows the answer
to that
As a quick interim fix you could switch of ipv6 on your PC (a little
severe). That would avoid the system going through the bad piece of
code.
I've temporarily fixed it by tweaking configure always to set
ac_cv_struct_in6_addr=yes
whether or not the test fails and rebuilding the binary. This is a horrid
workaround hack for my system only where I know ipv6 is running.
Hope that helps!
--
cannot allocate memory
https://bugs.launchpad.net/bugs/44676
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154525] Re: distribution upgrade continues to be an option after upgrade
I can confirm again on 2 separate systems. On one system update-manager kept crashing due to running out of apt cache space (i had a couple of extra sources in sources.list) irrespective of what I tried to change the settings to. Had to delete the extra sources and complete this on the command line using dist-upgrade etc. On the other it went OK but both systems now repeatedly offer the upgrade and fail with an error Your system is up to date -- distribution upgrade continues to be an option after upgrade https://bugs.launchpad.net/bugs/154525 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136469] Re: toshiba p100 series dsdt acpi error no sound, works with acpi turned off.
apt-get install linux-ubuntu-modules-2.6.22-14-386 fixed it for me. -- toshiba p100 series dsdt acpi error no sound, works with acpi turned off. https://bugs.launchpad.net/bugs/136469 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
