Bug#885182: [kmail] Once more, with feeling ...
Package: kmail Version: 4:17.12.3-1 --- Please enter the report below this line. --- I am running Sid so must accept occasional breakage. However, such long-term breakage on TESTING of the Kmail/Akonadi stuff is not acceptable. --- System information. --- Architecture: Kernel: Linux 4.15.0-1-amd64 Debian Release: buster/sid 500 yakkety ppa.launchpad.net 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com 500 lucid ppa.launchpad.net 100 jessie-backports ftp.us.debian.org 1 experimentalftp.us.debian.org --- Package information. --- Depends (Version) | Installed =-+- == akonadi-server (>= 4:17.08~) | 4:17.12.3-2+b1 kdepim-runtime (>= 4:17.08~) | 4:17.12.3-1 libkf5akonadisearch-bin (>= 4:17.08~) | 4:17.12.3-1 libkf5akonadisearch-plugins (>= 4:17.08~) | 4:17.12.3-1 libkf5grantleetheme-plugins (>= 17.08~) | 17.12.3-1 kio | 5.44.0-2 libc6 (>= 2.14) | libgcc1(>= 1:3.0) | libgpgmepp6 (>= 1.10.0) | libkf5akonadiagentbase5 (>= 4:15.07.90) | libkf5akonadicontact5 (>= 4:17.12.2) | libkf5akonadicore5abi1 (>= 4:17.12.1) | libkf5akonadimime5 (>= 4:17.12.2) | libkf5akonadisearchdebug5 (>= 4:17.12.2) | libkf5akonadisearchpim5(>= 4:16.08.0) | libkf5akonadiwidgets5abi1 (>= 4:17.12.1) | libkf5bookmarks5 (>= 4.96.0) | libkf5calendarcore5abi1(>= 4:17.12.1) | libkf5calendarutils5 (>= 4:17.12.2) | libkf5codecs5 (>= 5.4.0+git20141202.0008+15.04) | libkf5completion5 (>= 4.97.0) | libkf5configcore5 (>= 4.98.0) | libkf5configgui5 (>= 4.97.0) | libkf5configwidgets5 (>= 5.23.0) | libkf5contacts5(>= 4:15.12.0) | libkf5coreaddons5 (>= 5.2.0) | libkf5crash5 (>= 5.15.0) | libkf5dbusaddons5 (>= 4.97.0) | libkf5followupreminder5(>= 4:16.04.0) | libkf5gravatar5abi1(>= 4:17.12.2) | libkf5guiaddons5 (>= 4.96.0) | libkf5i18n5 (>= 4.97.0) | libkf5iconthemes5 (>= 5.0.0) | libkf5identitymanagement5(>= 17.12.2) | libkf5itemmodels5 (>= 4.96.0) | libkf5itemviews5 (>= 4.96.0) | libkf5jobwidgets5 (>= 4.96.0) | libkf5kcmutils5(>= 5.2.0+git20141003) | libkf5kiocore5(>= 4.96.0) | libkf5kiofilewidgets5 (>= 4.96.0) | libkf5kiowidgets5 (>= 5.35.0) | libkf5kontactinterface5 (>= 17.12.2) | libkf5ksieveui5(>= 4:17.12.2) | libkf5libkdepim-plugins | libkf5libkdepim5 (>= 4:16.04.0) | libkf5libkdepimakonadi5(>= 4:17.12.2) | libkf5libkleo5 (>= 4:17.08.0) | libkf5mailcommon5abi1 (>= 4:17.12.2) | libkf5mailtransport5 (>= 17.12.2) | libkf5mailtransportakonadi5 (>= 17.12.2) | libkf5messagecomposer5 (>= 4:17.12.2) | libkf5messagecore5 (>= 4:17.12.2) | libkf5messagelist5 (>= 4:17.12.2) | libkf5messageviewer5 (>= 4:17.12.2) | libkf5mime5abi1 (>= 17.12.1) | libkf5mimetreeparser5 (>= 4:17.12.2) | libkf5notifications5 (>= 4.96.0) | libkf5notifyconfig5 (>= 4.96.0) | libkf5parts5 (>= 4.96.0) | libkf5pimcommon5abi1
Bug#892596: [systemsettings] Comes up with black windows
Package: systemsettings Version: 4:5.12.3-1 Severity: grave --- Please enter the report below this line. --- Previous version and current version: Application comes up with black windows. The left pane will show its MouseOver toolboxes. --- System information. --- Architecture: Kernel: Linux 4.15.0-1-amd64 Debian Release: buster/sid 500 yakkety ppa.launchpad.net 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com 500 lucid ppa.launchpad.net 100 jessie-backports ftp.us.debian.org 1 experimentalftp.us.debian.org --- Package information. --- Depends(Version) | Installed -+- qml-module-org-kde-kcm | 5.42.0-2 qml-module-org-kde-kirigami2 | 5.42.0-3 qml-module-qtquick-controls | 5.9.2-2 qml-module-qtquick-layouts | 5.9.2-3 qml-module-qtquick2 | 5.9.2-3 kio | 5.42.0-3 kpackagetool5| 5.42.0-2 libc6 (>= 2.14) | libkf5activities5(>= 4.96.0) | libkf5activitiesstats1 (>= 5.20) | libkf5auth5 (>= 4.96.0) | libkf5completion5(>= 4.97.0) | libkf5configcore5(>= 4.98.0) | libkf5configgui5 (>= 4.97.0) | libkf5configwidgets5 (>= 4.96.0) | libkf5coreaddons5(>= 5.16.0) | libkf5crash5 (>= 5.15.0) | libkf5dbusaddons5(>= 4.99.0) | libkf5declarative5 (>= 4.96.0) | libkf5i18n5 (>= 5.17.0) | libkf5iconthemes5(>= 4.96.0) | libkf5itemviews5 (>= 4.96.0) | libkf5kcmutils5 (>= 4.96.0) | libkf5khtml5 (>= 4.96.0) | libkf5kiowidgets5(>= 4.96.0) | libkf5package5(>= 5.5.0+git) | libkf5service-bin| libkf5service5 (>= 4.99.0) | libkf5widgetsaddons5 (>= 5.35.0) | libkf5windowsystem5 (>= 4.96.0) | libkf5xmlgui5(>= 4.98.0) | libqt5core5a (>= 5.9.0~beta) | libqt5dbus5 (>= 5.7.0~) | libqt5gui5(>= 5.7.0) | libqt5qml5(>= 5.0.2) | libqt5quick5 (>= 5.0.2) | libqt5quickwidgets5 (>= 5.5.0) | libqt5widgets5 (>= 5.7.0~) | libstdc++6(>= 4.1.1) | Package's Recommends field is empty. Package's Suggests field is empty.
Bug#885182: [kmail] Time overdue to fix this stuff
Package: kmail Version: 4:17.08.3-2 --- Please enter the report below this line. --- Yes, I realize that on Sid, some breakage is expected. Been running this long enough. But there is a limit. Releasing versions that are not ready to play. Putting those on testing!! And just letting it sit. Yes, time to fix it already. --- System information. --- Architecture: Kernel: Linux 4.14.0-2-amd64 Debian Release: buster/sid 500 yakkety ppa.launchpad.net 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com 500 lucid ppa.launchpad.net 100 jessie-backports ftp.us.debian.org 1 experimentalftp.us.debian.org --- Package information. --- Depends (Version) | Installed =-+- == akonadi-server (>= 4:17.08~) | 4:17.08.3-2 kdepim-runtime (>= 4:17.08~) | 4:17.08.3-3 libkf5akonadisearch-bin (>= 4:17.08~) | 4:17.08.3-1 libkf5akonadisearch-plugins (>= 4:17.08~) | 4:17.08.3-1 libkf5grantleetheme-plugins (>= 17.08~) | 17.08.3-1 kio | 5.37.0-2 libc6 (>= 2.14) | libgcc1(>= 1:3.0) | libgpgmepp6 (>= 1.10.0) | libkf5akonadiagentbase5 (>= 15.07.90) | libkf5akonadicontact5 | libkf5akonadicore5 (>= 4:17.08.0) | libkf5akonadimime5| libkf5akonadisearchdebug5 | libkf5akonadisearchpim5 (>= 16.08.0) | libkf5akonadiwidgets5 (>= 4:17.08.0) | libkf5bookmarks5 (>= 4.96.0) | libkf5calendarcore5 (>= 15.07.90) | libkf5calendarutils5 | libkf5codecs5 (>= 5.4.0+git20141202.0008+15.04) | libkf5completion5 (>= 4.97.0) | libkf5configcore5 (>= 4.98.0) | libkf5configgui5 (>= 4.97.0) | libkf5configwidgets5 (>= 5.23.0) | libkf5contacts5 (>= 15.12.0) | libkf5coreaddons5 (>= 5.2.0) | libkf5crash5 (>= 5.15.0) | libkf5dbusaddons5 (>= 4.97.0) | libkf5followupreminder5(>= 4:16.04.0) | libkf5gravatar5 (>= 4:15.12) | libkf5guiaddons5 (>= 4.96.0) | libkf5i18n5 (>= 4.97.0) | libkf5iconthemes5 (>= 5.0.0) | libkf5identitymanagement5(>= 17.08.0) | libkf5itemmodels5 (>= 4.96.0) | libkf5itemviews5 (>= 4.96.0) | libkf5jobwidgets5 (>= 4.96.0) | libkf5kcmutils5(>= 5.2.0+git20141003) | libkf5kiocore5(>= 4.96.0) | libkf5kiofilewidgets5 (>= 4.96.0) | libkf5kiowidgets5 (>= 5.35.0) | libkf5kontactinterface5 | libkf5ksieveui5 | libkf5libkdepim-plugins | libkf5libkdepim5 (>= 16.04) | libkf5libkdepimakonadi5 | libkf5libkleo5 (>= 4:17.08.0) | libkf5mailcommon-plugins | libkf5mailcommon5 (>= 4:17.08.3) | libkf5mailtransport5 | libkf5mailtransportakonadi5 | libkf5messagecomposer5| libkf5messagecore5| libkf5messagelist5| libkf5messageviewer5 | libkf5mime5 (>= 15.12.0) | libkf5mimetreeparser5 | libkf5notifications5 (>= 4.96.0) |
Bug#885182: [kmail] KMail Does Not Receive Messages (IMAP)
Package: kmail Version: 4:17.08.3-1 Severity: important --- Please enter the report below this line. --- After recent update, KMail does not receive message (IMAP, GMail). Reported password rejections that worked once reset or retried. Still no new messages. Old messages (this is IMAP, inbox) are intact. --- System information. --- Architecture: Kernel: Linux 4.14.0-1-amd64 Debian Release: buster/sid 500 yakkety ppa.launchpad.net 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com 500 lucid ppa.launchpad.net 100 jessie-backports ftp.us.debian.org 1 experimentalftp.us.debian.org --- Package information. --- Depends (Version) | Installed =-+- == akonadi-server (>= 4:17.08~) | 4:17.08.3-1 kdepim-runtime (>= 4:17.08~) | 4:17.08.3-1 libkf5akonadisearch-bin (>= 4:17.08~) | 4:17.08.3-1 libkf5akonadisearch-plugins (>= 4:17.08~) | 4:17.08.3-1 libkf5grantleetheme-plugins (>= 17.08~) | 17.08.3-1 kio | 5.37.0-2 libc6 (>= 2.14) | libgcc1(>= 1:3.0) | libgpgmepp6 (>= 1.10.0) | libkf5akonadiagentbase5 (>= 15.07.90) | libkf5akonadicontact5 | libkf5akonadicore5 (>= 4:17.08.0) | libkf5akonadimime5| libkf5akonadisearchdebug5 | libkf5akonadisearchpim5 (>= 16.08.0) | libkf5akonadiwidgets5 (>= 4:17.08.0) | libkf5bookmarks5 (>= 4.96.0) | libkf5calendarcore5 (>= 15.07.90) | libkf5calendarutils5 | libkf5codecs5 (>= 5.4.0+git20141202.0008+15.04) | libkf5completion5 (>= 4.97.0) | libkf5configcore5 (>= 4.98.0) | libkf5configgui5 (>= 4.97.0) | libkf5configwidgets5 (>= 5.23.0) | libkf5contacts5 (>= 15.12.0) | libkf5coreaddons5 (>= 5.2.0) | libkf5crash5 (>= 5.15.0) | libkf5dbusaddons5 (>= 4.97.0) | libkf5followupreminder5(>= 4:16.04.0) | libkf5gravatar5 (>= 4:15.12) | libkf5guiaddons5 (>= 4.96.0) | libkf5i18n5 (>= 4.97.0) | libkf5iconthemes5 (>= 5.0.0) | libkf5identitymanagement5(>= 17.08.0) | libkf5itemmodels5 (>= 4.96.0) | libkf5itemviews5 (>= 4.96.0) | libkf5jobwidgets5 (>= 4.96.0) | libkf5kcmutils5(>= 5.2.0+git20141003) | libkf5kiocore5(>= 4.96.0) | libkf5kiofilewidgets5 (>= 4.96.0) | libkf5kiowidgets5 (>= 5.35.0) | libkf5kontactinterface5 | libkf5ksieveui5 | libkf5libkdepim-plugins | libkf5libkdepim5 (>= 16.04) | libkf5libkdepimakonadi5 | libkf5libkleo5 (>= 4:17.08.0) | libkf5mailcommon-plugins | libkf5mailcommon5 (>= 4:17.08.3) | libkf5mailtransport5 | libkf5mailtransportakonadi5 | libkf5messagecomposer5| libkf5messagecore5| libkf5messagelist5| libkf5messageviewer5 | libkf5mime5 (>= 15.12.0) | libkf5mimetreeparser5 | libkf5notifications5 (>= 4.96.0) |
Bug#885175: [kmail] Message Content Window Blacked Out
Package: kmail Version: 4:17.08.3-1 Severity: important --- Please enter the report below this line. --- Message content window (displayed below list) is blacked out. Seems not to display at all along side. Message content is intact. --- System information. --- Architecture: Kernel: Linux 4.14.0-1-amd64 Debian Release: buster/sid 500 yakkety ppa.launchpad.net 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com 500 lucid ppa.launchpad.net 100 jessie-backports ftp.us.debian.org 1 experimentalftp.us.debian.org --- Package information. --- Depends (Version) | Installed =-+- == akonadi-server (>= 4:17.08~) | 4:17.08.3-1 kdepim-runtime (>= 4:17.08~) | 4:17.08.3-1 libkf5akonadisearch-bin (>= 4:17.08~) | 4:17.08.3-1 libkf5akonadisearch-plugins (>= 4:17.08~) | 4:17.08.3-1 libkf5grantleetheme-plugins (>= 17.08~) | 17.08.3-1 kio | 5.37.0-2 libc6 (>= 2.14) | libgcc1(>= 1:3.0) | libgpgmepp6 (>= 1.10.0) | libkf5akonadiagentbase5 (>= 15.07.90) | libkf5akonadicontact5 | libkf5akonadicore5 (>= 4:17.08.0) | libkf5akonadimime5| libkf5akonadisearchdebug5 | libkf5akonadisearchpim5 (>= 16.08.0) | libkf5akonadiwidgets5 (>= 4:17.08.0) | libkf5bookmarks5 (>= 4.96.0) | libkf5calendarcore5 (>= 15.07.90) | libkf5calendarutils5 | libkf5codecs5 (>= 5.4.0+git20141202.0008+15.04) | libkf5completion5 (>= 4.97.0) | libkf5configcore5 (>= 4.98.0) | libkf5configgui5 (>= 4.97.0) | libkf5configwidgets5 (>= 5.23.0) | libkf5contacts5 (>= 15.12.0) | libkf5coreaddons5 (>= 5.2.0) | libkf5crash5 (>= 5.15.0) | libkf5dbusaddons5 (>= 4.97.0) | libkf5followupreminder5(>= 4:16.04.0) | libkf5gravatar5 (>= 4:15.12) | libkf5guiaddons5 (>= 4.96.0) | libkf5i18n5 (>= 4.97.0) | libkf5iconthemes5 (>= 5.0.0) | libkf5identitymanagement5(>= 17.08.0) | libkf5itemmodels5 (>= 4.96.0) | libkf5itemviews5 (>= 4.96.0) | libkf5jobwidgets5 (>= 4.96.0) | libkf5kcmutils5(>= 5.2.0+git20141003) | libkf5kiocore5(>= 4.96.0) | libkf5kiofilewidgets5 (>= 4.96.0) | libkf5kiowidgets5 (>= 5.35.0) | libkf5kontactinterface5 | libkf5ksieveui5 | libkf5libkdepim-plugins | libkf5libkdepim5 (>= 16.04) | libkf5libkdepimakonadi5 | libkf5libkleo5 (>= 4:17.08.0) | libkf5mailcommon-plugins | libkf5mailcommon5 (>= 4:17.08.3) | libkf5mailtransport5 | libkf5mailtransportakonadi5 | libkf5messagecomposer5| libkf5messagecore5| libkf5messagelist5| libkf5messageviewer5 | libkf5mime5 (>= 15.12.0) | libkf5mimetreeparser5 | libkf5notifications5 (>= 4.96.0) | libkf5notifyconfig5 (>= 4.96.0) | libkf5parts5
Re: Kmail often stuck at "Retrieving folder contents..."
On יום רביעי, 1 במרץ 2017 11:17:56 IST Martin Steigerwald wrote: > Hello Tim. > > Am Mittwoch, 1. März 2017, 10:56:45 CET schrieb Tim Ruehsen: > > Please wait... > > > > No matter how long I wait, KMail is stuck. > > I have to restart KMail. > > > > My impression: It happens regular when changing folders too fast. > > > > Of course I tried akonadictl (fsck + vacuum + restart) with no success. > > > > Any idea where to look at or what to do ? > > This topic has been discussed just recently on kdepim-users mailing list. It > appears to be a known issue. > > Please review > > "Retrieving Folders..." hang and a possible solution > > thread there. > > https://mail.kde.org/mailman/listinfo/kdepim-users > > Thanks, Select the option to download for off-line use. Once the stuff is there, problem will not recur. I was under the impression there were problems on GMail servers but apparently more widespread.
Re: linux-image-4.9.0-1-amd64 + nvidia-legacy-304xx-driver + xserver-xorg-video-nouveau
On יום שלישי, 24 בינואר 2017 14:35:18 IST Jimmy Johnson wrote: > On 01/23/2017 11:54 PM, David Baron wrote: > > On יום שני, 23 בינואר 2017 21:14:58 IST Jimmy Johnson wrote: > >> On 01/14/2017 02:26 PM, Jimmy Johnson wrote: > >> > >> I'm happy to report linux-image-4.9.0-1-amd64 + > >> nvidia-legacy-304xx-driver are currently working swell together. > > > > I just updated, rebooted. See no change. Window decorations still missing, > > both in openGL and Xrender. > > Yes, Plasma defaults to OpenGL 2.0 and it's not good that it's not > working, you have to use XRender, but compositing is working. Once you > switch to XRender you need to logout/login to see the change. I am on Xrender. I do not enable compositor on startup as I had hangups when doing that. I still see no change.
Re: linux-image-4.9.0-1-amd64 + nvidia-legacy-304xx-driver + xserver-xorg-video-nouveau
On יום שני, 23 בינואר 2017 21:14:58 IST Jimmy Johnson wrote: > On 01/14/2017 02:26 PM, Jimmy Johnson wrote: > > And it still works. > > I updated Sid/testing a couple days ago and retested current drivers, > > "nouveau" is working with sddm okay but froze with plasma(colorful > > lighting bolts). Current nvidia-legacy-304xx is working with XRender > > and compositing enabled and I'm good with that, tested on Stretch too, > > now I can do clean upgrades and I'm happy. Thank you Debian! > > > > linux-image-4.9.0-1-amd64 is behaving like image-4.8 used to behave > > nouveau froze with plasma(colorful lighting bolts). Debian's > > nvidia-legacy-304xx-driver is freezing with plasma start. > > > > On first boot plasma loaded the vga driver giving me the wrong screen > > size and did not load the installed nvidia driver at all. Booting > > linux-image-4.9.0-1-amd64 and reinstalling nvidia-legacy-304xx-driver > > crashed plasma and so did nouveau. I'm back to using > > nvidia-legacy-304xx-driver and linux-image-4.8.0-2-amd64 with XRender > > and compositing enabled. > > I'm happy to report linux-image-4.9.0-1-amd64 + > nvidia-legacy-304xx-driver are currently working swell together. > > Thank you Debian! I just updated, rebooted. See no change. Window decorations still missing, both in openGL and Xrender.
Re: linux-image-4.9.0-1-amd64 + nvidia-legacy-304xx-driver + xserver-xorg-video-nouveau
On יום שבת, 14 בינואר 2017 14:26:53 IST Jimmy Johnson wrote: > And it still works. > I updated Sid/testing a couple days ago and retested current drivers, > "nouveau" is working with sddm okay but froze with plasma(colorful > lighting bolts). Current nvidia-legacy-304xx is working with XRender > and compositing enabled and I'm good with that, tested on Stretch too, > now I can do clean upgrades and I'm happy. Thank you Debian! > > linux-image-4.9.0-1-amd64 is behaving like image-4.8 used to behave > nouveau froze with plasma(colorful lighting bolts). Debian's > nvidia-legacy-304xx-driver is freezing with plasma start. > > On first boot plasma loaded the vga driver giving me the wrong screen > size and did not load the installed nvidia driver at all. Booting > linux-image-4.9.0-1-amd64 and reinstalling nvidia-legacy-304xx-driver > crashed plasma and so did nouveau. I'm back to using > nvidia-legacy-304xx-driver and linux-image-4.8.0-2-amd64 with XRender > and compositing enabled. I just tried the 4.9.0-1-amd64. Worked for me the same as the 4.8. No better with XRender.
Re: Compositing Problem
On יום שבת, 7 בינואר 2017 4:36:59 IST Jimmy Johnson wrote: > On 10/19/2016 11:33 PM, Jimmy Johnson wrote: > > 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. > > I updated Sid/testing a couple days ago and retested current drivers, > "nouveau" is working with sddm okay but froze with plasma(colorful > lighting bolts). Current nvidia-legacy-304xx is working with XRender > and compositing enabled and I'm good with that, tested on Stretch too, > now I can do clean upgrades and I'm happy. Thank you Debian! Mine does NOT work with xrender
Re: KDE Frameworks 5.28.0
On יום ראשון, 20 בנובמבר 2016 9:30:10 IST Luc Castermans wrote: > Hi, > > 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!
Bug#841242: Latest Plasma/Kwin: NO window decorations.
Used to have them with KDE applications. Not now.
Re: Warning: Please delay dist-upgrade to Debian Sid (qtdeclarative, sddm, Plasma) (fix coming soon)
On יום שני, 7 בנובמבר 2016 10:33:37 IST MERLIN Philippe wrote: > Le lundi 7 novembre 2016, 08:02:47 CET Valerio Passini a écrit : > > On domenica 6 novembre 2016 19:23:22 CET Ferdinand Thommes wrote: > > > --- > > > Moin, > > > > > > > > > > > > > > > greetz > > > Ferdinand > > > > > > Am 06.11.2016 18:42 schrieb Martin Steigerwald: > > > > Am Sonntag, 6. November 2016, 17:43:58 CET schrieben Sie: > > > >> On יום ראשון, 6 בנובמבר 2016 15:56:20 IST Martin Steigerwald wrote: > > > >> > Am Sonntag, 6. November 2016, 11:14:04 CET schrieb Martin > > Steigerwald: > > > >> > > Am Sonntag, 6. November 2016, 00:59:07 CET schrieb Diederik de > > Haas: > > > >> > > > On zaterdag 5 november 2016 20:25:32 CET Andrey Rahmatullin > > wrote: > > > >> > > > > > If so, that is/was your problem and you'll likely have > > > >> > > > > > various > > > >> > > > > > qt5 > > > >> > > > > > package > > > >> > > > > > at version 5.7.1~20161021+dfsg-N. > > > >> > > > > > Downgrade those packages to their version in testing and > > > >> > > > > > there's a > > > >> > > > > > reasonable chance things start working again. See also > > > >> > > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843208#10 > > > >> > > > > > > >> > > > The current state is that it's highly likely that a bug in > > > >> > > > qtdeclarative- > > > >> > > > opensource-src (source package) version 5.7.1~20161021-4 is the > > > >> > > > cause > > > >> > > > for > > > >> > > > the issue various people are seeing. > > > >> > > > One of the Debian Qt maintainers filed the following bug for > > > >> > > > it: > > > >> > > > https://bugreports.qt.io/browse/QTBUG-56932 > > > >> > > > > > > >> > > > In Debian the following bugs have been reported which are > > > >> > > > likely > > > >> > > > all > > > >> > > > caused > > > >> > > > by this issue: > > > >> > > > https://bugs.debian.org/843250 > > > >> > > > https://bugs.debian.org/843332 > > > >> > > > > > > >> > > > and probably more will follow ... > > > >> > > > > > >> > > More indeed followed already, so: > > > >> > > > > > >> > > 1) Please delay updates to Debian Sid. > > > >> > > > > >> > Dmitry (aka Mitya57) gave us updated Qt Declarative packages for > > > >> > testing > > > >> > and they fix the issue. So a fix should be available soon. > > > >> > > > > >> > So I am on Qt 5.7.1 now without any instabilities. But > > > >> > > > > >> > quasselclient currently crashes, see: > > > >> > > > > >> > Bug#843416: libqt5widgets5: quasselclient segfaults with version > > > >> > 5.7.1~20161021+dfsg-5 of libqt5widgets5 > > > >> > > > > >> > binNMU to fix that is scheduled. > > > > > > > > […] > > > > > > > >> Good news! > > > >> Maybe let us know when to go ahead and upgrade. > > > >> Thanx. > > > > > > > > To have sddm and plasma session QML stuff work correctly: > > > > > > > > qtdeclarative-opensource-src 5.7.1~20161021-5 > > > > > > > > for the fix you need at least libqt5qml5 and libqt5quick5 > > > > 5.7.1~20161021-5. > > > > > > > > So wait till apt-cache policy shows the required versions for these > > > > *and* you > > > > can safely apt dist-upgrade without removing a ton of packages. > > > > > > > > > > > > To fix quassel: > > > > > > > > plasma-integration_5.8.2-1+b1_amd64 > > > > > > > > which Dmitry aka mitya57 also just uploaded. > > > > > > > > > > > > I´d say tomorrow, maybe even earlier, depending on buildd speeds. > > > > > > > > > > > > I suggest you monitor #debian-qt-kde IRC channel. Can have benefits as > > > > mitya > > > > provides links to packages he built there, so on my system Quassel > > > > client is > > > > also already fixed. > > > > > > > > Ciao, > > > > > > All neccessary packages are already in incoming. > > > So they will be in Sid with the next mirror sync in ~ 3.5 hours > > > > Hi, > > > > Today KDE is back again. Thanks for being so fast in fixing this bug > > > > Valerio > > +1 > Philippe Merlin Thanks for the warnings (saved a lot of heart-ache). Thanks for the fixes.
Re: Warning: Please delay dist-upgrade to Debian Sid (qtdeclarative, sddm, Plasma)
On יום ראשון, 6 בנובמבר 2016 15:56:20 IST Martin Steigerwald wrote: > Am Sonntag, 6. November 2016, 11:14:04 CET schrieb Martin Steigerwald: > > Am Sonntag, 6. November 2016, 00:59:07 CET schrieb Diederik de Haas: > > > On zaterdag 5 november 2016 20:25:32 CET Andrey Rahmatullin wrote: > > > > > If so, that is/was your problem and you'll likely have various qt5 > > > > > package > > > > > at version 5.7.1~20161021+dfsg-N. > > > > > Downgrade those packages to their version in testing and there's a > > > > > reasonable chance things start working again. See also > > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843208#10 > > > > > > The current state is that it's highly likely that a bug in > > > qtdeclarative- > > > opensource-src (source package) version 5.7.1~20161021-4 is the cause > > > for > > > the issue various people are seeing. > > > One of the Debian Qt maintainers filed the following bug for it: > > > https://bugreports.qt.io/browse/QTBUG-56932 > > > > > > In Debian the following bugs have been reported which are likely all > > > caused > > > by this issue: > > > https://bugs.debian.org/843250 > > > https://bugs.debian.org/843332 > > > > > > and probably more will follow ... > > > > More indeed followed already, so: > > > > 1) Please delay updates to Debian Sid. > > Dmitry (aka Mitya57) gave us updated Qt Declarative packages for testing and > they fix the issue. So a fix should be available soon. > > So I am on Qt 5.7.1 now without any instabilities. But > > quasselclient currently crashes, see: > > Bug#843416: libqt5widgets5: quasselclient segfaults with version > 5.7.1~20161021+dfsg-5 of libqt5widgets5 > > binNMU to fix that is scheduled. > > Ciao, Good news! Maybe let us know when to go ahead and upgrade. Thanx.
Re: Compositing Problem
On יום שבת, 22 באוקטובר 2016 21:54:34 IDT Brad Rogers wrote: > On Sat, 22 Oct 2016 22:22:22 +0300 > David Baron <dbaron...@gmail.com> wrote: > > Hello David, > > >Dkms will build it against my kernels. > > True, but that still doesn't restart X using the new drivers & modules. > Obviously. If I can downgrade, dkms will run. Then I reboot. > >As I said, maybe time to get plasma to play with Nouveau, get it out of > >Nvidia's hands. > > Maybe.
Re: Compositing Problem
Dkms will build it against my kernels. I have to get the needed packages first and this does not work. As I said, maybe time to get plasma to play with Nouveau, get it out of Nvidia's hands. > On Sat, 22 Oct 2016 21:16:42 +0300 > David Baron <dbaron...@gmail.com> wrote: > > Hello David, > > >Did not succede in downgrading (using synaptic, force version). > >Same problem as downgrading to testing. Broken packages. > > Just downgrading isn't enough. There's the whole "build against the > correct kernel" issue to consider, then you have to restart the X server.
Re: Compositing Problem
Did not succede in downgrading (using synaptic, force version). Same problem as downgrading to testing. Broken packages. > Control: tag -1 + help > > ¡Hola NVIDIA Maintainers! > > It seems that the new plasma version has some kind of incompatibility with > the nvidia-legacy-304xx packages in sid. The following mail reports that > using the nvidia packages from backports works as expected. > > In the kde team we are not using nvidia cards, so we can't reproduce/test > this. And frankly, this might be way out of our league. :( Thus the request > for help. > > Is this issue known to you? > Should this bug be reassigned to the nvidia packages? > Can you reproduce it? If so, can you point us to what the problem might be? > > Happy hacking, > > El 2016-10-19 a las 23:33 -0700, Jimmy Johnson escribió: > > 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.
Bug#841242: Compositing Problem
Just maybe it be time that plasma worked correctly with Nouveau. Nouveau is beautiful for everything else. At least, Debian folks are maintaining that, not dependent on Nvidia to maintain for legacy devices they would rather forget. > Control: tag -1 + help > > ¡Hola NVIDIA Maintainers! > > It seems that the new plasma version has some kind of incompatibility with > the nvidia-legacy-304xx packages in sid. The following mail reports that > using the nvidia packages from backports works as expected. > > In the kde team we are not using nvidia cards, so we can't reproduce/test > this. And frankly, this might be way out of our league. :( Thus the request > for help. > > Is this issue known to you? > Should this bug be reassigned to the nvidia packages? > Can you reproduce it? If so, can you point us to what the problem might be? > > Happy hacking, > > El 2016-10-19 a las 23:33 -0700, Jimmy Johnson escribió: > > 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.
Re: Compositing Problem
Just maybe it be time that plasma worked correctly with Nouveau. Nouveau is beautiful for everything else. At least, Debian folks are maintaining that, not dependent on Nvidia to maintain for legacy devices they would rather forget. > Control: tag -1 + help > > ¡Hola NVIDIA Maintainers! > > It seems that the new plasma version has some kind of incompatibility with > the nvidia-legacy-304xx packages in sid. The following mail reports that > using the nvidia packages from backports works as expected. > > In the kde team we are not using nvidia cards, so we can't reproduce/test > this. And frankly, this might be way out of our league. :( Thus the request > for help. > > Is this issue known to you? > Should this bug be reassigned to the nvidia packages? > Can you reproduce it? If so, can you point us to what the problem might be? > > Happy hacking, > > El 2016-10-19 a las 23:33 -0700, Jimmy Johnson escribió: > > 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.
Bug#841451: [ark] Ark Kicks at Android "apk" Files.
Maybe was a fluke. Worked fine today. Maybe close it. On יום שישי, 21 באוקטובר 2016 12:56:50 IDT Maximiliano Curia wrote: > Control: tag -1 + unreproducible > > ¡Hola David! > > El 2016-10-20 a las 22:37 +0300, David Baron escribió: > > Package: ark > > Version: 4:16.08.2-1 > > Severity: normal > > > > Says they are corrupt, offers to open read-only which works. > > > > Previous versions opened them just fine, without complaint. > > > > They seem to be straight-up zip. > > They might be corrupt, I could open the apk files I had around just fine. > > > Depends (Version) | Installed > > ===-+- > > == > > libarchive13 (>= 3.2.1) | 3.2.1-5 > > libc6 (>= 2.14) | > > libkf5archive5 (>= 4.96.0) | > > libkf5completion5 (>= 4.97.0) | > > libkf5configcore5 (>= 4.98.0) | > > libkf5configgui5(>= 4.97.0) | > > libkf5configwidgets5(>= 4.96.0) | > > libkf5coreaddons5 (>= 5.16.0) | > > libkf5crash5(>= 5.15.0) | > > libkf5dbusaddons5 (>= 4.97.0) | > > libkf5i18n5 (>= 4.97.0) | > > libkf5iconthemes5 (>= 4.96.0) | > > libkf5jobwidgets5 (>= 4.96.0) | > > libkf5kiocore5 (>= 4.96.0) | > > libkf5kiofilewidgets5 (>= 4.96.0) | > > libkf5kiowidgets5 (>= 5.5.0+git20150101.0309+15.04) | > > libkf5parts5(>= 4.96.0) | > > libkf5pty5 (>= 4.96.0) | > > libkf5service-bin | > > libkf5service5 (>= 4.99.0) | > > libkf5widgetsaddons5(>= 5.16.0) | > > libkf5xmlgui5 (>= 4.98.0) | > > libqt5core5a(>= 5.6.0~beta) | > > libqt5dbus5 (>= 5.4.0~) | > > libqt5gui5 (>= 5.4.0~) | > > libqt5widgets5 (>= 5.4.0~) | > > libstdc++6 (>= 4.1.1) | > > reportbug-ng reports are missing the package versions, which reduces the > value of this information considerably. > > > Recommends (Version) | Installed > > =-+-=== > > bzip2 | 1.0.6-8 > > p7zip-full| 16.02+dfsg-1 > > unar | > > unzip | 6.0-20 > > zip | 3.0-11 > > You might want to install unar to handle the rar files. > > Happy hacking,
Bug#841451: [ark] Ark Kicks at Android "apk" Files.
Package: ark Version: 4:16.08.2-1 Severity: normal --- Please enter the report below this line. --- Says they are corrupt, offers to open read-only which works. Previous versions opened them just fine, without complaint. They seem to be straight-up zip. --- System information. --- Architecture: amd64 Kernel: Linux 4.7.0-1-amd64 Debian Release: stretch/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com 500 lucid ppa.launchpad.net 100 jessie-backports ftp.us.debian.org 1 experimentalftp.us.debian.org --- Package information. --- Depends (Version) | Installed ===-+- == libarchive13 (>= 3.2.1) | 3.2.1-5 libc6 (>= 2.14) | libkf5archive5 (>= 4.96.0) | libkf5completion5 (>= 4.97.0) | libkf5configcore5 (>= 4.98.0) | libkf5configgui5(>= 4.97.0) | libkf5configwidgets5(>= 4.96.0) | libkf5coreaddons5 (>= 5.16.0) | libkf5crash5(>= 5.15.0) | libkf5dbusaddons5 (>= 4.97.0) | libkf5i18n5 (>= 4.97.0) | libkf5iconthemes5 (>= 4.96.0) | libkf5jobwidgets5 (>= 4.96.0) | libkf5kiocore5 (>= 4.96.0) | libkf5kiofilewidgets5 (>= 4.96.0) | libkf5kiowidgets5 (>= 5.5.0+git20150101.0309+15.04) | libkf5parts5(>= 4.96.0) | libkf5pty5 (>= 4.96.0) | libkf5service-bin | libkf5service5 (>= 4.99.0) | libkf5widgetsaddons5(>= 5.16.0) | libkf5xmlgui5 (>= 4.98.0) | libqt5core5a(>= 5.6.0~beta) | libqt5dbus5 (>= 5.4.0~) | libqt5gui5 (>= 5.4.0~) | libqt5widgets5 (>= 5.4.0~) | libstdc++6 (>= 4.1.1) | Recommends (Version) | Installed =-+-=== bzip2 | 1.0.6-8 p7zip-full| 16.02+dfsg-1 unar | unzip | 6.0-20 zip | 3.0-11 Package's Suggests field is empty.
Bug#841242: Compositing Problem
On יום חמישי, 20 באוקטובר 2016 9:22:29 IDT Maximiliano Curia wrote: > Control: tag -1 + help > > ¡Hola NVIDIA Maintainers! > > It seems that the new plasma version has some kind of incompatibility with > the nvidia-legacy-304xx packages in sid. The following mail reports that > using the nvidia packages from backports works as expected. > > In the kde team we are not using nvidia cards, so we can't reproduce/test > this. And frankly, this might be way out of our league. :( Thus the request > for help. > > Is this issue known to you? > Should this bug be reassigned to the nvidia packages? > Can you reproduce it? If so, can you point us to what the problem might be? > > Happy hacking, > > El 2016-10-19 a las 23:33 -0700, Jimmy Johnson escribió: > > 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. 1. Previous bug reassigned to 304xx of AceofPeguins Freecell game failing to start apparently healed itself, no new 304xx so maybe something else! 2. For 841242 (I filed this one as well as starting this thread beforehand), Plasma does start. What will not work is starting compositing on start, had to hand edit that out of the rc file. 3. Toggling compisitor choices will restore the title bar decorations for the current session. This might seem to contra-indicate 304xx being the source of the problem. If this assessment is not correct, maybe do reassign. 4. If downgrading 304xx be the only way now, please give me step by step how to do this since testing packages are broken. Using dkms.
Re: Compositing Problem
On יום חמישי, 20 באוקטובר 2016 9:22:29 IDT Maximiliano Curia wrote: > Control: tag -1 + help > > ¡Hola NVIDIA Maintainers! > > It seems that the new plasma version has some kind of incompatibility with > the nvidia-legacy-304xx packages in sid. The following mail reports that > using the nvidia packages from backports works as expected. > > In the kde team we are not using nvidia cards, so we can't reproduce/test > this. And frankly, this might be way out of our league. :( Thus the request > for help. > > Is this issue known to you? > Should this bug be reassigned to the nvidia packages? > Can you reproduce it? If so, can you point us to what the problem might be? > > Happy hacking, > > El 2016-10-19 a las 23:33 -0700, Jimmy Johnson escribió: > > 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. 1. Previous bug reassigned to 304xx of AceofPeguins Freecell game failing to start apparently healed itself, no new 304xx so maybe something else! 2. For 841242 (I filed this one as well as starting this thread beforehand), Plasma does start. What will not work is starting compositing on start, had to hand edit that out of the rc file. 3. Toggling compisitor choices will restore the title bar decorations for the current session. This might seem to contra-indicate 304xx being the source of the problem. If this assessment is not correct, maybe do reassign. 4. If downgrading 304xx be the only way now, please give me step by step how to do this since testing packages are broken. Using dkms.
Bug#841242: [kwin-x11] Non-KDE Windows Titlebar Not Visible but Operational
On יום רביעי, 19 באוקטובר 2016 10:26:29 IDT Maximiliano Curia wrote: > Control: tag -1 + unreproducible > > ¡Hola David! > > El 2016-10-19 a las 00:05 +0300, David Baron escribió: > > Package: kwin-x11 > > Version: 4:5.8.1-1 > > Severity: normal > > > > Non-KDE Windows, such as Firefox, Ace-Penguin games, etc., come up > > without > > their title bar. The title bar's functionality is active, clicking at the > > appropriate place works. Dragging the window this area may drag background > > that would be behind the title bar. > > I'm not being able to reproduce this issue, this might be an specific > problem/configuration of the window decorations you are using. > > > This occurs on all compositor alternatives. Changing the compositor will > > restore the title bars but they are delayed. Next KDE session will have > > them not visible again. > > Which compositor alternatives are you refering to? OpenGL3,3,Xrender. > > > KDE windows work fine. > > > > (This might not be the correct package for this bug?) > > What decoration are you using? > Could you check which versions of: > libkdecorations2-5v5 > kwin-style-breeze > kwin-decoration-oxygen > you are have currently installed? 4.5.8.1-1 Current Sid. > > Also, could you try switching to the breeze window decorations? (you might > need to restart your plasma session afterwards) Had Breeze. > > > --- System information. --- > > Architecture: amd64 > > Kernel: Linux 4.7.0-1-amd64 > > > > Debian Release: stretch/sid > > > > 500 unstableftp.us.debian.org > > 500 testing ftp.us.debian.org > > 500 sid linux.dropbox.com > > > > 500 lucid ppa.launchpad.net > > > >1 experimentalftp.us.debian.org > > > > --- Package information. --- > > Depends (Version) | Installed > > ==-+- > > == > > kwin-common (= 4:5.8.1-1) | 4:5.8.1-1 > > libc6(>= 2.14) | > > libepoxy0 (>= 1.0) | > > libgcc1 (>= 1:3.4) | > > libkf5configcore5 (>= 4.97.0) | > > libkf5coreaddons5 (>= 5.11.0) | > > libkf5crash5 (>= 4.96.0) | > > libkf5i18n5(>= 4.97.0) | > > libkf5windowsystem5(>= 4.96.0) | > > libkwinglutils9 (>= 4:5.1.95+git20150122) | > > libkwinxrenderutils9 (>= 4:5.1.95+git20150122) | > > libqt5core5a (>= 5.6.0~beta) | > > libqt5gui5 (>= 5.5.0~) | > > libqt5widgets5 (>= 5.5.0~) | > > libqt5x11extras5(>= 5.6.0) | > > libstdc++6 (>= 4.4.0) | > > libx11-6 | > > libxcb-cursor0 (>= 0.0.99) | > > libxcb-randr0 (>= 1.3) | > > libxcb-xfixes0 | > > libxcb1 (>= 1.6) | > > libxi6 (>= 2:1.2.99.4) | > > This list is missing the installed versions of the kwin-x11 dependencies. I > think this is a reportbug-ng issue, could you try sending this information > with: reportbug -N 841242 > > Happy hacking,
Bug#841242: [kwin-x11] Non-KDE Windows Titlebar Not Visible but Operational
Package: kwin-x11 Version: 4:5.8.1-1 Severity: normal --- Please enter the report below this line. --- Non-KDE Windows, such as Firefox, Ace-Penguin games, etc., come up without their title bar. The title bar's functionality is active, clicking at the appropriate place works. Dragging the window this area may drag background that would be behind the title bar. This occurs on all compositor alternatives. Changing the compositor will restore the title bars but they are delayed. Next KDE session will have them not visible again. KDE windows work fine. (This might not be the correct package for this bug?) --- System information. --- Architecture: amd64 Kernel: Linux 4.7.0-1-amd64 Debian Release: stretch/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com 500 lucid ppa.launchpad.net 1 experimentalftp.us.debian.org --- Package information. --- Depends (Version) | Installed ==-+- == kwin-common (= 4:5.8.1-1) | 4:5.8.1-1 libc6(>= 2.14) | libepoxy0 (>= 1.0) | libgcc1 (>= 1:3.4) | libkf5configcore5 (>= 4.97.0) | libkf5coreaddons5 (>= 5.11.0) | libkf5crash5 (>= 4.96.0) | libkf5i18n5(>= 4.97.0) | libkf5windowsystem5(>= 4.96.0) | libkwinglutils9 (>= 4:5.1.95+git20150122) | libkwinxrenderutils9 (>= 4:5.1.95+git20150122) | libqt5core5a (>= 5.6.0~beta) | libqt5gui5 (>= 5.5.0~) | libqt5widgets5 (>= 5.5.0~) | libqt5x11extras5(>= 5.6.0) | libstdc++6 (>= 4.4.0) | libx11-6 | libxcb-cursor0 (>= 0.0.99) | libxcb-randr0 (>= 1.3) | libxcb-xfixes0 | libxcb1 (>= 1.6) | libxi6 (>= 2:1.2.99.4) | Package's Recommends field is empty. Package's Suggests field is empty.
Compositing Problem
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?
Plasma 5.8 Woes
Came about with the demise of legacy nvidia drivers, testing versions gone forever it seems. Unstable version are really that. Back to Nouveau. Now I like Nouveau, but newer Plasma does not. So now the thing crashes every few minutes, restarts fine. Nothing lost since whatever window I have opened stays there through the mess. But still ... Up-to-date Sid. What to do about this?
Bug#839990: [akonadi-server] Latest Upgrade Unstable
On יום שישי, 7 באוקטובר 2016 10:46:56 IDT Maximiliano Curia wrote: > On October 7, 2016 9:24:08 AM GMT+02:00, David Baron <dbaron...@gmail.com> wrote: > >Package: akonadi-server > >Version: 4:16.04.3-2 > >Severity: normal > > > >--- Please enter the report below this line. --- > >When exercising emails in KMail2, the server will crash out. > > What do you mean by exercising? Are you able to reproduce the crash with a > particular (small of possible) set of emails that you can share? > >Brings up box to "start" it. > >Restarts by itself, box disappears > > That's the expected way to handle a crash. > > >Note: Can duplicate this by stopping server via akonadiconsole. > > By this last part it seems to me that you are more concerned about the > crashing message than of the crash itself. > > I might be wrong, of course, but from this report I don't see anything wrong > in the crash message when the server stops unexpectedly (either by a crash > or because of a forced stop). Does not matter. Scrolling, moving, deleting, sometimes just reading. Writing this answer.
Bug#839990: [akonadi-server] Latest Upgrade Unstable
Package: akonadi-server Version: 4:16.04.3-2 Severity: normal --- Please enter the report below this line. --- When exercising emails in KMail2, the server will crash out. Brings up box to "start" it. Restarts by itself, box disappears Note: Can duplicate this by stopping server via akonadiconsole. --- System information. --- Architecture: amd64 Kernel: Linux 4.7.0-1-amd64 Debian Release: stretch/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com 500 lucid ppa.launchpad.net 1 experimentalftp.us.debian.org --- Package information. --- Depends (Version) | Installed ===-+-= akonadi-backend-mysql (= 4:16.04.3-2) | 4:16.04.3-2 OR akonadi-backend-sqlite (= 4:16.04.3-2) | 4:16.04.3-2 OR akonadi-backend-postgresql (= 4:16.04.3-2) | 4:16.04.3-2 libc6 (>= 2.14) | libgcc1 (>= 1:3.0) | libkf5akonadiprivate5 (= 4:16.04.3-2) | libkf5configcore5 (>= 4.97.0) | libqt5core5a(>= 5.6.0~beta) | libqt5dbus5 (>= 5.4.0~) | libqt5gui5(>= 5.6.0~rc) | libqt5network5 (>= 5.4.0~) | libqt5sql5 (>= 5.4.0~) | libqt5widgets5 (>= 5.4.0~) | libqt5xml5 (>= 5.4.0~) | libstdc++6 (>= 5.2) | Package's Recommends field is empty. Suggests (Version) | Installed ==-+- akonadi-backend-mysql (= 4:16.04.3-2) | 4:16.04.3-2 akonadi-backend-postgresql (= 4:16.04.3-2) | 4:16.04.3-2 akonadi-backend-sqlite (= 4:16.04.3-2) | 4:16.04.3-2
Re: Latest and Greatest: Dropbox Disappears
On יום שבת, 27 באוגוסט 2016 21:45:26 IDT Alex DEKKER wrote: > On 27/08/16 21:14, David Baron wrote: > > Running up-to-date Sid. > > > > Plasma desktop come up, the Dropbox icon (actually NOT, but a folder icon) > > appears on the system bar. After a while, it is gone. > > > > The daemon is still running. > > Does it reappear if you run xembedsniproxy? > > alexd That was previous kde/plasma, now deprecated I believe. Correct icon showed up this morning. See if it lasts.
Latest and Greatest: Dropbox Disappears
Running up-to-date Sid. Plasma desktop come up, the Dropbox icon (actually NOT, but a folder icon) appears on the system bar. After a while, it is gone. The daemon is still running.
Re: Need help regarding experimental KDEPIM/Kmail
With today's Sid upgrades. 1. Akonadi worked. 2. KMail repeatedly timed out looking for a lock, BUT ... Individual account setups remained and enabled configuration to proceed. 3. After logout, login to KDE, FINALLY can use KMail once again.
Re: plasma-systray-legacy replacement?
On Thursday 09 June 2016 08:32:51 Thomas Fjellstrom wrote: > Hi, > > I've been monitoring the "big upgrade" thats been rolling out, and the only > thing that seems to be blocking it on my desktop is a missing > plasma-systray- legacy package. Is that going to make it to the new kde > packages? or is it being discontinued? > > I find it very useful as there are still plenty of irreplaceable apps that > still use the old systray interface. > > thanks! Likely, no longer needed. The icons for which I installed it show just fine now without it.
Upgrade with new kactivity module
Works quite well. Please fix dependencies in plasma-desktop so that this one gets pulled in as well rather than having to do this manually. Legacy panel is no longer needed, it seems. Plasma-containments-addons is listed as no longer needed, in autoremove list. Old 4.14 stuff.
Re: Kmail / Akonadi hanging
On Wednesday 13 April 2016 15:13:24 Tim Ruehsen wrote: > Since a while (few months) akonadi 'hangs' from time to time. > This happens when reading or removing emails from my folders. > When it happens, Kmail shows me a nice gfx saying "Retrieving Folder > Contents" and "Please wait ..." > > No matter how long I wait... Kmail does not recover. > Then, I open a console and do 'akonadictl restart', sometimes 'akonadictl > fsck'. Kmail starts working again for a while... > BTW, restarting Kmail does not help at all. >. Sometimes, killing it and restarting will get it back on track. Logging out and re-logging in most reliable.
Re: Plasmashell is eating too much CPU sometimes
On Thursday 03 March 2016 11:32:56 C. Mourad Jaber wrote: > Hi, > > I'm currently experimenting an issue with plasmashell > (plasma-framework:5.16.0-1). > > For an unknown reason plasmashell process start to eat 1 CPU at 100% and it > stay stuck to consume all that power... > > It seem to be linked to suspend-resume cycle. > > Is there any possibility to have some logs or to analyse that issue ? > > As workaround, when it happen, I kill and restart plasmashell : > $ killall plasmashell ; kstart plasmashell > > And Cpu consumption goes down normally... > > Regards > > Mourad I had previously posted: When I start a new session (old session still running), the older session's plasmashell CPU is way up, sometimes bogging the system! If I unlock the old session's desktop, that problem subsides, though its plasmashell can still sometimes eat a lot of CPU, but not crippling. What is the difference between "kstart plasmashell" and (simply) "plasmashell" to restart it?
Bug#801702: [plasma-desktop] Recent Sid Upgrades Including Numerous KF5... Break Plasma-desktop
Package: plasma-desktop
Version: 4:5.4.2-1
Severity: grave
--- Please enter the report below this line. ---
Recent upgrade from Sid breaks plasma-desktop. All apps can be run from a
command line (i.e
Yakuake starts and works!) but there is no desktop.
Plasmashell is running using few resources. If I kill it and restart it (what I
too often must do to
get the desktop!), then is loops with:
* * *
Reusing existing ksycoca
Recreating ksycoca file
("/home/david/.cache/ksycoca5_en_3F1fXXDsrvdw3By1XvCKEDww3hA=", version 303)
Still in the time dict (i.e. deleted files) ("apps")
Saving
Reusing existing ksycoca
Recreating ksycoca file
("/home/david/.cache/ksycoca5_en_3F1fXXDsrvdw3By1XvCKEDww3hA=", version 303)
Still in the time dict (i.e. deleted files) ("apps")
Saving
Reusing existing ksycoca ...
Reboots, trying new .kde, nothing helps.
--- System information. ---
Architecture: amd64
Kernel: Linux 4.0.0-1-amd64
Debian Release: Kali Linux 2.0
500 unstableftp.us.debian.org
500 testing ftp.us.debian.org
500 kali-currentsecurity.kali.org
500 kali-currenthttp.kali.org
500 jessie linux.dropbox.com
1 experimentalftp.us.debian.org
--- Package information. ---
Depends (Version) | Installed
===-+-===
kde-wallpapers-default | 4:15.04.2-1
plasma-widgets-workspace(= 4:4.11.11-1) | 4:4.11.22-2
kde-runtime (>> 4:4.10) | 4:15.08.1-1
libc6 (>= 2.14) |
libkactivities6 (>= 4:4.11) |
libkcmutils4(>= 4:4.11) |
libkdecore5 (>= 4:4.11) |
libkdeui5 (>= 4:4.11) |
libkephal4abi1 (= 4:4.11.11-1) |
libkfile4 (>= 4:4.11) |
libkidletime4 (>= 4:4.11) |
libkio5 (>= 4:4.11) |
libknewstuff3-4 (>= 4:4.11) |
libktexteditor4 (>= 4:4.11) |
libkworkspace4abi2 (= 4:4.11.11-1) |
libplasma3 (>= 4:4.11) |
libplasmagenericshell4 (= 4:4.11.11-1) |
libqt4-dbus(>= 4:4.6.1) |
libqt4-declarative (>= 4:4.7.0~rc1) |
libqt4-xml (>= 4:4.5.3) |
libqtcore4 (>= 4:4.7.0~beta1) |
libqtgui4 (>= 4:4.8.0) |
libsolid4 (>= 4:4.11) |
libstdc++6 (>= 4.1.1) |
libtaskmanager4abi4 (= 4:4.11.11-1) |
libx11-6|
libxext6|
Recommends (Version) | Installed
-+-===
kde-workspace|
Package's Suggests field is empty.
Re: Plasma past G++ transition
On Tuesday 08 September 2015 14:17:54 Martin Steigerwald wrote: > On Monday, 7 September 2015 09:17:54 CEST Marc Haber wrote: > > On Wed, Sep 02, 2015 at 10:26:29AM +0200, Martin Steigerwald wrote: > > > I am now past G++ transition on my system (full dist-upgrade) as I > > > wrote. > > > And tomorrow I was able to install kdepim again, in a newer upstream > > > version to 4.4.10. It works nicely so far. > > > > in testing or unstable? > > unstable. > > For testing I suggest to wait another week or so, maybe longer. > > Thanks, Working now, more or less the same as before.
Plasmashell Balky -- Workaround
More than occasionally, plasmashell fails to paint the screen. Remains black with a cursor. Various functions and notifications do occur. Formerly had to restart kdm (and have it still do this) or reboot ... Workaround: Have Yakuake part of active session startup. This will still operate. Hit F12 Kill errant Plasmashell, i.e killall or kill -9 pid of this plasmashell. Now re-run Plasmashell Home screen will now come up.
Re: SDDM lost display monitor
On Sunday 19 July 2015 21:08:31 Jimmy Johnson wrote: I use the Nvidia driver and I moved from KDM to SDDM and lost the display monitor after login, I got a bright colored out of focus desktop and then the display signal was gone. I installed KDE LightDM and all is well. Any idea what could have happened to cause the display to be lost? Can't answer this but I tried ssdm. Did work but a major difference from kdm is that I can control kdm fully from a command line. If something is awry, I can stop and restart kdm and usually be OK. Ssdm did not stop, so the only out was a reboot. For now, I would not recommend ssdm. BTW, these can coexist. Do a reconfigure to set to different display manager. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1615563.j69htuOsSt@dovidhalevi
Re: So I have a Plasma 5 desktop!
I have been running (mostly just fine) with kdm. What is different about sddm? This only installs with a couple of breeze themes so will not interfere with anything else. Kdm is not removed. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1931404.I09QnvjnD2@dovidhalevi
Re: So I have a Plasma 5 desktop!
Sometimes, the desktop does not come up. I have yakuake active so can get that. Top reveals no (or dormant) plasmashell. Happens more often as second session. Usually requires a reboot to get up again. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/3086801.ByTahDqadE@dovidhalevi
Re: Where to set KDEDIRS or alternative?
On Tuesday 14 July 2015 19:28:47 Martin Steigerwald wrote: Am Montag, 13. Juli 2015, 14:10:15 schrieb Kevin Krammer: On Sunday, 2015-07-12, 19:53:38, Sune Vuorela wrote: On 2015-07-12, Brad Rogers b...@fineby.me.uk wrote: Oh, but /usr/local/kde4/bin *is* in the PATH on my system. And with=20 KDEDIRS set appropriately, KDE did find them there, too. I'm unclear on that; Was /usr/local/kde4/bin(1) included in the PATH setting and KDEDIRS _also_ referred to it, or did only KDEDIRS reference that specific directory? Not that it matter much; If the directory is in the PATH, IDK why things aren't being found there. KDEDIRS is needed to have sycoca4 pick up things like plugins and stuff. And very many apps is mostly built out of plugins. For example KDevelop, Kontact and Konqueror. My guess would be that there is a QT_PLUGIN_PATH variable or similar being used now. For me: martin@merkaba:~ cat .kde/env/kdedirs.sh #!/bin/bash if [ -z $KDEDIRS ]; then export KDEDIRS=/usr/local/ else export KDEDIRS=/usr/local/:$KDEDIRS fi if [ -z $QT_PLUGIN_PATH ]; then export QT_PLUGIN_PATH=/usr/local/lib/kde4 else export QT_PLUGIN_PATH=/usr/local/lib/kde4:$QT_PLUGIN_PATH fi only appears to work partly anymore with self compiled KDEPIM and Akonadi. KMail still says 4.14.10 version instead of the latest 4:4.14.5-1 packaged in experimental, but ps aux shows /usr/bin instead of /usr/local/bin as path. And akonadi also is loaded from /usr/bin. I didn´t even notice it. Ciao, This is OK for KDE4. No longer appropriate for plasma5. Stuff in the kde4 folders is not accepted. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/12718275.UCI08cBvjE@dovidhalevi
Re: So I have a Plasma 5 desktop!
I had placed a script in .kde/env to get locally compiled plasmoids on board in QT_PLUGIN_PATH. Plasma-5 is not exercising this. My env is: QT_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins:/lib/kde5/plugins/ So ... Locally compiled plasmoids are in kde4 folders. Currently missing more more functional versions of installed plasmoids are in kde4 folders. Only the few newly installed ones, many very limited, are in kde5 folders! Safe to make a .kde/Autostart of get the .kde/env script to run and append such these folders to QT_PLUGIN_PATH env? -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1653290.tG3yubJGpx@dovidhalevi
Re: So I have a Plasma 5 desktop!
Installing the kwin stuff stopped the immediate crashes. Could not see any text except some highlighted stuff and pieces of menus. Go to system settings, somehow, and set the compositor to xrender. This got everything painted again. Now of course, had to start over. Some pieces, widgets, are missing, even thought they were explicitly installed. Icon themes have missing pieces, and size-related flaws. But ... Plasma 5 is up and running and (mostly) quite nicely! -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2005777.5c0yEHm2FE@dovidhalevi
Re: So I have a Plasma 5 desktop!
I am not on the inside so cannot tell anything. I did NOT use anything from experimental. It is a bit slow (debug versions?), less than 100% stable, had some hangups. Growing pains. Any word on when the rest of it will land in Sid? I have been holding off packaging work because I didn't really want to use experimental. I hope it is soon, I wont have time for Debian stuff once school restarts. On Thursday, July 09, 2015 16:50:51 David Baron wrote: Installing the kwin stuff stopped the immediate crashes. Could not see any text except some highlighted stuff and pieces of menus. Go to system settings, somehow, and set the compositor to xrender. This got everything painted again. Now of course, had to start over. Some pieces, widgets, are missing, even thought they were explicitly installed. Icon themes have missing pieces, and size-related flaws. But ... Plasma 5 is up and running and (mostly) quite nicely! -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/4004552.GrbuRJr06z@dovidhalevi
Re: Getting Locally Compiled Plasmoids to Show Up
On Sunday 12 April 2015 22:16:54 Martin Steigerwald wrote: Am Dienstag, 7. April 2015, 10:51:03 schrieb David Baron: On Tuesday 07 April 2015 00:10:21 Lisandro Damián Nicanor Pérez Meyer wrote: On Monday 06 April 2015 18:06:51 David Baron wrote: Running 64-bit Sid. My plasmoids (and runners) compile fine, but do not show up. Cannot figure out why. Worked before. There is a QT_PLUGIN_PATH env which does not include /usr/local/lib/kde4 to which these install. Could not find where this gets set. Any ideas or is this the problem at all? QT_PLUGIN_PATH is indeed used by Qt, but setted by KDE somehow. It might not be a bad idea to also add usr/local to it, but I'm pretty sure this should be discussed upstream. With the /usr/local, they still do not show up. However, the /usr/local is shown in a terminal window, might not be active when plasma-desktop starts. Does this work? martin@merkaba:~ cat .kde/env/kdedirs.sh #!/bin/bash if [ -z $KDEDIRS ]; then export KDEDIRS=/usr/local/ else export KDEDIRS=/usr/local/:$KDEDIRS fi if [ -z $QT_PLUGIN_PATH ]; then export QT_PLUGIN_PATH=/usr/local/lib/kde4 else export QT_PLUGIN_PATH=/usr/local/lib/kde4:$QT_PLUGIN_PATH fi Ciao, Like a charm! Much thanks. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/3977198.2gtMBc2Zk0@dovidhalevi
Re: Getting Locally Compiled Plasmoids to Show Up
On Tuesday 07 April 2015 00:10:21 Lisandro Damián Nicanor Pérez Meyer wrote: On Monday 06 April 2015 18:06:51 David Baron wrote: Running 64-bit Sid. My plasmoids (and runners) compile fine, but do not show up. Cannot figure out why. Worked before. There is a QT_PLUGIN_PATH env which does not include /usr/local/lib/kde4 to which these install. Could not find where this gets set. Any ideas or is this the problem at all? QT_PLUGIN_PATH is indeed used by Qt, but setted by KDE somehow. It might not be a bad idea to also add usr/local to it, but I'm pretty sure this should be discussed upstream. With the /usr/local, they still do not show up. However, the /usr/local is shown in a terminal window, might not be active when plasma-desktop starts. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/8667079.QTqY4dPrae@dovidhalevi
Re: Getting Locally Compiled Plasmoids to Show Up
On Tuesday 07 April 2015 00:10:21 Lisandro Damián Nicanor Pérez Meyer wrote: On Monday 06 April 2015 18:06:51 David Baron wrote: Running 64-bit Sid. My plasmoids (and runners) compile fine, but do not show up. Cannot figure out why. Worked before. There is a QT_PLUGIN_PATH env which does not include /usr/local/lib/kde4 to which these install. Could not find where this gets set. Any ideas or is this the problem at all? QT_PLUGIN_PATH is indeed used by Qt, but setted by KDE somehow. It might not be a bad idea to also add usr/local to it, but I'm pretty sure this should be discussed upstream. With the /usr/local, they still do not show up. However, the /usr/local is shown in a terminal window, might not be active when plasma-desktop starts. MORE: I set a startup script to append the path before kde startup. It actually prepended it with a leading ':'--in other words, before kde startup, there was no such env item, so appended to blank and then the usual env item was appended to this. Incorrect. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/3635516.pxdSIrIrAm@dovidhalevi
Re: Getting Locally Compiled Plasmoids to Show Up
On Tuesday 07 April 2015 00:10:21 Lisandro Damián Nicanor Pérez Meyer wrote: On Monday 06 April 2015 18:06:51 David Baron wrote: Running 64-bit Sid. My plasmoids (and runners) compile fine, but do not show up. Cannot figure out why. Worked before. There is a QT_PLUGIN_PATH env which does not include /usr/local/lib/kde4 to which these install. Could not find where this gets set. Any ideas or is this the problem at all? QT_PLUGIN_PATH is indeed used by Qt, but setted by KDE somehow. It might not be a bad idea to also add usr/local to it, but I'm pretty sure this should be discussed upstream. With the /usr/local, they still do not show up. However, the /usr/local is shown in a terminal window, might not be active when plasma-desktop starts. MORE: I set a startup script to append the path before kde startup. It actually prepended it with a leading ':'--in other words, before kde startup, there was no such env item, so appended to blank and then the usual env item was appended to this. Incorrect. SO: Found it in /usr/bin/startkde and appended there. Did so correctly, but they still do not show up so this is not a (complete) solution. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1605159.zsUi9h1bfW@dovidhalevi
Getting Locally Compiled Plasmoids to Show Up
Running 64-bit Sid. My plasmoids (and runners) compile fine, but do not show up. Cannot figure out why. Worked before. There is a QT_PLUGIN_PATH env which does not include /usr/local/lib/kde4 to which these install. Could not find where this gets set. Any ideas or is this the problem at all? -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1634717.xIGVvesgoK@dovidhalevi
Bug#781516: [qtchooser] Qtchooser will always find qt5
On Wednesday 01 April 2015 11:46:38 Dmitry Shachnev wrote: Control: tags -1 moreinfo Hi David, On Mon, 30 Mar 2015 13:51:51 +0300, David Baron wrote: Attempts to use qmake-qtchooser always yields qt5 libraries. Cannot make anything in qt4 unless manually running qmake-qt4 and ./configure may not set up completely correct Makefile. [snip] Suggests (Version) | Installed ==-+-=== qt4-default| qt5-default| 5.3.2+dfsg-4+b1 You have qt5-default installed, which means that *default* Qt will be 5.x for you. If you want to use e.g. qmake from Qt 4, you need to either call it as ‘qmake -qt4’, or export QT_SELECT=4. This is how qtchooser works. If any of these methods does not work, then it is a bug. But I don’t see a mention of that in your bug report. -- Dmitry Shachnev OK. I did not know such a package was around. Since I assume many of us will be compiling for either or both, this solution (mutually exclusive packages) is not, in my mind, the best. I have requested from one dev so far that the QT_SELECT by done by his configure script. Another alternative could be a /etc/default/qtchooser. This could specify even more default properties, if desirable. Comment out the build alternative not desired #QT_SELECT=4 QT_SELECT=5 I guess a situation of name-your-poison. Can rephrase bug as wishlist. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1519345.YNnxSNPEWI@dovidhalevi
Bug#781516: [qtchooser] Qtchooser will always find qt5
On Wednesday 01 April 2015 14:03:47 Dmitry Shachnev wrote: Control: severity -1 wishlist On Wed, 01 Apr 2015 12:21:57 +0300, David Baron wrote: Another alternative could be a /etc/default/qtchooser. This could specify even more default properties, if desirable. Comment out the build alternative not desired #QT_SELECT=4 QT_SELECT=5 You have a $(qmake -query QT_INSTALL_LIBS)/qtchooser/default.conf file, which you can make a symlink to qt4 or qt5 configuration file (this is exactly what qt4-default and qt5-default packages do), or fill it yourself with the paths you want qtchooser to use. Why do we need one more way to specify the default Qt? -- Dmitry Shachnev (More-or-less) standard manner to which folks are accustomed. But this is OK as well, if not adequately documented. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2672469.Nu54X4hBu5@dovidhalevi
Bug#781516: [qtchooser] Qtchooser will always find qt5
Package: qtchooser Version: 47-gd2b7997-2 Severity: grave --- Please enter the report below this line. --- Might be corollary to #781226 Attempts to use qmake-qtchooser always yields qt5 libraries. Cannot make anything in qt4 unless manually running qmake-qt4 and ./configure may not set up completely correct Makefile. --- System information. --- Architecture: amd64 Kernel: Linux 3.16.0-4-amd64 Debian Release: 8.0 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 jessie linux.dropbox.com --- Package information. --- Depends (Version) | Installed ===-+-= libc6 (= 2.4) | libgcc1(= 1:4.1.1) | libstdc++6 (= 4.1.1) | Package's Recommends field is empty. Suggests (Version) | Installed ==-+-=== qt4-default| qt5-default| 5.3.2+dfsg-4+b1 -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20117107.Q4nQ517dbz@dovidhalevi
Bug#470654: Another round - newer version available
On Wednesday 21 January 2015 23:24:34 Sandro Knauß wrote: tag 470654 +moreinfo thanks Another round of: there are newer versions of kmail are available in the Debian repos. Could you please check that this bug still applies? Regads, sandro Judging from the number, this is extremely old, 2008! So best to simply close this. If such an bug is noticed in newest version, can resubmit. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1812491.PhNJZKplg5@dovidhalevi
Re: Little problem with Kde
I believe the problem is memory. Sign out, it releases a whole bunch of memory (KDE is not exactly economical). Get this behavior going from account to account if I have two sessions going and log out from one. Once the log out is done, the poweroff is very quick (systemd). Hi, Not the same behaviour here : computer and akonadi close fast. However I remember some closing problems in akonadi in the past. What kde version are you running ? Which startup system (sysvinit, upstart, systemd) ? How it works if you try to stop your computer from a fresh test account ? Hello, First on my computer it's an Debian Sid up to date and kde 4.14.2. First of all I would want to congratulate the Kde team on its really fantastic work. However I collide with Kde with a problem which bores me a lot. When I click to Switch off the computer in Kde, the current duration of this phase is nearby of 2 minutes and the computer does not go out electrically what is very boring. By comparison if I stop Kontact then the server Akonadi by means of one akonadictl stop and I launch a halt p in Konsole the stop total is lower than 40 seconds. My question is the following one why Kde puts so much time to make an extinction of the computer without arriving there completely, for the complete extinction I think of having the solution instead of making a halt it is necessary to launch a halt - p. For excessive duration I do not know. Other small problem in the starting up, would be you it possible to launch the akonadi server very quickly, because often during the opening of the window Kontact I have the message akonadi server not yet completely launched. Philippe Merlin -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2081016.0Cpv5BsFj4@dovidhalevi
Re: Little problem with Kde
On Thursday 11 December 2014 17:56:52 MERLIN Philippe wrote: Le jeudi 11 décembre 2014, 18:14:02 David Baron a écrit : I believe the problem is memory. Sign out, it releases a whole bunch of memory (KDE is not exactly economical). Get this behavior going from account to account if I have two sessions going and log out from one. Once the log out is done, the poweroff is very quick (systemd). Its very interesting, you say, that you obtain an *poweroff* with kde, for me i have only an *halt* which with systemd does not stop electrically the computer. Philippe Merlin I think this is configurable -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2224013.e6JPzo8Dqp@dovidhalevi
Bug#762166: [plasma-widget-folderview] Icon Positions Not Preserved
Package: plasma-widget-folderview Version: 4:4.14.0-1 Severity: normal --- Please enter the report below this line. --- Place icons is desired positions. Log out. Log in again, positions are back to some (random?) default. Not dependent on placement options selected--Even if fixed positions option selected, positions get changed back. --- System information. --- Architecture: amd64 Kernel: Linux 3.16-1-amd64 Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends (Version) | Installed ===-+-=== libc6 (= 2.14) | libkdecore5 (= 4:4.11) | libkdeui5 (= 4:4.11) | libkfile4 (= 4:4.11) | libkio5 (= 4:4.11) | libkonq5abi1 (= 4:4.8.2) | libplasma3 (= 4:4.11) | libqt4-dbus(= 4:4.5.3) | libqtcore4 (= 4:4.7.0~beta1) | libqtgui4 (= 4:4.8.0) | libsolid4 (= 4:4.11) | libstdc++6 (= 4.1.1) | libx11-6| 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: https://lists.debian.org/1770675.6oJqv1LqUu@dovidhalevi
Bug#746810: [ark] Removing Empty Directories: Incorrect Results
On Wednesday 30 July 2014 19:56:13 Maximiliano Curia wrote: Hi, The current ark version in sid uses libarchive correctly to write zip files, while the previous attemps produced a badly named tar.gz file, could you please test it and report back if this fixes the issues for you? Happy hacking, Current 4.13.3-1 fails deleting anything! ErrorBox Setting the format failed with the following error: No such format -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1451392.bcm8p9HpWq@dovidhalevi
Bug#754387: Latest and Greatest 4.13-3 May be OK!
Went back to IMAP, no ghosts so far. Will be testing and using :-) -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/4962899.g4fIsfhkHu@dovidhalevi
Bug#754387: More
I am presently not running kmail using dovecot imap but direct access to the mbox folder. Deletions work. However, the folder does not get compacted (cited earlier, just grows and grows). Click to explicitly compact fails. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/3274655.INTBQmJdbx@dovidhalevi
Bug#754257: [kdm] Workaround: Started with Empty Home Directory
On Monday 21 July 2014 12:39:05 Maximiliano Curia wrote: Control: tag -1 + unreproducible ¡Hola David! El 2014-07-17 a las 12:50 +0300, David Baron escribió: Both users now work, second user started with new, empty home directory. It did NOT make any difference whether it was a primary or secondary login. When it still did not work, did not. Does work, does... Well, I still can't reproduce the issue, and since you can no longer reproduce it I'm tagging the issue as unreproducible, and will probably close it if no one can provide a simple way to reproduce it. Posters on other forums said gdm worked when kdm did not. were not Debian posters. This may indicate an upstream issue, but I thought the issue was upgrading your system from wheezy to jessie, that would be updating the kdm package from 4:4.8.4-6 to 4:4.11.9-1. If the issue is present in other distributions it might be possible to narrow the versions gap with that information. Would a copy of the original (from the 32 bit former installation) home directory be of use? Problem was not in .kde because I tried it with the old one and with none--never tried to read or initial it. Maybe something in .config. As I said, very little was in this user's home. The issue was present in both the 4.4.8 and the 4.4.11 versions. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/10277679.zRUlAdJ9X3@dovidhalevi
Bug#755388: [kmail] Kmail mail directory messages keep returning
Package: kmail Version: 4:4.12.4-1 Severity: normal --- Please enter the report below this line. --- If I delete new messages from any subfolder to the kmail mail directory, next time I click on that subfolder, update or check mail, those messages will return to their former subfolders. This is so even if trash folders were cleared. Only way to permanently get rid of them is to expire the subfolder, for example, one day back. Does not effect inbox placed in this folder-tree. Inbox in local-mail does have this problem, however. could be corollary to other bugs I submitted or be relevant to akonadi. --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends (Version) | Installed ===-+-=== perl| 5.18.2-7 kde-runtime ( 4:4.10) | 4:4.13.1-1 kdepim-runtime(= 4:4.10.2) | 4:4.12.4-2 kdepimlibs-kio-plugins | 4:4.12.4-1 libakonadi-calendar4 (= 4:4.11.1) | 4:4.12.4-1 libakonadi-contact4 (= 4:4.12.2) | 4:4.12.4-1 libakonadi-kde4 (= 4:4.12.2) | 4:4.12.4-1 libakonadi-kmime4 (= 4:4.12.2) | 4:4.12.4-1 libakonadiprotocolinternals1 (= 1.5.1) | 1.12.1-1+b1 libc6 (= 2.14) | 2.19-7 libcalendarsupport4 (= 4:4.12.4-1) | 4:4.12.4-1 libfolderarchive4(= 4:4.12.4-1) | 4:4.12.4-1 libgcc1(= 1:4.1.1) | 1:4.9.1-1 libgpgme++2 (= 4:4.12.2) | 4:4.12.4-1 libgrantlee-core0(= 0.3.0) | 0.3.0-5 libincidenceeditorsng4 (= 4:4.12.4-1) | 4:4.12.4-1 libkabc4 (= 4:4.12.2) | 4:4.12.4-1 libkalarmcal2 (= 4:4.8.1) | 4:4.12.4-1 libkcalcore4 (= 4:4.5.86) | 4:4.12.4-1 libkcalutils4 (= 4:4.5.86) | 4:4.12.4-1 libkcmutils4 (= 4:4.5.86) | 4:4.13.3-1 libkdecore5 (= 4:4.4.95) | 4:4.13.3-1 libkdepim4 (= 4:4.12.4-1) | 4:4.12.4-1 libkdeui5 (= 4:4.10.0) | 4:4.13.3-1 libkio5 (= 4:4.5.85) | 4:4.13.3-1 libkleo4 (= 4:4.12.4-1) | 4:4.12.4-1 libkmime4 (= 4:4.12.2) | 4:4.12.4-1 libknewstuff3-4 (= 4:4.5.85) | 4:4.13.3-1 libknotifyconfig4 (= 4:4.3.4) | 4:4.13.3-1 libkontactinterface4 (= 4:4.12.2) | 4:4.12.4-1 libkparts4(= 4:4.5.85) | 4:4.13.3-1 libkpgp4 (= 4:4.12.4-1) | 4:4.12.4-1 libkpimidentities4(= 4:4.12.2) | 4:4.12.4-1 libkpimtextedit4 (= 4:4.12.2) | 4:4.12.4-1 libkpimutils4 (= 4:4.12.2) | 4:4.12.4-1 libkprintutils4 (= 4:4.4.95) | 4:4.13.3-1 libksieveui4 (= 4:4.12.4-1) | 4:4.12.4-1 libktnef4 (= 4:4.12.2) | 4:4.12.4-1 libmailcommon4 (= 4:4.12.4-1) | 4:4.12.4-1 libmailimporter4 (= 4:4.12.4-1) | 4:4.12.4-1 libmailtransport4 (= 4:4.12.2) | 4:4.12.4-1 libmessagecomposer4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessagecore4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessagelist4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessageviewer4(= 4:4.12.4-1) | 4:4.12.4-1 libnepomukcore4(= 4:4.9.3) | 4:4.12.4-1+b1 libpimcommon4(= 4:4.12.4-1) | 4:4.12.4-1 libqt4-dbus(= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-network (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-xml (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqtcore4 (= 4:4.7.0~beta1) | 4:4.8.6+dfsg-2 libqtgui4 (= 4:4.8.0) | 4:4.8.6+dfsg-2 libqtwebkit4 (= 2.2.0) | 2.2.1-7 libsendlater4(= 4:4.12.4-1) | 4:4.12.4-1 libsolid4 (= 4:4.3.4) | 4:4.13.3-1 libsoprano4 (= 2.9.0) | 2.9.4+dfsg-1.1 libstdc++6 (= 4.1.1) | 4.9.1-1 libtemplateparser4 (= 4:4.12.4-1) | 4:4.12.4-1 Recommends(Version) | Installed ===-+-=== gnupg-agent | 2.0.25-1 gnupg2 | 2.0.25-1 pinentry-qt4| OR pinentry-x11| Suggests
Bug#754387: [kmail] Correction ...
Package: kmail Version: 4:4.12.4-1 --- Please enter the report below this line. --- Messages not being left on server. Problem of their untimely return is only on local folders-inbox. If I feed them to a different one, all is fine. So there is still a bug here, but not the same as reported for imap. --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends (Version) | Installed ===-+-=== perl| 5.18.2-7 kde-runtime ( 4:4.10) | 4:4.13.1-1 kdepim-runtime(= 4:4.10.2) | 4:4.12.4-2 kdepimlibs-kio-plugins | 4:4.12.4-1 libakonadi-calendar4 (= 4:4.11.1) | 4:4.12.4-1 libakonadi-contact4 (= 4:4.12.2) | 4:4.12.4-1 libakonadi-kde4 (= 4:4.12.2) | 4:4.12.4-1 libakonadi-kmime4 (= 4:4.12.2) | 4:4.12.4-1 libakonadiprotocolinternals1 (= 1.5.1) | 1.12.1-1+b1 libc6 (= 2.14) | 2.19-7 libcalendarsupport4 (= 4:4.12.4-1) | 4:4.12.4-1 libfolderarchive4(= 4:4.12.4-1) | 4:4.12.4-1 libgcc1(= 1:4.1.1) | 1:4.9.0-11 libgpgme++2 (= 4:4.12.2) | 4:4.12.4-1 libgrantlee-core0(= 0.3.0) | 0.3.0-5 libincidenceeditorsng4 (= 4:4.12.4-1) | 4:4.12.4-1 libkabc4 (= 4:4.12.2) | 4:4.12.4-1 libkalarmcal2 (= 4:4.8.1) | 4:4.12.4-1 libkcalcore4 (= 4:4.5.86) | 4:4.12.4-1 libkcalutils4 (= 4:4.5.86) | 4:4.12.4-1 libkcmutils4 (= 4:4.5.86) | 4:4.13.1-1 libkdecore5 (= 4:4.4.95) | 4:4.13.1-1 libkdepim4 (= 4:4.12.4-1) | 4:4.12.4-1 libkdeui5 (= 4:4.10.0) | 4:4.13.1-1 libkio5 (= 4:4.5.85) | 4:4.13.1-1 libkleo4 (= 4:4.12.4-1) | 4:4.12.4-1 libkmime4 (= 4:4.12.2) | 4:4.12.4-1 libknewstuff3-4 (= 4:4.5.85) | 4:4.13.1-1 libknotifyconfig4 (= 4:4.3.4) | 4:4.13.1-1 libkontactinterface4 (= 4:4.12.2) | 4:4.12.4-1 libkparts4(= 4:4.5.85) | 4:4.13.1-1 libkpgp4 (= 4:4.12.4-1) | 4:4.12.4-1 libkpimidentities4(= 4:4.12.2) | 4:4.12.4-1 libkpimtextedit4 (= 4:4.12.2) | 4:4.12.4-1 libkpimutils4 (= 4:4.12.2) | 4:4.12.4-1 libkprintutils4 (= 4:4.4.95) | 4:4.13.1-1 libksieveui4 (= 4:4.12.4-1) | 4:4.12.4-1 libktnef4 (= 4:4.12.2) | 4:4.12.4-1 libmailcommon4 (= 4:4.12.4-1) | 4:4.12.4-1 libmailimporter4 (= 4:4.12.4-1) | 4:4.12.4-1 libmailtransport4 (= 4:4.12.2) | 4:4.12.4-1 libmessagecomposer4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessagecore4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessagelist4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessageviewer4(= 4:4.12.4-1) | 4:4.12.4-1 libnepomukcore4(= 4:4.9.3) | 4:4.12.4-1+b1 libpimcommon4(= 4:4.12.4-1) | 4:4.12.4-1 libqt4-dbus(= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-network (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-xml (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqtcore4 (= 4:4.7.0~beta1) | 4:4.8.6+dfsg-2 libqtgui4 (= 4:4.8.0) | 4:4.8.6+dfsg-2 libqtwebkit4 (= 2.2.0) | 2.2.1-7 libsendlater4(= 4:4.12.4-1) | 4:4.12.4-1 libsolid4 (= 4:4.3.4) | 4:4.13.1-1 libsoprano4 (= 2.9.0) | 2.9.4+dfsg-1.1 libstdc++6 (= 4.1.1) | 4.9.0-11 libtemplateparser4 (= 4:4.12.4-1) | 4:4.12.4-1 Recommends(Version) | Installed ===-+-=== gnupg-agent | 2.0.25-1 gnupg2 | 2.0.25-1 pinentry-qt4| OR pinentry-x11| Suggests (Version) | Installed ==-+-== clamav | 0.98.4+dfsg-2+b1 OR f-prot-installer | kaddressbook | 4:4.12.4-1 kleopatra | procmail | 3.22-21
Bug#754257: [kdm] Workaround: Started with Empty Home Directory
On Thursday 17 July 2014 11:34:46 Maximiliano Curia wrote: Control: priority -1 normal Control: tag -1 + moreinfo ¡Hola David! El 2014-07-16 a las 14:50 +0300, David Baron escribió: Yes, empty home directory for user and it logs in. Any data, of course, can be brought in from the saved copy. Let's make a summary so far: * You have at least one user in your system that fails to log in using kdm. * In the same system you have other users that do work correctly. * With a new user the session starts correctly. I couldn't find in the reports what kind of session you are trying to start with the users that can't login, I'm assuming you are trying to start kde plasma. With this information, I would suspect of a composite/opengl related issue, and of some corrupted data in the home user directory that causes the session to fail completely. Please respond as clearly as possible the questions bellow: You mentioned that the bug doesn't happend with your user, which makes me wonder if you are loging in your user in the first graphical session and the failling users are trying to log in in the secondary graphical sessions (Change users/ New Login in kde). Can you confirm me if you log the failling user in the first graphical session if it works or not? Both users now work, second user started with new, empty home directory. It did NOT make any difference whether it was a primary or secondary login. When it still did not work, did not. Does work, does... Does the session of the failling users start correctly using another display manager (lightdm, gdm, etc)? Was not tried. Posters on other forums said gdm worked when kdm did not. These were not Debian posters. lightdm is Ubuntu Does the session starts correctly if you use another type of session/desktop environment/window manager (like openbox, for example)? Did not try other graphical sessions. I could log the user onto a bash shell. After replying these questions, a good way to find the culprit would be to do a binary search with the data in the home user. It would be particularly useful if you could reproduce the issue copying a failling user ~/.kde and ~/.config to a newly created user home. I no longer have them, no important data. However, when it did fail, old or blank or no .kde made no difference. Problem was outside of .kde directory. One other hint. My session which I got working with dist-upgrade started with a fresh (no) .kde. However, the menus that I had were the old menus from previous installation. So maybe something outside of .kde, in .config or wherever the menu info is stored. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2240449.xvGXL1TOdn@dovidhalevi
Bug#755080: [plasma-widget-folderview] Select Properties Dialog Always Checks All
Package: plasma-widget-folderview Version: 4:4.12.4-1 Severity: normal --- Please enter the report below this line. --- After I have set up a folder view, such as to show certain file types, and I wish to modify the properties, the dialog will come up with ALL file types checked. In other words, to add one, for example, I must redo the whole list. Properties dialog should come up as previous set up. --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends (Version) | Installed ===-+-=== libc6 (= 2.14) | 2.19-7 libkdecore5 (= 4:4.11) | 4:4.13.1-1 libkdeui5 (= 4:4.11) | 4:4.13.1-1 libkfile4 (= 4:4.11) | 4:4.13.1-1 libkio5 (= 4:4.11) | 4:4.13.1-1 libkonq5abi1 (= 4:4.8.2) | 4:4.12.4-1 libplasma3 (= 4:4.11) | 4:4.13.1-1 libqt4-dbus(= 4:4.5.3) | 4:4.8.6+dfsg-2 libqtcore4 (= 4:4.7.0~beta1) | 4:4.8.6+dfsg-2 libqtgui4 (= 4:4.8.0) | 4:4.8.6+dfsg-2 libsolid4 (= 4:4.11) | 4:4.13.1-1 libstdc++6 (= 4.1.1) | 4.9.0-11 libx11-6| 2:1.6.2-2 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: https://lists.debian.org/6034928.iuQktp0Zvl@dovidhalevi
Bug#754387: [kmail] More, tried local dovecot pop3
Package: kmail Version: 4:4.12.4-1 --- Please enter the report below this line. --- and messages were not removed from the /var/mail/username file. If messages were routed to local inbox, they doubled. Other inboxes they simply repeated. --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends (Version) | Installed ===-+-=== perl| 5.18.2-7 kde-runtime ( 4:4.10) | 4:4.13.1-1 kdepim-runtime(= 4:4.10.2) | 4:4.12.4-2 kdepimlibs-kio-plugins | 4:4.12.4-1 libakonadi-calendar4 (= 4:4.11.1) | 4:4.12.4-1 libakonadi-contact4 (= 4:4.12.2) | 4:4.12.4-1 libakonadi-kde4 (= 4:4.12.2) | 4:4.12.4-1 libakonadi-kmime4 (= 4:4.12.2) | 4:4.12.4-1 libakonadiprotocolinternals1 (= 1.5.1) | 1.12.1-1+b1 libc6 (= 2.14) | 2.19-7 libcalendarsupport4 (= 4:4.12.4-1) | 4:4.12.4-1 libfolderarchive4(= 4:4.12.4-1) | 4:4.12.4-1 libgcc1(= 1:4.1.1) | 1:4.9.0-11 libgpgme++2 (= 4:4.12.2) | 4:4.12.4-1 libgrantlee-core0(= 0.3.0) | 0.3.0-5 libincidenceeditorsng4 (= 4:4.12.4-1) | 4:4.12.4-1 libkabc4 (= 4:4.12.2) | 4:4.12.4-1 libkalarmcal2 (= 4:4.8.1) | 4:4.12.4-1 libkcalcore4 (= 4:4.5.86) | 4:4.12.4-1 libkcalutils4 (= 4:4.5.86) | 4:4.12.4-1 libkcmutils4 (= 4:4.5.86) | 4:4.13.1-1 libkdecore5 (= 4:4.4.95) | 4:4.13.1-1 libkdepim4 (= 4:4.12.4-1) | 4:4.12.4-1 libkdeui5 (= 4:4.10.0) | 4:4.13.1-1 libkio5 (= 4:4.5.85) | 4:4.13.1-1 libkleo4 (= 4:4.12.4-1) | 4:4.12.4-1 libkmime4 (= 4:4.12.2) | 4:4.12.4-1 libknewstuff3-4 (= 4:4.5.85) | 4:4.13.1-1 libknotifyconfig4 (= 4:4.3.4) | 4:4.13.1-1 libkontactinterface4 (= 4:4.12.2) | 4:4.12.4-1 libkparts4(= 4:4.5.85) | 4:4.13.1-1 libkpgp4 (= 4:4.12.4-1) | 4:4.12.4-1 libkpimidentities4(= 4:4.12.2) | 4:4.12.4-1 libkpimtextedit4 (= 4:4.12.2) | 4:4.12.4-1 libkpimutils4 (= 4:4.12.2) | 4:4.12.4-1 libkprintutils4 (= 4:4.4.95) | 4:4.13.1-1 libksieveui4 (= 4:4.12.4-1) | 4:4.12.4-1 libktnef4 (= 4:4.12.2) | 4:4.12.4-1 libmailcommon4 (= 4:4.12.4-1) | 4:4.12.4-1 libmailimporter4 (= 4:4.12.4-1) | 4:4.12.4-1 libmailtransport4 (= 4:4.12.2) | 4:4.12.4-1 libmessagecomposer4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessagecore4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessagelist4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessageviewer4(= 4:4.12.4-1) | 4:4.12.4-1 libnepomukcore4(= 4:4.9.3) | 4:4.12.4-1+b1 libpimcommon4(= 4:4.12.4-1) | 4:4.12.4-1 libqt4-dbus(= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-network (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-xml (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqtcore4 (= 4:4.7.0~beta1) | 4:4.8.6+dfsg-2 libqtgui4 (= 4:4.8.0) | 4:4.8.6+dfsg-2 libqtwebkit4 (= 2.2.0) | 2.2.1-7 libsendlater4(= 4:4.12.4-1) | 4:4.12.4-1 libsolid4 (= 4:4.3.4) | 4:4.13.1-1 libsoprano4 (= 2.9.0) | 2.9.4+dfsg-1.1 libstdc++6 (= 4.1.1) | 4.9.0-11 libtemplateparser4 (= 4:4.12.4-1) | 4:4.12.4-1 Recommends(Version) | Installed ===-+-=== gnupg-agent | 2.0.25-1 gnupg2 | 2.0.25-1 pinentry-qt4| OR pinentry-x11| Suggests (Version) | Installed ==-+-== clamav | 0.98.4+dfsg-2+b1 OR f-prot-installer | kaddressbook | 4:4.12.4-1 kleopatra | procmail | 3.22-21 spamassassin | 3.4.0-2 OR bogofilter
Bug#754257: [kdm] Workaround: Started with Empty Home Directory
Package: kdm Version: 4:4.11.9-1 --- Please enter the report below this line. --- Yes, empty home directory for user and it logs in. Any data, of course, can be brought in from the saved copy. --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends (Version) | Installed ===-+-=== adduser | 3.113+nmu3 consolekit | 0.4.6-5 debconf (= 0.5) | 1.5.53 OR debconf-2.0 | kde-wallpapers-default | 4:4.12.4-1 kde-workspace-kgreet-plugins (= 4:4.11.9-1) | 4:4.11.9-1 lsb-base(= 3.2-14) | 4.1+Debian13 kde-runtime ( 4:4.10) | 4:4.13.1-1 libc6 (= 2.15) | 2.19-7 libck-connector0 (= 0.2.1) | 0.4.6-5 libdbus-1-3 (= 1.0.2) | 1.8.6-1 libkdecore5 (= 4:4.11) | 4:4.13.1-1 libkdeui5 (= 4:4.11) | 4:4.13.1-1 libkio5 (= 4:4.11) | 4:4.13.1-1 libknewstuff3-4 (= 4:4.11) | 4:4.13.1-1 libkworkspace4abi2 (= 4:4.11.9-1) | 4:4.11.9-1 libpam0g (= 0.99.7.1) | 1.1.8-3 libqimageblitz4(= 1:0.0.4) | 1:0.0.6-4 libqt4-svg (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-xml (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqtcore4 (= 4:4.7.0~beta1) | 4:4.8.6+dfsg-2 libqtgui4 (= 4:4.8.0) | 4:4.8.6+dfsg-2 libstdc++6 (= 4.1.1) | 4.9.0-11 libx11-6| 2:1.6.2-2 libxau6 | 1:1.0.8-1 libxdmcp6 | 1:1.1.1-1 libxtst6| 2:1.2.2-1 Recommends (Version) | Installed ==-+-=== kde-workspace | 4:4.11.9-1 OR x-session-manager | OR x-window-manager | logrotate | 3.8.7-1 xserver-xorg | 1:7.7+7 OR xserver| xterm | 308-1 OR x-terminal-emulator| Suggests(Version) | Installed =-+-=== kde-wallpapers| 4:4.12.4-1 kdepasswd | 4:4.12.4-1 -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2582351.YsKsv1p6Cy@dovidhalevi
Bug#754387: [kmail] Must not be issuing the expunge!
Package: kmail Version: 4:4.12.4-1 --- Please enter the report below this line. --- Seems conclusive, that though the expunge option is checked in the imap account configuration, the expunge is not being done. This could be an important bug since it renders use of imap less than practical. Gmail auto- expunges, apparently. The delayed move workaround described for the possibly related bug have no effect on the problem. --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends (Version) | Installed ===-+-=== perl| 5.18.2-7 kde-runtime ( 4:4.10) | 4:4.13.1-1 kdepim-runtime(= 4:4.10.2) | 4:4.12.4-2 kdepimlibs-kio-plugins | 4:4.12.4-1 libakonadi-calendar4 (= 4:4.11.1) | 4:4.12.4-1 libakonadi-contact4 (= 4:4.12.2) | 4:4.12.4-1 libakonadi-kde4 (= 4:4.12.2) | 4:4.12.4-1 libakonadi-kmime4 (= 4:4.12.2) | 4:4.12.4-1 libakonadiprotocolinternals1 (= 1.5.1) | 1.12.1-1+b1 libc6 (= 2.14) | 2.19-7 libcalendarsupport4 (= 4:4.12.4-1) | 4:4.12.4-1 libfolderarchive4(= 4:4.12.4-1) | 4:4.12.4-1 libgcc1(= 1:4.1.1) | 1:4.9.0-11 libgpgme++2 (= 4:4.12.2) | 4:4.12.4-1 libgrantlee-core0(= 0.3.0) | 0.3.0-5 libincidenceeditorsng4 (= 4:4.12.4-1) | 4:4.12.4-1 libkabc4 (= 4:4.12.2) | 4:4.12.4-1 libkalarmcal2 (= 4:4.8.1) | 4:4.12.4-1 libkcalcore4 (= 4:4.5.86) | 4:4.12.4-1 libkcalutils4 (= 4:4.5.86) | 4:4.12.4-1 libkcmutils4 (= 4:4.5.86) | 4:4.13.1-1 libkdecore5 (= 4:4.4.95) | 4:4.13.1-1 libkdepim4 (= 4:4.12.4-1) | 4:4.12.4-1 libkdeui5 (= 4:4.10.0) | 4:4.13.1-1 libkio5 (= 4:4.5.85) | 4:4.13.1-1 libkleo4 (= 4:4.12.4-1) | 4:4.12.4-1 libkmime4 (= 4:4.12.2) | 4:4.12.4-1 libknewstuff3-4 (= 4:4.5.85) | 4:4.13.1-1 libknotifyconfig4 (= 4:4.3.4) | 4:4.13.1-1 libkontactinterface4 (= 4:4.12.2) | 4:4.12.4-1 libkparts4(= 4:4.5.85) | 4:4.13.1-1 libkpgp4 (= 4:4.12.4-1) | 4:4.12.4-1 libkpimidentities4(= 4:4.12.2) | 4:4.12.4-1 libkpimtextedit4 (= 4:4.12.2) | 4:4.12.4-1 libkpimutils4 (= 4:4.12.2) | 4:4.12.4-1 libkprintutils4 (= 4:4.4.95) | 4:4.13.1-1 libksieveui4 (= 4:4.12.4-1) | 4:4.12.4-1 libktnef4 (= 4:4.12.2) | 4:4.12.4-1 libmailcommon4 (= 4:4.12.4-1) | 4:4.12.4-1 libmailimporter4 (= 4:4.12.4-1) | 4:4.12.4-1 libmailtransport4 (= 4:4.12.2) | 4:4.12.4-1 libmessagecomposer4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessagecore4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessagelist4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessageviewer4(= 4:4.12.4-1) | 4:4.12.4-1 libnepomukcore4(= 4:4.9.3) | 4:4.12.4-1+b1 libpimcommon4(= 4:4.12.4-1) | 4:4.12.4-1 libqt4-dbus(= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-network (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-xml (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqtcore4 (= 4:4.7.0~beta1) | 4:4.8.6+dfsg-2 libqtgui4 (= 4:4.8.0) | 4:4.8.6+dfsg-2 libqtwebkit4 (= 2.2.0) | 2.2.1-7 libsendlater4(= 4:4.12.4-1) | 4:4.12.4-1 libsolid4 (= 4:4.3.4) | 4:4.13.1-1 libsoprano4 (= 2.9.0) | 2.9.4+dfsg-1.1 libstdc++6 (= 4.1.1) | 4.9.0-11 libtemplateparser4 (= 4:4.12.4-1) | 4:4.12.4-1 Recommends(Version) | Installed ===-+-=== gnupg-agent | 2.0.25-1 gnupg2 | 2.0.25-1 pinentry-qt4| OR pinentry-x11| Suggests (Version) | Installed ==-+-== clamav | 0.98.4+dfsg-2+b1 OR f-prot-installer |
Bug#754387: [kmail] More ... POP3 also does not remove messages!
Package: kmail Version: 4:4.12.4-1 --- Please enter the report below this line. --- Leave on server NOT checked. I delete retrieved messages, they come right back. At least they are not ghosts. --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends (Version) | Installed ===-+-=== perl| 5.18.2-7 kde-runtime ( 4:4.10) | 4:4.13.1-1 kdepim-runtime(= 4:4.10.2) | 4:4.12.4-2 kdepimlibs-kio-plugins | 4:4.12.4-1 libakonadi-calendar4 (= 4:4.11.1) | 4:4.12.4-1 libakonadi-contact4 (= 4:4.12.2) | 4:4.12.4-1 libakonadi-kde4 (= 4:4.12.2) | 4:4.12.4-1 libakonadi-kmime4 (= 4:4.12.2) | 4:4.12.4-1 libakonadiprotocolinternals1 (= 1.5.1) | 1.12.1-1+b1 libc6 (= 2.14) | 2.19-7 libcalendarsupport4 (= 4:4.12.4-1) | 4:4.12.4-1 libfolderarchive4(= 4:4.12.4-1) | 4:4.12.4-1 libgcc1(= 1:4.1.1) | 1:4.9.0-11 libgpgme++2 (= 4:4.12.2) | 4:4.12.4-1 libgrantlee-core0(= 0.3.0) | 0.3.0-5 libincidenceeditorsng4 (= 4:4.12.4-1) | 4:4.12.4-1 libkabc4 (= 4:4.12.2) | 4:4.12.4-1 libkalarmcal2 (= 4:4.8.1) | 4:4.12.4-1 libkcalcore4 (= 4:4.5.86) | 4:4.12.4-1 libkcalutils4 (= 4:4.5.86) | 4:4.12.4-1 libkcmutils4 (= 4:4.5.86) | 4:4.13.1-1 libkdecore5 (= 4:4.4.95) | 4:4.13.1-1 libkdepim4 (= 4:4.12.4-1) | 4:4.12.4-1 libkdeui5 (= 4:4.10.0) | 4:4.13.1-1 libkio5 (= 4:4.5.85) | 4:4.13.1-1 libkleo4 (= 4:4.12.4-1) | 4:4.12.4-1 libkmime4 (= 4:4.12.2) | 4:4.12.4-1 libknewstuff3-4 (= 4:4.5.85) | 4:4.13.1-1 libknotifyconfig4 (= 4:4.3.4) | 4:4.13.1-1 libkontactinterface4 (= 4:4.12.2) | 4:4.12.4-1 libkparts4(= 4:4.5.85) | 4:4.13.1-1 libkpgp4 (= 4:4.12.4-1) | 4:4.12.4-1 libkpimidentities4(= 4:4.12.2) | 4:4.12.4-1 libkpimtextedit4 (= 4:4.12.2) | 4:4.12.4-1 libkpimutils4 (= 4:4.12.2) | 4:4.12.4-1 libkprintutils4 (= 4:4.4.95) | 4:4.13.1-1 libksieveui4 (= 4:4.12.4-1) | 4:4.12.4-1 libktnef4 (= 4:4.12.2) | 4:4.12.4-1 libmailcommon4 (= 4:4.12.4-1) | 4:4.12.4-1 libmailimporter4 (= 4:4.12.4-1) | 4:4.12.4-1 libmailtransport4 (= 4:4.12.2) | 4:4.12.4-1 libmessagecomposer4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessagecore4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessagelist4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessageviewer4(= 4:4.12.4-1) | 4:4.12.4-1 libnepomukcore4(= 4:4.9.3) | 4:4.12.4-1+b1 libpimcommon4(= 4:4.12.4-1) | 4:4.12.4-1 libqt4-dbus(= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-network (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-xml (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqtcore4 (= 4:4.7.0~beta1) | 4:4.8.6+dfsg-2 libqtgui4 (= 4:4.8.0) | 4:4.8.6+dfsg-2 libqtwebkit4 (= 2.2.0) | 2.2.1-7 libsendlater4(= 4:4.12.4-1) | 4:4.12.4-1 libsolid4 (= 4:4.3.4) | 4:4.13.1-1 libsoprano4 (= 2.9.0) | 2.9.4+dfsg-1.1 libstdc++6 (= 4.1.1) | 4.9.0-11 libtemplateparser4 (= 4:4.12.4-1) | 4:4.12.4-1 Recommends(Version) | Installed ===-+-=== gnupg-agent | 2.0.25-1 gnupg2 | 2.0.25-1 pinentry-qt4| OR pinentry-x11| Suggests (Version) | Installed ==-+-== clamav | 0.98.4+dfsg-2+b1 OR f-prot-installer | kaddressbook | 4:4.12.4-1 kleopatra | procmail | 3.22-21 spamassassin | 3.4.0-2 OR bogofilter | OR annoyance-filter
Bug#754797: [plasma-desktop] Needs additional packages
Package: plasma-desktop Version: 4:4.11.9-1 --- Please enter the report below this line. --- Installed additional packages, have activities. However, creation of the activities made problems for the original single activity. That desktop got reverted to a previous configuration I thought was lost. No big deal, but indicates instability. Can close this one. --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends (Version) | Installed ===-+-=== kde-wallpapers-default | 4:4.12.4-1 plasma-widgets-workspace (= 4:4.11.9-1) | 4:4.11.9-1 kde-runtime ( 4:4.10) | 4:4.13.1-1 libc6 (= 2.14) | 2.19-7 libkactivities6 (= 4:4.11) | 4:4.13.1-1 libkcmutils4(= 4:4.11) | 4:4.13.1-1 libkdecore5 (= 4:4.11) | 4:4.13.1-1 libkdeui5 (= 4:4.11) | 4:4.13.1-1 libkephal4abi1 (= 4:4.11.9-1) | 4:4.11.9-1 libkfile4 (= 4:4.11) | 4:4.13.1-1 libkidletime4 (= 4:4.11) | 4:4.13.1-1 libkio5 (= 4:4.11) | 4:4.13.1-1 libknewstuff3-4 (= 4:4.11) | 4:4.13.1-1 libktexteditor4 (= 4:4.11) | 4:4.13.1-1 libkworkspace4abi2 (= 4:4.11.9-1) | 4:4.11.9-1 libplasma3 (= 4:4.11) | 4:4.13.1-1 libplasmagenericshell4 (= 4:4.11.9-1) | 4:4.11.9-1 libqt4-dbus(= 4:4.6.1) | 4:4.8.6+dfsg-2 libqt4-declarative (= 4:4.7.0~rc1) | 4:4.8.6+dfsg-2 libqt4-xml (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqtcore4 (= 4:4.7.0~beta1) | 4:4.8.6+dfsg-2 libqtgui4 (= 4:4.8.0) | 4:4.8.6+dfsg-2 libsolid4 (= 4:4.11) | 4:4.13.1-1 libstdc++6 (= 4.1.1) | 4.9.0-11 libtaskmanager4abi4 (= 4:4.11.9-1) | 4:4.11.9-1 libx11-6| 2:1.6.2-2 libxext6| 2:1.3.2-1 Recommends (Version) | Installed -+-=== kde-workspace| 4:4.11.9-1 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: https://lists.debian.org/175700834.0lZeLHMtaJ@dovidhalevi
Bug#754797: [plasma-desktop] Cannot Create New Activities
Package: plasma-desktop Version: 4:4.11.9-1 Severity: normal --- Please enter the report below this line. --- Using the default activity widget, cannot add any activities to the desktop. Note the previous stable version came with several activities pre-loaded, this did not. --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends (Version) | Installed ===-+-=== kde-wallpapers-default | 4:4.12.4-1 plasma-widgets-workspace (= 4:4.11.9-1) | 4:4.11.9-1 kde-runtime ( 4:4.10) | 4:4.13.1-1 libc6 (= 2.14) | 2.19-7 libkactivities6 (= 4:4.11) | 4:4.13.1-1 libkcmutils4(= 4:4.11) | 4:4.13.1-1 libkdecore5 (= 4:4.11) | 4:4.13.1-1 libkdeui5 (= 4:4.11) | 4:4.13.1-1 libkephal4abi1 (= 4:4.11.9-1) | 4:4.11.9-1 libkfile4 (= 4:4.11) | 4:4.13.1-1 libkidletime4 (= 4:4.11) | 4:4.13.1-1 libkio5 (= 4:4.11) | 4:4.13.1-1 libknewstuff3-4 (= 4:4.11) | 4:4.13.1-1 libktexteditor4 (= 4:4.11) | 4:4.13.1-1 libkworkspace4abi2 (= 4:4.11.9-1) | 4:4.11.9-1 libplasma3 (= 4:4.11) | 4:4.13.1-1 libplasmagenericshell4 (= 4:4.11.9-1) | 4:4.11.9-1 libqt4-dbus(= 4:4.6.1) | 4:4.8.6+dfsg-2 libqt4-declarative (= 4:4.7.0~rc1) | 4:4.8.6+dfsg-2 libqt4-xml (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqtcore4 (= 4:4.7.0~beta1) | 4:4.8.6+dfsg-2 libqtgui4 (= 4:4.8.0) | 4:4.8.6+dfsg-2 libsolid4 (= 4:4.11) | 4:4.13.1-1 libstdc++6 (= 4.1.1) | 4.9.0-11 libtaskmanager4abi4 (= 4:4.11.9-1) | 4:4.11.9-1 libx11-6| 2:1.6.2-2 libxext6| 2:1.3.2-1 Recommends (Version) | Installed -+-=== kde-workspace| 4:4.11.9-1 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: https://lists.debian.org/1520944.q405Q35MEx@dovidhalevi
Bug#754257: [kdm] Other users still cannot login
Package: kdm Version: 4:4.11.9-1 --- Please enter the report below this line. --- Yes, my user account is working fine. Others simply blink and back to login dialog. I do not think that the user's home .kde is accessed at all. Never gets out of kdm. All the permissions seem to be OK. Enough space. At wits end here. I would close this were it not for this continuing problem. --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends (Version) | Installed ===-+-=== adduser | 3.113+nmu3 consolekit | 0.4.6-5 debconf (= 0.5) | 1.5.53 OR debconf-2.0 | kde-wallpapers-default | 4:4.12.4-1 kde-workspace-kgreet-plugins (= 4:4.11.9-1) | 4:4.11.9-1 lsb-base(= 3.2-14) | 4.1+Debian13 kde-runtime ( 4:4.10) | 4:4.13.1-1 libc6 (= 2.15) | 2.19-6 libck-connector0 (= 0.2.1) | 0.4.6-5 libdbus-1-3 (= 1.0.2) | 1.8.6-1 libkdecore5 (= 4:4.11) | 4:4.13.1-1 libkdeui5 (= 4:4.11) | 4:4.13.1-1 libkio5 (= 4:4.11) | 4:4.13.1-1 libknewstuff3-4 (= 4:4.11) | 4:4.13.1-1 libkworkspace4abi2 (= 4:4.11.9-1) | 4:4.11.9-1 libpam0g (= 0.99.7.1) | 1.1.8-3 libqimageblitz4(= 1:0.0.4) | 1:0.0.6-4 libqt4-svg (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-xml (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqtcore4 (= 4:4.7.0~beta1) | 4:4.8.6+dfsg-2 libqtgui4 (= 4:4.8.0) | 4:4.8.6+dfsg-2 libstdc++6 (= 4.1.1) | 4.9.0-11 libx11-6| 2:1.6.2-2 libxau6 | 1:1.0.8-1 libxdmcp6 | 1:1.1.1-1 libxtst6| 2:1.2.2-1 Recommends (Version) | Installed ==-+-=== kde-workspace | 4:4.11.9-1 OR x-session-manager | OR x-window-manager | logrotate | 3.8.7-1 xserver-xorg | 1:7.7+7 OR xserver| xterm | 308-1 OR x-terminal-emulator| Suggests(Version) | Installed =-+-=== kde-wallpapers| 4:4.12.4-1 kdepasswd | 4:4.12.4-1 -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5586964.eKUyhG4xOs@dovidhalevi
Bug#754387: [kmail] Expunging?
Package: kmail Version: 4:4.12.4-1 --- Please enter the report below this line. --- Dovecot maintainers (filed similar bug on this!) ask: Is kmail issuing the expunge command to the IMAP server (this is what is reality does the deletion)?? --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends (Version) | Installed ===-+-=== perl| 5.18.2-6 kde-runtime ( 4:4.10) | 4:4.13.1-1 kdepim-runtime(= 4:4.10.2) | 4:4.12.4-2 kdepimlibs-kio-plugins | 4:4.12.4-1 libakonadi-calendar4 (= 4:4.11.1) | 4:4.12.4-1 libakonadi-contact4 (= 4:4.12.2) | 4:4.12.4-1 libakonadi-kde4 (= 4:4.12.2) | 4:4.12.4-1 libakonadi-kmime4 (= 4:4.12.2) | 4:4.12.4-1 libakonadiprotocolinternals1 (= 1.5.1) | 1.12.1-1+b1 libc6 (= 2.14) | 2.19-5 libcalendarsupport4 (= 4:4.12.4-1) | 4:4.12.4-1 libfolderarchive4(= 4:4.12.4-1) | 4:4.12.4-1 libgcc1(= 1:4.1.1) | 1:4.9.0-10 libgpgme++2 (= 4:4.12.2) | 4:4.12.4-1 libgrantlee-core0(= 0.3.0) | 0.3.0-5 libincidenceeditorsng4 (= 4:4.12.4-1) | 4:4.12.4-1 libkabc4 (= 4:4.12.2) | 4:4.12.4-1 libkalarmcal2 (= 4:4.8.1) | 4:4.12.4-1 libkcalcore4 (= 4:4.5.86) | 4:4.12.4-1 libkcalutils4 (= 4:4.5.86) | 4:4.12.4-1 libkcmutils4 (= 4:4.5.86) | 4:4.13.1-1 libkdecore5 (= 4:4.4.95) | 4:4.13.1-1 libkdepim4 (= 4:4.12.4-1) | 4:4.12.4-1 libkdeui5 (= 4:4.10.0) | 4:4.13.1-1 libkio5 (= 4:4.5.85) | 4:4.13.1-1 libkleo4 (= 4:4.12.4-1) | 4:4.12.4-1 libkmime4 (= 4:4.12.2) | 4:4.12.4-1 libknewstuff3-4 (= 4:4.5.85) | 4:4.13.1-1 libknotifyconfig4 (= 4:4.3.4) | 4:4.13.1-1 libkontactinterface4 (= 4:4.12.2) | 4:4.12.4-1 libkparts4(= 4:4.5.85) | 4:4.13.1-1 libkpgp4 (= 4:4.12.4-1) | 4:4.12.4-1 libkpimidentities4(= 4:4.12.2) | 4:4.12.4-1 libkpimtextedit4 (= 4:4.12.2) | 4:4.12.4-1 libkpimutils4 (= 4:4.12.2) | 4:4.12.4-1 libkprintutils4 (= 4:4.4.95) | 4:4.13.1-1 libksieveui4 (= 4:4.12.4-1) | 4:4.12.4-1 libktnef4 (= 4:4.12.2) | 4:4.12.4-1 libmailcommon4 (= 4:4.12.4-1) | 4:4.12.4-1 libmailimporter4 (= 4:4.12.4-1) | 4:4.12.4-1 libmailtransport4 (= 4:4.12.2) | 4:4.12.4-1 libmessagecomposer4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessagecore4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessagelist4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessageviewer4(= 4:4.12.4-1) | 4:4.12.4-1 libnepomukcore4(= 4:4.9.3) | 4:4.12.4-1+b1 libpimcommon4(= 4:4.12.4-1) | 4:4.12.4-1 libqt4-dbus(= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-network (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-xml (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqtcore4 (= 4:4.7.0~beta1) | 4:4.8.6+dfsg-2 libqtgui4 (= 4:4.8.0) | 4:4.8.6+dfsg-2 libqtwebkit4 (= 2.2.0) | 2.2.1-7 libsendlater4(= 4:4.12.4-1) | 4:4.12.4-1 libsolid4 (= 4:4.3.4) | 4:4.13.1-1 libsoprano4 (= 2.9.0) | 2.9.4+dfsg-1.1 libstdc++6 (= 4.1.1) | 4.9.0-10 libtemplateparser4 (= 4:4.12.4-1) | 4:4.12.4-1 Recommends(Version) | Installed ===-+-=== gnupg-agent | 2.0.25-1 gnupg2 | 2.0.25-1 pinentry-qt4| OR pinentry-x11| Suggests (Version) | Installed ==-+-== clamav | 0.98.4+dfsg-2+b1 OR f-prot-installer | kaddressbook | 4:4.12.4-1 kleopatra | procmail | 3.22-21 spamassassin | 3.4.0-2 OR bogofilter
Bug#754387: [kmail] May be related to #750818
Package: kmail Version: 4:4.12.4-1 --- Please enter the report below this line. --- This problem may be related to previous #750818. While the described workaround might help with filters, moving to trash is not configurable this way. This problem has not been around for years, at least on 32-bit versions I used previously. --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends (Version) | Installed ===-+-=== perl| 5.18.2-6 kde-runtime ( 4:4.10) | 4:4.13.1-1 kdepim-runtime(= 4:4.10.2) | 4:4.12.4-2 kdepimlibs-kio-plugins | 4:4.12.4-1 libakonadi-calendar4 (= 4:4.11.1) | 4:4.12.4-1 libakonadi-contact4 (= 4:4.12.2) | 4:4.12.4-1 libakonadi-kde4 (= 4:4.12.2) | 4:4.12.4-1 libakonadi-kmime4 (= 4:4.12.2) | 4:4.12.4-1 libakonadiprotocolinternals1 (= 1.5.1) | 1.12.1-1+b1 libc6 (= 2.14) | 2.19-5 libcalendarsupport4 (= 4:4.12.4-1) | 4:4.12.4-1 libfolderarchive4(= 4:4.12.4-1) | 4:4.12.4-1 libgcc1(= 1:4.1.1) | 1:4.9.0-10 libgpgme++2 (= 4:4.12.2) | 4:4.12.4-1 libgrantlee-core0(= 0.3.0) | 0.3.0-5 libincidenceeditorsng4 (= 4:4.12.4-1) | 4:4.12.4-1 libkabc4 (= 4:4.12.2) | 4:4.12.4-1 libkalarmcal2 (= 4:4.8.1) | 4:4.12.4-1 libkcalcore4 (= 4:4.5.86) | 4:4.12.4-1 libkcalutils4 (= 4:4.5.86) | 4:4.12.4-1 libkcmutils4 (= 4:4.5.86) | 4:4.13.1-1 libkdecore5 (= 4:4.4.95) | 4:4.13.1-1 libkdepim4 (= 4:4.12.4-1) | 4:4.12.4-1 libkdeui5 (= 4:4.10.0) | 4:4.13.1-1 libkio5 (= 4:4.5.85) | 4:4.13.1-1 libkleo4 (= 4:4.12.4-1) | 4:4.12.4-1 libkmime4 (= 4:4.12.2) | 4:4.12.4-1 libknewstuff3-4 (= 4:4.5.85) | 4:4.13.1-1 libknotifyconfig4 (= 4:4.3.4) | 4:4.13.1-1 libkontactinterface4 (= 4:4.12.2) | 4:4.12.4-1 libkparts4(= 4:4.5.85) | 4:4.13.1-1 libkpgp4 (= 4:4.12.4-1) | 4:4.12.4-1 libkpimidentities4(= 4:4.12.2) | 4:4.12.4-1 libkpimtextedit4 (= 4:4.12.2) | 4:4.12.4-1 libkpimutils4 (= 4:4.12.2) | 4:4.12.4-1 libkprintutils4 (= 4:4.4.95) | 4:4.13.1-1 libksieveui4 (= 4:4.12.4-1) | 4:4.12.4-1 libktnef4 (= 4:4.12.2) | 4:4.12.4-1 libmailcommon4 (= 4:4.12.4-1) | 4:4.12.4-1 libmailimporter4 (= 4:4.12.4-1) | 4:4.12.4-1 libmailtransport4 (= 4:4.12.2) | 4:4.12.4-1 libmessagecomposer4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessagecore4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessagelist4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessageviewer4(= 4:4.12.4-1) | 4:4.12.4-1 libnepomukcore4(= 4:4.9.3) | 4:4.12.4-1+b1 libpimcommon4(= 4:4.12.4-1) | 4:4.12.4-1 libqt4-dbus(= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-network (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-xml (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqtcore4 (= 4:4.7.0~beta1) | 4:4.8.6+dfsg-2 libqtgui4 (= 4:4.8.0) | 4:4.8.6+dfsg-2 libqtwebkit4 (= 2.2.0) | 2.2.1-7 libsendlater4(= 4:4.12.4-1) | 4:4.12.4-1 libsolid4 (= 4:4.3.4) | 4:4.13.1-1 libsoprano4 (= 2.9.0) | 2.9.4+dfsg-1.1 libstdc++6 (= 4.1.1) | 4.9.0-10 libtemplateparser4 (= 4:4.12.4-1) | 4:4.12.4-1 Recommends(Version) | Installed ===-+-=== gnupg-agent | 2.0.25-1 gnupg2 | 2.0.25-1 pinentry-qt4| OR pinentry-x11| Suggests (Version) | Installed ==-+-== clamav | 0.98.4+dfsg-2+b1 OR f-prot-installer | kaddressbook | 4:4.12.4-1 kleopatra | procmail
Bug#754387: [kmail] Inbox for local imap server keeps ghosts of messages
Package: kmail Version: 4:4.12.4-1 Severity: normal --- Please enter the report below this line. --- I pop email off provider and use dovecot as imap server. Use kmail locally and k9-mail on android phone successfully to access and read mail. After latest dist-upgrade to Sid, deleted messages remain, grayed out, in the inbox. Can sometimes but not always get rid of them by removing the inbox which is then re-generated. This is not a continuing problem on gmail. Had a folder there with hundreds of old messages, seems to have gotten rid of it. These were not grayed, but were active. Their problem. The kmail bug is our problem :-) --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends (Version) | Installed ===-+-=== perl| 5.18.2-6 kde-runtime ( 4:4.10) | 4:4.13.1-1 kdepim-runtime(= 4:4.10.2) | 4:4.12.4-2 kdepimlibs-kio-plugins | 4:4.12.4-1 libakonadi-calendar4 (= 4:4.11.1) | 4:4.12.4-1 libakonadi-contact4 (= 4:4.12.2) | 4:4.12.4-1 libakonadi-kde4 (= 4:4.12.2) | 4:4.12.4-1 libakonadi-kmime4 (= 4:4.12.2) | 4:4.12.4-1 libakonadiprotocolinternals1 (= 1.5.1) | 1.12.1-1+b1 libc6 (= 2.14) | 2.19-5 libcalendarsupport4 (= 4:4.12.4-1) | 4:4.12.4-1 libfolderarchive4(= 4:4.12.4-1) | 4:4.12.4-1 libgcc1(= 1:4.1.1) | 1:4.9.0-10 libgpgme++2 (= 4:4.12.2) | 4:4.12.4-1 libgrantlee-core0(= 0.3.0) | 0.3.0-5 libincidenceeditorsng4 (= 4:4.12.4-1) | 4:4.12.4-1 libkabc4 (= 4:4.12.2) | 4:4.12.4-1 libkalarmcal2 (= 4:4.8.1) | 4:4.12.4-1 libkcalcore4 (= 4:4.5.86) | 4:4.12.4-1 libkcalutils4 (= 4:4.5.86) | 4:4.12.4-1 libkcmutils4 (= 4:4.5.86) | 4:4.13.1-1 libkdecore5 (= 4:4.4.95) | 4:4.13.1-1 libkdepim4 (= 4:4.12.4-1) | 4:4.12.4-1 libkdeui5 (= 4:4.10.0) | 4:4.13.1-1 libkio5 (= 4:4.5.85) | 4:4.13.1-1 libkleo4 (= 4:4.12.4-1) | 4:4.12.4-1 libkmime4 (= 4:4.12.2) | 4:4.12.4-1 libknewstuff3-4 (= 4:4.5.85) | 4:4.13.1-1 libknotifyconfig4 (= 4:4.3.4) | 4:4.13.1-1 libkontactinterface4 (= 4:4.12.2) | 4:4.12.4-1 libkparts4(= 4:4.5.85) | 4:4.13.1-1 libkpgp4 (= 4:4.12.4-1) | 4:4.12.4-1 libkpimidentities4(= 4:4.12.2) | 4:4.12.4-1 libkpimtextedit4 (= 4:4.12.2) | 4:4.12.4-1 libkpimutils4 (= 4:4.12.2) | 4:4.12.4-1 libkprintutils4 (= 4:4.4.95) | 4:4.13.1-1 libksieveui4 (= 4:4.12.4-1) | 4:4.12.4-1 libktnef4 (= 4:4.12.2) | 4:4.12.4-1 libmailcommon4 (= 4:4.12.4-1) | 4:4.12.4-1 libmailimporter4 (= 4:4.12.4-1) | 4:4.12.4-1 libmailtransport4 (= 4:4.12.2) | 4:4.12.4-1 libmessagecomposer4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessagecore4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessagelist4 (= 4:4.12.4-1) | 4:4.12.4-1 libmessageviewer4(= 4:4.12.4-1) | 4:4.12.4-1 libnepomukcore4(= 4:4.9.3) | 4:4.12.4-1+b1 libpimcommon4(= 4:4.12.4-1) | 4:4.12.4-1 libqt4-dbus(= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-network (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-xml (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqtcore4 (= 4:4.7.0~beta1) | 4:4.8.6+dfsg-2 libqtgui4 (= 4:4.8.0) | 4:4.8.6+dfsg-2 libqtwebkit4 (= 2.2.0) | 2.2.1-7 libsendlater4(= 4:4.12.4-1) | 4:4.12.4-1 libsolid4 (= 4:4.3.4) | 4:4.13.1-1 libsoprano4 (= 2.9.0) | 2.9.4+dfsg-1.1 libstdc++6 (= 4.1.1) | 4.9.0-10 libtemplateparser4 (= 4:4.12.4-1) | 4:4.12.4-1 Recommends(Version) | Installed ===-+-=== gnupg-agent | 2.0.25-1 gnupg2 | 2.0.25-1 pinentry-qt4| OR
Bug#754257: [kdm] Got back on after dist-upgrade
Package: kdm Version: 4:4.11.9-1 --- Please enter the report below this line. --- I got back on after (most of a) dist-upgrade. This was suggested by a poster elsewhere. The dbus error may or may not have been relevant at all. Might have been generated once and simple viewed again. KDE came up garbled but toggling desktop effects got it back to usability (another report). Other users besides me still cannot login, may be permissions or space problems, will continue to investigate. --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends (Version) | Installed ===-+-=== adduser | 3.113+nmu3 consolekit | 0.4.6-5 debconf (= 0.5) | 1.5.53 OR debconf-2.0 | kde-wallpapers-default | 4:4.12.4-1 kde-workspace-kgreet-plugins (= 4:4.11.9-1) | 4:4.11.9-1 lsb-base(= 3.2-14) | 4.1+Debian13 kde-runtime ( 4:4.10) | 4:4.13.1-1 libc6 (= 2.15) | 2.19-5 libck-connector0 (= 0.2.1) | 0.4.6-5 libdbus-1-3 (= 1.0.2) | 1.8.6-1 libkdecore5 (= 4:4.11) | 4:4.13.1-1 libkdeui5 (= 4:4.11) | 4:4.13.1-1 libkio5 (= 4:4.11) | 4:4.13.1-1 libknewstuff3-4 (= 4:4.11) | 4:4.13.1-1 libkworkspace4abi2 (= 4:4.11.9-1) | 4:4.11.9-1 libpam0g (= 0.99.7.1) | 1.1.8-3 libqimageblitz4(= 1:0.0.4) | 1:0.0.6-4 libqt4-svg (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqt4-xml (= 4:4.5.3) | 4:4.8.6+dfsg-2 libqtcore4 (= 4:4.7.0~beta1) | 4:4.8.6+dfsg-2 libqtgui4 (= 4:4.8.0) | 4:4.8.6+dfsg-2 libstdc++6 (= 4.1.1) | 4.9.0-10 libx11-6| 2:1.6.2-2 libxau6 | 1:1.0.8-1 libxdmcp6 | 1:1.1.1-1 libxtst6| 2:1.2.2-1 Recommends (Version) | Installed ==-+-=== kde-workspace | 4:4.11.9-1 OR x-session-manager | OR x-window-manager | logrotate | 3.8.7-1 xserver-xorg | 1:7.7+7 OR xserver| xterm | 308-1 OR x-terminal-emulator| Suggests(Version) | Installed =-+-=== kde-wallpapers| 4:4.12.4-1 kdepasswd | 4:4.12.4-1 -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/3223709.pSQoBBeUA3@dovidhalevi
Bug#746810: Acknowledgement ([ark] Removing Empty Directories: Incorrect Results)
KDE 4.12 version now on Testing. This bug persists. So maybe should not be on testing yet. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/3923272.uouoHHXkmN@dovidhalevi
Bug#746810: [ark] Removing Empty Directories: Incorrect Results
Package: ark Version: 4:4.12 from unstable Severity: normal --- Please enter the report below this line. --- I use program for editing, trimming zipped file-system data, i.e. for Android ROMs. One such operation involves an undesired directory at the end of several subdirectories. I want to remove that whole tree so I select the head directory, delete. Innermost files removed normally. Delete again, empty directory takes a while to delete--4:4.11 version is immediate. Results: Zip still readable, functional in ark. Zip file is substantially larger than it was. Attempts to use zip to add or replace an item in resulting zip file fail. Downgraded meanwhile. --- System information. --- Architecture: i386 Kernel: Linux 3.14-1-686-pae Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 unstabledebian.qelectrotech.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com 500 precise ppa.launchpad.net 1 experimentalftp.us.debian.org --- Package information. --- Depends (Version) | Installed ===-+-=== kde-runtime ( 4:4.10) | 4:4.12.4-1 libarchive13| 3.1.2-8 libc6 (= 2.4) | libkdecore5 (= 4:4.11) | libkdeui5 (= 4:4.11) | libkfile4 (= 4:4.11) | libkhtml5 (= 4:4.11) | libkio5 (= 4:4.11) | libkonq5abi1 (= 4:4.6.1) | libkparts4 (= 4:4.11) | libkpty4(= 4:4.11) | libqt4-dbus(= 4:4.5.3) | libqtcore4 (= 4:4.7.0~beta1) | libqtgui4 (= 4:4.5.3) | libstdc++6 (= 4.1.1) | Recommends (Version) | Installed =-+-=== bzip2 | 1.0.6-5 p7zip-full| 9.20.1~dfsg.1-4 zip | 3.0-8 unzip | 6.0-12 Suggests(Version) | Installed =-+-=== rar | 2:4.2.0-1 unrar | 1:5.0.10-1 OR unrar-free| -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/3561465.B3vaFhQlCc@dovidhalevi
Re: What happened to rekonq?
On Monday, 02 December, 2013 16:28:32 José Manuel Santamaría Lema wrote: Diederik de Haas didi.deb...@cknow.org Hi! I just found a website that doesn't display properly in iceweasel, so I wanted to try it with rekonq, only to find it's no longer in the archives. What happened and will rekonq return to the archives? Cheers, Diederik Some time ago it was removed - allegedly - for security reasons with regarding to qtwebkit. See: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712808 As you can see in the bug report: * The removal wasn't asked by its current maintainer (me) * I tried to stop the removal, but it was removed anyway Furthermore as I explained here and in the other bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714688#35 There are other browsers which use the qtwebkit (which aren't maintained by me) which weren't removed from debian sid. So I don't buy the it's for security argument. Probably the removal of rekonq has more to do with a group of powerful people trying to make impossible any contribution from me to debian. The same people was responsible (among other things) for the unexplainable disappearing of qt-kde.debian.net several months ago (remember the bunch of mails of people asking how does one install kde 4.10 from experimental?) Also note that I offered myself to package a newer qtwebkit (I have updated it in siduction a few weeks ago) and the reply was: Please refrain from forwarding changes to the pkg-kde team for reasons you are very well aware of. So at this point I have two possible conclusions about that diversity statement[1] which generated some debate in the mailing lists, it's either: a) packaging qtwebkit doesn't count as a contribution which interacts constructively with our community or b) it's the greatest bullshit ever told about debian. I have uploaded it here again a long time ago: http://mentors.debian.net/package/rekonq and made the corresponding RFS (request for sponsoring, the procedure to follow for those who don't have permissions to upload packages to sid). Nobody uploaded it. Also I have been maintaining it in siduction where is up to date. So, if you ask my opinion it's just a shame, but: If you want to use rekonq you can: a) Build it yourself from the mentors package. b) Add to your sources.list the siduction's kdenext repository. c) Switch completely to any debian derivative or just use other distribution. [1]http://www.debian.org/intro/diversity.en.html Just get it from kde-apps.org and compile it. Program has problems but it is quicker than the others. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1991450.us3W49t5Ee@dovidhalevi
Re: Improving user experience KDEconnect and Android
OK, I found all the package components: Service, KCM devices module, plasmoid. Installed kdeconnect on phone. The only thins that seems paired is the computer to itself! Nothing listed on phone app, phone not listed on computer. How do I use this thing? -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1486190.CN8Ry4Zrfj@dovidhalevi
Re: Improving user experience KDEconnect and Android
On Sunday, 17 November, 2013 11:26:21 newbee...@nativobject.net wrote: Le 17/11/2013 10:37, David Baron a écrit : OK, I found all the package components: Service, KCM devices module, plasmoid. Installed kdeconnect on phone. The only thins that seems paired is the computer to itself! Nothing listed on phone app, phone not listed on computer. How do I use this thing? The only constraint, all devices must be on the same local network (same wifi and it works also with the android WIFI connection sharing network)... The pairing is a little bit magic (sometime nothing happen), I don't know really how it detect devices (probably multicast socket or broadcast packet). I manage to control amarok (start-stop-pause) and to share my clipboard between a Galaxy Nexus and a KDE debian laptop ! Regards Mourad How do you get it to pair up? On the same WIFI. What protocols involved? Firewall? -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1952462.iZMCGVf1oh@dovidhalevi
Re: Improving user experience KDEconnect and Android
On Wednesday, 13 November, 2013 14:25:52 newbee...@nativobject.net wrote: Hi, I'm experimenting KDEConnect on android and debian jessie. I manage to install the ubuntu packages and that seems to work well ! Packages are available here http://www.ubuntuupdates.org/package/core/saucy/universe/base/kdeconnect-kde http://www.ubuntuupdates.org/package/core/saucy/universe/base/libkdeconnect 1 And for android you can find it here : https://play.google.com/store/apps/details?id=org.kde.kdeconnect_tphl=fr Is it possible to have some debian native package (in experimental, of course !) ? Installing this. How does on use it? I.e. Start it up, syncing, etc.? -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2150583.t5carD5ojH@dovidhalevi
Re: KMail problems followup
On Sunday, 27 October, 2013 13:02:11 Johannes Zarl wrote: Hi, As I've written before[1,2], kmail2 has been very slow for me. Today, I finally took the time to look into it and I found a workaround. In case anyone else has got the same problem, maybe this will help: Since I had already turned off email-indexing, I somehow thought that nepomuk cannot really to blame. Well, today I realized that my nepomuk database uses 2.8 GB of storage! I have no idea how there could be as much metadata for my files (~280.000) and email (maybe 10.000 mails total). Creating a new nepomuk database (therefore losing any ratings and other metadata I might have entered previously) indeed solved the problem for me: 1. Disable nepomuk completely in control center (kcmshell4 kcm_nepomuk) 2. Kill remaining virtuoso-t processes 3. cd ~/.kde/share/apps/nepomuk/ ; mv repository repository.bak 4. Reenable nepomuk KMail is now as fast as it used to be. I've also reenabled file and email indexing (mostly to see if the problems return). So before you give up on kmail completely, you might want to see if nepomuk is the problem... Cheers, Johannes P.S.: I just realised that there is a program called nepomukcleaner which supposedly cleans up corrupted databases. You might want to try this before removing the database completely. [1] https://lists.debian.org/debian-kde/2013/08/msg9.html [2] https://lists.debian.org/debian-kde/2013/10/msg00012.html I have no real use for nepomuk which has been a plague on KDE. Recoll just works nicely niced in the background, none of the problems. Find my runner for using recoll on kde-apps site. Unfortunately, it is now not possible to search messages within kmail without Nepomuk. Want find in message, find messages, etc., we're stuck with Nepomuk. Even without neomuk, kmail is a mess, however.
Re: KDE 4.11
On Monday, 21 October, 2013 20:07:32 David Baron wrote: On Monday, 21 October, 2013 19:59:27 Edward J. Shornock wrote: * Rubin Abdi ru...@starset.net [21-10-2013 19:31 EEST]: Just inquiring, 4.11 isn't in the sid repo yet, is it? No, but most of it has made it to experimental. Pieces have been in experimental. My normal upgrade got 4.11 and this does not draw from experimental! Sid packages are site listed as 4.10, however. So who knows what happened. I guess no turning back. NOW, packages are shown as experimental, but on that fateful day, they were somehow, not labeled. Also, nothing is labeled as unstable, just testing or experimental. Today things are back to normal so I must tag experimental to complete or further upgrade.
KDE 4.11
On Sid, runs without a hitch. KMail seems better behaved. Great update
Re: KMail2 quirks
On Thursday, 22 August, 2013 20:03:40 Johannes Zarl wrote: Hi, Since the upgrade to kmail2 (the migration went really smooth by the way), kmail shows some quirks on my system: 1) After logging into the desktop session, kmail needs 1-2 minutes until the window appears, and a little while longer until the folders are ready. During that time, the virtuoso-t is quite busy (which may or may not be related). 2) During normal operation, kmail is sometimes slow to display data (e.g. when switching folders, or when pressing reply to all), with a delay of up to several seconds. Other times (gladly most of the time), the speed is as ever. How about you others? Have you had similar experiences? Has anyone got some ideas what might be the problem? Lucky one. Just a little slow. Kmail2 is very flakey.
Re: KMail2 filter's duplicating messages, and other misc issues
Temporarily losing messages until program restart. All those old messages mysteriously once again unread. KMail resource, broken, online until next kde start. Kmail2 is a mess bordering on unusability. Cant search messages without Nepomuk but we all know the mess that is. I use recoll on files without a hitch, no lags. I lived fine with kwallet until now and kmail kept my passwords for me. No more. Might need a different mail program unless our beloved kmail is brought back from the abyss.
Re: akonadi failing to connect to database
My akonadi works ... until it doesn't Had few if any problems with 4.8 4.10 from the beginning, kmail is quite flakey. Messages will sort of dissappear, the number in the folder will show but no message. Until I restart kmail. After a while, mail resources broken, on line. Must restart kde to get off that one.
Re: In the update to 4.10 ...
On Tuesday, 16 July, 2013 13:37:16 David Goodenough wrote: On Tuesday 16 Jul 2013, Sune Vuorela wrote: On 2013-07-16, David Goodenough david.goodeno...@btconnect.com wrote: how many packages are expected to be removed. apt-get is telling me 213, including things like akregator that I use every day. I would say like a handful plus some replacements (like libfoo6abi1 replaced by libfoo6abi2) It might be that the mirror is slightly outdated or that the build network just is catching up. If the error still persist tomorrow, please tell your architecture and exactly what apt is telling you. /Sune This has been going on for a few days now, but I will check again tomorrow. The architecture is x86. If it is still a problem in the morning I will cut and paste the apt-get output and post it here. David I have updated a couple of times from Sid without any problems (once restarted or rebooted). Had the siduction and some experimental packages installed before this, however. Kmail remains flakey.
Re: In the update to 4.10 ...
On Tuesday, 16 July, 2013 16:09:41 David Baron wrote: On Tuesday, 16 July, 2013 13:37:16 David Goodenough wrote: On Tuesday 16 Jul 2013, Sune Vuorela wrote: On 2013-07-16, David Goodenough david.goodeno...@btconnect.com wrote: how many packages are expected to be removed. apt-get is telling me 213, including things like akregator that I use every day. I would say like a handful plus some replacements (like libfoo6abi1 replaced by libfoo6abi2) It might be that the mirror is slightly outdated or that the build network just is catching up. If the error still persist tomorrow, please tell your architecture and exactly what apt is telling you. /Sune This has been going on for a few days now, but I will check again tomorrow. The architecture is x86. If it is still a problem in the morning I will cut and paste the apt-get output and post it here. David I have updated a couple of times from Sid without any problems (once restarted or rebooted). Had the siduction and some experimental packages installed before this, however. Kmail remains flakey. Now that kde4.10 is on Debian Sid, I am, thankfully, rid of the mix, now pure Debian Sid. I mention Siduction because haveing these might have avoided the upgrade problems reported by the original poster.
Re: KMail2
On Thursday, 09 May, 2013 23:51:00 Josep Febrer wrote: On Thursday 09 May 2013 19:00:38 David Baron wrote: I have the new kmail up and running. First questions: How do I import my old filters? Have you exported them before? If so you can reimport them via Settings - Configure filters and there Import - Kmail filters. Found them in their ...rc file in a saved .kde/config. So far, runs nicely except it is always asking for account passwords, no option to remember. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4938206.CGbgIIuLtB@dovidhalevi
KMail2
I have the new kmail up and running. First questions: How do I import my old filters? -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1548424.bU71AqIUUn@dovidhalevi
Shisensho
This very lovely Majong matching game is part of kde games. I have installed the siduction kde4.10 packages. The game on 4.8 took forever to accept, remove matched tiles. On 4.10, in runs beautifully on my login, no lags at all. But on my wife's, its the same old story. Almost unusable. What might be the problem and how to fix. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201304132212.54810.d_ba...@012.net.il
Re: Shisensho
On Saturday, 13 April, 2013 10:40:16 PM Sune Vuorela wrote: On 2013-04-13, David Baron d_ba...@012.net.il wrote: This very lovely Majong matching game is part of kde games. I have installed the siduction kde4.10 packages. for a second time, please take stuff related to siduction off this list. OK. Once our experimental packages are in order, all this siduction thing can simply disappear. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201304132309.26855.d_ba...@012.net.il
Re: KDE SC 4.10
On Thursday, 04 April, 2013 02:08:00 AM José Manuel Santamaría Lema wrote: David Baron d_ba...@012.net.il Up and running, quite nicely My wife's desktop came up, no problem. Mine crashed plasma-desktop. Had to start over, new .kde. Found problem was actually the yaWP weather plasmoid. When I put that back, crashed, so had to do some surgery on plasma-desktop-appletrc to get rid of it. I have updated the KDE packages to 4.10.2 and plasma-widget-yawp to 0.4.5 rebuilt against 4.8. Do you still have the same problem? Question is are the appropriate dev packages up-to-date? I rebuilt 0.4.5 and still crashed. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201304040932.04253.d_ba...@012.net.il
Re: KDE SC 4.10
On Thursday, 04 April, 2013 09:32:04 AM David Baron wrote: On Thursday, 04 April, 2013 02:08:00 AM José Manuel Santamaría Lema wrote: David Baron d_ba...@012.net.il Up and running, quite nicely My wife's desktop came up, no problem. Mine crashed plasma-desktop. Had to start over, new .kde. Found problem was actually the yaWP weather plasmoid. When I put that back, crashed, so had to do some surgery on plasma-desktop-appletrc to get rid of it. I have updated the KDE packages to 4.10.2 and plasma-widget-yawp to 0.4.5 rebuilt against 4.8. Do you still have the same problem? Question is are the appropriate dev packages up-to-date? I rebuilt 0.4.5 and still crashed. All siduction pakages upgraded today, saw -dev packages there as well. Rebuild yaWP 0.4.5 Still crashes. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201304041142.53067.d_ba...@012.net.il
Re: KDE SC 4.10
On Thursday, 04 April, 2013 01:44:08 PM Martin Steigerwald wrote: Am Dienstag, 2. April 2013 schrieb José Manuel Santamaría Lema: Hello Marin, Hi José, Hi! I have browsed some basic packages at git.debian.org and it seems José and others work on KDE SC 4.10. Are any of these already in a testable state? I may be inclined to build some during the free week after the coming week. Anyway, keep up the good work. Thanks, I have switched to siduction[1], this means I will be working providing packages for that project from now on. The packages of debian's git are almost ready but they probably need some few changes (some Breaks/Replaces here and there), I have hacked them a bit and I released them for siduction, While this packages are meant to be included in that distro, I tried to install them in a debian machine and they work, you José, thank you. I am reluctant about switching (partly) to a Debian derivative. I didn´t switch to Ubuntu and seeing the recent stuff happening there I now know why. And while I think end of freeze period times in Debian are sometimes difficult to deal with I am also a bit tired of the ton of Debian derivatives, their renames, closings and reopenings somewhere else and so on and would like a rolling Debian instead :). Debian is a constant for me, it has always been there, since I use it. It may not have been the best in all cases, but at last its still there and rocking. And anyway, there is a way to provide rolling KDE SC in qt-kde.debian.net or wasn´t there? Also I don´t like to ask for feedback regarding any possible installation of your packages on this list, cause, well, the list is called debian-kde not siduction-kde :) [1] It's a rolling release based on debian sid, so no freezes because they are not needed. I agree. I have two (count 'em) experimental snapshot sets of KDE, the KDE4.9 on qt-kde.debian.net/debian and now the 4.10 on packages.siduction.org/kdenext. This is certainly not desirable and probably, the 4.10 shouild be copied or moved to the debian snapshots. Once 4.10 is installed, it is not possible to go back so no need for both. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201304041354.01775.d_ba...@012.net.il
Re: KDE SC 4.10
Up and running, quite nicely My wife's desktop came up, no problem. Mine crashed plasma-desktop. Had to start over, new .kde. Found problem was actually the yaWP weather plasmoid. When I put that back, crashed, so had to do some surgery on plasma-desktop-appletrc to get rid of it. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/0mkp00m9o1wuw...@a-mtaout20.012.net.il
Re: Deebian 7.0 needs to support MTP (for Android), else it will lose relevance
On Wednesday 06 February 2013 19:33:05 Alexey Eromenko wrote: History: USB MTP (universal serial bus - media transfer protocol) was developed to replace the USB Mass Storage. Problem with mass storage is that it is not reliable - it is block-device-level protocol. And if PC goes power down (or blue screen, on certain O.S) the data on the smartphone will be damaged, and there is no scandisk on the smartphone, so it will become unreadable. MTP overcomes this problem by being filesystem level protocol (as opposed to block device), and is supported since Windows hasta-la-Vista. (since 2006) The result: Google decided to remove USB Mass Storage from Android 4.x devices. Newer Android devices support MTP-only. These are excerpted from ~$ locate mtp | grep usr /usr/bin/mtp-albumart /usr/bin/mtp-albums /usr/bin/mtp-connect /usr/bin/mtp-delfile /usr/bin/mtp-detect /usr/bin/mtp-emptyfolders /usr/bin/mtp-files /usr/bin/mtp-filetree /usr/bin/mtp-folders /usr/bin/mtp-format /usr/bin/mtp-getfile /usr/bin/mtp-getplaylist /usr/bin/mtp-hotplug /usr/bin/mtp-newfolder /usr/bin/mtp-newplaylist /usr/bin/mtp-playlists /usr/bin/mtp-reset /usr/bin/mtp-sendfile /usr/bin/mtp-sendtr /usr/bin/mtp-thumb /usr/bin/mtp-tracks /usr/bin/mtp-trexist /usr/bin/mtpfs * * * /usr/share/man/man1/mount.mtpfs.1.gz /usr/share/man/man1/mtp-albumart.1.gz /usr/share/man/man1/mtp-albums.1.gz /usr/share/man/man1/mtp-connect.1.gz /usr/share/man/man1/mtp-delfile.1.gz /usr/share/man/man1/mtp-detect.1.gz /usr/share/man/man1/mtp-emptyfolders.1.gz /usr/share/man/man1/mtp-files.1.gz /usr/share/man/man1/mtp-filetree.1.gz /usr/share/man/man1/mtp-folders.1.gz /usr/share/man/man1/mtp-format.1.gz /usr/share/man/man1/mtp-getfile.1.gz /usr/share/man/man1/mtp-getplaylist.1.gz /usr/share/man/man1/mtp-hotplug.1.gz /usr/share/man/man1/mtp-newfolder.1.gz /usr/share/man/man1/mtp-newplaylist.1.gz /usr/share/man/man1/mtp-playlists.1.gz /usr/share/man/man1/mtp-reset.1.gz /usr/share/man/man1/mtp-sendfile.1.gz /usr/share/man/man1/mtp-sendtr.1.gz /usr/share/man/man1/mtp-thumb.1.gz /usr/share/man/man1/mtp-tools.1.gz /usr/share/man/man1/mtp-tracks.1.gz /usr/share/man/man1/mtp-trexist.1.gz /usr/share/man/man1/mtpfs.1.gz * * * /usr/src/linux-headers-3.2.0-4-686-pae/include/config/bt/cmtp.h /usr/src/linux-headers-3.2.0-4-686-pae/include/config/snd/mtpav.h /usr/src/linux-headers-3.2.0-4-rt-686-pae/include/config/bt/cmtp.h /usr/src/linux-headers-3.2.0-4-rt-686-pae/include/config/snd/mtpav.h These might not all be relevant but I remember installing some mtp stuff a while back!
