Dustin,
I just wrote a quick patch for this, but it will still need some
testing. So far, all I know is that it builds. This patch is in nm-
applet rather than NM itself since we want to keep having NM report
things as they are (see upstream bug) :)
I don't happen to have a Free Public WiFi netwo
*** This bug is a duplicate of bug 630748 ***
https://bugs.launchpad.net/bugs/630748
Right. Please note comments 8 and 9 on bug 630748. As mentioned above,
it's very relevant, so I'm marking this as duplicate since the issue of
not being able to connect to a N network if the router is set to a
** Package changed: network-manager (Ubuntu) => network-manager-applet
(Ubuntu)
--
filter out fakey Free-Public-Wifi ad hoc networks
https://bugs.launchpad.net/bugs/659461
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
I'm sorry but there is just not enough information to properly triage
this bug -- without knowing exactly which drivers these are, there is
little that can be done.
In order to help us deal with this issue, could you try the live CD
again and use the 'apport-cli linux --save /tmp/drivers.apport' c
Thanks for the patch Anders, preparing to upload it now...
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel (mathieu-tl)
--
Leaves unreachable entries in /etc/host
Jean-Baptiste,
To me it looks like a different issue specific to IPv6 after all. In
reality, you probably shouldn't even have this new IPv6 entry in
/etc/hosts if your system is set to Ignore for IPv6 in NM. Can you
please open a bug for that and report the number here just so we can
track this? I
Looks reasonable, marking as Triaged/Low, and assigning myself.
** Changed in: network-manager (Ubuntu)
Assignee: Сергій Матрунчик (SkyMan) (skymanphp) => Mathieu Trudel
(mathieu-tl)
** Changed in: network-manager (Ubuntu)
Status: New => Triaged
** Changed in: network-m
Your netmask looks okay in the logs and attachments, but I'll assume you
did something manually to get to reporting this bug...
There's nothing I can find in the logs to indicate there is anything
wrong with netmask. The 255.255.255.255 you see is simply standard DHCP
behaviour of broadcasting to
*** This bug is a duplicate of bug 659872 ***
https://bugs.launchpad.net/bugs/659872
Thanks for reporting this bug. It appears the issue you are describing
has already been reported in bug 659872, so I'm marking this as a
duplicate.
** This bug has been marked a duplicate of bug 659872
Ali
Matti, Rickard,
This bug was filed in 2008, for a largely different version of network-
manager. Since then, carrier detection has improved and changed a lot
and there are additionally other ways you can force NetworkManager to
restart a connection (re-establish the DHCP session), e.g. clicking th
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Would you be able to test if this is still not working in
the newest release of Ubuntu - Maverick Meerkat? You don't need to
reinstall or upgrade: testing using a live CD will be sufficient.
Additionally, it looks
Since this is a hardware-specific issue, I'm marking setting this bug's
importance to "Low".
** Changed in: modemmanager (Ubuntu)
Importance: Undecided => Low
--
Sony Ericsson PC300 broadband device PIN not set automatically
https://bugs.launchpad.net/bugs/568069
You received this bug notific
It seems to me like this would be a bug with the yenta_socket driver or
udev more than with NM, especially since drivers are not getting
removed...
Unfortunately, it seems that since this bug was reported against
network-manager, only NM-specific data is available in the syslog
capture that was au
I fear there has been an issue when you generated the ModemManager logs;
as it hasn't started properly. Could you please retry the same steps and
attach another copy of the output of ModemManager with what happens as
it successfully connects or fails to connect?
** Changed in: network-manager (Ubu
Looking through the attached modemmanager logs I can't see the case
where the second connection attempt causes MM to start establishing a
connection.
Seeing the messages:
** Message: (ttyHS2) closing serial device...
Maybe what happens is that MM puts the modem into a mode this specific
device do
Robert, if you could connect with the steps in that thread, I don't
think it's the same issue. This bug report mentions having to issue a
second PIN to complete initialization, and the thread you linked is
really old. I would suggest you open a separate bug instead and tell us
the number here so we
** Tags added: nm-sta-icon
--
nm-applet shows no connection, but connection is fine
https://bugs.launchpad.net/bugs/658537
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://
** Tags added: nm-sta-icon
--
My wireless is working fine, but I'm always seeing the red excalamtion point
icon indicating there's a problem... I'd really like to easily view signal
strength.
https://bugs.launchpad.net/bugs/591424
You received this bug notification because you are a member of U
*** This bug is a duplicate of bug 591424 ***
https://bugs.launchpad.net/bugs/591424
** This bug has been marked a duplicate of bug 591424
My wireless is working fine, but I'm always seeing the red excalamtion point
icon indicating there's a problem... I'd really like to easily view signal
Status: New
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
** Changed in: network-manager (Ubuntu)
Status: New => In Progress
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel (mathieu-tl)
** Changed in: network-manager-a
** Changed in: network-manager (Ubuntu Lucid)
Status: Confirmed => In Progress
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
David, is it feasible to get this fix to Lucid in an SRU?
--
[Realtek ALC269] no sound on external speaker jack (Optiplex 980)
https://bugs.launchpad.net/bugs/588031
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: xorg
Suspending the system seems to work, but on resume the screen remains
blank.
Hibernate works fine.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6
--
blank screen on resume (Dell XPS M1330)
https://bugs.launchpad.net/bugs/659458
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/listinfo/ubuntu
Sounds reasonable.
** Changed in: network-manager (Ubuntu)
Status: New => Triaged
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Wishlist
--
filter out fakey Free-Public-Wifi ad hoc networks
https://bugs.launchpad.net/bugs/659461
You received this bug notification be
The only issue I see is that users shouldn't be blocked from actually
setting up such a network if they really wanted to, so I think it should
be treated as a special case for just this one -- filter it out from the
scanning results, but still allow a user to connect to it with the
"connect to a hi
** Bug watch added: GNOME Bug Tracker #632010
https://bugzilla.gnome.org/show_bug.cgi?id=632010
** Also affects: network-manager via
https://bugzilla.gnome.org/show_bug.cgi?id=632010
Importance: Unknown
Status: Unknown
--
filter out fakey Free-Public-Wifi ad hoc networks
https://
med
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Low
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel (mathieu-tl)
** Also affects: connman (Ubuntu)
Importance: Undecided
Status: New
** Changed in: connman (Ub
I'm not as certain it's really a bug in ibus. The same search and typing
in chinese characters (gibberish though, not going to give out any
results) in List View yields no crash. On the other hand, I can
reproduce this as soon as I set IBus as an input method and set it to
something other than Off
*** This bug is a duplicate of bug 539300 ***
https://bugs.launchpad.net/bugs/539300
** This bug is no longer a duplicate of bug 602605
nm-applet shows the wrong status when connected to a unsecured wifi network
** This bug has been marked a duplicate of bug 539300
[Lucid] Network Manage
*** This bug is a duplicate of bug 539300 ***
https://bugs.launchpad.net/bugs/539300
Right. So this is totally reproducible with the shiki-colors icon theme
set, and ends up being the same issue with broadcom drivers not
reporting the right signal level information -- marking as a duplicate
of
As per the comments above, this was fixed in commits upstream which made
it in Maverick, so I've marking this as Fix Released.
** Also affects: network-manager (Ubuntu Maverick)
Importance: Medium
Status: Confirmed
** Changed in: network-manager (Ubuntu Maverick)
Status: Confirme
Sheryl, this might be what causes your system to fail to suspend
properly (assuming it does and you then reboot the system completely,
which is how this bug is usually triggered). I don't think it has any
link in why NM starts disabled though.
--
Networking is disabled on boot (usually after susp
I can confirm the patch appears to fix the issue, so I marked this bug
Invalid for ibus and Triaged for nautilus. I applied the patch to a
local copy of the maverick nautilus branch, which I just pushed to LP
and should appear on this bug report shortly...
** Changed in: nautilus (Ubuntu Maverick)
** Branch unlinked: lp:~mathieu-tl/ubuntu/maverick/nautilus/lp625696
--
Nautilus crash when IM preedit
https://bugs.launchpad.net/bugs/625696
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.
I can't reproduce this issue on my system unless I forcibly remove the
device (or suspend as commented by komputes), on the other hand, it
happens as well in nautilus, which leads me to believe the issue lies in
udisks rather than cryptsetup or elsewhere.
I can also see that udisks doesn't seem (t
** Branch unlinked: lp:~mathieu-tl/+junk/lp484429
--
Plugging in a LUKS device causes the following error: Error unlocking device:
cryptsetup exited with exit code 239: Command failed: Device already exists
https://bugs.launchpad.net/bugs/484429
You received this bug notification because you are
** Branch linked: lp:~mathieu-tl/ubuntu/maverick/udisks/lp484429
--
Plugging in a LUKS device causes the following error: Error unlocking device:
cryptsetup exited with exit code 239: Command failed: Device already exists
https://bugs.launchpad.net/bugs/484429
You received this bug notification
I can't reproduce this in Maverick with network-manager-gnome
0.8.1+git.20100809t190028.290dc70-0ubuntu3, so marking this as Invalid.
I followed the exact steps you used to edit a wireless connection, and
change the network mask or gateway then apply in mid-edit, and the value
I entered does get a
The wired device is always preferred if available, so it indicates
(along with the fact you mention you need to click the Auto eth0
connection to have it get established) that there is something else
going on than NetworkManager not preferring the wired device.
Looks to me, at a quick glance, like
Confirming since there is an upstream bug about this.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
--
Leaves unreachable entries in /etc/hosts when stopping network
https://bugs.launchpad.net/b
** Changed in: network-manager (Ubuntu)
Status: New => Triaged
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Wishlist
--
IP Conflicts should show a warning
https://bugs.launchpad.net/bugs/640687
You received this bug notification because you are a member of Ubuntu
Bu
Could you please attach a screenshot that shows this behavior?
This seems like a valid issue but it's not a simple one to fix -- there
is already a (large) icon displayed for the current state, and a padlock
emblem is pretty small and might not be "noticed" as a progress
indication.
** Changed in
Seems like this was already reported as bug 632896.
--
network-manager updates /etc/hosts, breaks hostname -f
https://bugs.launchpad.net/bugs/645648
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
Ok so it looks like this isn't quite the same thing.
FWIW, I can make sure the domain name and hostname appear properly in
hostname / hostname -f by setting /etc/domainname as well as
/etc/hostname, and in that case NM properly add a line for both in
/etc/hosts:
10.10.10.16 demeter.cyphermox.
Could someone please test this in Maverick or confirm that the bug is
still present? There were some changes made to the way IPv6 is handled
upstream, but also requiring ISC-DHCPv4, which we don't have yet... but
would be a clear plan for Natty.
It's very likely that with the correct settings in M
In Maverick, NetworkManager already does rewrite /etc/hosts with some
amounts of success.
FWIW, I can also pretty nicely workaround having the FQDN available or
not by adding just the domain part in /etc/domainname. It's not pretty
but it does work, and from there on connection I have /etc/hosts l
Looking through the code, this really looks fixed if not in Karmic, then
definitely in Lucid and later releases. That's what the "no-auto-
default=," key in /etc/NetworkManager/nm-system-
settings.conf is for, and is automatically added when Auto eth0 is
created so that it doesn't get re-added if d
Tom,
What happens if instead of changing .font.conf or Appearance settings
you create a new user? Is there bleeding in this case?
We need to be certain this is not caused by another piece of
configuration elsewhere.
Also, please make sure your nvidia driver is at the latest version
available. F
onfig (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel (mathieu-tl)
--
Activate font auto hinting by default
https://bugs.launchpad.net/bugs/191654
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Thanks for reporting this bug and any supporting documentation. Since
this bug has enough information provided for a developer to begin work,
I'm going to mark it as confirmed and let them handle it from here.
Thanks for taking the time to make Ubuntu better!
** Changed in: fontconfig (Ubuntu)
FWIW, testing with an install from the amd64 20100628 alternate image
(kernel 2.6.35-6-generic) shows the screen correctly lighting up,
desktop is now visible with no modification to boot parameters after the
installation. However, there seems to be an issue with blanking the
screen for power manag
As there is an important but in acct 6.5.4-1, perhaps it would be best
to wait for 6.5.4-2 (waiting for sponsorship in Debian), or additionally
re-patch configure to set the correct ACCT_FILE paths.
--
Merge acct 6.5.4-1 (main) from Debian unstable (main)
https://bugs.launchpad.net/bugs/609754
Yo
Marking as Fix Released as suggested by the reporter in comment 2.
** Changed in: wpasupplicant (Ubuntu)
Status: New => Fix Released
--
wpa_gui must be opened as root by default
https://bugs.launchpad.net/bugs/549698
You received this bug notification because you are a member of Ubuntu
Bu
Wrote a (quick) patch that seems to correct the issue. That said, it's
making use of a function that is sourced from /init inside the initrd,
and apparently not in casper itself, which seems far from optimal.
Perhaps it would be a good idea to re-copy this function in casper-
functions or casper-he
SF, please don't hesitate to open a new bug report (and use ubuntu-bug to do
so) and report here with the bug number so that we can look at your issue
and so that it can be fixed as well.
On Jun 18, 2010 10:55 AM, "SF Basilix" wrote:
I just realized that the op has a separate issue - similar to
Works with the latest maverick image (20100713). Will test on Lucid with
the mainline kernel and report today.
--
[lucid] [nouveau] blank screen on Dell Latitude E6410 (NVS 3100M [10de:0a6c])
https://bugs.launchpad.net/bugs/556872
You received this bug notification because you are a member of Ubu
Works with the latest maverick image (20100713). Will test on Lucid with
the mainline kernel and report today.
--
[lucid] [M92 LP] blank screen on Mobility Radeon HD 4300 with KMS enabled
https://bugs.launchpad.net/bugs/555943
You received this bug notification because you are a member of Ubuntu
Actually, let me clarify that: it tends to work (it's no longer a blank
screen), but there is a lot of distortion, to the point the desktop is
unusable -- only the mouse pointer moves (again, this is maverick
20100713).
--
[lucid] [M92 LP] blank screen on Mobility Radeon HD 4300 with KMS enabled
Hi,
I've re-added building and installing ./usr/lib/pppd/2.4.5/nm-pppd-
plugin.so, could you please confirm that it is working fine now?
** Changed in: network-manager (Ubuntu)
Status: New => Fix Committed
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
--
Fil
Public bug reported:
Binary package hint: initramfs-tools
BOOTIF appears to not be set after going through today's iso image for
maverick-desktop-i386 (20100706) and the accompanying pxelinux.0 file.
This in turn causes DEVICE not to be set in casper, which causes the
PXE-booted installation to f
Attaching casper.log with the boot started with the debug= parameter.
** Attachment added: "casper.log.debug"
http://launchpadlibrarian.net/51463314/casper.log.debug
--
PXE booting the desktop image fails to configure network
https://bugs.launchpad.net/bugs/602273
You received this bug notifi
Attaching the contents of /proc/cmdline.
** Attachment added: "cmdline.txt"
http://launchpadlibrarian.net/51463318/cmdline.txt
--
PXE booting the desktop image fails to configure network
https://bugs.launchpad.net/bugs/602273
You received this bug notification because you are a member of Ubun
Attaching the contents of dmesg.
** Attachment added: "dmesg"
http://launchpadlibrarian.net/51463386/dmesg
--
PXE booting the desktop image fails to configure network
https://bugs.launchpad.net/bugs/602273
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
I've been able to test this on two different Vostro V13, however, it
seems to be the case on all the systems in the lab, so Toshibas, Dells,
netbooks, etc.
--
PXE booting the desktop image fails to configure network
https://bugs.launchpad.net/bugs/602273
You received this bug notification because
Angel, Daniel,
AFAIK, the Ubuntu version of network-manager doesn't usually follow
Debian, so I'm not sure it should be merged. I know in some cases
Michael Biebl (the Debian maintainer for NM and the plugins) used code
from the Ubuntu branches directly for upload to debian, at least, that
was the
Michael, no, the things I commented about won't have any effect in your
case. You have a point though, managed could be set to true, and this is
something I may look into in future releases. As for the leading zero,
no need to worry about it. It's customary to leave it out in some cases.
I'd still
Ok, apparently -1 works on the Inspiron 1545 as well, but this solution
is not usable as it makes other machines (e.g. Toshiba systems) fail to
boot in the same way described above.
--
grub hangs at early booting after handoff from PXE
https://bugs.launchpad.net/bugs/625383
You received this bug
Public bug reported:
Binary package hint: grub2
On three different Dell Inspiron 1545 (and 1546) systems, grub hangs
right after hand-off from PXE.
I've tried 'localboot 0', 'localboot 0x80', and 'localboot -1'. -1 seems
to work but only on the Inspiron 1546.
'localboot 5' was also attempted in
grego77,
Can you make sure IPv6 adressing is set to Ignore in the IPv6 tab for
your wireless connection if you don't need IPv6, and then post
/var/log/syslog again?
Thanks.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
WiFi randomly disconnects in Maverick
https:/
** Tags added: desktop-testing
--
Cannot export VPN connection
https://bugs.launchpad.net/bugs/633988
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/mail
Replacing tag 'patch' with 'patch-accepted-upstream' as the fix was
included upstream as per comment 2. I'm working on getting this in
Ubuntu now.
** Tags added: patch-accepted-upstream
** Tags removed: patch
--
Plans for 3 italian provider are wrong
https://bugs.launchpad.net/bugs/632300
You re
Ameet, Colin,
Just to clarify things (though I agree there is sadly little than can be
done anyway) I marked this bug as affecting grub because (if I recall
correctly) using Shift would still sometimes yield the GRUB menu. We'll
re-test this in the lab first though.
--
grub hangs at early bootin
grego77, there seems to be some stuff missing from your log, like
initial connection that got dropped. If that's all you have in your
syslog file, could you also attach syslog.1 or whatever file came
before, just to we have the full process from the first successful auth,
through the dropped connec
0.8.1 was uploaded to maverick some time ago. Could someone please
confirm whether the signal level appears correctly with the wl wifi
driver now?
--
Network manager applet does not display the current connection
https://bugs.launchpad.net/bugs/569335
You received this bug notification because yo
That's really weird, as there is absolutely no change between network-
manager 0.8.1+git.20100810t184654.ab580f4-0ubuntu1 and -0ubuntu2 besides
installing the nmcli binary in /usr/bin, which wasn't done previously.
Just to be clear, can you confirm that the previous version you had was
indeed -0ub
It so happens that I was also due to do that upgrade one of my systems
after reinstalling it with yesterday's Maverick ISO. Unfortunately, I
can't reproduce the issue, either before or after rebooting the system
after the upgrade.
Felix, please see above and confirm the previous questions. If you
Public bug reported:
I've noticed spamming from the kernel in /var/log/syslog regarding
exceeding the CPU and MCP thermal or power limits:
Sep 1 11:36:28 demeter kernel: [98490.237702] intel ips :00:1f.6: MCP
power or thermal limit exceeded
Sep 1 11:36:33 demeter kernel: [98495.244545] int
** Attachment added: "AcpiTables.txt"
https://bugs.launchpad.net/bugs/628163/+attachment/1534744/+files/AcpiTables.txt
** Attachment added: "AlsaDevices.txt"
https://bugs.launchpad.net/bugs/628163/+attachment/1534745/+files/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http
rykel, please do not assume that another distribution is the same as
Ubuntu even if it may be based on it: they may well have done additional
changes, applied additional patches, etc.
Looking at this quickly, it's the first time I see the actual model of
dongle being mentioned in the bug report.
As per Joao's comment, the hardware on which I reported the bug still
shows a blank, black screen when booting, even with the kernel in
-proposed.
--
[i915] blank screen on Latitude E6410
https://bugs.launchpad.net/bugs/561802
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 appears to be an issue with modemmanager, so reassigning as such.
Could you please follow the steps in
https://wiki.ubuntu.com/DebuggingModemmanager to attach a debug log for
Modem Manager? Thanks!
** Package changed: network
Such as the outcome upstream, this is not a bug. Just after installing,
NetworkManager will not automatically connect to any network, just
report that some are available. On the other hand, if networks have
already been configured (e.g. common names such as "linksys", "dlink",
etc.) then NetworkMan
Public bug reported:
Please sync isc-dhcp 4.1.1-P1-7 (universe) from Debian unstable (main)
All changelog entries:
isc-dhcp (4.1.1-P1-7) unstable; urgency=low
* The "There goes the neighbourhood" release
* No changes rebuild to upload to unstable
-- Andrew Pollock Sun, 04 Jul 2010 22:58
Arguably, there is an impact for users of the dhcp3-* packages, since
this one includes transitional packages to replace them. I've also
prepared a branch with the transitional packages removed.
This is needed by NetworkManager for versions past 0.8.
--
Sync isc-dhcp 4.1.1-P1-7 (universe) from D
Thanks for taking the time to report a bug and helping to make Ubuntu
better.
The goal I think is to provide reasonable support of VPNs in
NetworkManager, which is already largely achieved with the plugins in
universe as they are: they are pretty up to date (and a daily build is
available), and cl
Usually you'd mostly just want to use one or two different plugins,
since it's largely dependent on the environment and network setup. Is
there a reason I'm not thinking of where having a virtual package to
install all the VPN plugins be a benefit?
** Changed in: network-manager (Ubuntu)
St
Let's try again -- in lp:~network-manager/network-manager/ubuntu.head:
revno: 195
fixes bug(s): https://launchpad.net/bugs/348521
committer: Mathieu Trudel-Lapierre
branch nick: network-manager
timestamp: Wed 2010-07-14 23:38:09
I haven't seen this a single time on a new installation of Lucid in the
final release. Are there VPNs in use, or remote filesystems mounted,
etc. Any changes that could cause nm-dispatcher to fail to stop?
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Incomplete
** Changed i
Removing pcert tag -- this does not affect the certification labs as
described by Alex, it's an unrelated issue caused by eth0 being manually
configured in /etc/network/interfaces, thus ignored by NM
** Tags removed: pcert
--
Network manager icon does not appear in notification panel at startup
If you use a static IP in NetworkManager, but in the configuration for
eth0, under "Routes", click "Use this connection only for resources on
its network", is it any better? Enabling this should be keeping NM from
setting the default gateway to use eth0 when connected (and/or manually
configured).
Thanks for reporting a bug and helping to make Ubuntu better! In order
to better help you we would need some additional information:
- Does NetworkManager behave any differently if used with a secured wifi
connection?
- Please try to set your system, through "Restricted Drivers" under Settings,
** Tags added: nm-trunk
--
eth0 not allowed; Wireless gets no DNS
https://bugs.launchpad.net/bugs/601456
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/m
** Bug watch added: GNOME Bug Tracker #559134
https://bugzilla.gnome.org/show_bug.cgi?id=559134
** Also affects: network-manager via
https://bugzilla.gnome.org/show_bug.cgi?id=559134
Importance: Unknown
Status: Unknown
** Changed in: network-manager (Ubuntu)
Status: New =>
jarome,
So we can clarify what is happening at the NetworkManager level, could
you please run 'apport-collect 601456' after setting up your connection
with nameservers in resolv.conf? We need to see if there are any errors
in logs.
Also, for /etc/network/interfaces, it's perfectly fine; NetworkMa
*** This bug is a duplicate of bug 232172 ***
https://bugs.launchpad.net/bugs/232172
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it has
already been brought to the attention of the developers of the soft
** Tags added: likely-dup
--
nm-applet n'apparait dans la barre de notification
https://bugs.launchpad.net/bugs/597597
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://list
Public bug reported:
Recording using the internal microphone on a Dell Precision M6500 laptop
produces no sound. Even with the volume for capture cranked above 100%,
all that is retrieved is static, or a very faint sound (e.g. if tapping
near the mic).
ProblemType: Bug
DistroRelease: Ubuntu 10.04
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/51977983/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/51977984/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/51977985/BootDmesg.txt
** Att
Seems like it's much of an off and on thing: with the 20100714 image,
screen is extremely dark, and I can only faintly see the color of the
run dialog, for example. The screen is far too dark to distinguish text
or anything other than the light grey background of windows and dialogs.
--
[lucid] [
401 - 500 of 8571 matches
Mail list logo
