Ditto here for PJSingh5000. I had added a google account as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720400
Title:
/usr/bin/gnome-control-
center:11:update_buffers:image_get_buffers:
This issue occurs for Logitech Gaming Keyboard G110 as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717340
Title:
[artful] Keyboard Logitech G15 doesn't work after logging in to gnome
To ma
Having this problem with freeipa on xenial.
ii sssd-ipa 1.13.4-1ubuntu1.8
amd64System Security Services Daemon -- IPA back end
--- client side output ---
alvinc@ipa-client-02:~$ sudo systemctl restart autofs
[sudo] password for alvinc:
alvinc@ipa-client-02:~$ su
Perhaps you might find it in backports. Not sure what has been decided
with it, if it goes to updates or backports.
On Tue, Sep 20, 2016 at 6:34 AM, Ken Haase wrote:
> I can't quite tell from the report page on launchpad, but is this fix
> available in Trusty? Are there plans to make it availab
Post-reboot, "dpkg --configure -a" worked, and I am able to boot and run
the new kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557686
Title:
package linux-image-4.4.0-13-generic 4.4.0-13.29
Public bug reported:
During apt-get dist-upgrade, having already been updated to 16.04.
Current: 4.2.0-19-generic #23-Ubuntu SMP Wed Nov 11 11:39:30 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-13-generic 4.4.0-13.29
ProcVer
I am not seeing this problem on Hardy 8.04.3. Can anyone confirm/deny?
--
xen guest hangs after mounting filesystem
https://bugs.launchpad.net/bugs/144631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
Axel,
Please let me know how I can help.
- alvinc
--
xen-tools is not available in lucid
https://bugs.launchpad.net/bugs/538917
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
h
I notice that this bug has not received any attention.
It should be noted that I have not seen this bug in jaunty or karmic,
and do not recall if I saw it in hardy or intrepid.
--
no xm console prompt after debootstrap debian or ubuntu
https://bugs.launchpad.net/bugs/139046
You received this bug
I am seeing this issue in Karmic after an upgrade from Jaunty.
Could not create message.
Because "Cannot find certificat for '", you may need to
select different mail options."
Configuration is identical to the working one in Jaunty, except that my
certificate expired, and I replaced it.
--
Un
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/35190113/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/35190114/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/35190116/BootDmesg.txt
** Att
Public bug reported:
Dell Precision M65 Laptop
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be
restarted.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx
I'm very excited for this to be fixed in Hardy, as I have had quite a
bit of trouble with it.
I am perhaps not up-to-speed on things. But although I know that KVM is
now the preferred virtualization solution, due in part to ease-of-use at
the desktop, Xen still has a lot of usefulness at the serv
I was searching through bugs, and found this one un-updated.
I am no longer seeing these errors under Hardy 8.04.1 and its xen
kernel. Is the right thing to do in this case to do an SRU for Gutsy?
The kernel team needs to do this one, correct?
- alvinc
--
Gutsy xen-3.1/kernel-2.6.22 dom0 kerne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It would be my honour to work on the SRU of this bug. Alas, I
have not looked at it in a while, and it will take me a little bit of
time to review the documentation which Emmet referred me to at the
beginning.
I expect to look at it this weekend (US
*** This bug is a duplicate of bug 215036 ***
https://bugs.launchpad.net/bugs/215036
Removing ~/.mythtv/themecache solved the problem.
--
mythfrontend.real crashed with SIGSEGV in MythThemedMenuPrivate::keyHandler()
https://bugs.launchpad.net/bugs/216174
You received this bug notification be
Thank you Henrik!
I will read the SRU process.
- alvinc
--
/etc/init.d/iscsitarget broken with migration to /bin/dash
https://bugs.launchpad.net/bugs/160106
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
I think marking status as "Confirmed" may have been a mistake on my
part? Have these diffs been reviewed?
Cheers,
- alvinc
** Changed in: iscsitarget (Ubuntu)
Status: Confirmed => In Progress
--
/etc/init.d/iscsitarget broken with migration to /bin/dash
https://bugs.launchpad.net/bugs/
Hi Emmet!
Bug #160104 is the kernel module bug. This one is the bug that the
initscript in Debian is written for /bin/bash, whereas the diff which I
added includes a script which is Bourne Shell virgin, and runs under
/bin/dash.
--
/etc/init.d/iscsitarget broken with migration to /bin/dash
http
Attached is the diff with fixes for Hardy (on version 0.4.15-5, sync'd
from Debian)
** Attachment added: "Fix for 0.4.15-5 on hardy"
http://launchpadlibrarian.net/10681080/iscsitarget_0.4.15-6.diff.gz
--
/etc/init.d/iscsitarget broken with migration to /bin/dash
https://bugs.launchpad.net/bu
Confirmed that this issue still occurs in Hardy at version 0.4.15-5.
** Changed in: iscsitarget (Ubuntu)
Status: In Progress => Confirmed
--
/etc/init.d/iscsitarget broken with migration to /bin/dash
https://bugs.launchpad.net/bugs/160106
You received this bug notification because you are
Fixes are attached.
Fixes for Bug #160106 are included in the diff. I put in a control
structure to check for kernel version as well.
Cheers,
- alvinc
** Attachment added: "iscsitarget_0.4.15-3.diff.gz"
http://launchpadlibrarian.net/10597545/iscsitarget_0.4.15-3.diff.gz
--
iscsitarget ker
Fixes are attached.
Fixes for Bug #160104 are included in the diff.
Hopefully I've become proficient enough at pbuilder and debuild that the
data is in the proper format now. :)
Cheers,
- alvinc
** Attachment added: "iscsitarget_0.4.15-3.diff.gz"
http://launchpadlibrarian.net/10597577/iscs
Hi Brendan,
Further up in this bug, I attached a diff of event.c. Changing line
98 of event.c in accordance with the diff will do the trick.
This will be fixed in the future, I'm working that out now (learning
pbuilder and experimenting with doing things properly). But if you're
in patient, you
My second test did not fare so well. Even with sysvinit, there seems to
be a race condition with samba.
I believe the right course it to put logic into the startup script to
wait for the network. In my first test case, spanning-tree portfast was
set on the switch in question, which leads to fast
Confirmed that replacing upstart with sysvinit eliminates the problem.
This is no fix, but it does seem to point at upstart.
HOST INFO:
# uname -a
Linux mpk-acura1 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686
GNU/Linux
[EMAIL PROTECTED]:/var/log/apt# cat /etc/issue
Ubuntu 7.10 \n \l
This problem is persisting in Gutsy as well.
I am suspecting race conditions with upstart as root cause. I will run
test cases with sysvinit and see what the results are.
--
Samba does not start on boot.
https://bugs.launchpad.net/bugs/125687
You received this bug notification because you are a
Did some searching. Possible similarities to Bug #84537. Also, mlind
has a comment in Bug #25931 that sounds somewhat similar. I will run a
couple of use tests by tomorrow.
--
Samba does not start on boot.
https://bugs.launchpad.net/bugs/125687
You received this bug notification because you ar
I have FAI'd an edgy system and done a CD install of a dapper system.
iscsitarget is not present in either release, nor is it listed in any of
the repositories (updates, security, backports, commercial).
Would this then qualify as a backport?
Best regards,
- alvinc
--
iscsitarget kernel module
With guidance from Emmet, work on evaluating the impact of this bug is
proceeding.
I configuring dapper and feisty environments, and constructing FAI
classes and nfsroot for edgy (as the edgy ISO images are no longer
available in any of the mirrors which I have checked).
More status will be added
Thanks Emmet.
For the purposes of staying on top of the issue... What is the target
kernel version for hardy?
As hardy is slated to be an LTS release, I am very interested that
these bugs are fixed by the time hardy releases.
iscsitarget is a service which has a lot of usefulness in Production
Fix attached
** Attachment added: "debdiff of fixes"
http://launchpadlibrarian.net/10372620/iscsitarget_0.4.15-3.debdiff
--
/etc/init.d/iscsitarget broken with migration to /bin/dash
https://bugs.launchpad.net/bugs/160106
You received this bug notification because you are a member of Ubuntu
Fixes attached. Also includes fixes for Bug #160106
** Attachment added: "iscsitarget_0.4.15-3.debdiff"
http://launchpadlibrarian.net/10372626/iscsitarget_0.4.15-3.debdiff
--
iscsitarget kernel module compile fails in event.c:98
https://bugs.launchpad.net/bugs/160104
You received this bug no
Public bug reported:
Binary package hint: hybserv
/etc/init.d/hybserv does not work on stop. The control structure in the
script is looking for a pid file, which the hybserv daemon is not
generating.
** Affects: hybserv (Ubuntu)
Importance: Undecided
Status: New
--
hybserv inits
** Changed in: iscsitarget (Ubuntu)
Assignee: (unassigned) => Alvin Cura (alvinc)
** Changed in: gutsy-backports
Assignee: (unassigned) => Alvin Cura (alvinc)
--
iscsitarget kernel module compile fails in event.c:98
https://bugs.launchpad.net/bugs/160104
You received th
** Changed in: gutsy-backports
Assignee: (unassigned) => Alvin Cura (alvinc)
** Changed in: iscsitarget (Ubuntu)
Assignee: (unassigned) => Alvin Cura (alvinc)
--
/etc/init.d/iscsitarget broken with migration to /bin/dash
https://bugs.launchpad.net/bugs/160106
You received th
Public bug reported:
Binary package hint: ubuntu-xen-server
I had been commenting on Bug #135818, however it is marked as fixed.
This issue seems related, but is not identical:
//**//
Alvin Cura wrote on 2007-11-05: (permalink)
I'm afraid I'm still seeing this bug. Or
More bad news. Problem is persisting, even with a different NIC
(although also a Realtek, this one a PCI card instead of the onboard):
syslog:Nov 11 23:22:17 xen1 kernel: [ 8113.207809] PCI-DMA: Out of SW-IOMMU
space for 7222 bytes at device :03:05.0
syslog:Nov 11 23:22:40 xen1 kernel: [ 813
Interestingly, here is the result of "fai-setup -v" on a Feisty xendomu.
It tried to continue past the error, and aborted in a different place
than Gutsy:
Setting up file (4.19-1ubuntu2) ...
Setting up cfengine2 (2.1.20-1) ...
Making a key pair for cfengine, please wait, this could take a minute.
I'll look into it and let you know what I find.
On Nov 7, 2007 12:16 AM, Castang Jerome <[EMAIL PROTECTED]> wrote:
> Alvin Cura a écrit :
> > Jerome,
> >
> > What are you running for xendom0? I am beginning to suspect running
> > gutsy on a feisty xendom
Jerome,
What are you running for xendom0? I am beginning to suspect running
gutsy on a feisty xendom0 is part of the issue.
Thanks,
- alvinc
--
dpkg seg-fault with fai-nfsroot
https://bugs.launchpad.net/bugs/159536
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Changed in: fai (Ubuntu)
Assignee: (unassigned) => Ubuntu FAI Developers (fai)
--
dpkg seg-fault with fai-nfsroot
https://bugs.launchpad.net/bugs/159536
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailin
Further analysis seems to point at a xen-only problem.
I have installed Gutsy Server from the CD image on a VMware VM and
installed the ppa FAI with no errors:
// * //
[EMAIL PROTECTED]:~# fai-setup -v
Using configuration files from /etc/fai
Creating FAI nfsroot in /srv/fai/nfsroot/live/file
Gutsy (Ubuntu 7.10). Host is a Dell 2970.
On Nov 6, 2007 1:03 AM, Castang Jerome <[EMAIL PROTECTED]> wrote:
> Alvin Cura a écrit :
>
> I am in the same situation.
> I reproduce the same error on a xen domU.
> Dom0 is a CentOS 5 (last updates).
>
> Which OS do you us
I just reproduced it.
--- BEGIN CUT-N-PASTE
[EMAIL PROTECTED]:/etc/fai# fai-setup -v
Using configuration files from /etc/fai
Creating FAI nfsroot in /srv/fai/nfsroot/live/filesystem.dir.
By default it needs more than 330 MBytes disk space.
This may take a long time.
Creating base system using de
Thanks siretart.
Question: What is the criteria for deciding whether this belongs in
universe or multiverse? I'm afraid I don't know how that decision is
made.
Thanks!
--
broken apt installation dependency for fai-quickstart-3.2.1-0ubuntu2
https://bugs.launchpad.net/bugs/156836
You received t
Public bug reported:
Binary package hint: iscsitarget-source
Module build using module assistant
m-a a-i iscsitarget
-
Following are the errors:
CC [M] /usr/src/modules/iscsitarget-module/kernel/event.o
/usr/src/modules/iscsitarget-module/kernel/event.c: In function
I'm sorry. Running Gutsy:
[EMAIL PROTECTED]:/usr/src# uname -a
Linux xen1 2.6.22-14-xen #1 SMP Sun Oct 14 23:20:20 GMT 2007 x86_64 GNU/Linux
** Also affects: gutsy-backports
Importance: Undecided
Status: New
--
iscsitarget kernel module compile fails in event.c:98
https://bugs.launc
Public bug reported:
Binary package hint: iscsitarget
Errors are as follows:
[EMAIL PROTECTED]:/usr/src# apt-get install iscsitarget
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
iscsitarget
0 upgraded, 1
I'm afraid I'm still seeing this bug. Or something similar.
I did not get a kernel panic, but my network died and stayed dead. I
was, however, able to reboot.
Nov 4 16:44:43 xen1 -- MARK --
Nov 4 17:04:36 xen1 kernel: [19235.154900] PCI-DMA: Out of SW-IOMMU space for
7222 bytes at device 0
Public bug reported:
Binary package hint: fai-quickstart
Broken dependency in fai-quickstart (using PPA):
[EMAIL PROTECTED]:~# apt-get install fai-quickstart
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may me
Would it be worthy then to roll it into a Launchpad team and maintain it
from there?
--
rpmstrap using /bin/sh when it should use /bin/bash
https://bugs.launchpad.net/bugs/64032
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
u
Hi Cesare!
I read your link briefly. The project is dead? I thought there would be
new life for it with the use of Xen.
--
rpmstrap using /bin/sh when it should use /bin/bash
https://bugs.launchpad.net/bugs/64032
You received this bug notification because you are a member of Ubuntu
Bugs, w
Confirmed: Fix is working with Fedora Core 4 (Stentz) script (with
regard to parsing the array of packages). Output is attached.
HOWEVER! The rpm installation actions are failing. I have not yet
looked into why. If anyone already knows why, I'd appreciate some info
rather than spending too mu
Additional info (verifying that the wget on the array works):
[EMAIL PROTECTED]:/tmp/rpmstrap.295074023# ls
basesystem-8.0-4.noarch.rpm libacl-2.2.23-5.x86_64.rpm
bash-3.0-17.x86_64.rpmlibattr-2.4.16-3.i386.rpm
chkconfig-1.3.11.1-1.x86_64.rpm libattr-2.4.16-3.x86_64.rpm
crackli
Will this be fixed in gutsy?
I can confirm my own experience with the problem. It has to do the the
"echo -e" statements in /usr/lib/rpmstrap/functions which don't work in
dash.
--
rpmstrap using /bin/sh when it should use /bin/bash
https://bugs.launchpad.net/bugs/64032
You received this bug no
I think we may be chasing the wrong problem by pursuing xen-tools for
the fix.
This problem is also 100% reproducible using manual domain creation.
The only working fix I have found is to add extra='xencons=tty1' to the
xendomu config file.
This would be incorrect behaviour. It should work out-
I think we may be chasing the wrong problem by pursuing xen-tools for
the fix.
This problem is also 100% reproducible using manual domain creation.
The only working fix I have found is to add extra='xencons=tty1' to the
xendomu config file.
This would be incorrect behaviour. It should work out-
? Is it needed to fulfill the requirement for LTS?
** Affects: dapper-backports
Importance: Undecided
Assignee: Ubuntu FAI Developers (fai)
Status: New
** Affects: feisty-backports
Importance: Undecided
Assignee: Alvin Cura (alvinc)
Status: New
** Affects
I can also confirm this.
This error does not appear during ifdown.
ifup shows this in strace:
read(3, "lo=lo\neth0=eth0\neth1=eth1\n", 4096) = 26
fstat64(4, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7f33000
read(3,
Ah ha! "strace -ff -F -o out ifup eth1:1" does the trick.
** Attachment added: "zipfile of strace logs"
http://launchpadlibrarian.net/9574365/strace-ifup.zip
--
'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias
https://bugs.launchpad.net/bugs/123773
You received this b
Actually, I see this behaviour during dpkg installation of a custom-
built kernel as well. Also it is during update-initramfs.
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.20.3-ubuntu1-sysdudez-fw-live
find: /lib/firmware/2.6.20.3-ubuntu1-sysdudez-fw-live: No such file or dir
62 matches
Mail list logo