[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#748314: marked as done (kde-runtime-data: kuiserver parse initrd at each kde startup)

Your message dated Mon, 20 Mar 2017 21:48:34 +0100
with message-id <20170320204827.ckoig5ianms2pijo@gnuservers.com.ar>
and subject line Re: Bug#748314: kde-runtime-data: kuiserver parse initrd at each kde startup
has caused the Debian Bug report #748314,
regarding kde-runtime-data: kuiserver parse initrd at each kde startup
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 owner@bugs.debian.org
immediately.)


-- 
748314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748314
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: kde-runtime-data
Version: 4:4.12.4-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

Dear Maintainer,

kuiserver parse initrd at each kde startup AND output errors in [/var/log/] syslog, user.log and messages.
This can be seen as not critical, but the critical problem is in the log output.
While parsing initrd is totally useless and slow down the system a bit, the log output is the problem that makes the system unusable.
Because it output one line per "character" fond in initrd file. In a few days and some reboot or logout / login my little hard drive was full.

I've already search in kde's bug system and forums (and googling a bit too) but found nothing related. Search was made with keywords kuiserver, initrd and $
I've also checked my config (.config, .local and .kde) and found nothing.

   * What led up to the situation?

update to last kde packages and systemd

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

nothing

My best to the team
Xavier (zeroheure)


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

Kernel: Linux 3.14-1-686-pae (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kde-runtime-data depends on:
ii  perl  5.18.2-4

kde-runtime-data recommends no packages.

kde-runtime-data suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
¡Hola 748314!

El 2014-08-28 a las 20:04 +0200, Maximiliano Curia escribió:
Control: tag -1 + unreproducible Control: severity -1 important
We are not sure what triggers this issue in your system, but we couldn't reproduce it in ours. You may have some specific configuration that make some program to behave badly (appending / or /boot to KDEDIRS for instance). Or it could be an issue of some program that gets auto started on session startup. Please, can you test this issue with a new user? If that still doesnt fix the issue, please check which programs are autostarted. 


I'm downgrading the bug severity due to the apparent unreproducibility of it.
I'm closing the issue after 2 years and a half of inactivity. Please reopen if you can still reproduce the issue, but please, add the requested information. 

Happy hacking,
--
"The use of COBOL cripples the mind; its teaching should, therefore, be
regarded as a criminal offense."
-- Edsger W. Dijkstra
Saludos /\/\ /\ >< `/

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: