Public bug reported:
I tried to install but it says will not boot because ofgrub
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubiquity 17.04.9
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
It also affects me, i'm using fresh 13.10 with XMir server and 3.11
kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241180
Title:
Oversized "copy&paste" dialog in calculator
To manage notifi
Any progress on patching this on Precise?
Robert was pinged about this back on 9/12 since it wasn't ready before
12.04.1 but could be patched now. I've seen no update/response since...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
On my Lenovo IdeaPad Y550 with GeForce GT240M I can't get nvidia
proprietary drivers to work. On kernel 2.6 everything works fine. On 3.x
- it doesn't work. Google says nothing, askubuntu and #ubuntu on irc
says nothing. I don't have an Optimus.
ProblemType: Bug
DistroRelease
I'm not the reporter but I am a daily user of DRBD on precise.
If someone is running the old kernel then they should use the matching older
version of drbd8-utils.
So if the module in the kernel is 8.3.11 then the tools should be also or if
the module is 8.3.13 then the tools should be 8.3.13 al
Any chance of a patch to at least quiet this down? Or some additional
info we can provide to try to fix the problem??
These are writing to log every 15 seconds:
Dec 25 23:25:27 Condor snmpd[3908]: netsnmp_assert 1 == new_val->high failed
int64.c:419 netsnmp_c64_check32_and_update()
Dec 25 23:25
This is a known bug in Pacemaker version 1.1.6
I understand that with the LTS release there may be no hope of getting
the package upgraded to 1.1.7 but we should at least be able to get this
bug fixed I would hope.
Patch to fix this is here:
https://github.com/beekhof/pacemaker/commit/2bdb230
Ou
No log files available - known issue that was patched in 8.3.13 as noted
in comment #3 above.
Especially important since the new default scheduler of cfq in Precise
is known to cause the bug.
** Changed in: drbd8 (Ubuntu)
Status: Triaged => Confirmed
** Changed in: linux (Ubuntu)
S
Just for the record and if anyone wants to check on it.
Upstream bug submitted:
http://sourceforge.net/tracker/?func=detail&aid=3536008&group_id=312875&atid=1316824#
** Bug watch added: SourceForge.net Tracker #3536008
http://sourceforge.net/support/tracker.php?aid=3536008
--
You received th
I will look into it this week and respond accordingly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010625
Title:
named logs are not being reported in logwatch
To manage notifications about this b
I will give it a whirl... not sure the exact (best) steps but I assume:
Submit a bug against Logwatch at SourceForge.net
Follow/answer questions there as needed.
If it gets patched then would I need to try to get Debian to pickup the
patch before Ubuntu would consider an SRU to 12.04?
--
You re
Public bug reported:
After upgrading from 10.04 to 12.04 named logs no longer show up in logwatch
reports.
Not sure if this should be filed as a bug against rsyslog or logwatch.
There was a change to /etc/rsyslog.d/50-default.conf between 10.04 and
12.04 and a bunch of the seperate log files a
Here is the source commit that changed the samba.conf. The reason listed was:
"samba.conf patch to deal with cores dir -mgt"
I have no idea what that means honestly but maybe it would be of help to know...
http://logwatch.svn.sourceforge.net/viewvc/logwatch?view=revision&revision=5
--
You recei
** Attachment added: "Fix to revert back to prior working settings"
https://bugs.launchpad.net/bugs/1010602/+attachment/3181066/+files/samba.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/101060
Public bug reported:
After upgrading from 10.04 to 12.04 samba logs no longer show up in
logwatch reports.
There was a change to /usr/share/logwatch/default.conf/logfiles/samba.conf
between 10.04 and 12.04:
LogFile=samba/* was changed to LogFile=samba/*.log
In the samba package the default s
Hans - The patch is awaiting verification testing. I was unable to test
the proposed fix since I had mitigated the bug already on my servers by
the time it was available.
Looks like tmortensen has tested it so I would expect you to see the
patch available soon!
--
You received this bug notifica
** Changed in: drbd8 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000355
Title:
drbd fence-peer breaks when using kernel 2.6.32-41
To manage notifications
** Description changed:
Ubuntu 10.04 Lucid with 2.6.32-41 kernel and drbd8
Kernel 2.6.32-41 fixed a consistency issue around UMH_WAIT_PROC in this
bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/963685
This causes the drbd fencing script's exit codes to be incorrectly
Unfortunately unable to collect such log files due to the nature of the
bug and changes since to bring systems back to working order.
I might have further info I could give - if there are specific questions
I will try to answer.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
Public bug reported:
Ubuntu 10.04 Lucid with 2.6.32-41 kernel and drbd8
Kernel 2.6.32-41 fixed a consistency issue around UMH_WAIT_PROC in this
bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/963685
This causes the drbd fencing script's exit codes to be incorrectly
interpreted which t
It isn't fixed in Ubuntu but it has been patched in Debian.
Patched version is 2.1.4.18393-0.ds2-7
Not sure how we get someone to try get this in as an SRU patch since it
prevents anyone from removing or upgrading firebird2.1.
I manually applied the fix mentioned in the Debian bug
http://bugs.deb
I was finally able to get the half upgraded system fixed using the
proposed package.
After that was running for a bit I went ahead and upgraded another server in my
cluster running the same services.
I used the proposed libsasl2-2 package and the upgrade completed start to
finish without a hiccu
Cannot upgrade from firebird2.1-super to firebird2.5-super on 12.04 due
to this:
root@server:~# apt-get install firebird2.5-super
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
firebird2.5-server-common lib
I (mostly) figured out how to do-release-upgrade using proposed repo
with some help from the Ubuntu-HA group.
However I believe proposed is missing the second fix needed - the no
change rebuild of openldap?
Still getting errors:
Traceback (most recent call last):
File "/usr/bin/apt-listchanges
I have my server in that state now unfortunately so I should be able to
test.
How would I tested proposed while trying to do-release-upgrade?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/990742
Titl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994837
Title:
package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade:
ErrorMessage: subprocess new pre-installation script returned error
exit sta
Public bug reported:
Upgrading from 10.04 LTS to 12.04 LTS. Upgrade failed after slapd
failed to install.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: slapd 2.4.21-0ubuntu5.7
ProcVersionSignature: Ubuntu 2.6.32-40.87-server 2.6.32.57+drm33.23
Uname: Linux 2.6.32-40-server x86_64
Arc
** Description changed:
Description:Ubuntu 10.04.3 LTS
Release:10.04
Step 5 of the Samba and LDAP section of the Server Guide (in Network
- Authentication) shows the old way (incorrect) which doesn't work. Also
- the line after describing what it should look like when complet
Public bug reported:
Description:Ubuntu 10.04.3 LTS
Release:10.04
Step 5 of the Samba and LDAP section of the Server Guide (in Network
Authentication) shows the old way (incorrect) which doesn't work. Also
the line after describing what it should look like when complete has the
wrong
Not sure these symptoms would be the same on the later versions but on
Lucid I also encountered the following due to this bug:
service corosync stop - never completes. Hangs waiting for crmd to shutdown
(over 6 hours without a change)
crm ra info ocf:xx:xx - hangs the crm shell
crm configure pri
I have tested this a couple times a week since the fix was proposed and I have
had no ill effects and it has fixed the problem.
Hopefully we can get this update out to all!
If there is any other info I can provide please let me know.
** Tags removed: verification-needed
** Tags added: verificati
Henning
You are probably right that this isn't the right place to continue with
non-bug questions though Andres or others could answer that more
acurately.
I would recommend drbd-users mailing list as there are many experts
there for config and troubleshooting. Also the pacemaker mailing lists
i
Still working good - no issues. I've changed/rebooted both nodes and it
takes snapshots, re-syncs, then removes snapshots (at least 30 times
since applying the patch) without a hitch.
Thanks again for your help!
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Have an updated patch that returns properly when Arpwatch isn't running.
Will upload soon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/806145
Title:
Lacks a status action in the init script
To man
Thanks Adam/Andres
I've got to remember: Google first, ask second - always not just mostly!
I'll report in again in about a week on this. I am doing a lot of
reconfig, add resources, testing, and failing of my pacemaker cluster so
I will report on how the snapshot patch holds up. It *should* get
Ok looks good. No zombie processes. I updated and restarted node 1 -
drbd initiated snapsho on startup, synced properly (wouldn't get that
far before) and then removed them. After doing that on node 1 I updated
and restarted node 2 (causing everything to fail to node 1) and
everything moved and
I know how it might not look like a Pacemaker problem but I believe it
is. Pacemaker is in charge of everything. As I put in the comment
before I believe this line disallows Drbd2 to be master on node 2:
location locDrbd2Master msDrbd2 rule role=master inf: #uname eq node1
Since everything else
Thanks Adam - thought that was weird.
Only update available was drbd8-source after adding your ppa.
Maybe because I use amd64 builds? I noticed it says need to be built next to
those in your ppa.
I'll check again in the morning.
--
You received this bug notification because you are a member of
Still the same thing - zombie processes for lvm snapshots with 100% cpu.
Script still doesn't have the changes in the patch applied - still looks
identical as my post #8.
root@Vulture:~# apt-cache policy drbd8-source
drbd8-source:
Installed: 2:8.3.7-1ubuntu2.3
Candidate: 2:8.3.7-1ubuntu2.3
Found an error in my patch that was causing the incorrect output - not a
problem with init-functions.
** Changed in: lsb (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Andres - have you had a chance to review my last update?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/744293
Title:
Infinite loop in helper LVM script for DRBD 8 in Lucid
To manage notifications a
Anyone have any thoughts?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/806677
Title:
status_of_proc returns incorrect number
To manage notifications about this bug go to:
https://bugs.launchpad.ne
Hi Andres,
So I gave it a try and now I'm racking my brain because I thought I knew
what I was doing but it didn't behave as I expected and I don't know if
it's my ignorance or a problem so I'll let you be the judge!
Executed the following on both nodes, one after the other finished:
Added your P
I tried some further testing and comparison today:
I looked through the init script for NTP and how it calls status_of_proc
and my patch for Arpwatch looks identical. However if ntp is not running
and you execute /etc/init.d/ntp status; echo "return $?" you get return
3 which is the proper respons
Maybe someone else could take a look at the return code issue.
I looked through the init script for NTP and how it calls status_of_proc and
mine is identical. However if ntp is not running and you execute
/etc/init.d/ntp status; echo "return $?" you get return 3 which is the proper
response pe
Whoops! I put them backwards too!
"In this ordering statement I think you meant to put before not after...
:-)
order ordDlm-before-msDrbdMaster2 0: msDrbd2:promote cloneDlm"
I meant it should be "after" not "before"!
--
You received this bug notification because you are a member of Ubuntu
You have a location constraint for msDrbd2 that requires it to be master
on node 1 only. I would assume it's leftover from your master/slave
setup:
location locDrbd2Master msDrbd2 rule role=master inf: #uname eq node1
I would remove that and see what happens. Also a few other things:
In ord
Public bug reported:
I was patching the init script for Arpwatch so that it would be LSB
compliant (adding status) and came across this issue. I believe it
differs from the similarly named bug with code 3/4 problems.
Arpwatch not running. Using the status_of_proc function. Return code
is 0. A
Patch to implement status_of_proc() LSB init Function.
Everything works as defined in LSB standard with the exception of the
return code of status when daemon is not running. It is reported
incorrectly as 0 instead of 3. I believe this is because of a bug in
/lib/lsb/init-functions in the pidofp
Not to be a pain but any update on this? If it is put to SRU Proposed I
would gladly test it.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/744293
Title:
Infinite loop in helper LVM script
** Patch added: "Patch to fix spelling"
https://bugs.launchpad.net/ubuntu/+source/arpwatch/+bug/806177/+attachment/2193134/+files/LP806177.patch
** Changed in: arpwatch (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Public bug reported:
In init.d/arpwatch - misspelling of arpwatch on line 14
1) Description: Ubuntu 10.04.2 LTS
Release: 10.04
2) Installed: 2.1a15-1.1
Candidate: 2.1a15-1.1
Version table:
*** 2.1a15-1.1 0
500 http://us.archive.ubuntu.com/ubuntu/ lucid/universe Packages
Public bug reported:
Arpwatch is not LSB compliant since it lacks a status action in its'
init script.
1) Description:Ubuntu 10.04.2 LTS
Release:10.04
2) Installed: 2.1a15-1.1
Candidate: 2.1a15-1.1
Version table:
*** 2.1a15-1.1 0
500 http://us.archive.ubunt
Andres,
There hasn't been any activity (that I can see) on this since you
submitted the SRU. Do you have any further info or idea when this would
be mainstream available for 10.04?
Or would you be willing to put up a patched package on the Ubuntu-HA PPA
for Lucid?
Thanks!
--
You received this
Excellent!
Thank you Andres
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/744293
Title:
Infinite loop in helper LVM script for DRBD 8 in Lucid
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
Public bug reported:
Bug is related to the Launchpad bug system.
What happens:
Bug is reported such as bug 744293. There are subscribers listed for the bug
who are notified and below that on the bug page there are "Also Notified"
ppl/groups. Using the bug I listed as an example I would assume
Andres,
This is a real pain for those of us who would like to ensure that we
don't lose data due to a failure during re-sync. If we don't take a
snapshot prior to a re-sync of the secondary and there was a failure it
could be catastrophic. I'm pretty sure Lars put out a patch which is
mentioned
Andres,
Good point - I actually don't even have redhat-cluster installed...
What led me to this bug report is following the Pacemaker, DRBD8, and OCFS2
test case in the wiki from Ubuntu-HA and other info online. I encountered the
segfault problem and did a little digging to come across this bug
Great!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571612
Title:
dlm_controld.pcmk segfault
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubu
Any update on this? It's been 8 months since found and reported. Any
info would be great as it is a real pain!
Anyone who uses link aggregation (me), bridging, and vlans are affect
due to the time required to bring up the network after reboot. Corosync
comes up and dlm segfaults (something to d
Or maybe I read it wrong and the code window has the typo and should be
"security = share" depending upon how the doc is targeted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/684194
Title:
Samba P
Public bug reported:
Binary package hint: ubuntu-docs
In the Official Doc's under Samba Print Server there is a typo.
https://help.ubuntu.com/10.04/serverguide/C/samba-printserver.html
In the Configuration section it says to "change security to share: "
It should say "change security to user"
Thanks!
--
Cannot start guest when apparmor is running
https://bugs.launchpad.net/bugs/490370
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/list
Whoops that isn't correct - thats not where my XML resides. And I
figured out what it is.
I was trying to get auto-connect USB recognition to work (back when it
was 9.04) and the instructions here (http://david.wragg.org/blog/2009/03
/usb-pass-through-with-libvirt-and-kvm.html) said to make this
That is where the XML definitions resides on my system...
r...@it02:/home/jsmith# ls /etc/libvirt/
libvirtd.conf qemu qemu.conf storage
r...@it02:/home/jsmith# ls /etc/libvirt/qemu
autostart KarmicBeta1.xml kvm networks winXPpro.xml
r...@it02:/home/jsmith#
A bit of history (and maybe my
No files in /var/log/apparmor/
Entry in kern.log:
(Repeats everytime I tried to start guest - pid/parent varied but the rest is
identical - if more are needed let me know)
Nov 30 10:11:12 IT02 kernel: [ 405.887561] type=1503
audit(1259593872.142:29): operation="exec" pid=2402 parent=1933
profil
Host:
Linux IT02 2.6.31-14-server #48-Ubuntu SMP Fri Oct 16 15:07:34 UTC 2009
x86_64 GNU/Linux
Package versions:
libvirt-bin 0.7.0-1ubuntu13.1
libvirt0 0.7.0-1ubuntu13.1
python-libvirt 0.7.0-1ubuntu13.1
pytho
** Attachment added: "Guest XML definition file"
http://launchpadlibrarian.net/36260352/winXPpro.xml
--
Cannot start guest when apparmor is running
https://bugs.launchpad.net/bugs/490370
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When I try to start a Windows XP virtual machine (kvm) it fails with the
following error:
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 493, in run_domain
vm.startup()
File "/usr/share/virt-manager/virtManager/domain.py"
Public bug reported:
Binary package hint: xdg-utils
Attempting to launch a file URL with a query string attached fails using
xdg-open (calls gnome-open on my system). I can successfully launch
with an anchor tag but not query string. If you try to launch directly
with firefox it is successful.
Jean-Philippe Fleury - give this version of Alberto Milone's workaround
a try - I also had nvidia-common already installed but this worked for
me!
Alberto Milone - Thank you, your workaround worked for me with this
slight modification:
I already had nvidia-common and the nvidia-xxx-modaliases pac
Found syntactical error:
force group = +group-name should be
force group = group-name
No problem any longer. I hope that no one had spent much time as of yet.
** Changed in: samba (Ubuntu)
Status: New => Invalid
--
force group breaks share
https://bugs.launchpad.net/bugs/269627
You rec
Attachment is the error message received in WinXP.
--
force group breaks share
https://bugs.launchpad.net/bugs/269627
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
** Attachment added: "err1.jpg"
http://launchpadlibrarian.net/17568803/err1.jpg
--
force group breaks share
https://bugs.launchpad.net/bugs/269627
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
Public bug reported:
Binary package hint: samba
When you have 'force group = xxx' you receive "Network path not found"
error in a WinXP client trying to access share that contains the force
group directive.
Description:Ubuntu 8.04.1 Release:8.04
samba:
Installed: 3.0.28a-1ubuntu4.
I can confirm as well. The (upstream?) package is currently at 0.9.5
with that problem patched. (https://gna.org/projects/smbldap-tools/)
Any idea how long until that version would be packaged and available via
universe sources?
--
smbldap-passwd failed to modify unix password: shadowMax
https:/
76 matches
Mail list logo