I see the same behavior.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1905467
Title:
[USB-Audio - Logitech Wireless Headset, playback] volume slider -
sound
Happens to me as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1572244
Title:
Kubuntu requires that the WiFi password be entered twice before WiFi
can be
I tried that already with no luck.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1558331
Title:
message "The repository is insufficiently signed by key (weak
digest)" is
Public bug reported:
I use qtcreator and when setting a breakpoint somewhere in the code
containing a local std::string gdb lock up and start eating memory
forever.
I'm sorry I can not provide any more details.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: gdb 7.10-1ubuntu2
Eduards - that is most likely a different issue. If you look closer you
will probably find that your network is not even listed in the
networklist. This bugreport is about systems that do not reconnect even
when the network is listed.
--
You received this bug notification because you are a
But #13 is not a solution - it's a workaround.
I changed to Debian becasue of this bug. I've never looked back. The bug
has been present for 5 months now.
Btw. is this still occurring in the current 15.04? If it is and it's not
fixed for the release this bug has potential to be present until
Please try #51 also
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1354924
Title:
Networkmanager does not autoconnect to wireless network
Status in
@tobiasBora: YEs only for the current session. But that something every
fix has in common - except for the Allow all users to access this
network-option.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
As state in a previous post: You can change whatever setting you'd like.
It does not have to be the auto-connection setting. You can even
change the IP-allocation policy from DHCP to Manual.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
The spelling is bad in #32 but the essence is that the problem persists
on Unity, so it is not a desktop related problem (KDE, Unity, etc)
The later comments just state that Debian Unstable works, and since
Ubuntu is based on Debian Unstable that might help people tracking down
what's wrong.
--
I take my previous comment back. Debian unstable also does this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1354924
Title:
Networkmanager does not autoconnect
Debian actually does not have this problem after all. does that help
anything?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1354924
Title:
Networkmanager
FWIT it works in debian unable
network-manager 0.9.10.0-3
plasma-nm0.9.3.4-2
plasma-widget-networkmanagement 0.9.3.4-2
--
You received this bug notification because you are a
Ok - these are the facts while trying out Ubuntu 14.10. I did not try
Kubuntu 14.10 from USB because the steps below results in the exact same
weirdnesses on the Kubuntu 14.10 install I have,
1. Create boot disk - reserve 1GB for storage.
2. Boot the from USB
3. Setup wifi - it connects.
4.
Hervé - you are right. I works as a software developer and this bug
would clearly be a blocker - meaning that we cannot realease until it's
resolved. Simple John Joe tpye of things must always work. I know little
of any about networkmanager, but given the right instructions I'd be
able to debug
I can not see that file on my system.
I have these files.
-rwxr-xr-x 1 root root 549 Jan 18 2013 000resolvconf
-rwxr-xr-x 1 root root 881 Dec 30 2013 avahi-autoipd
-rwxr-xr-x 1 root root 484 Dec 30 2013 avahi-daemon
-rwxr-xr-x 1 root root 1675 Jan 28 2014 ethtool
-rwxr-xr-x 1 root root
Public bug reported:
On binaries with a lot of symbols a massive performance degradation has
happened between 14.04 and 14.10
I have bisected the gdb performance degradation to this gdb commit
commit 5840bf271c87c3fc14739173fdc91c6a14057130 (refs/bisect/bad)
Author: H.J. Lu hjl.to...@gmail.com
To sum up.
1. New connections always reconnect.
2. After reboot connections does NOT reconnect.
3. Allowing all users to connect makes auto-connection work even after reboot.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
That makes me happy and sad at the same time. Happy because this bug is really
annoying and maybe it can get some attention, and sad because it's present in
14.10 and potentially a lot of users will now end up fight to get wireless
connecting.
--
You received this bug notification because you
I can add that flipping ipv5 setting to ignore and then back to
automatic makes auto connection work again. I do think that it is
needed for every reboot though. But it's a workaround.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Do you have a possibility to try kubuntu 14.10 installed from scratch.
Maybe some upgrade-path related issue is at stake here.
Also - I think this _must_ be resolved for 14.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Could you please check that the audio-setup in system-setting looks
alright (the correct name of the detected devices etc.). I remember
someone on IRC telling me that it had something to do with that. But
then again I might be wrong...
--
You received this bug notification because you are a
I believe that should be alright. As long as the audio-setup dialog does
not change appearance with the change it's ok. Alternatively I'll report
back if I notice any changes.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I reopened the bug since it's still present. My comment above is still
valid, but auto connecting stops working when suspending to ram or
rebooting. So basically the desired behavior can be obtained temporarily
by removing and adding the network in question.
** Changed in: network-manager
After getting KDE 4.14 I tired to remove all the wifi connections and
add them again. Now everything seems to be alright.
** Changed in: network-manager (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Do you have any good ideas as to what I could try out to figure out
what's wrong?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1354924
Title:
Networkmanager
Works on current 14.10 also. Good job juanmanuel !!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is started twice - effectively making
Public bug reported:
When adding a net wireless network and enable connect automatically'
networkmanager does not automatically connect to the network wenever
possible.
I'm running kubuntu 14.10 daily.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: network-manager 0.9.8.8-0ubuntu23
28 matches
Mail list logo