For anyone who likes to test our upcoming rolling release RC3 to report bugs, here is your chance:
http://sourceforge.net/projects/netrunneros/files/netrunner-rolling/netrunner-rolling-2015.11-rc3-x86_64.iso/download
Have fun! 
Hi,
Installed on Asus X99 Deluxe hyperx predator 240 gb / Nvidia 780TI!
Went very well, had only a minor glitch with black screen on first boot.
Had to perform a logout and login to get to the DE.
Installed also a couple of games and had no trouble so far.
I will continue to test but so far nice job!
Installed here without a hitch and, unlike 2015.09, there have been no video issues with the nVidia drivers.
One bug to report:
Every time I add a widget to the Panel, my desktop changes from “Desktop” to “Netrunner Desktop” but this also happens with 2015.09
One observation:
The launcher icons on the Panel are too close together and I can’t see a way of changing the spacing:
[attachment=788]
The Nvidia driver has been downgraded upstream by Manjaro, this was because of major issues reported with the latest coming from Nvidia. Adding a widget to the panel should not effect the desktop containment, I could not replicate this behavior. Launcher icons are part of the task manager, there is currently no way of adjusting the spacing there. However, my icons are not appearing that close together.
[attachment=789]
Did you by chance keep your home directory between installs?
I have the desktop containment issue on other distros and I’m wondering if it could be something to do with running dual monitors?
Just done an experiment to try and fix the icon spacing issue and I’ve discovered that if I “Add to Panel” instead of “Add as Launcher”, the icons are better spaced:
[attachment=790]
I never have a separate Home partition so the answer to that one is “No”, as I did the install on a new partition.
Since I don’t have a system setup with dual monitors you could be right. Add to panel creates separate icon widget for each one so they would be spaced out differently, and even if those were to close together you would only need to add a spacer widget and adjust it. I wonder if this one might just be a display resolution issue? If your other display has a longer horizontal length, try moving the panel to that display and see if they space out better.
Kde crashed…
Executable: plasmashell PID: 3762 Signal: Segmentation fault (11) Time: 08/11/2015 14:46:02
3762 0.7 1.0 268571624 338360 ? Tl 14:36 0:11 /usr/bin/plasmashell --shut-up
Was testing samba connections to my server in Yakuake.
Weird behavior!
I’ve had samba shares crash dolphin before, but so far not the shell. While testing were you pinging the shares, copying files to and from them, what exactly where you doing when it crashed? Were there any other applications running that might have been the cause of the crash? Some widgets also have a tendency to crash Plasmashell as well, did it recover from the crash? Could you post your .xsession-errors log file?
I was doing an ls of a remote sambashare
smbclient \\DEVIL\Downloads test
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 4.1.6-Ubuntu]
smb: > ls
Had Firefox and an open dolphin running in the background!
It did also recover from the crash!
.xsession-errors log from crash :
[code]yakuake(3785)/kdecore (KLibrary) findLibraryInternal: plugins should not have a ‘lib’ prefix: “libkonsolepart.so”
yakuake(3785)/konsole Konsole::Session::run: Attempted to re-run an already running session.
(process:4270): GLib-CRITICAL **: g_slice_set_config: assertion ‘sys_page_size == 0’ failed
no winId: probably startup task
KActivitiesStats( 0x1d7d410 ) ResultModel::Private::onResultAdded result added: “/home/papa/Documents/Kde_Crash_08_11_2015” score: 0 last: 1446991644 first: 1446991644
KActivitiesStats( 0x16ee560 ) ResultModel::Private::onResultAdded result added: “/home/papa/Documents/Kde_Crash_08_11_2015” score: 0 last: 1446991644 first: 1446991644
KActivitiesStats( 0x15e8d90 ) ResultModel::Private::onResultAdded result added: “/home/papa/Documents/Kde_Crash_08_11_2015” score: 0 last: 1446991644 first: 1446991644
KActivitiesStats( 0x1d7d410 ) ResultModel::Private::onResultAdded result added: “/home/papa/Documents/Kde_Crash_08_11_2015” score: 0 last: 1446991679 first: 1446991679
KActivitiesStats( 0x16ee560 ) ResultModel::Private::onResultAdded result added: “/home/papa/Documents/Kde_Crash_08_11_2015” score: 0 last: 1446991679 first: 1446991679
KActivitiesStats( 0x15e8d90 ) ResultModel::Private::onResultAdded result added: “/home/papa/Documents/Kde_Crash_08_11_2015” score: 0 last: 1446991679 first: 1446991679
KActivitiesStats( 0x1d7d410 ) ResultModel::Private::onResultAdded result added: “/home/papa/Documents/plasmashell-20151108-144602.kcrash.txt” score: 0 last: 1446991746 first: 1446991746
KActivitiesStats( 0x16ee560 ) ResultModel::Private::onResultAdded result added: “/home/papa/Documents/plasmashell-20151108-144602.kcrash.txt” score: 0 last: 1446991746 first: 1446991746
KActivitiesStats( 0x15e8d90 ) ResultModel::Private::onResultAdded result added: “/home/papa/Documents/plasmashell-20151108-144602.kcrash.txt” score: 0 last: 1446991746 first: 1446991746
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0xe00096
QXcbConnection: XCB error: 151 (Unknown), sequence: 10819, resource id: 10485808, major code: 143 (Unknown), minor code: 3
QXcbConnection: XCB error: 3 (BadWindow), sequence: 10838, resource id: 14680170, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 3 (BadWindow), sequence: 10991, resource id: 60869794, major code: 142 (Unknown), minor code: 3
QXcbConnection: XCB error: 3 (BadWindow), sequence: 12319, resource id: 60817552, major code: 142 (Unknown), minor code: 3
(process:4315): GLib-CRITICAL **: g_slice_set_config: assertion ‘sys_page_size == 0’ failed
no winId: probably startup task
no winId: probably startup task
no winId: probably startup task
2015-11-08 15:10:56: basic_code_modules.cc:70: ERROR: Module /usr/lib/libsystemd.so.0 could not be stored
no winId: probably startup task
no winId: probably startup task
no winId: probably startup task
no winId: probably startup task[/code]
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0xe00096
Did you right click and try to open the settings of a widget in the panel around the same time?
Like this:
[attachment=791]
No , i was working on the samba testing , left for 3 minutes to get a cup of coffe , came back an saw the crash dump!The only thing i did around that time was working on different sessions in Yakuake!
Now i did a little bit off fooling arround with new panels and widgets earlier but at that exact moment i was only using a terminal session.
Both monitors are the same and the secondary monitor is set up as a “Clone” of the primary monitor and the icons are spaced the same on both monitors.
Hmm, I was just wondering. Well, I’ve had plasma crashes like this before even on fresh installs of Manjaro, they usually don’t effect whatever it was your doing, and stop happening after a bit as well. I’ve chalked these up to Plasma growing pains myself, these seem to happen mostly after fresh installs and updates to Plasma 5.x itself.
Ok, thanks for the heads up.
I will continue testing and report back if i have more trouble! 
Keep in mind also that what is coming out from Manjaro/Arch is as close to upstream as it can get.
Lately the upstream development has been more focused on wayland.
http://blog.martin-graesslin.com/blog/tag/wayland/
http://vizzzion.org/blog/2015/11/screen-management-in-wayland/
Just a quick question, what’s the purpose of “RUN” as well as the icon:
[attachment=792]
I would have thought just the icon would be sufficient
Just a gimick like Win-logo+“Start”, but reminding you of running Net-RUN-ner.
Besides that, it is actually easier to hit the extended “Run”-Menu Button without much aiming effort whenever the panel is not fully extended into the left lower corner.
Personally I hate the RUN text, its ugly and seems catered to the Windows user and even they would say that its not needed.
Remove it.
My comments on the matter can be found on the companion thread on the Manjaro forums (I am MadmanRB over there)
https://forum.manjaro.org/index.php?topic=28116.0
Not only is it ugly, it’s very unprofessional IMO and it should definitely be removed for “final”.
I definitely concur!
Not needed at all…and i think we are all way beyond windows like gimmicks!