Hi everybody,
I’m new to OpenSuse and would like to give it a try.
I’ve made my bootable TumbleWeed USB, but due to an issue it never gets booted and I can’t install it, neither boot into Live!
I get this message over and over:
A start job is running for journal service.
Last time I waited for about 30 minutes but it kept repeating that message.
As far as i know, this issue is something about my Windows partitions, i have shut down my windows without hibernating, but can’t get rid of this issue.
PS: i don’t have such an issue with other distros like Mageia.
My system spec:
Ram: 8GB
GPU: Nvidia GTS 450
SSD 120GB + HDD1.5GB
CPU: Intel G2020
Yes, I followed the instruction correctly and can boot into the menu and have the options to try/install opensue, test memory and etc.
But when I chose to install or try OpenSuse, I get a lot of messages like the followings:
*A start job is running for journal service (20s/ 1min 27s)
**A start job is running for journal service (5s/ 4min 10s)
*A start job is running for journal service (13s/ 7min 47s)
Actually I hadn’t done that,
However, disabling fast boot didn’t solve the problem (I just did it), I still get those messages,
I also noticed that sometime "A start job is running for journal service" messages are followed by:
Don’t know seem like there are reports of that error on already installed system But I would not think it would appear on an install???
In any case if you are just coming to Linux I’d recommend not trying the rolling releases since they do tend to be more problematic because of how fast they change. Use a stable release current is 13.2 and Leap 42.1 is due in a couple of weeks.
Hi guys,
I have the same problem with a Tumbleweed KDE Live USB-Stick. Any Progress on this issue?
I have tried on two very different computers, one is 5 years old, the other 1 year. The new one has 16GiByte of RAM…
I am hesitant to install Tumbleweed as long as this issue is not solved…
There was upstream bug report that may be related (it resulted in deadlock between journald, D-Bus and systemd). This took quite a long time to debug and it was not easy to reproduce. Someone who can actually reproduce it reliably should open bug report. Fix was finally submitted upstream, but whether this is the same problem and how easy fix is to backport needs investigation.
Hi,
Same problem here and iso checksum is ok, OS boots from usb stick and installation cd check passed. Problem is not uefi or other bios options. No other OS on my laptop. There is enough memory…
Problem is 100% reproducable as simply as trying to boot opensuse Tumbleweed GNOME 64 bit Live or KDE 64 bit Live from an usb stick. DVD iso boots without problem to install process.
Is there any option to disable journal service on boot time from the kernel line?!
Any updates on this yet? I’ve been checking bugzilla and have not seen anything new other than using mksusecd and I’m not sure how to use it and if this will solve the problem.