Knetworkmanager is finally ported to KDE4 as i can see at http://techbase.kde.org/Schedules/KDE4/4.4_Feature_Plan and many announcement. Also KDE SC 4.4 gives us Network Manager Plasmoid. But I can't find this packages in portage or kde-overlay. Reproducible: Always
Not released with 4.4.0, closing. http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=tree;f=kde-misc/knetworkmanager;h=0dbf78784c64e110ae1acee75307695505e703fb;hb=HEAD
tampakrap promised to create snapshots, reopening
@Samuli: I don't think we should do our own snapshot. We should bash uspstream to release one since they promised to do so :]
faik the upstream plan is to be released in kdenetwork and not in extragear. It was supposed to be released in 4.4 but didn't make it, so it still resides in kdereview. It seems to work in my desktop, I'll try the snapshots and report back, but this will happen next week as i am still in devaway
(In reply to comment #4) Thanks, we'll wait...
I have added 4.4.0_p20050225 in kde overlay. keep in mind that it doesn't work here, it is crashy and can't connect to my wireless network. Please test. @dagger please take a look at it (CCing you just to let you know about this)
Knetworkmanager is still under heavy development and is not really usable. It does work, but as you mentioned - it's crashy and not all functionality is working. Hope they get it fully working before 4.5
following dagger's recommendation in irc, i added knetworkmanager in tree hardmasked. please test
it seems to work with networkmanager >0.8. I'd like some feedback on this, because if this was the issue i can unmask it in tree.
try with networkmanager-0.8 build failed [100%] Building CXX object monolithic/CMakeFiles/knetworkmanager.dir/connectioninfowirelesstab.o Linking CXX executable knetworkmanager [100%] Built target knetworkmanager make: *** [all] Ошибка 2 * ERROR: kde-misc/knetworkmanager-4.4.0_p20100225 failed: * Make failed! * * Call stack: * ebuild.sh, line 54: Called src_compile * environment, line 3813: Called kde4-base_src_compile * environment, line 2905: Called cmake-utils_src_compile * environment, line 1035: Called _execute_optionaly 'src_compile' * environment, line 457: Called enable_cmake-utils_src_compile * environment, line 1410: Called cmake-utils_src_make * environment, line 1054: Called die * The specific snippet of code: * emake "$@" || die "Make failed!"; * * If you need support, post the output of 'emerge --info =kde-misc/knetworkmanager-4.4.0_p20100225', * the complete build log and the output of 'emerge -pqv =kde-misc/knetworkmanager-4.4.0_p20100225'. * The complete build log is located at '/var/tmp/portage/kde-misc/knetworkmanager-4.4.0_p20100225/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/kde-misc/knetworkmanager-4.4.0_p20100225/temp/environment'. * S: '/var/tmp/portage/kde-misc/knetworkmanager-4.4.0_p20100225/work/knetworkmanager-4.4.0_p20100225' log in attach
Created attachment 221647 [details] emerge --info =kde-misc/knetworkmanager-4.4.0_p20100225
Created attachment 221649 [details] emerge -pqv =kde-misc/knetworkmanager-4.4.0_p20100225
Created attachment 221653 [details] build.log
Created attachment 221657 [details] environment
(In reply to comment #14) > Created an attachment (id=221657) [details] > environment > It compiles and installs here fine: ~amd64 running KDE 4.4. The only thing that it doesn't do it fix my problem where NM 0.8 does not seem to play well with either Solid or KNetworkManager because NM does not get the network configurations from KDE...
try to reemerge dbus with LDFAGS="" emerge -1 dbus (In reply to comment #15) > (In reply to comment #14) > > Created an attachment (id=221657) [details] [details] > > environment > > > It compiles and installs here fine: ~amd64 running KDE 4.4. The only thing that > it doesn't do it fix my problem where NM 0.8 does not seem to play well with > either Solid or KNetworkManager because NM does not get the network > configurations from KDE... >
(In reply to comment #16) > try to reemerge dbus with > LDFAGS="" emerge -1 dbus > I will try that in the morning. On a side note: it appears I had NM 0.7.2 still installed so I just upgraded to 0.8.0 and compiled Solid and KNM again (it compiled fine again) - still no dice. 'cnetworkmanager' can set up manual connections just fine so it appears to be an issue with the way KDE 4.4 (through Solid?) shares its network configurations.
I've noticed that knetworkmanager fails to compile on some gsm modules. So I reemerged networkmanager without bluetooth support and successfully emerged knetworkmanager. My results (~amd64, kernel 2.6.32, networkmanager-0.8): Successfully connect to eth0 and wifi WPA2 Personal. When I add plasmoid to desktop, plasma is crashed. Fails to connect to WPA2 Enterprise wifi because knetworkmanager looses settings to CA certs and always set it to "Use system CAs certs" Same behaviour (loose settings) when i connect to eth0 with 802.1x security, but sometimes it works. Waiting for new snapshots, may be it'll resolve my problems :)
new snapshot in da house, please test
Successfully compiled with bluetooth use flag. Other problems aren't solved. I've reported some bugs to bugs.kde.org
Does anyone know if it is intentional not to show available wireless networks even when `iwlist wlan0 scanning` (e.g.) shows them all and no error/warning message to be placed anywhere? Is there any of you *successfully* using knetworkmanager with capabilities to select available APs by clicking on the try icon (just like possible with other gnome tray frondends and (somehow) wpa_supplicant's wpa_gui)?
(In reply to comment #21) I had a similar problem, just rebuilding dbus worked out! hand saft
(In reply to comment #7) > Knetworkmanager is still under heavy development and is not really usable. It > does work, but as you mentioned - it's crashy and not all functionality is > working. > > Hope they get it fully working before 4.5 > I just replaced Wicd with KNetworkManager on my laptop and so far I have no problems. I used it to connect to my wireless network and the connection went without issue. Here is my emerge --info: $ emerge --info Portage 2.1.8.3 (default/linux/x86/10.0, gcc-4.4.3, glibc-2.11.1-r0, 2.6.33.4 i686) ================================================================= System uname: Linux-2.6.33.4-i686-Genuine_Intel-R-_CPU_T2400_@_1.83GHz-with-gentoo-2.0.1 Timestamp of tree: Sun, 16 May 2010 16:00:02 +0000 ccache version 2.4 [enabled] app-shells/bash: 4.1_p5 dev-java/java-config: 2.1.11 dev-lang/python: 2.6.5-r2, 3.1.2-r3 dev-util/ccache: 2.4-r8 dev-util/cmake: 2.8.1-r1 sys-apps/baselayout: 2.0.1 sys-apps/openrc: 0.6.1-r1 sys-apps/sandbox: 2.2 sys-devel/autoconf: 2.13, 2.65 sys-devel/automake: 1.8.5-r4, 1.9.6-r3, 1.10.3, 1.11.1 sys-devel/binutils: 2.20.1-r1 sys-devel/gcc: 4.4.3-r2 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 2.2.6b virtual/os-headers: 2.6.33 ACCEPT_KEYWORDS="x86 ~x86" ACCEPT_LICENSE="*" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=prescott --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=2048 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/X11/xkb /usr/share/config /var/lib/hsqldb" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c" CXXFLAGS="-O2 -march=prescott --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=2048 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="assume-digests buildpkg ccache distlocks fixpackages news parallel-fetch protect-owned sandbox sfperms strict unmerge-logs unmerge-orphans userfetch" FFLAGS="-O2 -march=prescott --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=2048 -pipe -fomit-frame-pointer" GENTOO_MIRRORS="http://mirror.csclub.uwaterloo.ca/gentoo-distfiles/ http://gentoo.netnitco.net http://distro.ibiblio.org/pub/linux/distributions/gentoo/" LDFLAGS="-Wl,-O1" LINGUAS="en" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/var/lib/layman/sunrise /var/lib/layman/vmware /var/lib/layman/java-overlay /usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X acpi alsa apm berkdb bzip2 cdr cli consolekit cracklib crypt cups cxx dbus dri dvd dvdr fftw fortran gd gdbm gif gnutls gpm hal iconv ipv6 java java6 jpeg kde lzma midi mmap mmx mng modules mp3 mudflap ncurses networkmanager nptl nptlonly nsplugin opengl openmp pam pcre perl png pppd python qt3 qt3support qt4 readline reflection samba session spl sqlite sse sse2 sse3 ssl svg sysfs tcpd threads tiff unicode vorbis x264 x86 xml xorg xvmc zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="evdev synaptics" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en" NETBEANS_MODULES="*" RUBY_TARGETS="ruby18" USERLAND="GNU" VIDEO_CARDS="nvidia" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS I noticed the net-misc/networkmanager-0.8-r1 is out and the latest snapshot is from March 31st. Perhaps some combination of the two resolved the problems you were seeing, because I cannot reproduce them on my system.
Any chance of having this at all (even M~) on ppc or ~ppc ?
(In reply to comment #24) > Any chance of having this at all (even M~) on ppc or ~ppc ? > You can try forcing it to install on ppc. This is off the top of my head, but you can try the following commands: echo "kde-misc/knetworkmanager ~*" >> /etc/portage/package.keywords echo "kde-misc/knetworkmanager" >> /etc/portage/package.umask The first command should unkeyword the package, despite it not being available on your architecture. The second should unmask it, assuming that the mask applies to your architecture considering that it is not supposed to run on your architecture according to the ebuild. At that point, it should be available for installation on your system. Please report back with whether or not this worked.
I seem to have made a small typo. The second command should be: echo "kde-misc/knetworkmanager" >> /etc/portage/package.unmask I omitted a letter in the file name by mistake.
(In reply to comment #21) > Does anyone know if it is intentional not to show available wireless networks > even when `iwlist wlan0 scanning` (e.g.) shows them all and no error/warning > message to be placed anywhere? Try removing the state file in /var/lib/NetworkManager/NetworkManager.state (mine occasionally jumps to disabled networking after updates - no clue how or why). > Is there any of you *successfully* using knetworkmanager with capabilities to > select available APs by clicking on the try icon (just like possible with other > gnome tray frondends and (somehow) wpa_supplicant's wpa_gui)? Yes, KNetworkManager preselects the correct security on my laptop although I am using a build of last weeks SVN. KDE 4 seems to have the same configuration panels but does not select the correct options for some reason. On a side note: I am currently using KNM to connect to a enterprise 802.x network (Secure2W) using TTLS and PAP without problems.
> You can try forcing it to install on ppc. This is off the top of my head, but > you can try the following commands: > [...] > Please report back with whether or not this worked. In ~/.xsession-errors: knetworkmanager(2476)/kdecore (KLibrary) kde4Factory: The library "/usr/lib/kde4/solid_networkmanager07.so" does not offer a qt_plugin_instance function and the knetworkmanager icon in the system tray has just one item on its pop-up menu: "networking disabled". I'm happy to work with you on this so if you want to stabilise this on ppc, shall we take it to private email ? One big caveat is that ppp seems to be unstable for me, frequently locking-up the machine, so I'm not sure how much I can do.
(In reply to comment #28) > > You can try forcing it to install on ppc. This is off the top of my head, but > > you can try the following commands: > > [...] > > Please report back with whether or not this worked. > > In ~/.xsession-errors: > > knetworkmanager(2476)/kdecore (KLibrary) kde4Factory: The library > "/usr/lib/kde4/solid_networkmanager07.so" does not offer a qt_plugin_instance > function > > and the knetworkmanager icon in the system tray has just one item on its pop-up > menu: "networking disabled". > > I'm happy to work with you on this so if you want to stabilise this on ppc, > shall we take it to private email ? One big caveat is that ppp seems to be > unstable for me, frequently locking-up the machine, so I'm not sure how much I > can do. > That ~/.xsession_errors message is something that appears on x86 and is unrelated to your "networking disabled" message. I filed bug #321243 a while ago about it. As for your current issue, it sounds like bug #212724. Try running "emerge -1 dbus". That should fix it for you.
(In reply to comment #28) > In ~/.xsession-errors: > > knetworkmanager(2476)/kdecore (KLibrary) kde4Factory: The library > "/usr/lib/kde4/solid_networkmanager07.so" does not offer a qt_plugin_instance > function Its the same on amd64 - still works fine over here. > > and the knetworkmanager icon in the system tray has just one item on its pop-up > menu: "networking disabled". Remove /var/lib/NetworkManager/NetworkManager.state, restart NetworkManager and KNM and it should work again. Try looking in that file first: I bet it says "Networking: false" or similar.
(In reply to comment #30) > (In reply to comment #28) > > In ~/.xsession-errors: > > > > knetworkmanager(2476)/kdecore (KLibrary) kde4Factory: The library > > "/usr/lib/kde4/solid_networkmanager07.so" does not offer a qt_plugin_instance > > function > Its the same on amd64 - still works fine over here. > > > > and the knetworkmanager icon in the system tray has just one item on its pop-up > > menu: "networking disabled". > Remove /var/lib/NetworkManager/NetworkManager.state, restart NetworkManager and > KNM and it should work again. > > Try looking in that file first: I bet it says "Networking: false" or similar. > That is usually only an issue when Networking has been disabled by going into standby mode or hibernation where you do not cleanly resume, in which case, he could run the following to fix it: dbus-send --print-reply --system --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.wake Since he just installed KNetworkManager, this sounds more like bug #212724 to me, in which case he needs to reinstall dbus. The cause of bug #212724 is not well understood at the moment, but it appears to be an upstream issue (as far too many issues in dbus I am discovering are) and it seems to have something to do with timestamps. A warning probably should be added to the NetworkManager ebuild to suggest reinstalling dbus as per recommendations in bug #212724 if it shows a "Networking Disabled" message immediately following installation, although that is not an issue specific to KNetworkManager itself. I would like to observe that since the network stack consists of the device drivers, the kernel, wpa_supplicant, networkmanager and knetworkmanager, with communication in the upper levels of the stack over dbus, an issue in one component often appears to be an issue in another component. :/
(In reply to comment #29) > (In reply to comment #28) > > [...] > That ~/.xsession_errors message is something that appears on x86 and is > unrelated to your "networking disabled" message. I filed bug #321243 a while > ago about it. As for your current issue, it sounds like bug #212724. Try > running "emerge -1 dbus". That should fix it for you. It does. Thank you very much. I'm replying on my superduper new ppc 1920x1200 screen desktop rather than my pokey little keyhole laptop screen. ppc connected to the interwebs thingy via my 3G stick. My offer stands: if you need ppc testing done, I'm still available.
(In reply to comment #32) > (In reply to comment #29) > > (In reply to comment #28) > > > [...] > > That ~/.xsession_errors message is something that appears on x86 and is > > unrelated to your "networking disabled" message. I filed bug #321243 a while > > ago about it. As for your current issue, it sounds like bug #212724. Try > > running "emerge -1 dbus". That should fix it for you. > > It does. Thank you very much. I'm replying on my superduper new ppc 1920x1200 > screen desktop rather than my pokey little keyhole laptop screen. ppc > connected to the interwebs thingy via my 3G stick. > > My offer stands: if you need ppc testing done, I'm still available. > Thankyou for your offer, but I am neither one of Gentoo's or KDE's developers. I am computer science student and I started using Gentoo Linux this past January because I wanted to learn about how software works on a more practical level than I would otherwise learn in my computer science classes. I am sure that Gentoo's developers would be happy to have your assistance. A bug report probably is not the place to volunteer, as it does not get much attention. You probably would want to post your offer on the Gentoo forums, most likely in the Gentoo chat forum: http://forums.gentoo.org/viewforum-f-7.html
> > My offer stands: if you need ppc testing done, I'm still available. > Best is probably if you join at the IRC channels, maybe #gentoo-powerpc or #gentoo-kde :) Here's more info about the powerpc people: http://www.gentoo.org/proj/en/base/ppc/index.xml
Is it possible to get a newer snapshot added? you can find it now under: http://websvn.kde.org/trunk/extragear/base/networkmanagement/ A commit says "The plan is to do a couple of independent releases, and then with 4.7 move to kdebase as networkmanagement should be really mature by then." thanks in advance
I bumped it yesterday and I am going to unmask it in a week if everything is ok. Please test and report any problems about it, with both KDE 4.4.5 and 4.5.0. Thanks
The knetworkmanager program no longer auto-starts with KDE. If you try starting it, it will say: "Another NetworkManager client is already running. Use KNetworkManager in future?" I used "qdbus org.kde.kded /kded loadedModules" to see that a network management module was already loaded, so I did some poking around and found a KDE plasmoid that I had to add to my panel to get things to work. It has a much nicer interface, but it fails to autoconnect to wireless networks when I start my system. Aside from those issues, the ebuild works.
(In reply to comment #37) > The knetworkmanager program no longer auto-starts with KDE. If you try starting > it, it will say: > > "Another NetworkManager client is already running. > Use KNetworkManager in future?" > > I used "qdbus org.kde.kded /kded loadedModules" to see that a network > management module was already loaded, so I did some poking around and found a > KDE plasmoid that I had to add to my panel to get things to work. It has a much > nicer interface, but it fails to autoconnect to wireless networks when I start > my system. > > Aside from those issues, the ebuild works. > I had to modify my wireless configuration settings to get it to auto start. For some reason, it had my WPA2 key and would connect when I manually asked it, but it did not know what my WPA2 key was in the configuration settings, which seems to have kept it from autoconnecting. Anyway, I have that resolved now and it autoconnects without issue. I suspect that my issues were caused by changes in the file formats, so it might be wise to recommend that users of the old knetworkmanager ebuild wipe their wireless settings after upgrading and start fresh.
This software seems to be overzealous when it comes to maintaining a connection. If you have it set to auto-connect to a wireless network in range, you are already connected and you tell it to disconnect, it will reconnect right after the disconnection was made, which is not exactly the sort of behavior I would like, especially when I have multiple wireless adapters and I want to test sending packets over on rather than the other. Killing wireless will not work there, but killing the connection should, however, this is probably a problem for upstream. Also, a while back I tried upgrading the version of knetworkmanager to a more recent version from the SVN. I specifically wanted the version that OpenSUSE 11.3 was using upon release (because it was well tested), and while portage uses a date of SVN checkout as the version number, OpenSUSE is using a SVN revision number as the version number, which confused me. I eventually figured out how to use the 9999 ebuild, but unfortunately, I never noticed the network manager plasmoid so I thought something was broken in the SVN and I went back to the in-tree version. Anyway, OpenSUSE 11.3 calls its package "NetworkManager-kde4-0.9.svn1057339-4", which can be found at the following url: http://en.opensuse.org/Package_list Ubuntu is also using the svn revision number as the version number for its packages: http://packages.ubuntu.com/lucid/network-manager-kde In the hypothetical event that someone finds that the version on Gentoo suffers from some bug, but the version used by X distribution does not, figuring out which is newer or older and how one can be changed to match the other for debugging purposes is a pain with the current version numbering scheme. If the version numbering was changed to match the scheme taht other distributions are using, it would make this sort of thing much easier.
Hi Richard, (In reply to comment #37) ... It has a much > nicer interface, but it fails to autoconnect to wireless networks when I start > my system. > > Aside from those issues, the ebuild works. > You might want to try 0.8.1. Version in portage can understand your standard Gentoo configuration. So if you configured your /etc/conf.d/net and/or /etc/wpa_supplicant/wpa_supplicant.conf - it will read it and enable system wide settings before you login to any DE. R
I am now using the Network Manager Plasmoid and I have been encountering out of sync issues with the Network Manager Plasmoid. One issue that occurred today is that whenever I would log into KDE, the plasmoid would indicate that the network interfaces were unmanaged. "Enable networking" was unchecked and "Enable wireless" was checked. Checking "Enable networking" would not fix it and it would forget that I had it checked if I relogged. Doing "sudo touch /etc/NetworkManager/nm-system-settings.conf" made Network Manager manage the interfaces again. I have net-misc/networkmanager-0.8.1-r6 installed and that configuration file is stock as far as I know. The issue turned out to be that "/var/lib/NetworkManager/NetworkManager.state" had "NetworkingEnabled=false". Changing that to "NetworkingEnabled=true" fixed the problem. This issue manifested itself when I was troubleshooting an unrelated issue regarding my VPN connection. I was not sure if the network manager was causing the issue, so I had unchecked "Enable networking" and "Enable wireless". I proceeded to do troubleshooting via the commandline where I would pull down the network interface, bring it up, tell it to associate with an access point and then try doing the VPN connection over it. At some point along the way of doing this, the NetworkManager.state file changed and the settings stuck. Both "Enable networking" and "Enable wireless" were initially unchecked, but I somehow managed to get "Enable wireless" to stay checked once I checked it after several tries, although I have no idea why it obeyed my wishes after so many tries while "Enable networking" did not. Another issue that occurs is when I want to connect to a new wireless network. If I try doing it via the Plasmoid, no matter what I do, it will not connect. The "Manage Connections" dialog never stores the information I enter when I try to connect to a network via the plasmoid, even though I basically go through the same dialog to connect to a network as I do when I manually configure a network inside the plasmoid. When I try specifying the wireless network's information in the "Manage Connections" dialog, then attempts to connect via the plasmoid work. One last issue that I have is possibly related to the second issue, possibly in a cause and effect relationship. Basically, if I delete ~/.kde4/share/config/networkmanagementrc and restart, the "Manage Connections" dialog's networks have been cleared, but when I try connecting to a network that I have used in the past (e.g. one with encryption), the plasmoid will remember my encryption information. I might be doing something wrong in that I am missing a configuration file, but I cannot find where else this information would be stored. I have done this a few times to try to resolve issues with the plasmoid and I think that it might be related to the second issue I had above.
I also have a few more things to report. The first is that since Network Manager does not appear to be logged to anything by default, figuring out the causes of problems with the Network Management Plasmoid that I encounter is very difficult. The second is that my second issue in #41 appears to be related to the following person's issue: http://chakra-project.org/bbs/viewtopic.php?id=922 I found it in one of the google searches I did before I found a page that described a fix for the first issue I encountered in #41. That page was the following: https://bbs.archlinux.org/viewtopic.php?id=102365
The ebuild is now unmasked in portage, please file separate bugs for any problems and try to avoid reporting upstream bugs to us. The snapshot will get updates every two weeks. Thanks to anyone involved
(In reply to comment #43) > The ebuild is now unmasked in portage, please file separate bugs for any > problems and try to avoid reporting upstream bugs to us. The snapshot will get > updates every two weeks. Thanks to anyone involved > Would it be inappropriate to report an issue with the ebuild here? There is a file collision with =kde-base/kdebase-desktoptheme-4.5.1. Both of them try to install /usr/share/apps/desktoptheme/default/icons/network.svgz and I had to modify the ebuild to resolve the collision. I added this small snippet of code to it which made it work: pkg_preinstall() { rm ${D}/usr/share/apps/desktoptheme/default/icons/network.svgz }
