[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers

2021-02-05 Thread Donald Krebs
https://bugs.kde.org/show_bug.cgi?id=341143

--- Comment #388 from Donald Krebs  ---
I get it! What we're asking for 'just not important enough' for the last 6
years! I get it - this will NEVER be important enough


Donald Krebs - mobile

On Wed, Jun 3, 2020, 4:49 AM pier andre  wrote:

> https://bugs.kde.org/show_bug.cgi?id=341143
>
> --- Comment #336 from pier andre  ---
> (In reply to Christoph Feck from comment #333)
> > Is there a reason you cannot use Vallpaper? The Plasma 5 architecture is
> > very different from KDE 4, and right now the only way to solve this
> issue is
> > exactly what Vallpaper does.
>
> as for the architecture of many buildings doesn't allow to run across them
> with
> wheelchair is wrong, the same for plasma5 architecture that doesn't allow
> to
> have different wallpapers and widgets for each desktop is also wrong, so, I
> hope the developers will change the next architecture to allow more things
> to
> run across :-)
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers

2020-09-10 Thread Donald Krebs
https://bugs.kde.org/show_bug.cgi?id=341143

--- Comment #376 from Donald Krebs  ---
I just added $25 to the bounty program.
I'm not a developer, just an old guy that enjoys building and maintaining
sites for friends and groups I want to support.
Way back when... I settled on a work flow that was easy and... fun. With
WordPress open on a Virtual Desktop (with a blue background), Chrome open
on another, (with a yellow background), and a Google Doc on another (with a
black background). The work flow was comfortable and intuitive.
Since losing the unique backgrounds, I find myself thinking "this used to
be easier."
I tried using "activities" but I abandoned it. It seems like adding
complexity to something that was valuable because of its simplicity.
Ditto using an app. Learning how to use the app took time and
concentration... once again, adding complexity to achieve simplicity.
My little arrangement is so simple that I get by without the feature I once
made use of.
I must admit that whenever I read through this thread, I'm a bit resentful
and more than a little perplexed. What developer thinks it's a good idea to
REMOVE features? Isn't it your job to improve and simplify your product?
Adding features and capabilities?
I changed the default $15 bounty to $25 because, in my mind, that's about
what I would be willing to pay for an app that would do nothing more than
allow unique backgrounds on Virtual Desktops.
For an eighty year old hobbyist living on Social Security, that $25 is
precious.
Forgive my rambling but one last thing... consider this a challenge. What
is it worth to YOU to get this done and put behind us?
~~~~
Donald Krebs - mobile

On Thu, Sep 10, 2020, 1:47 PM  wrote:

> https://bugs.kde.org/show_bug.cgi?id=341143
>
> --- Comment #374 from abrah...@acm.org ---
> I'm one of the early complainers about the loss of different wallpapers on
> different desktops.  I'd be quite happy if different activities could have
> different wallpapers and I could just think of activities as being desktops
> with some additional properties I'd never use.  If I could just think of
> activities as desktops called something else, I and presumably most of the
> other unhappy users would be satisfied.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 406325] New: Krita crashed on 'open file'

2019-04-08 Thread Donald Krebs
https://bugs.kde.org/show_bug.cgi?id=406325

Bug ID: 406325
   Summary: Krita  crashed on 'open file'
   Product: krita
   Version: 4.1.5
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: krebs@gmail.com
  Target Milestone: ---

Application: krita (4.1.5)
 (Compiled from sources)
Qt Version: 5.11.3
Frameworks Version: 5.56.0
Operating System: Linux 5.0.0-8-generic x86_64
Distribution: Ubuntu Disco Dingo (development branch)

-- Information about the crash:
- What I was doing when the application crashed: I downloaded an image from
Bing.com then selected 'open in Krita.' it didn't open the file but Krita
opened. From Krita, I selected 'open file' and Krita crashen

-- Backtrace:
Application: Krita (krita), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1f1659b800 (LWP 14449))]

Thread 9 (Thread 0x7f1ede62a700 (LWP 14458)):
#0  0x7f1f1dff3ba9 in __GI___poll (fds=0x7f1ed0004c00, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f1f19ebbcb6 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1f19ebbddc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1f1e58504b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f1f1e53214b in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f1f1e3810d6 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f1f0fcaf4a6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7f1f1e38ac77 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f1f1a685182 in start_thread (arg=) at
pthread_create.c:486
#9  0x7f1f1daf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7f1ee7fff700 (LWP 14457)):
#0  0x7fffc93e8637 in ?? ()
#1  0x7f1f1e00ebc6 in __GI___clock_gettime (clock_id=1, tp=0x7f1ee7ffeac0)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f1f1e584971 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f1f1e5831a9 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f1f1e5837a5 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f1f1e584dce in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f1f19ebb1e9 in g_main_context_prepare () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f1f19ebbbeb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f1f19ebbddc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f1f1e58504b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f1f1e53214b in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f1f1e3810d6 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f1f0fa2a3a5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#13 0x7f1f1e38ac77 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f1f1a685182 in start_thread (arg=) at
pthread_create.c:486
#15 0x7f1f1daf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7f1ee77fe700 (LWP 14456)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f1f1e37fff0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f1f1e37fe62 in QSemaphore::tryAcquire(int, int) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f1f1c801faa in KisTileDataSwapper::run() () from
/usr/lib/x86_64-linux-gnu/libkritaimage.so.17
#4  0x7f1f1e38ac77 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f1f1a685182 in start_thread (arg=) at
pthread_create.c:486
#6  0x7f1f1daf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7f1eecbf5700 (LWP 14454)):
#0  0x7f1f19ebbddc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f1f1e58504b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f1f1e53214b in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f1f1e3810d6 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f1f1e38ac77 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f1f1a685182 in start_thread (arg=) at
pthread_create.c:486
#6  0x7f1f1daf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7f1f08f78700 (LWP 14453)):
#0  __GI___libc_read (nbytes=16, 

[kde] [Bug 398164] New: WISH: Daily Bing wallpaper region select

2018-09-02 Thread Donald Krebs
https://bugs.kde.org/show_bug.cgi?id=398164

Bug ID: 398164
   Summary: WISH: Daily Bing wallpaper region select
   Product: kde
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: krebs@gmail.com
  Target Milestone: ---

Daily Wallpapers from Bing come from UK feed. I'd like to see the ability to
select other regions.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

2016-01-03 Thread Donald Krebs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341143

--- Comment #155 from Donald Krebs <krebs@gmail.com> ---
First to the developers; thanks. You have devised an OS like to use on my
primary, most stressed, computer. Thanks. Again, Thanks.
Now to everyone else: Back off a little. A free OS that just works. It doesn't
take  the almost daily tweaking that goes with my Windows machines. State your
case, without the threats and slurs.
MORE: Does anyone remember if Ver. 4 allowed Screen Savers? It seems so to me,
but I'm not going to back up just to research it.
This morning I had the bright idea to set up one of my 'activities' (I have 4
and 2 Virtual desktops for each) to have a screensaver. I was thinking, "look
at the pretty picture, then just wriggle the mouse and check my email."
So, my qx: Is screensavers another feature that was deprecated in Ver.5?
(Though this is probably not the place to ask that question)

-- 
You are receiving this mail because:
You are watching all bug changes.