Gary Dale - 19.11.20, 12:39:52 CET:
> > What I did was switch to Windows for the 3 day interval so I could
> > work whilst Debian sorted itself out. That worked for me. Other
> > things worked for other people. I'm cool with that.
>
> That's a terrible solution. While I don't particularly care
On 2020-11-12 23:45, Borden Rhodes wrote:
On Thu, 12 Nov 2020 at 23:32, Norbert Preining wrote:
Nothing related to plasma can make your system unbootable, that is FUD.
You can change the desktop session to any other and run it.
Does my computer power on and POST? Yes.
Do the kernel and
On 2020-11-12 15:58, Borden Rhodes wrote:
Confirmed I can use my computer again. Thank you.
Back to my earlier question, though, have we learnt anything in this
experience that can help us avoid unbootable KDE problems in the
future?
A previous time when this happened, I suggested marking the
Hi
On Thu, 12 Nov 2020, Borden Rhodes wrote:
> 1) To a point where I could do anything useful on my computer,
Again, you can select a different desktop session from the login screen
and start the programs you are normally using from the other DE menu or
the command terminal. That would have been
On Thu, 12 Nov 2020 at 23:32, Norbert Preining wrote:
> Nothing related to plasma can make your system unbootable, that is FUD.
> You can change the desktop session to any other and run it.
Does my computer power on and POST? Yes.
Do the kernel and systemd complete their start up routines? Yes.
On Thu, 12 Nov 2020, Borden Rhodes wrote:
> 1) An unbootable computer is not a "testing" system. It's an
Nothing related to plasma can make your system unbootable, that is FUD.
You can change the desktop session to any other and run it.
And yes, we are trying to fix this, in particular since
On Thu, 12 Nov 2020 at 20:36, Gary Dale wrote:
>
> However the point of testing is to do testing.
I understand that. But I want to make sure that my three points are understood:
1) An unbootable computer is not a "testing" system. It's an
"unstable" system. The update that broke KDE was
Confirmed I can use my computer again. Thank you.
Back to my earlier question, though, have we learnt anything in this
experience that can help us avoid unbootable KDE problems in the
future?
On 2020-11-12 08:38, Gary Dale wrote:
On 2020-11-09 01:37, Héctor Sales Llamas wrote:
Hello, today some plasma 5.19.5-3 packages have entered testing .
After reboot and logging into the system, plasma is partially
broken. I suspect it has to do with the partial plasma upgrade
5.19.x. How
On 2020-11-12 08:38, Gary Dale wrote:
On 2020-11-09 01:37, Héctor Sales Llamas wrote:
Hello, today some plasma 5.19.5-3 packages have entered testing .
After reboot and logging into the system, plasma is partially
broken. I suspect it has to do with the partial plasma upgrade
5.19.x. How
On 2020-11-09 01:37, Héctor Sales Llamas wrote:
Hello, today some plasma 5.19.5-3 packages have entered testing .
After reboot and logging into the system, plasma is partially
broken. I suspect it has to do with the partial plasma upgrade
5.19.x. How can i fix this ?. Why did these
On Thu, 12 Nov 2020 10:58:58 -0500
Gary Dale wrote:
Hello Gary,
>Got the taskbar back by removing
>.config/plasma-org.kde.plasma.desktop-appletsrc.
Thanks for the info Gary. If I have issues when I upgrade, I'll know
what to do as a result of your report. Cheers.
--
Regards _
On Tuesday, 10 November 2020 18:31:17 GMT Borden Rhodes wrote:
[...]
> Anyhow, is there a way to roll the repos back to 5.17 until 5.19 is
> fully ready or am I stuck with an unbootable operating system until
> 5.19 goes downstream?
As I posted earlier in the week ... and now refined:
#
# Fix
On Tue, 10 Nov 2020 17:19:25 -0500
Borden Rhodes wrote:
Hello Borden,
>Making sure that all the KF libraries are at the same version
>doesn't seem like a corner case to me,
In principal, I agree.
That said, read what Sandro wrote in reply to my comments about recent
KDE transitions.
On Tue, 10 Nov 2020 at 14:48, Brad Rogers wrote:
> Impossible to achieve. There's simply far too much that can go wrong to
> cover every single (corner) case there may be.
Is there anything to learn from this experience that can help us in
future? Controls are never perfect, and there's always
On Tue, 10 Nov 2020 13:31:17 -0500
Borden Rhodes wrote:
Hello Borden,
>over 30 years of packaging to prevent unbootable operating system
>errors from happening
Impossible to achieve. There's simply far too much that can go wrong to
cover every single (corner) case there may be.
It also
On Mon, 9 Nov 2020 at 16:20, Lisandro Damián Nicanor Pérez Meyer
wrote:
> That also means you have great expectations from us :-D
Are we being unreasonable assuming that we can turn our computers off
and back on and have them still boot?
> But let me assure you that if this kind of things
On 2020-11-09 4:04 a.m., Andy G Wood wrote:
I had the same problem this morning with testing.
My fix was to simply to back out the new libkdecorations2-5v5 :
debsnap -d . --binary -a amd64 libkdecorations2-5v5 4:5.17.5-2
sudo dpkg -i libkdecorations2-5v5_5.17.5-2_amd64.deb
dpkg --get-selections
Hi Gary!
On Mon, 9 Nov 2020 at 18:00, Gary Dale wrote:
[snip]
> I'm disappointed that the package maintainers didn't notice that there
> was a dependency on a particular version of something. The .deb format
> allows for this to be specified, so this problem could have been
> prevented - the
On Mon, 09 Nov 2020, Gary Dale wrote:
> this to be specified, so this problem could have been prevented - the newer
> decoration package would have held until its dependency was met.
An upload fixing this is already accepted. We are also only humans ;-)
Best
Norbert
--
PREINING Norbert
> I was to install from unstable kwin-x11 packages on testing.
Umpf yes, kdecorations migrated but kwin not, that is not working.
We need to tighten the deps.
Norbert
--
PREINING Norbert https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX
Hi everybody:
Finally the solution that works for me:
I was to install from unstable kwin-x11 packages on testing.
El 9/11/20 a las 10:52, Dimitris Paraschou escribió:
Hello everybody,
I had the same problem after upgrade and the reason was the outdated
version of event calendar plasmoid.
Hi, you saved my day. Thanks.
--
Facu
Hello everybody,
I had the same problem after upgrade and the reason was the outdated
version of event calendar plasmoid.
Removing the entry from
~/.config/plasma-org.kde.plasma.desktop-appletsrc
fixed the problem
On Monday, November 9, 2020 12:26:41 PM EET Erwan David wrote:
Le 09/11/2020 à 11:06, Erwan David a écrit :
> Le 09/11/2020 à 10:04, Andy G Wood a écrit :
>> I had the same problem this morning with testing.
>> My fix was to simply to back out the new libkdecorations2-5v5 :
>>
>> debsnap -d . --binary -a amd64 libkdecorations2-5v5 4:5.17.5-2
>> sudo dpkg -i
Le 09/11/2020 à 10:04, Andy G Wood a écrit :
I had the same problem this morning with testing.
My fix was to simply to back out the new libkdecorations2-5v5 :
debsnap -d . --binary -a amd64 libkdecorations2-5v5 4:5.17.5-2
sudo dpkg -i libkdecorations2-5v5_5.17.5-2_amd64.deb
dpkg
I had the same problem this morning with testing.
My fix was to simply to back out the new libkdecorations2-5v5 :
debsnap -d . --binary -a amd64 libkdecorations2-5v5 4:5.17.5-2
sudo dpkg -i libkdecorations2-5v5_5.17.5-2_amd64.deb
dpkg --get-selections \* | grep -P '^libkdecorations2-5v5' \
Hi Héctor,
Not sure if it was the same problem, but when I logged in today I did
not have window decorations and was generally missing some kwin
functionality. Turned out I could not start kwin due to a missing
symbol. Running `apt full-upgrade` resolved the issue by installing a
lot of kf5*
Hello, today some plasma 5.19.5-3 packages have entered testing . After
reboot and logging into the system, plasma is partially broken. I suspect
it has to do with the partial plasma upgrade 5.19.x. How can i fix this
?. Why did these packages go into testing partially ?
Start-Date: 2020-11-09
29 matches
Mail list logo
