[Bug 1559481] Re: lubuntu-extra-sessions conflicts has a conflicting plasma.desktop file with plasma-workspace

2024-03-27 Thread Paul White
** Changed in: hundredpapercuts Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559481 Title: lubuntu-extra-sessions conflicts has a conflicting plasma.desktop file

[Bug 1559481] Re: lubuntu-extra-sessions conflicts has a conflicting plasma.desktop file with plasma-workspace

2024-03-27 Thread ԜаӀtеr Ⅼарсһуnѕkі
lubuntu-extra-sessions isn't a thing anymore. ** Changed in: lubuntu-default-settings (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559481 Title:

[Bug 1559481] Re: lubuntu-extra-sessions conflicts has a conflicting plasma.desktop file with plasma-workspace

2016-12-15 Thread Flames_in_Paradise
Tending to add this bug to [master] bug 1508619 There it needs task bug-opening for xenial, yakkety (monitored in zesty) which I cannot do. ** Also affects: hundredpapercuts Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu

[Bug 1559481] Re: lubuntu-extra-sessions conflicts has a conflicting plasma.desktop file with plasma-workspace

2016-08-23 Thread Julien Lavergne
Until it fixed, lubuntu-default-settings still needs a conflicts / replace against the package which contains plasma.desktop (I think I forget to add it). So until bug 1582270 is fixed, this bug is still relevant. -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1559481] Re: lubuntu-extra-sessions conflicts has a conflicting plasma.desktop file with plasma-workspace

2016-08-09 Thread Simon Quigley
This is caused by bug 1582270 and a possbble fix is available on that bug report. Once a fix is looked at and eventually included in the Yakkety archive, lubuntu-default-settings should be able to drop that symlink. I'm subscribing Julien specifically as he proposed a fix in bug 1582270 . --