Public bug reported:
I was installing mythtv and mythbuntu from synaptices, then Mysql asked
a new root password when installing and chrashed.
1)I am using ubuntu 9.10
2)I don't know :(
3)I excepted that the enter new password window dissappear but
4) it crashed.
ProblemType: Package
** Attachment added: .etc.apparmor.d.usr.sbin.mysqld.txt
http://launchpadlibrarian.net/38629995/.etc.apparmor.d.usr.sbin.mysqld.txt
** Attachment added: AptOrdering.txt
http://launchpadlibrarian.net/38629996/AptOrdering.txt
** Attachment added: Dependencies.txt
I meant ubuntu 9.10 not 6.10 :o
** Description changed:
I was installing mythtv and mythbuntu from synaptices, then Mysql asked
a new root password when installing and chrashed.
- 1)I am using ubuntu 6.10
+ 1)I am using ubuntu 9.10
2)I don't know :(
- 3)I excepted that the enter new
OK I found the edit button...
--
Mysql asked new root password when installing and chrashed
https://bugs.launchpad.net/bugs/515661
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
--
Ubuntu-server-bugs mailing
Public bug reported:
Binary package hint: qemu-kvm
I have a Core 2 Duo E6550 which is physically 64-bit capable. When I run this
on 32-bit Ubuntu 10.04:
$ qemu-system-x86_64 -cdrom ubuntu-10.04-desktop-amd64.iso
I got the following message:
This kernel requires an x86-64 CPU, but only detected
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/47985103/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/47985104/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/47985105/Dependencies.txt
**
thx soren! it worked like a charm :)
--
qemu-system-x86_64 doesn't emulate 64bit CPU
https://bugs.launchpad.net/bugs/576856
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
Public bug reported:
Ubuntu Precise currently ships with dnsmasq 2.59, but due to the issue
reported in https://lists.launchpad.net/openstack/msg11696.html we
require that to be updated in Precise to at least 2.61. I see that
Quantal already has 2.63. Please backport this update for Precise!
**
How about this year? ;-) Has the broken udev rule been removed from
kpartx yet? It would be nice to have this resolved for Ubuntu 13.04.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
Ok, so to fix this problem follow these steps (assuming you are using
Ubuntu 11.04):
1. Modify this line in /lib/udev/rules.d/95-kpartx.rules
ENV{DM_STATE}==ACTIVE, ENV{DM_UUID}==dmraid-*, \
RUN+=/sbin/kpartx -p -part -a /dev/$kernel
by changing dmraid-* to DMRAID-* and
What is the status on this bug?
I recently clean installed Ubuntu 12.04 and had no problems mounting the
disks, so the steps in Post #15 are no longer necessary, at least for
Intel Matrix Raid. Looking at the kpartx udev rule in 12.04, the file
appears unchanged, but the kpartx-activate script
I am willing to test any changes that might help resolve this problem.
Just point me to the code.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/737027
Title:
kpartx udev
Yes, I am also wondering whether or not this will be resolved for 11.10.
I can upload the patch, but I first need to know the switch to tell
dmraid not to create the partitions that Phillip mentioned in comment
#9. I could not find such a switch in the dmraid man file.
--
You received this bug
Let me try and test this
--
Copying files to Windows Vista causes 'Invalid Parameter'
https://bugs.launchpad.net/bugs/108496
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
We can mark as fix release correct for the Ubuntu doc side of things?
THanks,
Jonathan
--
Ubuntu Server Guide Not Installed On Servers
https://bugs.launchpad.net/bugs/45944
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
--
in kubuntu 8.04.1 i have no problems browsing samba shares through
konqueror. either server 2003, xp, or vista shares. is it a nautilus
bug?
--
unable to connect to windows network pc's
https://bugs.launchpad.net/bugs/252245
You received this bug notification because you are a member of Ubuntu
@james-page We're testing your upstart openvswitch-switch.conf file on
Precise. It's looking good so far. Can this bug be marked as relevant
for Precise too, please? Once it's in Saucy we'd definitely like to see
it backported to Precise.
--
You received this bug notification because you are a
** Changed in: openvswitch (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1233703
Title:
openvswitch-datapath-dkms fails to build
** Branch linked: lp:~waigani/juju-core/lxc-trusty-autostart
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1271941
Title:
lxc container creation fails on trusty host service
I am unable to replicate this bug in either Intrepid or Jaunty. However
both of these are running KDE4. I don't know if it is specific to KDE3
vs. KDE4?
Jonathan
--
kubuntu intrepid 8.10: kde3 aps can not browse smb:// locations
https://bugs.launchpad.net/bugs/331576
You received this bug
I tested the latest version from mercurial (which includes the patch)
and it resolves the issue.
--
minicom scripts never exit
https://bugs.launchpad.net/bugs/585911
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to minicom in ubuntu.
--
** Changed in: minicom (Ubuntu)
Status: Confirmed = Fix Committed
--
minicom scripts never exit
https://bugs.launchpad.net/bugs/585911
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to minicom in ubuntu.
--
Ubuntu-server-bugs
OK, sorry -- I thought Fix Committed meant a fix had been committed to
the upstream source.
--
minicom scripts never exit
https://bugs.launchpad.net/bugs/585911
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to minicom in ubuntu.
--
On a related issue, I noticed the remote bug watcher for
alioth.debian.org isn't working -- it looks like it is using the wrong
URL.
--
minicom scripts never exit
https://bugs.launchpad.net/bugs/585911
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I suppose the chance of this fix being released for lucid is pretty low?
--
minicom scripts never exit
https://bugs.launchpad.net/bugs/585911
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to minicom in ubuntu.
--
Ubuntu-server-bugs
I would certainly be willing to do this since I would like to see it
fixed in lucid, but I don't have rights to upload a package to lucid-
proposed (I'm not a package maintainer).
--
minicom scripts never exit
https://bugs.launchpad.net/bugs/585911
You received this bug notification because you
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/634388/+attachment/1562180/+files/Dependencies.txt
** Attachment added: SSHDConfig.txt
https://bugs.launchpad.net/bugs/634388/+attachment/1562181/+files/SSHDConfig.txt
--
/etc/init.d/ssh stop doesn't stop sshd
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
--
umount.cifs does not work on logout with libpam-mount
https://bugs.launchpad.net/bugs/578587
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Upon further investigation, this kernel bug causing the system to hang
only occurs with one of our samba shares. However, I'm still not sure
why it is occurring at all.
--
umount.cifs does not work on logout with libpam-mount
https://bugs.launchpad.net/bugs/578587
You received this bug
** Bug watch added: alioth.debian.org/ #312517
http://alioth.debian.org/support/tracker.php?aid=312517
** Also affects: minicom via
http://alioth.debian.org/support/tracker.php?aid=312517
Importance: Unknown
Status: Unknown
--
minicom scripts never exit
** Also affects: qemu-kvm
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
** Changed in: openstack-ansible/trunk
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1488815
Title:
Kernel traces with
** Changed in: openstack-ansible/kilo
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1488815
Title:
Kernel traces with
Cheryl just pointed out that each unit needs to have a unit agent status
doc and a workload (unit status) doc. So we can:
1 - generate a list of all the units
2 - query the status for each unit (not agent status)
3 - if it returns not found, then create the status
--
You received this bug
When targeting the upgrade step in 1.25 I cannot see a way to
distinguish between 1. a correct agent statusDoc and 2. a unit statusDoc
with a agent style id - as the id is the only distinguishing feature
between the two.
I imagine fwereade will hit this when writing the fix-it script.
pr: http://reviews.vapour.ws/r/3279
** Changed in: juju-core
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status
** Changed in: juju-core
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage notifications
Unprivileged LXC still fails to start here...
kernel: 4.4.0-9.24
lxc: 2.0.0~rc4-0ubuntu1
$ lxc-start -d -n i386-trusty-gui
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in
foreground mode.
lxc-start:
38 matches
Mail list logo
