Re: Window decoration doesn't work in testing

[Thom Castermans]

Hi Mourad,

Does manually restarting kwin resolve the issue (execute `kwin
--replace` in Konsole or KRunner)? If not, does running that command
in Konsole show errors?

You may also want to check if you fully upgraded everything. Does `apt
upgrade` mention packages that were held back?

Hope that helps,
Thom

Op di 24 nov. 2020 om 21:23 schreef :
>
> Hi,
>
> This is now several days that plasma/kde in testing haven't any working 
> window decorator.
>
> As workaround, I'm launching manually fluxbox and it takes place of kwin.
>
> I'm not able to find any log about something wrong.
>
> I have tested workaround explained in "Upgrade partially some packages 
> (Plasma 5.19. 5 -
> 3) on testing broke plasma." threat but no success at all.
>
> Is there something to find the problem and to help to fix it ?
>
> Regards
>
> Mourad
>

Re: Current status of KDE in Sid

[Thom Castermans]

Hi Miguel,

As I just wrote in another thread, you may need to `apt full-upgrade`
instead of only `apt upgrade` to get the new KDE.

Best,
Thom

Op wo 4 nov. 2020 om 08:40 schreef Thom Castermans :
>
> Hi Miguel,
>
> This situation is normal when the Debian KDE team is going through a
> (relatively big) KDE upgrade. It may take a couple of weeks before all
> packages have been built, tested and moved from experimental to Sid.
> In my experience it is best to simply be patient and wait until apt
> tells you it is safe to upgrade. It hasn't failed me so far.
>
> Looking forward, thanks to all of the team for their work!
>
> Best,
> Thom
>
>
> Op di 3 nov. 2020 om 18:18 schreef Miguel A. Vallejo :
> >
> > Hello.
> >
> > Since a week ago (+/-) both apt upgrade and dist-upgrade want to keep
> > back / remove a TON of packages, most of them QT / KDE related. Since
> > I do not want to break the system, when will be safe to upgrade the
> > system?
> >
> > I tried to upgrade only some programs because I use them regularly but
> > because they are QT based the effect is the same: apt wants to remove
> > a ton of packages and libraries, packages like dolphin,
> > kde-plasma-desktop, kmail or knotes. It doesn't seem to be the best
> > option right now.
> >
> > What must I do? Wait some days more?
> >
> > Thanks in advance
> >

Re: Upgrade partially some packages (Plasma 5.19. 5 - 3) on testing broke plasma.

[Thom Castermans]

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* packages. I thought apt would protect me from this, but it
remains unstable/testing for a reason!

Hope that helps, best regards,
Thom

Op ma 9 nov. 2020 om 07:54 schreef Héctor Sales Llamas :
>
>
> 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  05:23:55
> Commandline: apt upgrade
> Requested-By: hector (1000)
> Install: libkdecorations2private7:amd64 (4:5.19.5-3, automatic)
> Upgrade: openssl:amd64 (1.1.1g-1, 1.1.1h-1), libkdecorations2-5v5:amd64 
> (4:5.17.5-2, 4:5.19.5-3), libxnvctrl0:amd64 (450.66-1, 450.80.02-1), 
> libkf5screen-bin:amd64 (4:5.17.5-3, 4:5.19.5-3), libkf5screen7:amd64 
> (4:5.17.5-3, 4:5.19.5-3), libssl-dev:amd64 (1.1.1g-1, 1.1.1h-1), 
> libssl1.1:amd64 (1.1.1g-1, 1.1.1h-1), libssl1.1:i386 (1.1.1g-1, 1.1.1h-1), 
> nvidia-settings:amd64 (450.66-1, 450.80.02-1)
> End-Date: 2020-11-09  05:24:18

Re: Current status of KDE in Sid

[Thom Castermans]

Hi Miguel,

This situation is normal when the Debian KDE team is going through a
(relatively big) KDE upgrade. It may take a couple of weeks before all
packages have been built, tested and moved from experimental to Sid.
In my experience it is best to simply be patient and wait until apt
tells you it is safe to upgrade. It hasn't failed me so far.

Looking forward, thanks to all of the team for their work!

Best,
Thom


Op di 3 nov. 2020 om 18:18 schreef Miguel A. Vallejo :
>
> Hello.
>
> Since a week ago (+/-) both apt upgrade and dist-upgrade want to keep
> back / remove a TON of packages, most of them QT / KDE related. Since
> I do not want to break the system, when will be safe to upgrade the
> system?
>
> I tried to upgrade only some programs because I use them regularly but
> because they are QT based the effect is the same: apt wants to remove
> a ton of packages and libraries, packages like dolphin,
> kde-plasma-desktop, kmail or knotes. It doesn't seem to be the best
> option right now.
>
> What must I do? Wait some days more?
>
> Thanks in advance
>

Re: window manager crash

[Thom Castermans]

Hi Rainer,

It sounds to me like it might be kwin that crashed, rather than
Plasma. You can restart that with `DISPLAY=:0 kwin --replace` from any
VTT.

> I can start new apps using the (former) K-menu,

If you mean the Application Launcher, then that means you can run
commands from there too. Either Luca's suggestions or `kwin --replace`
(does not need the DISPLAY) hopefully work for you.

Best,
Thom

Re: Bottom bar not hiding after switching window

[Thom Castermans]

Dear Simon,

That is odd and annoying. I am afraid I cannot reproduce that behavior
(although I am on unstable, I have not seen the behavior some time ago
either).

The only possible workaround I can suggest is setting your taskbar to
be always visible, keep it like that until the next reboot and then
switch back to auto-hide. It (seemed to) help(ed) me in the past.

Best,
Thom

Op wo 10 jun. 2020 om 18:43 schreef Simon Frei :
>
> Dear Thom,
>
> It doesn't matter how I switch, it's the same behaviour whether I
> "alt-tab" or click with the mouse onto another window: Switch window,
> bar is shown (regardless of where my mouse is, also far away from the
> bar), then move my mouse to the bar and away from it (no clicking) and
> it stays hidden until I switch windows again (or move the mouse to the
> bottom).
> And there's nothing asking for attention as far as I can dicern - the
> "program indicators" are usual orange if that's the case and none are now.
>
> Cheers,
> Simon
>
> On 10/06/2020 18:14, Thom Castermans wrote:
> > Dear Simon,
> >
> > I also have my taskbar set to auto-hide, and did have some problems
> > with it in the past, but those have been resolved. What exactly do you
> > mean with switching windows? Are you switching using a keyboard
> > shortcut? AFAIK the taskbar is shown if and only if the mouse cursor
> > is close to the bottom of the screen.
> >
> > What *might* be happening is that one window asks for attention
> > (notification etc.). That causes the taskbar to remain visible.
> >
> > Cheers,
> > Thom
> >
> >
> > Op wo 10 jun. 2020 om 14:56 schreef Simon Frei :
> >> I more or less recently switched over from XFCE to KDE and must say, I
> >> am pretty impressed :)
> >> Thanks a lot for packaging this fine DE for debian!
> >>
> >> I am on debian testing.
> >> One quite annoying behaviour I observe is that the bottom bar (set to
> >> auto-hide) is not auto-hiding when switching windows. It does auto-hide
> >> when I move the mouse onto the bottom bar and away again. That's quite
> >> annoying especially on a small laptop screen when the open window has an
> >> input field at the bottom (like most messengers).
> >> Can anyone reproduce? I assume not, at least I couldn't find any info on
> >> anyone having the same problem online.
> >> Is there a cache/config file relevant to this behaviour I could check or
> >> move out of place to see if it's a misconfig?
> >>
> >> Thanks in advance for any help.
> >>
> >> Cheers,
> >> Simon
> >>
>

Re: Bottom bar not hiding after switching window

[Thom Castermans]

Dear Simon,

I also have my taskbar set to auto-hide, and did have some problems
with it in the past, but those have been resolved. What exactly do you
mean with switching windows? Are you switching using a keyboard
shortcut? AFAIK the taskbar is shown if and only if the mouse cursor
is close to the bottom of the screen.

What *might* be happening is that one window asks for attention
(notification etc.). That causes the taskbar to remain visible.

Cheers,
Thom


Op wo 10 jun. 2020 om 14:56 schreef Simon Frei :
>
> I more or less recently switched over from XFCE to KDE and must say, I
> am pretty impressed :)
> Thanks a lot for packaging this fine DE for debian!
>
> I am on debian testing.
> One quite annoying behaviour I observe is that the bottom bar (set to
> auto-hide) is not auto-hiding when switching windows. It does auto-hide
> when I move the mouse onto the bottom bar and away again. That's quite
> annoying especially on a small laptop screen when the open window has an
> input field at the bottom (like most messengers).
> Can anyone reproduce? I assume not, at least I couldn't find any info on
> anyone having the same problem online.
> Is there a cache/config file relevant to this behaviour I could check or
> move out of place to see if it's a misconfig?
>
> Thanks in advance for any help.
>
> Cheers,
> Simon
>

Re: Resizing Keepass XC crashes Plasma

[Thom Castermans]

Hi M.,

I did not know what kind of message to expect, was just thinking along.

In general it helps if you have an error message, instead of only an
observed behavior.

Maybe your system logs have something related to Plasma? Try
`journalctl | grep -E "kde|plasma"` (as root) or KSystemLog.

Best, Thom

Op do 28 nov. 2019 om 19:38 schreef M. :
>
> Hi Thom,
>
> I checked those files and nothing jumps out, nothing out of the ordinary. 
> What kind of message should I look for?
>
> Thanks
>
> Em seg., 4 de nov. de 2019 às 08:03, Thom Castermans 
>  escreveu:
>>
>> Hi M.,
>>
>> You can check `~/.xsession-errors` and `/var/log/Xorg.0.log` for
>> errors, as well as kernel logs (`dmesg`) for errors specific to your
>> graphics drivers.
>>
>> Hope that helps.
>>
>> Thom
>>
>> Op za 2 nov. 2019 om 02:27 schreef M. :
>> >
>> > Hi all,
>> >
>> > Thanks for your answers. I'm running Stable, and it seems that keepass 
>> > version is the same on stable and on testing and sid, but the rest of the 
>> > system obviously is not. Any clues on how to try to debug this?
>> >
>> > Thanks
>> >
>> > Em seg, 28 de out de 2019 às 08:30, Sandro Knauß  
>> > escreveu:
>> >>
>> >> Hey,
>> >>
>> >> > > For what it's worth, I cannot reproduce the issue on testing/unstable
>> >> > > (Plasma 5.14.5, KeepassXC 2.4.3). How did you install KeepassXC? I 
>> >> > > had to
>> >> > > build it from source - if you did too, maybe a rebuild is required 
>> >> > > after
>> >> > > updates?
>> >>
>> >> I can't reproduce for KeePassXC 2.4.3+dfsg.1-1 and plasma-desktop 
>> >> 4:5.14.5.1-4
>> >> both from sid.
>> >> I also have a Intel graphic card too and everything works fine for me. 
>> >> Maybe
>> >> some package is not migrated to Buster.
>> >>
>> >> hefee
>> >>
>>

Re: Resizing Keepass XC crashes Plasma

[Thom Castermans]

Hi M.,

You can check `~/.xsession-errors` and `/var/log/Xorg.0.log` for
errors, as well as kernel logs (`dmesg`) for errors specific to your
graphics drivers.

Hope that helps.

Thom

Op za 2 nov. 2019 om 02:27 schreef M. :
>
> Hi all,
>
> Thanks for your answers. I'm running Stable, and it seems that keepass 
> version is the same on stable and on testing and sid, but the rest of the 
> system obviously is not. Any clues on how to try to debug this?
>
> Thanks
>
> Em seg, 28 de out de 2019 às 08:30, Sandro Knauß  escreveu:
>>
>> Hey,
>>
>> > > For what it's worth, I cannot reproduce the issue on testing/unstable
>> > > (Plasma 5.14.5, KeepassXC 2.4.3). How did you install KeepassXC? I had to
>> > > build it from source - if you did too, maybe a rebuild is required after
>> > > updates?
>>
>> I can't reproduce for KeePassXC 2.4.3+dfsg.1-1 and plasma-desktop 
>> 4:5.14.5.1-4
>> both from sid.
>> I also have a Intel graphic card too and everything works fine for me. Maybe
>> some package is not migrated to Buster.
>>
>> hefee
>>

Re: Resizing Keepass XC crashes Plasma

[Thom Castermans]

Addendum: I just built and installed KeepassXC 2.5.0, which was released a
few days ago. It also does not crash Plasma.

Best, Thom

Op ma 28 okt. 2019 om 08:51 schreef Thom Castermans <
thom.casterm...@gmail.com>:

> Hi M.,
>
> For what it's worth, I cannot reproduce the issue on testing/unstable
> (Plasma 5.14.5, KeepassXC 2.4.3). How did you install KeepassXC? I had to
> build it from source - if you did too, maybe a rebuild is required after
> updates?
>
> Best, Thom
>
> Op zo 27 okt. 2019 om 23:55 schreef M. :
>
>> Hi all,
>>
>> On Buster, resizing KeepassXC after opening a database completely crashes
>> Plasma - I have to restart it from the terminal. I'm running Buster up to
>> date, with Intel drivers, on an external monitor via HDMI. The only things
>> different on my dmesg is
>>
>> [27436.083291] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
>> failure on pipe B (start=51173 end=51174) time 175 us, min 1431, max 1439,
>> scanline start 1430, end 1446
>> [28814.602509] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
>> failure on pipe B (start=133816 end=133817) time 148 us, min 1431, max
>> 1439, scanline start 1428, end 1441
>>8.188923] DMAR: DRHD: handling fault status reg 2
>> [8.188932] DMAR: [DMA Write] Request device [02:00.0] fault addr 0
>> [fault reason 05] PTE Write access is not set
>>
>> and there is nothing abnormal on .xsession-errors. I'm using compositing
>> with OpenGL 3.1 and set intel_iommu=on,igfx_off. Any ideas on what's going
>> on?
>>
>> Cheers
>>
>

Re: Resizing Keepass XC crashes Plasma

[Thom Castermans]

Hi M.,

For what it's worth, I cannot reproduce the issue on testing/unstable
(Plasma 5.14.5, KeepassXC 2.4.3). How did you install KeepassXC? I had to
build it from source - if you did too, maybe a rebuild is required after
updates?

Best, Thom

Op zo 27 okt. 2019 om 23:55 schreef M. :

> Hi all,
>
> On Buster, resizing KeepassXC after opening a database completely crashes
> Plasma - I have to restart it from the terminal. I'm running Buster up to
> date, with Intel drivers, on an external monitor via HDMI. The only things
> different on my dmesg is
>
> [27436.083291] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
> failure on pipe B (start=51173 end=51174) time 175 us, min 1431, max 1439,
> scanline start 1430, end 1446
> [28814.602509] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
> failure on pipe B (start=133816 end=133817) time 148 us, min 1431, max
> 1439, scanline start 1428, end 1441
>8.188923] DMAR: DRHD: handling fault status reg 2
> [8.188932] DMAR: [DMA Write] Request device [02:00.0] fault addr 0
> [fault reason 05] PTE Write access is not set
>
> and there is nothing abnormal on .xsession-errors. I'm using compositing
> with OpenGL 3.1 and set intel_iommu=on,igfx_off. Any ideas on what's going
> on?
>
> Cheers
>

Re: Middle click functionality as paste in KDE

[Thom Castermans]

Hi Alexandros,

> Does anyone know how can i make middle click work as paste?
>
 Just wondering: do you want middle click to work the same as Ctrl+V?
Because by default, the middle click clipboard (this might have a proper
name) is separate from the KDE clipboard (i.e. klipper). When you select
text, you can paste that text anywhere else using middle click, but this is
not recorded in klipper. Are you trying to use that functionality and is
that broken, or are you trying to make middle click behave the same as
Ctrl+V?

Best, Thom

Re: kdeconnect clipboard passwords security

[Thom Castermans]

Dear Chris,

> Also there might be far superior solution to that password leaking issue of
> which I'm unaware of.

Some password managers (at least Keepass, which I use) have a function
to auto type the password. This means that they will send the sequence
of key events as if you were typing the password yourself. Keepass
even provides options to also type the username and other fields you
want. This is convenient on web pages:
 and you are logged in.

The above avoids having the password in your clipboard at any time.

Nevertheless I agree with you that it would be nice if the default
behavior could be changed.

Best,
Thom

Re: Warning! Current udisks2 in Sid is broken [SOLVED]

[Thom Castermans]

When I tried to update this morning, I was prevented from updating udisks2
by apt-listbugs.

So, I can confirm that the bug severity successfully prevented me from
breaking my system.

2017-08-30 9:20 GMT+02:00 Martin Steigerwald :

> Martin Steigerwald - 30.08.17, 09:12:
> > Martin Steigerwald - 30.08.17, 09:07:
> > > Put the package on hold.
> >
> > Before upgrading or downgrade to testing version.
> >
> > Alternatively use
> >
> > apt install libblockdev-fs2 libblockdev-part2 libblockdev-mdraid2
> > libblockdev- crypto2 libblockdev-loop2 libblockdev-swap2
> > systemctl restart udisks2
>
> You may also need gdisk package:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873634#26
>
>
> Bug is severity grave now, so I think it should show up in apt-listchanges.
> Don´t know why it didn´t for me.
>
> Its no Plasma specific issue. It breaks at least most modern desktop
> environments.
>
> Thanks,
> --
> Martin
>
>

Re: improving the UX with the default KDE installation

[Thom Castermans]

2017-03-20 16:11 GMT+01:00 Jimmy Johnson :

> Maybe you don't know it, but the average user does not know how to use a
> keyboard, like putting your index fingers on the f and j keys, basic typing.
>

I think that you are grossly underestimating the average computer user *who
is installing KDE on Debian Linux on their computer*.

[SOLVED] No SDDM on boot after upgrade, proprietary NVIDIA drivers

[Thom Castermans]

Dear all,

This is just for future reference and possibly to help others.

Today I did an upgrade in testing and got, on a later boot, no SDDM login
screen. I saw error messages scrolling by before I got TTY9. The last ones
repeatedly said that SDDM was started and then stopped immediately. In the
logs (`/var/log/kern.log`), I found that SDDM said that `Display server
failed to start. Exiting`.

I remembered and found in the APT logs that I had upgraded the kernel, but
saw that the NVIDIA kernel module was not recompiled, as it does normally.
Not sure why, maybe because it was a minor upgrade only? In any case,
reinstalling `nvidia-kernel-dkms` to trigger the recompile did the trick
for me: `aptitude reinstall nvidia-kernel-dkms`. The first time booting got
me a black screen for some reason, but the second boot (cold one this
time), I was greeted by SDDM again.

Cheers,
Thom

Re: KDE Frameworks 5.28.0

[Thom Castermans]

2016-11-20 10:45 GMT+01:00 Andrey Rahmatullin :

> On Sun, Nov 20, 2016 at 10:28:29AM +0100, Luc Castermans wrote:
> > > > > Just to let you know ´ aptitude -t sid safe-upgrade´  resulted in
> KDE
> > > > > Frameworks 5.28.0
> > > > >
> > > > > and other stuf.  All works nicely. Thanks !!
> > > > "Safe-upgrade?" First time I have heard of this. Next time, try it
> this way!
> > > It's the same as `apt upgrade`.
> > in contrast to ¨ aptitude dist-upgrade; which will upgrade all
> No, there is `aptitude full-upgrade` which is the same as `apt
> dist-upgrade`.
>
Just for completeness: aptitude in fact does recognize dist-upgrade. Its
man
page says the following about the full-upgrade option. "This command was
originally named dist-upgrade for historical reasons, and aptitude still
recognizes dist-upgrade as a synonym for full-upgrade."

More on topic: the man page for aptitude is actually very nice and explains
what
the difference is between a safe-upgrade and a full-upgrade in some detail.

Re: Compositing Problem

[Thom Castermans]

This may be something you already tried, but a friend of mine had this
issue so
I am suggesting it anyway.

Are you sure you need the 304.x version of the drivers? If you have a newer
graphics card, then using this older driver may cause problems. You can
check
this by running nvidia-debugdump --list to see your device name and then
searching for it in this list ,
or, probably easier, selecting it on this page
.

You can then search for the Debian package matching the suggested version.

Good luck, video drivers tend to be finicky...

Thom


2016-10-20 8:33 GMT+02:00 Jimmy Johnson :

> On 10/12/2016 12:10 PM, David Baron wrote:
>
>> Running must recent kwin, etc., with Sid nvidia-legacy-304xx driver.
>>
>> Window decorations slow or do not show on non-KDE windows. If they do not
>> show, one can pretend they are there and do everything.
>>
>> Effects all compositing options.
>>
>> Where to file bug?
>> Quick fix?
>>
>
> Quick fix, force install all your 'nvidia' and 'glx' installed packages
> back to 'Jessie-backports' and then 'lock-them' works, maybe 20-24 packages
> that you will be locking, varies a little with my installs, some I had not
> upgraded and I only had to lock the packages.  I used synaptic while in
> xfce4 and all your kde apps work from xfce4 too as a side note.  Note no
> problem with upgrades and those files being locked, at this time anyways.
> hehe
>
> There's a lot noise out there about fix's, I found nothing works for me.
> I came up with this fix and it works.  While gtk works with the upgrade,
> plasma don't, it's a problem with plasma, you can't blame nvidia and say
> they are not doing their part, this is a problem debian plasma, I'm sure
> they are working on it. Seems to affect only 'legacy-304' and could be a
> simple code error.
>
> With the Debian-nvidia driver: Plasma is unable to start as it could not
> correctly use OpenGL2.  Note dialog is working, sound is working, no plasma.
>
> With the Debian-free driver, computer freeze with colorful squiggly lines
> and I have to push the power button and repair the file system.
>
> David, do you have a better fix than down-grading the packages?  And I may
> not need to down grade as many packages as I do, but it works.
> --
> Jimmy Johnson
>
> Debian Sid/Testing - KDE Plasma Version 5.8.2 - EXT4 at sda15
> Registered Linux User #380263
>
>

Re: KF 5.27 and Plasma 5.8.1 coming

[Thom Castermans]

Yay indeed! :-)

It has been running like a charm for a couple of days now on my machine.

Thanks!


2016-10-16 23:47 GMT+02:00 Martin Steigerwald :

> Hello!
>
> Yay. :)
>
> Thank you,
> --
> Martin
>
>

Re: HIDPI insanity

[Thom Castermans]

Some time ago I got a laptop with a 4k display. I am not using that one
with
external monitors, but I still may be able to help a bit. With earlier
versions
of Plasma, scaling was pretty much not working. I was looking at tiny text
all
the time.

This changed at some point - I think when Plasma 5.6 rolled around, but not
exactly sure. Anyway, what I did was switching my scaling (System Settings
>
Display and Monitor > Display Configuration > Scale Display) back to 1, so
not
scaling up. On the other hand I set my font DPI (System Settings > Font >
Fonts
> Force fonts DPI) to 96 (after ticking the box of course). Since that
version
of Plasma, all interfaces appear to scale nicely in response to this.
Firefox
and Chrome apparently respect that setting too (although I may have played
around a bit with settings there, cannot remember).

Hopefully, the fonts DPI works across displays, given that Plasma knows the
DPI
of the monitor...?

Thom

2016-09-21 1:42 GMT+02:00 Rubin Abdi :

> I recently switched to an X1 Carbon 4th gen with the nicer HIDPI display.
> Sadly the rest of the desktop displays I plug into are still the old
> density. I noticed recently in 5.7.4 that most Qt based applications will
> do some notion of font DPI re-rendering when a window moves from one
> display to another, which is a step in the right direction though I wish
> there were some more exposed settings to specify which scaling factors for
> each monitor independently.
>
> Konsole has sadly stopped displaying the bitmap font Terminus properly on
> the HIDPI display (the letters look squished and the kerning is horrible),
> however when it pops onto my desktop display it looks fine. Using any other
> normal truetype or openfont causes 1px wide horizontal and vertical lines
> to get cut through the window displaying whatever is under it whenever
> there's a bunch of text that scrolls by or if I highlight text.
>
> Chrome (Chromium) thankfully respects my KDE global scale factor of 1.5,
> however it absolutely doesn't care about this new behavior of rescaling
> when the window moves between one display to another. It's been driving me
> mad to the point where I'm now saving up for a new 4k monitor just so I
> don't have to deal with this issue anymore.
>
> Anyone have some good tricks dealing with these issues?
>
> --
> Rubin
> ru...@starset.net
>

Re: task bar missing

[Thom Castermans]

2016-09-06 6:21 GMT+02:00 Gary Dale :

> This has been going on for a few weeks. I was hoping that it would get
> fixed but instead it's gotten worse.
>
> I'm running Debian/Testing on an AMD64 machine - with KDE obviously.
>
> When I reboot my computer, which I only do every week or so depending on
> on how it's behaving, the task bar is missing after I log in. Up until
> today, I could log out and it would reappear with the second login.
>

By task bar, do you mean a Plasma panel? I am not experiencing the same
issue. Does it happen when you add another panel too (to that panel)?
Something may have gone wrong during an update at some point. Also, it may
help to not lock your widgets between reboots. Last week there was a minor
issue with icons not appearing in the system tray that was fixed by that.


> Today it's just gone. A quick trip to Google came up with:
>kquitapp plasmashell && kstart plasmashell
> which brought it back.
>
> Just wanted to bring this to people's attention since reportbug doesn't
> seem to have done that.
>

Thank you :-)

Re: KDEPIM 16.04 - message view

[Thom Castermans]

Hi Andy,

Martin recently mentioned this an e-mail on this list.

On Mittwoch, 8. Juni 2016 17:20:38 CEST Martin Steigerwald wrote:
> Hi!
>
> In case you want to try it, also install the package kdepim-addons,
> otherwise mails are displayed without header and you cannot select a
header
> template in "View / Headers"

Do you have kdepim-addons installed?

Thom

2016-06-10 8:41 GMT+02:00 Andreas Bourges :

> Hi,
>
>
> ...I have a small problem customizing the message view in kontact/kmail
> 5.2. I
> use the layout where the message preview is shown below the message list,
> which works as expected so far.
>
> But within the message, no header information is shown (FROM:, CC:, ...)
> Only
> the message content itself is displayed :(
>
> So I tried to change the view via
>
> View -> Headers - which doesn't work. If I move to "View->Message List",
> another nested popup menu is displayed, which lets me select my desired
> Message aggregation/scheme/sorting.
>
> Not so for Headers. No additional Selection possibility (nested popup is
> not
> shown...) and I cannot change the way message headers are displayed.
>
> That's not really a showstopper, but kind of unconvenient, because the mail
> addresses of senders and receivers cannot be copied from a message anymore
> :(
>
> Does this feature work for others or is it a upstream problem?
>
> thanks,
>
> Andy
> --
>  Bdale is a contraction of Barksdale.
>  Hm.  It's definItely not something I'll ever remember.
>  Mind if I call you Wensleydale instead?
>
>

Re: jessie: stalled transfer notifications

[Thom Castermans]

>
> Synaptic does tell me that "apper" is installed.
>

Hopefully the reboot helped. If not, you may want to try uninstalling Apper
if
you use Synaptic anyway. Apper offers functionality to notify when there
are
updates, but in my experience it can eat up a lot of CPU while checking for
them all the time.

Re: jessie: stalled transfer notifications

[Thom Castermans]

Hi Doc,

Although I am not experiencing those issues myself, I can guess which
process(es) are responsible for those notifications and the CPU usage. Do
you
have KPackageKit, Apper or something similar installed? There are also a
couple
of different packages for update notifications related to this. You may
want to
`dpkg -l *update*` and `dpkg -l *noti*' (for notify, notification,
notifier) to find
packages related to this. I remember removing one or two of those packages
a while back, that got installed with an update.

Personally, I do not have very good experiences with these notifiers/GUIs
on top
of apt, but if you actually want to use them then it may be worth
investigating
more what causes the problems. If not, I would advise simply removing the
packages and using apt or aptitude directly.

Hope it helps!

Thom

2016-06-04 18:10 GMT+02:00 D. R. Evans :

> For the past few days, there have been several notifications on my desktop
> that refuse to terminate. (By this I mean that the little circle with the
> number of notifications has been sitting there with a non-zero number.)
>
> Right now, as I write this, the number of notifications is "10". Five of
> these
> are "Getting updates", and the other five are "Refreshing package cache". I
> associate these sorts of message with "dpkg" or "apt", but there is no
> process
> with those names running.
>
> The plasma-desktop process is using about 42% CPU, and nothing I have tried
> has either changed the amount of CPU being used, nor killed any of the jobs
> associated with the notifications.
>
> I have tried logging out and logging back in (several times), but that has
> no
> noticeable effect at all: the notifications remain, as does the CPU usage.
>
> Any suggestions as to how to get back to a situation with zero
> notifications
> and minimal CPU usage?
>
> For what it's worth, I have no idea at all what happened to cause this
> aberrant behaviour.
>
>   Doc
>
> --
> Web:  http://www.sff.net/people/N7DR
>
>