Your message dated Sun, 25 Aug 2019 15:29:15 +0000
with message-id <[email protected]>
and subject line Bug#935664: Removed package(s) from unstable
has caused the Debian Bug report #550877,
regarding componentchooser KCM shall not kill window manager not under KDE
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
550877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550877
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemsettings
Version: 4:4.3.2-1
Severity: critical
Justification: causes serious data loss

In systemsettings -> Default Applications -> Window Manager; i selected "use a 
different window manager", namely: Openbox. Before it was at "use the default 
KDE window manager (KWin)". Then a window came up, notifying me, that the new 
window manager will be started, so I clicked ok. It's funny that I was already 
in OpenBox, and so I thought nothing would happen. However after clicking ok, 
the X11 Session closed, and I was greeted with the LDM Login manager (used in 
LTSP), while potentially loosing all unsaved documents..  

I don't use KDE4, but I installed kdebase-workspace, so that Kded wouldn't spam 
my terminal window full of messages. I have Xorg running on a thin client via 
the standard Linux Terminal Server Project, and it has it's own login manager 
(LDM). systemsettings needs to:
- recognize that KDE isn't the window manager in use (why was it selected the 
first time i launched systemsettings?)
- a clearer warning should be issued to the user, that he should save his 
documents before X11 restarts

Another potential issue is that when I select "use the default KDE window 
manager (KWin)", the same thing happens as (hopefully well) described above. 
Yet, OpenBox starts, since LDM is the login manager and not KDM. 


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemsettings depends on:
ii  kdebase-runtime               4:4.3.2-1  runtime components from the offici
ii  kdelibs5                      4:4.3.2-2  core libraries for all KDE 4 appli
ii  libc6                         2.9-27     GNU C Library: Shared libraries
ii  libfontconfig1                2.6.0-4    generic font configuration library
ii  libqt4-dbus                   4:4.5.3-3  Qt 4 D-Bus module
ii  libqt4-xml                    4:4.5.3-3  Qt 4 XML module
ii  libqtcore4                    4:4.5.3-3  Qt 4 core module
ii  libqtgui4                     4:4.5.3-3  Qt 4 GUI module
ii  libstdc++6                    4.4.1-6    The GNU Standard C++ Library v3
ii  libx11-6                      2:1.2.2-1  X11 client-side library

systemsettings recommends no packages.

systemsettings suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 4:17.08.3-2.1+rm

Dear submitter,

as the package kde-runtime has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/935664

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to