Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 34

Thread: Plasma long loading after login

  1. Back To Top    #11
    Newbie
    Join Date
    Apr 2015
    Posts
    3
    Threads
    1
    Local Date
    Jan 4th 2018
    Local Time
    07:27 PM
    I have a similar and very strange issue. I upgraded from 15.04 to 15.10 and the update stalled with 8% to go. I was planning to rebuild anyway so did a clean install of 15.10.

    The install went fine, but after reboot I can only get a black screen. Wifi light works but nothing else. However... If I choose Recovery mode, then choose to resume normal boot it loads the display and I can use the laptop without issue. It seems like it isn't loading the display drivers but I am not sure.

    The hardware is a Pavilion G6 laptop with a Radeon HD 6520G

  2. Back To Top    #12
    Contributing Member
    Join Date
    Nov 2007
    Posts
    66
    Threads
    16
    Local Date
    Jan 4th 2018
    Local Time
    09:27 PM
    I have the same problem. The beta was fine. Then it started the slow loading the after a update.
    Last edited by roadrunner58; Oct 25th 2015 at 11:42 AM.

  3. Back To Top    #13
    Senior Member
    Join Date
    May 2012
    Posts
    113
    Threads
    5
    Local Date
    Jan 4th 2018
    Local Time
    09:27 PM
    Update from testing on an under-powered 1GB Netbook, where I have time to try things: Immediately after the login notification, krunner (Alt-F2) works, but neither the Panel nor the Application Launcher (Alt-F1) do.

    Update from the bug report: It looks as if the root cause is identified. It seems to be related to Bluetooth (We can see we're making some blocking calls to BlueZ here), and the proposed solution is to make those calls async.

  4. Back To Top    #14
    Newbie
    Join Date
    Oct 2015
    Posts
    3
    Threads
    1
    Local Date
    Jan 5th 2018
    Local Time
    02:27 AM
    Quote Originally Posted by mparillo View Post
    Update from testing on an under-powered 1GB Netbook, where I have time to try things: Immediately after the login notification, krunner (Alt-F2) works, but neither the Panel nor the Application Launcher (Alt-F1) do.

    Update from the bug report: It looks as if the root cause is identified. It seems to be related to Bluetooth (We can see we're making some blocking calls to BlueZ here), and the proposed solution is to make those calls async.
    If you don't need or don't have bluetooth just do:

    Code:
    $ sudo systemctl disable bluetooth.service
    And the systemtray will load quickly.

  5. Back To Top    #15
    Newbie
    Join Date
    Dec 2012
    Posts
    5
    Threads
    3
    Local Date
    Jan 5th 2018
    Local Time
    03:27 AM
    I have "solved" disabling from systemtray network manager.

  6. Back To Top    #16
    Newbie
    Join Date
    Feb 2012
    Posts
    5
    Threads
    1
    Local Date
    Jan 4th 2018
    Local Time
    07:27 PM
    Similar experience here from a clean install of Kubuntu 15.10. In my case:

    Grub to login screen: 9 seconds
    Splash screen: ~30 seconds
    From seeing wallpaper to functional desktop (I could also see the panel, but nothing was usable): ~60 seconds

    Disabling bluetooth as suggested in post 14 fixed the longer 60 second pause, but the 30 second one still exists. I've gone from ~100 second boot to ~40 second boot. I still think the 30 second delay is indicative of something being broken. To put this into perspective, my desktop has an i7 with 16 GB RAM and a name brand SSD (not that name brand matters all that much, but this is just to show that it's not the absolute cheapest and slowest SSD on the market). Windows 10 boots to a fully usable desktop in ~15 seconds, and that's with quick startup disabled so that Windows and Kubuntu play nicely together. A 40 second boot time almost requires that there is something still broken with the boot process.

  7. Back To Top    #17
    Kubuntu as Second Language NoWorries's Avatar
    Join Date
    Jun 2007
    Location
    Adelaide, South Australia
    Posts
    1,162
    Threads
    126
    Local Date
    Jan 5th 2018
    Local Time
    12:57 PM
    I also have been experiencing slow start-up. For my system it takes 20s from power on to the login screen. I now wait at least 10s at the login screen, as if I don't wait, I find that Wily does not recognize my second screen correctly. I suspect that kscreen is in dire need of serious surgery.

    The final step from Login to a working desktop takes about 33s. Sometimes I have a long period with a black screen. I think that this depends on how long I leave my system at the login screen. I remember a time, not long ago, when some on this forum were reporting boot times in 10-20s. I hope this problems is fixed soon!!!!

  8. Back To Top    #18
    Newbie
    Join Date
    Jul 2009
    Location
    Scotland, UK
    Posts
    9
    Threads
    4
    Local Date
    Jan 5th 2018
    Local Time
    02:27 AM

    Talking Got my 15.10 to load quickly

    I had a similar problem here with 15.10 although 15.04 was fine (i7 laptop with Intel Graphics & 8Mb memory). Boot times may not have been as long for me as some noted here, but there was a significant pause when the boot progress bar showed completed and then another with desktop wallpaper showing before the system tray loaded.

    I solved the latter problem by following advice here to disable the bluetooth service - '$ sudo systemctl disable bluetooth.service' - and the former by going into Settings/Start Up & Shutdown/Desktop Sessions/On Login and changing the setting to "Start with an Empty Session".

    My laptop now boots as fast as it used to: from power button pressed to login screen (including POST) = 14s; login screen to fully working desktop = 8s.

    I don't have Bluetooth on my laptop currently, as I had swapped out the original WiFi chip which was causing issues in Linux, so disabling it was not an issue for me - it maybe for some, though.
    Incidentally, prior to trying Kubuntu (which is looking better than it ever did), I had installed Atergos/KDE version and that wouldn't complete the install with bluetooth enabled in the pre-install checklist - so it may be that this is a wider problem (with KDE) rather than Kubuntu specific.

    Hope this helps :-)
    Last edited by siabost; Oct 26th 2015 at 07:21 PM.

  9. Back To Top    #19
    Contributing Member
    Join Date
    Jan 2007
    Posts
    66
    Threads
    16
    Local Date
    Jan 5th 2018
    Local Time
    02:27 AM

    The Power of the Atom

    I have got 15.10 on two Acer Aspire Revo computers; the R3600 has a 230 Atom 1.6GHz and the R3700 has a D525 Atom 1.8GHz (much more powerful and with faster graphics).

    I upgraded both to 15.04 only to find that it was broken. I further upgraded both to 15.10 and got KDE init and Plasma errors during the upgrade. Then I did a clean install on both.

    The R3600 has always been quite slow, but the R3700 used to belt along like a demented pixie with 14.04 and 14.10. Both machines now have the slow boot that the thread documents.

    On the powerful 3700 I did this,

    user@nettop-R3700:~$ service --status-all
    ~
    [ - ] bluetooth
    ~


    user@nettop-R3700:~$ sudo systemctl disable bluetooth.service
    [sudo] password for user:

    Synchronizing state of bluetooth.service with SysV init with /lib/systemd/systemd-sysv-install...
    Executing /lib/systemd/systemd-sysv-install disable bluetooth
    insserv: warning: current start runlevel(s) (empty) of script `bluetooth' overrides LSB defaults (2 3 4 5).
    insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `bluetooth' overrides LSB defaults (0 1 6).
    Removed symlink /etc/systemd/system/dbus-org.bluez.service.

    user@nettop-R3700:~$ service --status-all
    ~
    [ - ] bluetooth
    ~

    There was no subjective improvement. I deselected Bluetooth in the system tray with no apparent improvement.

    I should note that neither machine is taking processor time for file indexing.

    I think there is something very broken with the graphics system and, perhaps, Plasma. On the R3600, the computer often fails during the boot splash screen process. The progress bar never finishes, but icons from the panel start popping up and the mouse pointer will not move. The system does keep very good time, so a lot of Linux is running correctly. After a while the screen blanks and the display can be restored by moving the mouse, even though the mouse pointer does not move. I have both machines set to turn-off on the power button, but this does not work while in this state. A long stab on the power button is required. Every now and then, it boots after the long delays into a fully functioning 15.10 session.

    When I first installed 15.04 on the R3600, I got a black screen on the initial restart. I did a clean install of 15.10 and got the same thing. Hard power-downs and start-ups finally got it to work.

    The R3700 was much less of a problem (perhaps due to the better graphics circuitry in the D525 Atom). The were no splash screen problems, but it is just as slow to boot as the R3600. In addition, the system sometimes refuses to close down or run programs even though Plasma appears to be working OK. A hard power-down is required. A dab on the power button fails to close Linux.

    One final aberration on both systems which is, I think, unconnected with the slow boot process is that files open with the wrong tool. A deb will open with ark and a pdf with Inkscape. A check on filetypes in settings shows all the correct default programs.

    Just to end on a high, the search function in dolphin/baloo has now been restored. If the slow boot can be resolved so that it is as good as Kubuntu LTE, 15.10 will be a useful release. I don't think I could live with 15.04.

  10. Back To Top    #20
    Senior Member LinkBot's Avatar
    Join Date
    Mar 2015
    Posts
    222
    Threads
    16
    Local Date
    Jan 5th 2018
    Local Time
    02:27 AM
    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
    ...

Page 2 of 4 FirstFirst 1234 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •