Err, oops. This looks like a duplicate of bug 519066.
--
[IDT 92HD81B1C5] Recording using the internal mic catches no sound (Precision
M6500)
https://bugs.launchpad.net/bugs/605873
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
Public bug reported:
Binary package hint: ubiquity
Installing using a preseeded configuration with today's image
(20100614), there is a Segmentation fault error or wget aborts during
the download/processing of the preseed configuration, which causes it to
not be taken into account at all: ubiquit
** Attachment added: "Casper.gz"
http://launchpadlibrarian.net/50319043/Casper.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/50319044/Dependencies.txt
** Attachment added: "UbiquityDebug.gz"
http://launchpadlibrarian.net/50319045/UbiquityDebug.gz
** Attachmen
Casper.log displaying wget aborting with a failed assertion:
__getpagesize: Assertion `_rtld_global_ro._dl_pagesize != 0' failed.
** Attachment added: "casper.log"
http://launchpadlibrarian.net/50319590/casper.log
--
segmentation fault while downloading preseed file
https://bugs.launchpad.net
Tested again in Maverick with a custom-made adapter for this type of
connection.
There are two options: Line-In, Microphone.
- Line-In: works for the built-in microphone, does not get line signal
from the single mic/headphone jack (probably on purpose... maybe it just
doesn't belong on the Mini,
Ameet,
I confirm, this is reproducible on i386.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => New
--
segmentation fault while downloading preseed file
https://bugs.launchpad.net/bugs/594162
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Colin, the casper.log attachment is a log for i386. There is no
Segmentation fault, but there is an assertion error. Same goes for amd64
after I tried it again, I would still get assertion errors rather than a
segfault.
I've also tried to reproduce it by running wget by hand, with no luck.
--
se
Trying again today to get a clearer view of what's going on.
--
segmentation fault while downloading preseed file
https://bugs.launchpad.net/bugs/594162
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
Further testing shows it crashes with a segfault on amd64, and an
assertion error on i386. I could not find a core file to investigate.
--
segmentation fault while downloading preseed file
https://bugs.launchpad.net/bugs/594162
You received this bug notification because you are a member of Ubuntu
Hi! Thanks for filing this bug and helping to make Ubuntu better!
This is expected behaviour, as shutting down the NIC in some cases will
cause Wake on Lan to be unusable later (e.g. at some point Windows'
broadcom drivers would shut down a port making it totally unusable in
Ubuntu). Additionally,
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Maverick Meerkat. It would help us greatly if you
could test with it so we can
Public bug reported:
Binary package hint: network-manager
nmcli appears to be missing from an install of network-manager
0.8.1+git.20100810t184654.ab580f4-0ubuntu1, although it's one of the
nice new features introduced in 0.8.1 upstream.
It appears to be compiled, just not installed into the bin
The manpage for nmcli is already being installed, as demonstrated by the
logs from the build of revision -0ubuntu1:
http://launchpadlibrarian.net/53485508/buildlog_ubuntu-maverick-i386
.network-
manager_0.8.1%2Bgit.20100810t184654.ab580f4-0ubuntu1_FULLYBUILT.txt.gz
The debdiff is attached.
** Pat
Petar,
I'm sorry to have you confirm that again, but I wasn't exactly sure
following your last comment. Running 'ethtool -s eth0 autoneg off' fixed
your issue, correct? Are both 'Auto eth0' and 'T-home' ethernet
connections?
It's an important piece of information, because if it works, this issue
The fact that this message appears is not a bug, more of an informative
message; but it probably shouldn't be written out all the time like it
is; confirming and setting to Low, since more or less cosmetic and
doesn't impact functionality.
** Changed in: network-manager-applet (Ubuntu)
Stat
Closing as per initial reporter's comment.
Please, don't hesitate to open bugs for any future issues you may find;
thanks!
** Changed in: network-manager-applet (Ubuntu)
Status: Incomplete => Invalid
--
I can click on the nm-applet on the notification area only one time once I log
in. T
FWIW, I can't reproduce this on g-p-m 2.31.92-0ubuntu1 or
2.32.0-0ubuntu1.
--
Battery life estimation never comes around
https://bugs.launchpad.net/bugs/629258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Sorry Roman,
Yes, this is just the information I was looking for, I just need to go
through the log and see what is going on. I will let you know if I need
more information.
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Triaged
--
NetworkManager delay before connection
ht
Dave,
Could you tell us what kind of system this is? I'd like to test on two
netbooks to see if I can reproduce the issue (since I didn't see this on
my own netbook, but maybe I wasn't quite up to date). So I'd test with a
system similar to yours if I can put my hands on one, and another
without b
Just tested with the latest maverick desktop amd64 image (20100928) and
it's still kind of an issue: with a mic plugged in, I can hit the mic
and headphones to get it to pick some sound, but it doesn't get voice at
all -- I suspect the sound levels are too low and there is no way to
change it (it's
Forgot to add; to get sound at all from a connected microphone, one
needs to select Mic C in alsamixer. Mics B, E and F pickup no sound at
all, and there is no way to select the microphone to use in gnome-
volume-control
--
Microphones not working on Dell Vostro 320
https://bugs.launchpad.net/bug
I'm unable to reproduce this on a clean install of Maverick netbook with
image 20100928.2; on a very similar Compaq Mini which has the same
wireless chip (checked PCI IDs). I will test an upgrade from Lucid
netbook edition.
--
network-manager on une will not connect
https://bugs.launchpad.net/bug
Public bug reported:
Binary package hint: apport
As per the FTBFS report here: http://udd.debian.org/cgi-
bin/ubuntu_ftbfs.cgi
It looks like this doesn't happen in 1.14.1-0ubuntu7 in pbuilder or in
the buildds, but is definitely reproducible running 'bzr bd' with the
lp:ubuntu/apport branch. It
** Branch linked: lp:~mathieu-tl/apport/install-scalable-apps-icons
--
FTBFS in Maverick outside pbuilder/buildds
https://bugs.launchpad.net/bugs/651386
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
*** This bug is a duplicate of bug 647628 ***
https://bugs.launchpad.net/bugs/647628
Marking as a duplicate of bug 647628.
** This bug has been marked a duplicate of bug 647628
package hildon-desktop 1:2.0.11-1~svn15367-0ubuntu7 failed to
install/upgrade: trying to overwrite '/etc/xdg/men
The intended behavior is, AFAIK as written on the label; if the tooltip
is contradicting then it is indeed a bug; note that what you're
describing sounds like a bug as well (checking/unchecking with automatic
or without not yielding consitent results). Could you open separate bug
reports about thes
I'm marking this bug as Won't fix because I don't really see a benefit
in providing a virtual package that would install all VPN plugins at
once; and no one has responded with a use case to justify it.
This is without counting other issues with this, such as maintainability
as we add new plugins (
Hi,
Thank you for reporting this bug and helping to make Ubuntu better!
Unfortunately we can't start working on your problem yet because this
bug report does not currently contain enough information to understand
the problem.
Could you please make sure you do a clean boot of your system with
wire
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Maverick Meerkat. It would help us greatly if you
could test with it so we can
This looks to me like it is pretty much expected behaviour... There
couldn't be more namservers appended to the list in resolv.conf as only
the first three will ever be used by the libc resolver.
On the other hand, you may also mean that all DNS nameservers received
from the VPN should be authorit
Marking Low, Incomplete, also reassigning to network-manager-openvpn
since this is what will be handling the nameservers received from
openvpn.
** Package changed: network-manager (Ubuntu) => network-manager-openvpn
(Ubuntu)
--
Does not correctly write resolv.conf
https://bugs.launchpad.net/bugs
This is always a possibility and the case for various other
applications; authentication requests usually do steal focus as they
have higher "importance".
The issue you are reporting is an upstream one and it would be nice if
somebody having it could send the bug to the developers of the software
That icon means there is no connection.
You are right, this is an issue specific to the Broadcom drivers and how
they report signal strength, and has already been fixed in the
development release of Ubuntu.
If you want to test that it is indeed resolved for you (and you are not
hiting another bug
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Low
--
Documentation incomplete - Pling not explained
https://bugs.launchpad.net/bugs/649632
You received this bug notification because you are a member of
Is this only for the Huawei E620 or also for other devices where the
other sticks tested of the same model?
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD
** Branch unlinked: lp:~mathieu-tl/seamonkey/lp575160
--
seamonkey 2.0 crashes with 'RenderBadPicture' diagnostics
https://bugs.launchpad.net/bugs/575160
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
Reworked my branch to apply the patches from Mike Hommey (see upstream
bug), which seem to apply properly and correctly fix the issue.
** Changed in: seamonkey (Ubuntu Maverick)
Status: In Progress => Triaged
** Changed in: seamonkey (Ubuntu Maverick)
Assignee: Mathieu Tru
Looks like this can be fixed in Maverick, so I'm targetting it for the
release.
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
** Changed in: network-manager (Ubuntu)
Importance: Und
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Maverick Meerkat. It would help us greatly if you
could test with it so we can
I'm not sure whether this really should be set to High or not, but I
agree there is a slight usability issue. Marking as Triaged for now; for
Maverick+1 we could look at how much work it is to present the wizard,
if it helps usability, or if there are other options (such as showing a
new device tha
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Maverick Meerkat. It would help us greatly if you
could test with it so we can
Mitch,
Is this only an issue with the ~karmic package or also present for other
releases on the NM trunk PPA?
By the way, there is a patch available for this and applied to the
version uploaded to maverick (and should be applied on trunk as well,
once I unbreak the daily builds).
--
[NM trunk p
smidl,
Can you please confirm which version of NM you are running? You can do
this with the "dpkg -l network-manager" command.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Low
--
dhclient3 not reco
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Maverick Meerkat. It would help us greatly if you
could test with it so we can
Wow, that looks to me like a nice case of really bad luck during an
upgrade.
So yes, state file and enable/disable behavior has changed between 0.8
and 0.8.1 as shipped now in Maverick -- basically to make it more robust
and split enabling/disabling from the cases where a system has wifi
enabled a
This appears to be related to failed sleep/hibernate (if not, then it
seems like it would be 291062, which should have been fixed long ago).
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the l
What happens if you kill -HUP gnome-panel instead? If it still doesn't
appear, please make sure the "notification area" applet is added to
gnome-panel, since this is where nm-applet will show up.
Pouvez-vous essayer de tuer gnome-panel a la place: pkill -HUP gnome-
panel , pour voir si l'applet y
Hi!
Is there a DHCP server available on the network to give out addresses?
The attached syslog shows that eth0 is enabled and loaded but fails to
receive (or maybe send DHCP responses/requests. If there is no DHCP,
then you may want to set a static IP address on the interface, which can
be done fr
Marking as triaging and nominating for Maverick. I think we have enough
information to fix this before release provided I'm also able to
reproduce the issue (though I admit I haven't seen this happen yet --
but I also don't usually suspend).
** Also affects: network-manager (Ubuntu Maverick)
Im
Hi,
On the other hand, sorting networks this way will leave room for
suggestions similar to: current sorting doesn't list networks in signal
strength order, or "please sort in alphabetical order". This does
however seem like a good compromise to improve usability.
The best course of action would
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't start working on it yet, because
your bug report didn't include enough information.
Please include the information requested at
http://live.gnome.org/NetworkManager/Debugging under Debugging
Csaba, please post additional information, such as the contents of
/var/log/syslog as you bring up eth0.200 using ifup (with eth0.200 set
in /etc/network/interfaces), or using ubuntu-bug to add all relevant
info automatically for network-manager.
My take on this is that ifup takes down eth0 for a
Setting importance to low for now and marking as incomplete: roaming is
expected when there are multiple ESSIDs with the same name in range, but
it really should be to follow the one with the highest signal, which
shouldn't be changing that much. I also think this might have been fixed
or improved
Thanks for your report. The issue you are describing was most likely
caused by the fact that no VPN plugins were installed by default in
Ubuntu releases prior to Lucid Lynx. As you mention in comment 1 that
the issue is fixed in Lucid, I'm marking this as Fix Released.
For future reference you can
Confirming: there is a screenshot as witness. Marking as low since this
is a usability issue but does not render NM completely unusable. I will
try to reproduce this on my netbook.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
** Changed in: network-manager (Ubuntu)
I
Public bug reported:
Binary package hint: gdm
Every time I boot my system, GDM starts, but crashes (along with X,
apparently) as soon as I press Enter (such as to select the user name).
The second time it start up, GDM behaves correctly and accepts input.
ProblemType: Bug
DistroRelease: Ubuntu
** Attachment added: "First gdm startup with crash"
https://bugs.edge.launchpad.net/bugs/638061/+attachment/1583051/+files/%3A0-greeter.log.1
** Attachment added: "Dependencies.txt"
https://bugs.edge.launchpad.net/bugs/638061/+attachment/1583052/+files/Dependencies.txt
--
gdm crashes on
Attaching the /var/log/gdm/:0.log file as well, in case it offers any
additional data. X gets stopped with a SIGQUIT.
** Attachment added: ":0.log.1"
https://bugs.edge.launchpad.net/ubuntu/+source/gdm/+bug/638061/+attachment/1583053/+files/%3A0.log.1
--
gdm crashes once every boot
https://bu
According to the logs above, association takes too long and
NetworkManager gives up. Can you test with a different system (different
wifi device) to see if the same happens? You can use a live CD to do
this if the system isn't running Ubuntu (or you could you try on the
same system with a liveCD fo
Hi!
Thanks for reporting this bug and helping to make Ubuntu better.
Unfortunately the solutions you are proposing aren't the best, since
they involve either manual changes every time the system is being booted
(and assigned an IP), or changing attributes for resolv.conf which tends
to cause issue
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't start working on it yet, because
your bug report didn't include enough information.
Please include the information requested at
https://wiki.ubuntu.com/DebuggingNetworkManager. If you have tr
Hi Chris,
Seems like there is info missing on my bug :)
I don't think it's the same as 625239, since I don't have nvidia
hardware (unless I'm reading this wrong?). As for 626723, I have noticed
this text in the past. I will try to reproduce it later on.
** Changed in: gdm (Ubuntu)
Status:
Andrei,
Do you get any different behavior is you change the managed=false key in
nm-system-settings.conf to "true"?
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Low
--
Network manager manages "unman
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, according to this report, you are not using the
most recent version of this package for your Ubuntu release. Please
upgrade to the most recent version and let us know if you are still
having this issue. Tha
Reassigning to the mobile-broadband-provider-info package, we still need
to check whether upstream git already has a fix for this..
Testing with a live CD should be possible soon if the new m-b-p-i gets
synced from Debian.
** Package changed: network-manager (Ubuntu) => mobile-broadband-
provider
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Maverick Meerkat. It would help us greatly if you
could test with it so we can
NM already traps the important messages from pptp in order to give out
feedback to the user (or know that a password was asked for again).
Otherwise, it is possible to restart NM with the PPTP_DEBUG=1
environment variable in order to have it write debug information to a
log, so I'm not sure what el
BUGabundo, since Karmic, 3G modem functionality has been split to be
handled by ModemManager instead of directly in NetworkManager. Could you
report back here and confirm whether the issue has been fixed for you in
later releases?
** Changed in: network-manager (Ubuntu)
Status: New => Incom
Martin, can you give us more information about the interfaces on your
system? You don't appear to be running Ubuntu in a different localized
environment, so the only thing I can think of is special interfaces like
bridges set up on your system...
Please post the output of ifconfig -a, or ip addr l
Hi Rolf,
Would you please be able to attach the contents of /var/log/syslog?
Following that we may be able to understand how and why the killswitch
also touches the ethernet interface (which clearly shouldn't happen).
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
Hi!
In your bug report, there appears to be the result of start NM missing,
up to when it gets restarted and detects your eth1 device.
In order to add the information, could you:
1) reboot, let NM start
2) restart NetworkManager
3) attach the full contents of /var/log/syslog to this bug.
Ideall
Hi,
Can you please confirm when this showed and and whether this is still
the case? I've noticed this kind of thing happening right after an
upgrade until a restart, but not as much after.
Thanks!
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
** Changed in: network-ma
Hi,
Could you please specific exactly which extra entries are added, and
aren't removed?
Thanks!
--
Leaves unreachable entries in /etc/hosts when stopping network
https://bugs.launchpad.net/bugs/632896
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Hi,
Please confirm which entries have been added to /etc/hosts, as well as
which are already in the file.
Also, if possible, can you find out where the name comes from? You may
be able to do this with the following command:
dig -x
Please post the output of that command if you can, you should b
Maybe this was due to a failed suspend. could you try check this out,
maybe suspend to see if it completes properly and wifi is still fine?
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
Wifi no longer works after kernel update 2.6.32-24-generic-pae #42
https://bugs.
Hi Bob,
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't start working on it yet, because
your bug report didn't include enough information.
Please include the information requested at
https://wiki.ubuntu.com/DebuggingNetworkManager under
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't start working on it yet, because
your bug report didn't include enough information.
Please include the information requested at
https://wiki.ubuntu.com/DebuggingModemmanager under Get Debug L
There appears to be clashing between different applications claiming the
device, there is at least rhythmbox and gvfs trying to load the device.
Is this an actual USB modem (or even integrated) or are you connecting a
smart phone over USB?
To begin with, please try to make sure that rhythmbox isn'
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, according to this report, you are not using the
most recent version of this package for your Ubuntu release. Please
upgrade to the most recent version and let us know if you are still
having this issue. Tha
Hi, Notch-1,
Could you please include the contents of /var/log/syslog as well as your
file .xsession-errors from your home directory?
At the same time, please verify if you have files with names starting
with "org.freedesktop.NetworkManager" under /usr/share/dbus-1/system-
services/.
Thanks in a
Hi,
Was this with a successful suspend and resume, or after attempting to
suspend but with suspend failing and the system needs to be rebooted
(e.g. you can know because if suspend works and resume too, you get a
screensaver password prompt instead of a login prompt).
Thanks in advance!
** Chang
Looks like this means ModemManager doesn't claim the device.
Could you please post the relevant IDs (USB ID from lsusb), and the
exact model if you can find it on the device (or what lsusb reports), so
we can add this in a report on the GNOME bugzilla?
If you could open the upstream bug on GNOME
Hi,
Could you please post the output of the 'ip addr list' and 'ip route
list' commands both before and after Networkmanager is reset to make
wireless work? What I mean by this is that we should see the list of
routes before restart NM, when it doesn't allow traffic, and then after.
This is to mak
** Also affects: network-manager-applet (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: network-manager-applet (Ubuntu Maverick)
Importance: Undecided
Status: New
** Changed in: network-manager-applet (Ubuntu Maverick)
Status: New => Confirmed
** Chan
I've marked this as Fix Released since the commits mentioned by Dan are
already available in Maverick (though I can't test it for now). Let's
keep this one in mind for a possible SRU.
--
Network Manager showing SIM code cleartext
https://bugs.launchpad.net/bugs/589139
You received this bug notifi
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Maverick Meerkat. It would help us greatly if you
could test with it so we can
This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more a
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, according to this report, you are not using the
most recent version of this package for your Ubuntu release. Please
upgrade to the most recent version and let us know if you are still
having this issue. Tha
All this appears to me as being available in various ways: in Lucid, the
NM icon should change depending on the type of 3G connection (a little
yellow mark). You should also be able to see more information if you
right click the icon, and select Connection Information, then go on to
your connection
Hi,
The issue you're describing should have been fixed in later releases of
Ubuntu. Is there any way you can test this using a live CD, for example,
with the latest release of Ubuntu - Lucid Lynx? Please don't hesitate to
ask if you need assistance with this.
Thanks!
** Changed in: network-manag
A fix for this is available out of the box in Maverick, afaik (it
includes the commits that fix this according to upstream bug reports).
** Also affects: network-manager-applet (Ubuntu Maverick)
Importance: Undecided
Status: New
** Changed in: network-manager-applet (Ubuntu Maverick)
Does it ever show up if you just wait for the device to be recognized?
I've seen it take a few minutes with a ZTE MF636 modem.
** Changed in: network-manager-applet (Ubuntu)
Status: New => Incomplete
--
nm-applet does not show available mobile broadband connection
https://bugs.launchpad.n
** Also affects: network-manager-applet (Ubuntu Maverick)
Importance: Undecided
Status: New
** Changed in: network-manager-applet (Ubuntu Maverick)
Status: New => Confirmed
** Changed in: network-manager-applet (Ubuntu Maverick)
Importance: Undecided => Low
--
Network Manage
Please see if you remove the line "no-auto-default=00:27:0e:1c:f4:ab,"
from /etc/NetworkManager/nm-system-settings.conf if the situation
improves.
If you use NetworkManager only to manage your network connections, you should
also be able to safely remove all entries for eth0 from
/etc/network/in
Public bug reported:
Binary package hint: samba
After having the samba postinst script run and do nothing for well over
an hour, I killed it with a signal 15 in order to unjam an upgrade.
root 21390 18831 0 16:27 pts/000:00:00 /usr/bin/perl -w
/usr/share/debconf/frontend /var/lib/dpkg/i
** Attachment added: "AptOrdering.txt"
https://bugs.edge.launchpad.net/bugs/638479/+attachment/1585571/+files/AptOrdering.txt
** Attachment added: "Dependencies.txt"
https://bugs.edge.launchpad.net/bugs/638479/+attachment/1585572/+files/Dependencies.txt
** Attachment added: "Df.txt"
h
Just ran 'dpkg --configure -a' after the end of the upgrade process and
the postinst script ran without issues.
--
package samba 2:3.5.4~dfsg-1ubuntu5 failed to install/upgrade: sous-processus
script post-installation installé tué par le signal (Complété)
https://bugs.launchpad.net/bugs/638479
Y
Just tried a custom initrd.lz image; after applying the suggested
workaround for bug 602273, further modifying the initrd to call wget
directly and dropping preseed file in /root/tmp rather than going
through 'chroot /root', the file is properly downloaded, preseed is
valid and the install continue
It seems the system I am working with isn't equipped with a microphone
at all (I checked, and hda-verb does nothing, and forcing a reconfigure
fails with device busy).
I think the course of action from now would be to close this bug as
invalid and for yanuzz and Thomas to open new bugs re: their s
Paul,
What happens if you modify the kernel parameters passed to remove 'quiet
splash' and whatever else (though not ro)? Actually, even just adding a
space to the end would sometimes cause my Mini 500 to complete booting,
when it would otherwise also stop at
"b43-pci-bridge :01:00.0: PCI INT
501 - 600 of 8571 matches
Mail list logo
