[Bug 366780] Re: Please provide a mechanism whereby Wi-Fi networks can be prioritized
Launchpad has imported 6 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=194101. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2009-05-26T01:06:14+00:00 M-wege wrote: Version:(using KDE 4.2.3) Installed from:Ubuntu Packages The networkmanager applet should offer to sort the configured networks by priorities and connect to the one with the highest priority. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/366780/comments/1 On 2009-08-04T09:04:46+00:00 X-wstephenson wrote: The new logic is: In the main popup, only show connections that are currently connectable - eg there is a configuration for this network and the access point(s) providing this is currently found via scan. Networks that are configured but where the access point is not present are not shown. The other, unconfigured scanned networks are in a submenu. Is this an acceptable prioritisation? Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/366780/comments/4 On 2009-08-04T09:17:25+00:00 M-wege wrote: Actually I a meant something different. I want the list of already configured networks sorted by priority, no matter if they are available or not. For example I want to put cable network as first. If cable is available then disconnect wireless. If I have the choice between Wireless A and B, B is my choice and so on Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/366780/comments/5 On 2009-08-04T09:59:54+00:00 X-wstephenson wrote: It's not possible with NetworkManager - the policies the daemon uses are quite inflexible. The only way you can influence this is to set some connections as 'never default' (which sucks when the cable connection is not present) or change the timestamp on wireless connection B so it is newer than A and NM will prefer it. It also tries to keep as many 'connect automatically' connections up as possible so the 'disable wireless when connected to cable' idea is not possible. Sorry. Please try and convince NM to add client policy control and then I'lll implement it in the KDE UI. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/366780/comments/6 On 2009-08-19T11:03:52+00:00 M-wege wrote: Bug has been reported upstream. http://bugzilla.gnome.org/show_bug.cgi?id=580018 Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/366780/comments/7 On 2009-11-28T19:42:18+00:00 Hbarmeter76 wrote: I'd like to add that I experience a related (annoying) behavior (I am not sure if I should submit this as bug or here): If two wireless networks have been configured with autoconnect, knetworkmanager seems to choose the weaker connection instead of the stronger - this should be fixed. Is this also an issue of nm policies? Please advice if I should file a bug report elsewhere. Thank you! Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/366780/comments/9 ** Changed in: plasma-widget-networkmanagement Status: Unknown => Won't Fix ** Changed in: plasma-widget-networkmanagement Importance: Unknown => Wishlist -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to networkmanagement in Ubuntu. https://bugs.launchpad.net/bugs/366780 Title: Please provide a mechanism whereby Wi-Fi networks can be prioritized To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/366780/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
Regarding #51: in today's 14.10 daily I was affected by the same problem. I copied /usr/lib/syslinux/gfxboot.c32 from my 14.04 system into the usb /syslinux and it now boots fine. This is 14.10 Ubuntu 64. The boot disk was created on a 14.04 Ubuntu 64 system, up to date, with usb-creator-gtk. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1381042] [NEW] No networking after suspend and resume
You have been subscribed to a public bug by Paul White (paulw2u): I started having problems with suspend and resume after upgrading to kernel 3.13.0-37. Resume takes a long time, suspend sometimes takes me to the log in screen and I have no networking after resuming (I need to restart Network Manager). I am running Ubuntu 14.04 (64 bit) on a DELL XPS 13 (full HD, Intel GPU) notebook. Everything works fine with kernel 3.13.0-36. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Tue Oct 14 09:19:50 2014 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-04-27 (170 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.25.1 dev wlan0 proto static 192.168.25.0/24 dev wlan0 proto kernel scope link src 192.168.25.2 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CC:07:AB:0D:ED:A4 bluetooth disconnected /org/freedesktop/NetworkManager/Devices/3 9C:65:B0:BF:D2:55 bluetooth disconnected /org/freedesktop/NetworkManager/Devices/2 30:19:66:26:90:06 bluetooth disconnected /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug kubuntu trusty utopic -- No networking after suspend and resume https://bugs.launchpad.net/bugs/1381042 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 366780] Re: Please provide a mechanism whereby Wi-Fi networks can be prioritized
Well, the fix must be released, and the fixed version be included into Ubuntu. Be awere that this is just a feature implemented with an API in the Network manager core with an API, so clients like nm-applet must expose this functionality for it to be easily used. ** Also affects: networkmanagement (Ubuntu) Importance: Undecided Status: New ** Bug watch added: KDE Bug Tracking System #194101 https://bugs.kde.org/show_bug.cgi?id=194101 ** Also affects: plasma-widget-networkmanagement via https://bugs.kde.org/show_bug.cgi?id=194101 Importance: Unknown Status: Unknown ** Also affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to networkmanagement in Ubuntu. https://bugs.launchpad.net/bugs/366780 Title: Please provide a mechanism whereby Wi-Fi networks can be prioritized To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/366780/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1382184] [NEW] IPP printing stopped working after 12.10
Public bug reported: I have a Brother Printer that is connected to my NAS and which I could print to in 11.10, 12.04 and 12.10. I'm using a Brother printer driver from the Brother page. After upgrading one of my PCs to 13.04 it stopped working, ever since (13.10, 14.04) I cannot print over IPP anymore. When I connect it straight to the Notebook per USB the printer works fine though. As I'm sitting right next to my printer with this notebook most of the time, I always hoped that it will be fixed in another release and lived with it to plug the cable into the pc whenever needed. For that reason my other notebook is still running on 12.10, it is still printing fine and I refuse to update it, as my wife wouldn't be happy if she'd had to plug in the usb cable each time. I had several attempts and fresh installs on my other notebook and spent after each release upgrade several hours to try to get it working again, but couldn't get it working ever since. I checked into every detail and compared the setup between the 2 computers thinking I must have missed something, but I couldn't find anything. When I print over IPP on 14.04 it just prints several blank papers until I cancel it. My connection setting that works on 12.10 but not on 13.04 upwards: ipp://nas:631/printers/NASPR2 Driver: Brother DCP7030 for CUPS My distro is Kubuntu ** Affects: kde-workspace (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1382184 Title: IPP printing stopped working after 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1382184/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1362750] Re: qt and gtk themes not set up by default
installing plasma5 image today, qt4 and 5 both good for everything, gtk 2 and 3 both unthemed -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to Kubuntu PPA. https://bugs.launchpad.net/bugs/1362750 Title: qt and gtk themes not set up by default To manage notifications about this bug go to: https://bugs.launchpad.net/kubuntu-ppa/+bug/1362750/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1382096] [NEW] on upgrade old plasma xsession file still default
Public bug reported: 16:06 < seaLne> some thing i noticed when trying plasma 5 was that after installing it and rebooting lightdm was trying to use last session which just left you with just the 4.14 or lightdm background after logging in which resulted in it appearing to me that 5 didn't work at all which was disapointing and may have put others off. rather than when i changed manually to a plasma session from the login i got lots of 16:06 < seaLne> nice shiny plasma 5 working. not sure if there is any way to fix that. sorry if this has already been seen before 16:07 < seaLne> i guess its a failure on lightdm's part ** Affects: kubuntu-ppa Importance: Undecided Status: New ** Tags: plasma5 ** Tags added: plasma5 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to Kubuntu PPA. https://bugs.launchpad.net/bugs/1382096 Title: on upgrade old plasma xsession file still default To manage notifications about this bug go to: https://bugs.launchpad.net/kubuntu-ppa/+bug/1382096/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1358271] Re: Eclipse crashes with 'oxygen-gtk' theme enabled
I confirm the "new project" dialog leads a crash due to an not fulfilled assertion. "java: /build/buildd/gtk2-engines- oxygen-1.4.5/src/animations/oxygencomboboxdata.cpp:87: void Oxygen::ComboBoxData::setButton(GtkWidget*): assertion »!_button._widget« not met " https://bugzilla.redhat.com/show_bug.cgi?id=1053565#c15 this is fixed in upstream and should be released soon. ** Bug watch added: Red Hat Bugzilla #1053565 https://bugzilla.redhat.com/show_bug.cgi?id=1053565 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to gtk2-engines-oxygen in Ubuntu. https://bugs.launchpad.net/bugs/1358271 Title: Eclipse crashes with 'oxygen-gtk' theme enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-oxygen/+bug/1358271/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1347397] Re: Kmix won't start Kubuntu 14.04
I have the same problem: Launching Kmix I got: :~$ kmix QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. Fully upgraded Kubuntu 14.04 (October Equipment: computer descripción: Notebook producto: TECRA R950 (PT534E) fabricante: TOSHIBA versión: PT534E-04F025CE serie: [REMOVED] anchura: 32 bits capacidades: smbios-2.5 dmi-2.5 configuración: administrator_password=disabled boot=normal chassis=notebook family=00 frontpanel_password=disabled keyboard_password=disabled power-on_password=disabled sku=PT534E uuid=[REMOVED] *-core descripción: Placa base producto: TECRA R950 fabricante: TOSHIBA id físico: 0 versión: Version A0 serie: [REMOVED] ranura: Center *-firmware descripción: BIOS fabricante: TOSHIBA id físico: 0 versión: Version 6.80 date: 06/25/2013 tamaño: 128KiB capacidad: 8128KiB capacidades: isa pci pnp upgrade shadowing vesa cdboot bootselect edd int13floppytoshiba int13floppy720 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification netboot *-memory descripción: Memoria de sistema id físico: 1f ranura: Placa de sistema o placa base tamaño: 8GiB *-cpu descripción: CPU producto: Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz fabricante: Intel Corp. id físico: 25 información del bus: cpu@0 versión: 6.10.9 serie: [REMOVED] ranura: Socket rPGA988B tamaño: 1200MHz capacidad: 1200MHz anchura: 64 bits reloj: 100MHz capacidades: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms cpufreq configuración: cores=2 enabledcores=2 id=1 threads=4 *-multimedia descripción: Audio device producto: 7 Series/C210 Series Chipset Family High Definition Audio Controller fabricante: Intel Corporation id físico: 1b información del bus: pci@:00:1b.0 versión: 04 anchura: 64 bits reloj: 33MHz capacidades: pm msi pciexpress bus_master cap_list configuración: driver=snd_hda_intel latency=0 recursos: irq:46 memoria:e073-e0733fff :~$ ps aux | grep dbus message+ 891 0.0 0.0 5332 2268 ?Ss 10:26 0:00 dbus-daemon --system --fork nobody1734 0.0 0.0 6836 1484 ?S10:27 0:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid --listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf --cache-size=0 --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d ciberde+ 2268 0.0 0.0 3856 544 ?S10:27 0:00 dbus-launch --autolaunch=da9f2ce52a86f1eb9ba1751b5364a002 --binary-syntax --close-stderr user+ 2269 0.0 0.0 4240 1060 ?Ss 10:27 0:00 //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session user+ 2289 0.0 0.0 4844 1784 ?Ss 10:27 0:00 dbus-daemon --fork --session --address=unix:abstract=/tmp/dbus-1bkueByiB4 user+ 2310 0.0 0.0 6180 340 ?S10:27 0:00 upstart-dbus-bridge --daemon --system --user --bus-name system user+ 2312 0.0 0.0 6180 340 ?S10:27 0:00 upstart-dbus-bridge --daemon --session --user --bus-name session user+ 2358 0.0 0.0 4240 1672 ?S10:27 0:00 /bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3 root 2701 0.0 0.0 14024 7456 ?S10:27 0:00 /usr/bin/python /usr/share/apt-xapian-index/update-apt-xapian-index-dbus Best regards -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kmix in Ubuntu. https://bugs.launchpad.net/bugs/1347397 Title: Kmix won't start Kubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmix/+bug/1347397/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
