[Expired for snapd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: snapd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576500
[Expired for Snappy because there has been no activity for 60 days.]
** Changed in: snappy
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576500
Title:
Plasma
Ok, issue solved. Because my home partition had run full and therefore I
wanted to get rid of baloo-kf5, I had purged plasma-desktop :/. That's
the reason why autoremove deleted plasma-desktop-data I assume.
Reinstalling plasma-desktop fixed the issue completely.
--
You received this bug
I have issue too now. Looking in /var/log/apt/history.log I noted:
Start-Date: 2017-02-07 21:27:42
Commandline: apt autoremove
Requested-By: carlo (1000)
Remove: fonts-noto-unhinted:amd64 (20160116-1), muon-updater:amd64
(4:5.6.2-1ubuntu1.1), liboxygenstyle5-5:amd64 (4:5.5.5-0ubuntu1),
The etc/X11/Xsession.d/65snappy got fixed some time ago - is this still
a problem with a snapd version > 2.0.5?
** Changed in: snapd (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: snappy
Status: Confirmed => Incomplete
--
You received this bug notification because you
Installing kubuntu-desktop fixed it for me.
I also purged snapd first, after reading this bug report. But that did
not fix it, and a subsequent "apt-get install kubuntu-desktop" did. I
had to setup some parts of kde again, including multiple desktops and
focus-follows-mouse.
--
You received
** Package changed: plasma-desktop (Ubuntu) => snapd (Ubuntu)
** Also affects: snappy
Importance: Undecided
Status: New
** Changed in: snappy
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Version 2.0.5 of snapd in -proposed has a fix for this script. See
https://bugs.launchpad.net/bugs/1575014 for details and even more
problems seemingly unrelated to snapd, but caused by its broken
$XDG_DATA_DIRS handling.
It's actually perfectly fine to not have the variable set at all if only
@Symaxtry to make it:
else
if [ -z "$XDG_CONFIG_DIRS" ]; then
XDG_CONFIG_DIRS="$DEFAULT_XDG_CONFIG_DIRS"
fi
if [ -z "$XDG_DATA_DIRS" ]; then
XDG_DATA_DIRS="$DEFAULT_XDG_DATA_DIRS"
fi
fi
so the default is only defined in one place (and an update of the
default at the top is
** Changed in: plasma-desktop (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576500
Title:
Plasma fails to load: "all shell packages missing"
To
I was able to fix the issue between Snappy and XDG_DATA_DIRS by
modifying /etc/X11/Xsession.d/60x11-common_xdg_path to read as follows:
# This file is sourced by Xsession(5), not executed.
# Add additionnal xdg paths depending on selected desktop session
DEFAULT_XDG_CONFIG_DIRS='/etc/xdg'
I personally think it is a slight issue with snappy because of the
XDG_DATA_DIRS variable and how it is handled.
X11/Xsession.d/60x11-common_xdg_path is supposed to set up the XDG_DATA_DIRS
variable.
X11/Xsession.d/65snappy doesn't check if XDG_DATA_DIRS is empty or not like
jklasdf, I think you are correct. It seems more related to the bug here:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1571564
which you also mention as possibly related, even if my problem didn't
appear in the same way or at the same tie (straight after upgrade/when
installing).
I have very similar issues to those reported here. Upgraded to 16.04
from 15.10 (from australia - au.archive.ubuntu.com seemed flakey when I
started, but got there after a few days of trying). Couldn't start
plasma, could only get to a terminal prompt. Running startx yielded the
exact screen
I don't think you actually have the same problem as us. See the picture
attached to the bug report...if alt-f2 is working and krunner doesn't
crash you probably have a different problem. I'd recommend opening a
separate bug report with just your symptoms.
If you want to check if your problem is
After reading jklasdf comment (#13) I tried to purge snapd (using apt-get purge
ad i dont have aptitude installed. Rebooted. Same problem
echo $XDG_DATA_DIRS yields:
/usr/share//usr/share/xsessions/plasma:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
So i reinstall snapd, created a symlink
For anyone curious:
Non-functional black-screen-with-pointer X:
$ echo $XDG_DATA_DIRS
:/var/lib/snapd/desktop
Workaround second X with plasma:
$ echo $XDG_DATA_DIRS
/usr/share//usr/share/xsessions/plasma:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
After fully removing snapd:
$ echo
I guess because I usually figure that something installed by default
that I haven't heard of is useful or important? Removing it entirely,
everything loaded and I didn't have to use my ridiculous workaround.
Success! Thanks!
Now:
$ echo $XDG_DATA_DIRS
/usr/share:/usr/share:/usr/local/share
Why did you not try purging snapd, and not reinstalling?
What does echo $XDG_DATA_DIRS show?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576500
Title:
Plasma fails to load: "all shell packages
Doesn't quite fix it for me.
Purging and reinstalling snapd had no effect.
~/.local/share/plasma already had one thing in it, so I created a
variety of new links into /usr/share/plasma/*. That gave me a KDE
splash screen, the popup about plasmashell being missing went away, and
the crash report
Wow, I never would have found that. Can you please file a bug against snapd?
Seems to be a show breaker.
Cheers,
Scarlett
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576500
Title:
Plasma fails
Alright thanks for the help scarlett.
I looked into it a bit more. Purging snapd for me seems to solve the
problem: running strace -f on krunner, it seemed to be trying to access
~/.local/share/plasma and /var/lib/snapd/desktop/plasma instead of the
correct location /usr/share/plasma. I
Afraid this is over my head. I am just a packager and this seems beyond
packaging issues. Have you reported this upstream KDE (krunner) Sorry I
am not much help. I had answers to the two items I mentioned only.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Further to my comment #3:
X ran in parallel with the instance of KDE/Plasma that was started
accidentally via kdesudo and/or teamviewer daemon for an hour or two
(confusing some software), then X died in the background. Plasma is
still running, days later.
"Everything works" was a bit of an
$ lspci -v
...
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland
XT [Radeon HD 8670 / R7 250/350] (prog-if 00 [VGA controller])
Subsystem: Dell Radeon R7 250
Flags: bus master, fast devsel, latency 0, IRQ 31
Memory at e000 (64-bit,
In my case, the GPU is an ATI Radeon of some form, but at the moment I
can't tell you exactly what.
Language is English-Canadian, installed while in China so there's some
odd localization in places.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is
Here's the backtrace for running krunner from the command line:
(gdb) run
Starting program: /usr/bin/krunner
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe3fa0700 (LWP 13738)]
[New Thread 0x7fffe08fd700
This happens with english, I don't have any of the kde-l10n packages
installed.
I'm using the radeon driver:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape
Verde PRO [Radeon HD 7750/8740 / R7 250E] (prog-if 00 [VGA controller])
Subsystem: Hightech
I need to know a few things:
What language? There were some missing translations that caused a series of
issues like this one.
Video card? Nvidia seems to be also causing similiar issues.
That dmesg log shows coredumps and according to it plasma is indeed
installed or it would not be core
I have the exact same problem after upgrading from 15.10.
dmesg shows:
[75364.605395] kactivitymanage[8268]: segfault at 7f04d244fcd0 ip
7f04ab385261 sp 7ffc035f3028 error 4 in
libQt5Sql.so.5.5.1[7f04ab371000+3f000]
[75374.038291] ksplashqml[13784]: segfault at 8 ip 7f250867e547 sp
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: plasma-desktop (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576500
OK, this is truly bizarre:
Starting the teamviewer daemon from Konsole on :0 (ctrl-alt-F1) asks for
password authentication in a usual popup window. Entering the password
to allow the teamviewer daemon to run also starts a fully functional X
with KDE/plasma on :1 (ctrl-alt-F7, where it would
$ krunner
Icon theme "breeze" not found.
Icon theme "oxygen" not found.
Error: standard icon theme "oxygen" not found!
File name empty!
KCrash: Attempting to start /usr/bin/krunner from kdeinit
sock_file=/run/user/1000/kdeinit5__0
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application
33 matches
Mail list logo
