Processed: closing 573421
Processing commands for cont...@bugs.debian.org: # kdeprint is not in kde 4 close 573421 4:4.2.2-1 Bug#573421: kdeprint: deletes some files when printing multiple files 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 4:4.2.2-1, send any further explanations to Konrad Wilhelm Kleine kon...@konradwilhelm.de thanks Stopping processing here. Please contact me if you need assistance. -- 573421: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.12756379852592.transcr...@bugs.debian.org
Bug#582953: kmail deleted all non-local incoming mail settings on upgrade
tags 582953 unreproducible thanks Hello, On pirmadienis 24 Gegužė 2010 23:33:15 Juha Jäykkä wrote: Kmail is running with dimap, imap, imap and pop3 accounts. All is well. I run aptitude safe-upgrade. Upon next login and start of kmail, all the said accounts are gone from the settings. During this startup of kmail (and the corresponding startup of akonadi), there were numerous messages about unreadable mail folders. These happened to be folders of the dimap account, but I suspect that is simply coincidence: kmail listed the folders first and someone destroyed them before kmail actually accessed them. This makes me wonder if akonadi is the real culprit here, after all, but I have no way of finding out. The safe-upgrade did not update kmail, but it did update akonadi-server. There is no way akonadi could have destroyed your local mail. If the problem was with address book, then it would be another story. Critical: data loss: if pop3 account emails are on local disc instead of the server, those messages are lost. I suspect you had file system problems and kmail configs got eaten in the process ( ~/.kde/share/config/kmail* ). There might even be some leftovers with odd names ~/.kde/share/config/kmailrc*.new etc. Try recovering from them. The mail should still be there in ~/Mail or somewhere in ~/.kde/share/apps/kmail/ Unless you give more proof that it's really a problem with kmail, the next step will be severity downgrade of this bug. testing-testing and sid-sid upgrades are not 100% supported anyway though I'm pretty sure upgrade had nothing to do with it. However, if you upgrade with kmail/KDE running, sometimes odd things happen. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#582953: kmail deleted all non-local incoming mail settings on upgrade
Processing commands for cont...@bugs.debian.org: tags 582953 unreproducible Bug #582953 [kmail] kmail deleted all non-local incoming mail settings on upgrade Added tag(s) unreproducible. thanks Stopping processing here. Please contact me if you need assistance. -- 582953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127563942511337.transcr...@bugs.debian.org
Bug#582953: kmail deleted all non-local incoming mail settings on upgrade
I suspect you had file system problems and kmail configs got eaten in the process ( ~/.kde/share/config/kmail* ). There might even be some leftovers with odd names ~/.kde/share/config/kmailrc*.new etc. Try recovering from them. The mail should still be there in ~/Mail or somewhere in ~/.kde/share/apps/kmail/ File system was clean both before and after. As to the configs getting eaten, yes, they did vanish. Likewise, ~/.kde/share/apps/kmail/ was empty apart from some directories after the upgrade. No files were present. Thus no mail. Unless you give more proof that it's really a problem with kmail, the next Quite impossible since the upgrade is done. nothing to do with it. However, if you upgrade with kmail/KDE running, sometimes odd things happen. What do you mean KDE running? I did not have kmail, but I did have kded and several other KDE-related processes running, but I never run KDE because it forces me to logout for upgrades; by running just openbox the only userspace program upgrades I need to log off for are X and openbox. If the deletion of data is due to odd things happening when upgrading while kde-related processes are running, this is a bug: very many people use graphical apt-front-ends to upgrade their machines and it simply must work. A logoff or reboot may be required, yes, but under no circumstances must user data be deleted without explicit permission. What was the upgrade doing inside $HOME anyway? Packages should not touch anything in $HOME. That said, there was that odd set of error messages at first start of kmail after the upgrade, so perhaps the package did not touch $HOME, but kmail itself, for some reason, deleted all its mail settings and data at first restart. I suggest you go though the kmail code to see where it does unlink() on its mail during startup and under what conditions that happens. Clearly, the only condition when that should happen is when the user explicitly asks kmail to delete messages. -Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#582953: kmail deleted all non-local incoming mail settings on upgrade
Hello, On penktadienis 04 Birželis 2010 11:46:52 Juha Jäykkä wrote: What do you mean KDE running? I did not have kmail, but I did have kded and several other KDE-related processes running, but I never run KDE because it forces me to logout for upgrades; by running just openbox the only userspace program upgrades I need to log off for are X and openbox. If the deletion of data is due to odd things happening when upgrading while kde-related processes are running, this is a bug: very many people use graphical apt-front-ends to upgrade their machines and it simply must work. A logoff or reboot may be required, yes, but under no circumstances must user data be deleted without explicit permission. What was the upgrade doing inside $HOME anyway? Packages should not touch anything in $HOME. So as I said it is very unlikely to have been caused by upgrade. That said, there was that odd set of error messages at first start of kmail after the upgrade, so perhaps the package did not touch $HOME, but kmail itself, for some reason, deleted all its mail settings and data at first restart. I suggest you go though the kmail code to see where it does unlink() on its mail during startup and under what conditions that happens. Clearly, the only condition when that should happen is when the user explicitly asks kmail to delete messages. Well, your report does not have much useful information: odd set of error messages, apart from some directories etc. You aren't very specific. And my kmail stores mails in ~/Mail. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Processed: inappropriate mass bug filing
Processing commands for cont...@bugs.debian.org: # See comment below close 583634 Bug#583634: evince: Insecure ghostscript invocation 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 583668 Bug#583668: Possibly insecure temporary file when parsing pdf files 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 583996 Bug#583996: asymptote: Security bugs in ghostscript 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 583997 Bug#583997: bmv: Security bugs in ghostscript 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 583998 Bug#583998: c2050: Security bugs in ghostscript 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 584000 Bug#584000: capisuite: Security bugs in ghostscript 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 584004 Bug#584004: epix1: Security bugs in ghostscript 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 584006 Bug#584006: fbi: Security bugs in ghostscript 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 584007 Bug#584007: fig2ps: Security bugs in ghostscript 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 584008 Bug#584008: flpsed: Security bugs in ghostscript 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 584010 Bug#584010: hpijs: Security bugs in ghostscript 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 584011 Bug#584011: hylafax-client: Security bugs in ghostscript 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 584012 Bug#584012: hylafax-server: Security bugs in ghostscript 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 584013 Bug#584013: hyperlatex: Security bugs in ghostscript 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 584014 Bug#584014: ifhp: Security bugs in ghostscript 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 584015 Bug#584015: ijsgutenprint: Security bugs in ghostscript 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 584016 Bug#584016: kghostview: Security bugs in ghostscript 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 584018 Bug#584018: libgs-dev: Security bugs in ghostscript 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 584022 Bug#584022: page-crunch: Security bugs in ghostscript 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 584024 Bug#584024: pkpgcounter: Security bugs in ghostscript 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 584025 Bug#584025: pnm2ppa: Security bugs in ghostscript 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 584026 Bug#584026: printconf: Security bugs in ghostscript 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Paul Szabo paul.sz...@sydney.edu.au close 584027 Bug#584027: ps2eps: Security
Bug#584157: [korganizer] Reminder doesn't remind anything
Peter Fritzsche wrote:
Package: korganizer
Version: 4:4.4.3-1
Severity: normal
korgac doesn't remind me on any dates I have added to korganizer (of course
I added events with reminders enabled). I am using akonadi with file
backend and birthday backend. I think that events with time associated
show normally. Just tried to test it using an event for today (qwe - warn
15 minutes before start; zxc - warn 15 minutes after start) and one event
with time associated (warn 2 minutes before start)
I tried to use dumpAlarms of dbus org.kde.korganizer.KOrgac and it shows
{AlarmDeamon::dumpAlarms() from 2010-06-01T00:00:00+02:00 to
2010-06-01T23:59:59+02:00, asd (2010-06-01T21:39:00+02:00), qwe
(2010-06-01), zxc (2010-06-01)}
I see a reminder for asd, but still miss the one for qwe and zxc.
The problem seems to be that akonadi (at least on debian) isn't finished
loading itself and all resource handler when korgac tries the first time to
get all alarms since it was closed. See
https://bugs.kde.org/show_bug.cgi?id=223388 for more information. The only fix
which can be done by the user is to _not_ use akonadi resources in korganizer.
Best regards,
Peter
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201006041701.15941.peter.fritzs...@gmx.de
Bug#584157: [korganizer] Reminder doesn't remind anything
Peter Fritzsche wrote:
Peter Fritzsche wrote:
Package: korganizer
Version: 4:4.4.3-1
Severity: normal
korgac doesn't remind me on any dates I have added to korganizer (of
course I added events with reminders enabled). I am using akonadi with
file backend and birthday backend. I think that events with time
associated show normally. Just tried to test it using an event for today
(qwe - warn 15 minutes before start; zxc - warn 15 minutes after start)
and one event with time associated (warn 2 minutes before start)
I tried to use dumpAlarms of dbus org.kde.korganizer.KOrgac and it shows
{AlarmDeamon::dumpAlarms() from 2010-06-01T00:00:00+02:00 to
2010-06-01T23:59:59+02:00, asd (2010-06-01T21:39:00+02:00), qwe
(2010-06-01), zxc (2010-06-01)}
I see a reminder for asd, but still miss the one for qwe and zxc.
The problem seems to be that akonadi (at least on debian) isn't finished
loading itself and all resource handler when korgac tries the first time to
get all alarms since it was closed. See
https://bugs.kde.org/show_bug.cgi?id=223388 for more information. The only
fix which can be done by the user is to _not_ use akonadi resources in
korganizer.
A workaround for now could be that a akonadi is started using a script with
#! /bin/sh
/usr/bin/akonadictl start
In $HOME/.kde/Autostart/force-akonadistart.sh (dont forget to make it
executable).
At least here it works a lot better than automatic starting of akonadi by kde
itself.
Best regards,
Peter
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201006041709.56621.peter.fritzs...@gmx.de
Bug#584577: kde-plasma-desktop: Panel resizes unexpectedly
Package: kde-plasma-desktop Version: 5:61 Severity: normal Tags: squeeze Panel resizes unexpectedly from full-screen to half-screen, left justified. Can be reset, but the issue recurs. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-15-phenom (SMP w/4 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 kde-plasma-desktop depends on: ii kdebase-apps 4:4.4.3-1 base applications from the officia ii kdebase-runtime 4:4.4.3-1 runtime components from the offici ii kdebase-workspace 4:4.4.3-1 base workspace components from the ii plasma-desktop4:4.4.3-1 The KDE Plasma workspace for deskt Versions of packages kde-plasma-desktop recommends: ii kdm 4:4.4.3-1 KDE Display Manager for X11 ii xserver-xorg 1:7.5+6the X.Org X server Versions of packages kde-plasma-desktop suggests: pn kde-l10n none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100604183614.11659.95298.report...@localhost.localdomain
Bug#584602: [ksudoku] The ksudoku is easy to solve in spite of the most difficult request
Package: ksudoku Version: 4:4.4.4-1 Severity: normal --- Please enter the report below this line. --- When I select the most difficulty level in ksudoku, I solved it between 3 and 5 minutes, being normal is between 15 and 30 minutes --- System information. --- Architecture: amd64 Kernel: Linux 2.6.32-5-amd64 Debian Release: squeeze/sid 500 unstableftp.caliu.cat 500 unstableftp.bg.debian.org 500 testing security.debian.org 500 testing ftp.es.debian.org 500 testing ftp.caliu.cat 500 lucid ppa.launchpad.net 1 experimentalftp.caliu.cat --- Package information. --- Depends(Version) | Installed -+-= kdebase-runtime | 4:4.4.4-1 libc6 (= 2.2.5) | 2.11.1-2 libgl1-mesa-glx | 7.7.1-2 OR libgl1 | libglu1-mesa | 7.7.1-2 OR libglu1 | libkdecore5 (= 4:4.4.0) | 4:4.4.4-1 libkdegames5(= 4:4.3.4) | 4:4.4.4-1 libkdeui5 (= 4:4.4) | 4:4.4.4-1 libkio5 (= 4:4.4) | 4:4.4.4-1 libqt4-opengl (= 4:4.5.3) | 4:4.6.2-5 libqt4-svg (= 4:4.5.3) | 4:4.6.2-5 libqt4-xml (= 4:4.5.3) | 4:4.6.2-5 libqtcore4 (= 4:4.6.1) | 4:4.6.2-5 libqtgui4 (= 4:4.5.3) | 4:4.6.2-5 libstdc++6(= 4.1.1) | 4.4.4-3 Package's Recommends field is empty. Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100604233244.ga7...@despatx.nubiola.cat
Bug#584614: Blogilo: missing dependency on libqt4-sql-sqlite
Package: blogilo Version: 4:4.4.3-1 Severity: normal Launching from GNOME. l...@liberty:~ $ Blogilo 1.0.1 Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kwalletd(16002) KWalletD::setupDialog: Application ' Blogilo ' using kwallet without parent window! kdeinit4: preparing to launch /usr/bin/kwalletmanager QSqlDatabase: QSQLITE driver not loaded QSqlDatabase: available drivers: QMYSQL3 QMYSQL knotify(16010) KNotify::event: 6 ref= 0 [1]+ Doneblogilo l...@liberty:~ $ knotify(16010) NotifyByPopup::slotDBusNotificationClosed: 514 - 0 knotify(16010) NotifyByPopup::slotDBusNotificationClosed: failed to find knotify id for dbus_id 514 Asks for kdewallet, then pops up error message saying Driver not loaded Driver not loaded (sic). Installing libqt4-sql-sqlite fixes. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (700, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-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/bash Versions of packages blogilo depends on: ii kdebase-runtime 4:4.4.3-1 runtime components from the offici ii kdepim-runtime4:4.4.3-1 Runtime components for akonadi-kde ii libc6 2.10.2-9 Embedded GNU C Library: Shared lib ii libkblog4 4:4.4.3-1 client-side support library for we ii libkdecore5 4:4.4.3-2 the KDE Platform Core Library ii libkdeui5 4:4.4.3-2 the KDE Platform User Interface Li ii libkhtml5 4:4.4.3-2 the KHTML Web Content Rendering En ii libkio5 4:4.4.3-2 the Network-enabled File Managemen ii libktexteditor4 4:4.4.3-2 the KTextEditor interfaces for the ii libqt4-sql4:4.6.2-4 Qt 4 SQL module ii libqtcore44:4.6.2-4 Qt 4 core module ii libqtgui4 4:4.6.2-4 Qt 4 GUI module ii libstdc++64.4.4-1The GNU Standard C++ Library v3 blogilo recommends no packages. blogilo suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100605040053.18460.28283.report...@localhost.localdomain
