Announcement

Collapse
No announcement yet.

Plasma long loading after login

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • john2
    replied
    It seems to assume that the machine has Bluetooth hardware, and if not it hangs until it times out. It makes no difference if Bluetooth is disabled. I fixed it by plugging in a USB Bluetooth dongle that was lying about (£1 from Poundland).

    Leave a comment:


  • NoWorries
    replied
    Originally posted by devnulljp View Post
    I have this on my 2nd monitor too. Black screen, I can move windows into it, but no right click for settings etc.
    Disabling Bluetooth seems to have fixed it.
    The first thing I did was to disable Bluetooth and then tested the boot time which was unchanged. I then started with an empty session and that decreased the boot time but gave the black auxiliary monitor. So a disabled Bluetooth did not solve the problem on my system.

    Leave a comment:


  • devnulljp
    replied
    Originally posted by NoWorries View Post
    I also have an auxiliary monitor which does not initialize correctly. It has a black auxiliary screen which I can move applications to and from, but right mouse click provides nothing, including no "Desktop Settings".
    I have this on my 2nd monitor too. Black screen, I can move windows into it, but no right click for settings etc.
    Disabling Bluetooth seems to have fixed it.
    Last edited by devnulljp; Nov 02, 2015, 03:28 PM.

    Leave a comment:


  • pider
    replied
    This made my KDE panel show up at once. , I never use Bluetooth anyway, I use KDE Contact to have a interface with my phone.

    Code:
    $ sudo systemctl disable bluetooth.service
    But how do I turn it on again?

    Leave a comment:


  • NoWorries
    replied
    On my system, when I "Start with an Empty Session", I get the HPLIP Status Service message with no system tray detected. I also have an auxiliary monitor which does not initialize correctly. It has a black auxiliary screen which I can move applications to and from, but right mouse click provides nothing, including no "Desktop Settings".

    For these reasons I have reverted to "Restore previous session" and put up with the extra 23s boot time. I certainly hope that a solution to this problem is found soon.

    The times reported here a dismal compared to what was being measured with Kubuntu 13.04. I have an SSD and I am wondering what is slowing the system boot time down so much. Once the desktop is up it is very fast.

    Leave a comment:


  • Spadge
    replied
    Originally posted by siabost View Post
    I solved the latter problem by following advice here [...] and the former by going into Settings/Start Up & Shutdown/Desktop Sessions/On Login and changing the setting to "Start with an Empty Session".

    Hope this helps :-)
    And that fixed the other 30 second delay!

    Thanks.

    Login to working desktop now around ten seconds, down from about a minute.

    Leave a comment:


  • Spadge
    replied
    Originally posted by arunce View Post
    If you don't need or don't have bluetooth just do:

    Code:
    $ sudo systemctl disable bluetooth.service
    And the systemtray will load quickly.
    That's brilliant. That fixes one of my 30 second delays - now if I could just work out what the other is caused by.

    Thanks!

    Leave a comment:


  • Teunis
    replied
    On my Thinkpad there was a problem with the broadband modem causing slowness and eventually lock up.
    Starting up in 14.04 or Windows and then (hot) rebooting into 15.04 would prevent the problem.

    This link by Spadge solved it:
    https://www.kubuntuforums.net/showth...ight=broadband

    Leave a comment:


  • roadrunner58
    replied
    I fixed my slow start problem up by going in to the system tray settings and disabling "networks (automatic load)"

    Leave a comment:


  • pider
    replied
    Still long loading here too!

    Leave a comment:


  • NoWorries
    replied
    Originally posted by Snowhog View Post
    For me, on my VM of 15.10 (Oracle VirtualBox), Plasma was also taking quite a while to load after the greeter login. Others have suggested/pointed to Bluetooth being involved in this long loading time. As my 15.10 VM doesn't have or use Bluetooth, but Bluetooth packages were installed, I purged all bluez* installed packages except for libbluetooth3 (removing/purging it removes your functioning system/desktop!) and rebooted. Plasma now loads extremely fast after typing in my password.
    Sorry to say that I did not get any improvement by purging bluez. I did this using muon as when I used the command line with the purge of bluez* it would have nuked my system. I changed my system to auto login and the times from power on to a desktop was about 49s both with and without bluez. I even tried commenting out the swap file in fstab and that made no difference for me.

    I have found that by not having kontact active when shutting down, the reboot doesn't cause problems with my auxiliary monitor not being correctly activated, ie a blank screen.

    P.S.

    I tried bootchart to get an accurate measure but that failed to generate the file /var/log/bootchart.tgz. So I seem to be snookered no matter what I try to do.
    Last edited by NoWorries; Oct 30, 2015, 06:50 PM.

    Leave a comment:


  • Guest
    Guest replied
    Does seem to be bluetooth related

    Originally posted by Snowhog View Post
    For me, on my VM of 15.10 (Oracle VirtualBox), Plasma was also taking quite a while to load after the greeter login. Others have suggested/pointed to Bluetooth being involved in this long loading time. As my 15.10 VM doesn't have or use Bluetooth, but Bluetooth packages were installed, I purged all bluez* installed packages except for libbluetooth3 (removing/purging it removes your functioning system/desktop!) and rebooted. Plasma now loads extremely fast after typing in my password.

    I updated my wireless card in laptop (the new card included bluetooth). As soon as I booted up with the new wifi/bluetooth card the problem went away. The loading time went from 1min. to about 5 seconds.

    Leave a comment:


  • Snowhog
    replied
    For me, on my VM of 15.10 (Oracle VirtualBox), Plasma was also taking quite a while to load after the greeter login. Others have suggested/pointed to Bluetooth being involved in this long loading time. As my 15.10 VM doesn't have or use Bluetooth, but Bluetooth packages were installed, I purged all bluez* installed packages except for libbluetooth3 (removing/purging it removes your functioning system/desktop!) and rebooted. Plasma now loads extremely fast after typing in my password.

    Leave a comment:


  • gjringo
    replied
    I also had slow boot after updating Wily "testing" from the22nd Oct. Upon booting I checked the boot message for errors ( Ctrl+Alt+Tab) which showed something similar to "a start job is runnning for dev-disk-by \ x2duuid-xxxx ".........(37s / 1min30s).
    A google search landed me at http://jayshomebrew.blogspot.com.au/...nning-for.html
    He sugested to edit /etc/fstab
    and comment out the swap file that was used during installation. Reboot, and all should be fine. That fix worked for me

    Leave a comment:


  • LinkBot
    replied
    Minutes Monday Plasma Hangout: https://mail.kde.org/pipermail/plasm...er/045409.html
    ...
    David:
    - 30 sec freeze during startup in Kubuntu due to bluetooth, Jan fixed it
    ...

    Leave a comment:

Users Viewing This Topic

Collapse

There are 0 users viewing this topic.

Working...
X