** Attachment added: "apt.log"
http://launchpadlibrarian.net/48676071/apt.log
--
Could not install pacemaker
https://bugs.launchpad.net/bugs/580277
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
** Attachment added: "lspci.txt"
http://launchpadlibrarian.net/48676197/lspci.txt
--
Could not install pacemaker
https://bugs.launchpad.net/bugs/580277
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
** Attachment added: "apt-term.log"
http://launchpadlibrarian.net/48676203/apt-term.log
--
Could not install pacemaker
https://bugs.launchpad.net/bugs/580277
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
** Attachment added: "main.log"
http://launchpadlibrarian.net/48676214/main.log
--
Could not install pacemaker
https://bugs.launchpad.net/bugs/580277
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
** Attachment added: "system_state.tar.gz"
http://launchpadlibrarian.net/48676222/system_state.tar.gz
--
Could not install pacemaker
https://bugs.launchpad.net/bugs/580277
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
** Attachment added: "term.log"
http://launchpadlibrarian.net/48676230/term.log
--
Could not install pacemaker
https://bugs.launchpad.net/bugs/580277
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
** Attachment added: "xorg_fixup.log"
http://launchpadlibrarian.net/48676242/xorg_fixup.log
--
Could not install pacemaker
https://bugs.launchpad.net/bugs/580277
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Public bug reported:
Binary package hint: update-manager
Updating Kubuntu Karmic to Lucid; received error saying I could not
install pacemaker.
** Affects: update-manager (Ubuntu)
Importance: Undecided
Status: New
--
Could not install pacemaker
https://bugs.launchpad.net/bugs/580
I can confirm a hung qaptworker process when using Muon and Etckeeper
(git backend; don't know if that matters). My process list shows
Etckeeper trying to run its post install hooks:
root 21547 0.0 0.3 209940 12076 pts/1S+ 09:38 0:00
/usr/bin/qaptworker
root 21548 0.0 0.0 42
The 3.0 release candidate 4 kernel worked for me (from Mainline Kernel
Builds), as above. 9 hours so far, stable connection on Kubuntu 11.04,
connecting to a WPA2-PSK AP. I've got the Realtek 8191SE chipset in a
Toshiba Satellite A500. So this seems fixed for Oneiric. Going to try
drivers Realtek j
I received drivers from Realtek today that seem to fix this problem for
me. Stable connection so far without having to resort to the 3.0 kernel.
I posted the drivers here:
http://ubuntuforums.org/showpost.php?p=10989459&postcount=135
Go to page 14 of that thread for context, but it seems that the
@filsd: The latest Realtek drivers seem to do the trick. I posted the
driver package they sent me on page 14 of the forum thread William Ray
Yeager links to:
http://ubuntuforums.org/showthread.php?t=1267961&page=14
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Here's a potential solution: Realtek drivers from June 20, 2011, which
solved the issue for me. I attached the package they sent me over at
http://ubuntuforums.org/showthread.php?t=1267961&page=14
Hope this helps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Looks like you've got the same chipset as me. I was having all kinds of
problems with keeping my wireless connected when I went from Lucid to
Natty; I got the latest drivers from Realtek today and they seem to have
sorted me out. I've posted them over in the forums:
http://ubuntuforums.org/showthre
Same issue, same chipset. I e-mailed Realtek and got their latest
driver, which I posted here:
http://ubuntuforums.org/showthread.php?t=1267961&page=14
I also had luck with the 3.0 kernel, but I wanted to stay on the stock
Natty kernel rather than the RC4 3.0. Hope this helps.
--
You received th
Hi Ante,
I just tried to install pacemaker again, and it again chokes on the
warning:
Selecting previously deselected package libcorosync4.
(Reading database ... 251107 files and directories currently installed.)
Unpacking libcorosync4 (from .../libcorosync4_1.2.0-0ubuntu1_i386.deb) ...
Selecting
Possibly of interest: I only received this error when I upgraded my work
laptop from Karmic to Lucid. I don't have the option to do a clean
install of Lucid on that laptop. However, on my personal laptop, I did
do a clean install of Lucid Lynx. That clean install does not attempt to
install pacemak
u...@host:~$ sudo DPKG_DEBUG="developer" dpkg --configure -a
Setting up pacemaker (1.0.8+hg15494-2ubuntu2) ...
addgroup: The group `haclient' already exists as a system group. Exiting.
Warning: The home dir /var/lib/heartbeat you specified already exists.
adduser: The user `hacluster' already exist
u...@host:~$ sudo DEBCONF_DEBUG="developer" dpkg --configure -a
Setting up pacemaker (1.0.8+hg15494-2ubuntu2) ...
addgroup: The group `haclient' already exists as a system group. Exiting.
Warning: The home dir /var/lib/heartbeat you specified already exists.
adduser: The user `hacluster' already ex
u...@host:~$ sudo sh -x /var/lib/dpkg/info/pacemaker.postinst configure
+ set -e
+ addgroup --system haclient
addgroup: The group `haclient' already exists as a system group. Exiting.
+ adduser --system hacluster --ingroup haclient --home /var/lib/heartbeat
Warning: The home dir /var/lib/heartbeat
u...@host:~$ getent passwd hacluster
hacluster:x:1001:122:Heartbeat System Account:/usr/lib/heartbeat:/bin/false
--
Could not install pacemaker: addgroup: The group `haclient' already exists as a
system group. Exiting.
https://bugs.launchpad.net/bugs/580277
You received this bug notification bec
That did the trick. Thanks, Jean-Baptiste; I changed user UID to 128,
which was not currently being used (after a quick inspection of UIDs in
my passwd file) and pacemaker's installation was able to finish.
--
pacemaker fails to install/upgrade if the user hacluster already exists and is
not a s
22 matches
Mail list logo
