Re: It's impossible to install KDE in unstable
On Sat, Mar 02, 2024 at 11:14:33AM +0100, Valerio Passini wrote: > Hello, > > I'm having a lot of troubles to install KDE in unstable, apt tells there > are held packages but I've checked and there are not. > > sudo apt install plasma-desktop > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > kactivitymanagerd : Depends: libqt5sql5 (>= 5.15.2~) but it is not > installable > libkf5plasma5 : Depends: libqt5sql5 (>= 5.15.2~) but it is not installable #1065154 > Recommends: kio-extras but it is not installable This can additionally be caused by kio-extras not rebuilt against libsmbclient0 if you have libsmbclient0 installed. > Is it a known problem? sid is currently broken in general because of the ongoing t64 transitions and problems caused by it. -- WBR, wRAR signature.asc Description: PGP signature
Re: [SOLVED] Re: Any issues with Juk in Bookworm?
On Fri, Jun 17, 2022 at 01:56:33PM +0200, local10 wrote: > Jun 17, 2022, 10:40 by b...@fineby.me.uk: > > > Identical versions here. Sad to say (from your PoV) all works correctly. > > > > What happens if you move the ~/.local/juk directory out of the way? > > It's possible the databases therein have become corrupt. > > > > Beyond that, I have no idea. Sorry. > > > > Deleting the "~/.local/share/juk" directory resolved the issue. All of my > setup is gone but at least Juk can start normally. (hence "move out of the way", not "delete", if you did that you would be able to try finding the exact problem) -- WBR, wRAR signature.asc Description: PGP signature
Re: plasma 5.25
On Fri, Jun 17, 2022 at 01:52:40AM +0200, Diederik de Haas wrote: > > >Yesterday I was able to install Plasma 5.25 from Experimental. All good > > >sofar. > > > > good to know, thanks for the feedback. > > > > There's an ongoing Qt 5 transition so I won't upload to unstable just now to > > avoid it and the Plasma transition stepping onto each other's toes. > > I seem to have run into an issue: Which matches the quote above AFAICS. I guess Luc being able to install it was either an already closed possibility or it worked because of a smaller set of installed packages. > it looks like some/most packages are compiled against > qtdeclarative-abi-5-15-4, but others against qtdeclarative-abi-5-15-2 ? The ones in experimental, including libkpimitinerary5 in your error output, need old Qt but you have new Qt from sid already installed. -- WBR, wRAR signature.asc Description: PGP signature
Re: Akonadi using 100% CPU resources
On Mon, Apr 18, 2022 at 08:41:13PM +0100, piorunz wrote:
> Thank you all,
>
> I was able to uninstall many akonadi packages, including akonadi server,
> and installed back (marked as installed manually) LibreOffice, system
> printing and few other things. Unfortunately akregator which I use
> (sporadically) still requires a few akonadi packages:
> $ dpkg -l | grep akona | awk {print'$2'}
> akonadi-contacts-data
> akonadi-mime-data
> libkf5akonadi-data
> libkf5akonadicontact5:amd64
> libkf5akonadicore5abi2:amd64
> libkf5akonadimime5:amd64
> libkf5akonadiprivate5abi2:amd64
> libkf5akonadiwidgets5abi1:amd64
> libkf5mailtransportakonadi5:amd64
None of these include the actual service. When in doubt you should read
package descriptions, though often package names are enough.
--
WBR, wRAR
signature.asc
Description: PGP signature
Re: Akonadi using 100% CPU resources
On Fri, Apr 15, 2022 at 11:10:55AM +0100, piorunz wrote: > > > > > Yes, totally. Why this abomination cannot be uninstalled without > > > > > pulling > > > > > half of KDE out? > > > > This is definitely not true. > > > > > > > $ sudo apt purge akonadi-server > > [...] > > > The following packages will be REMOVED: > > >akonadi-server* kaddressbook* kde-standard* kdepim-runtime* kmail* > > > knotes* korganizer* task-kde-desktop* > > > 0 upgraded, 0 newly installed, 8 to remove and 1 not upgraded. > > Correct. > > > > > Printing gone. Libreoffice gone. Speech gone. That's what I can see here. > > No, you should learn to read the apt output before drawing conclusions. > > > I probably know what you mean. Thanks. You mean I can install them > manually, and they will stay as manually installed? I mean nothing changes about these packages except for apt now thinking they can be safely removed when the user asks for that, and even that can be changed by marking packages you need with `apt-mark manual`. > So only akonadi-server* kaddressbook* kde-standard* kdepim-runtime* > kmail* knotes* korganizer* task-kde-desktop* will be gone effectively? That's what the command output says. > Shouldn't I have task-kde-desktop installed to track all packages > required by entire KDE? So my Testing system evolves with changing deps? Well, if you want "entire KDE" you want Akonadi. -- WBR, wRAR signature.asc Description: PGP signature
Re: Akonadi using 100% CPU resources
On Fri, Apr 15, 2022 at 11:05:03AM +0100, piorunz wrote: > > > Yes, totally. Why this abomination cannot be uninstalled without pulling > > > half of KDE out? > > This is definitely not true. > > > $ sudo apt purge akonadi-server [...] > The following packages will be REMOVED: > akonadi-server* kaddressbook* kde-standard* kdepim-runtime* kmail* > knotes* korganizer* task-kde-desktop* > 0 upgraded, 0 newly installed, 8 to remove and 1 not upgraded. Correct. > Printing gone. Libreoffice gone. Speech gone. That's what I can see here. No, you should learn to read the apt output before drawing conclusions. -- WBR, wRAR signature.asc Description: PGP signature
Re: Akonadi using 100% CPU resources
On Fri, Apr 15, 2022 at 10:56:28AM +0100, piorunz wrote: > Yes, totally. Why this abomination cannot be uninstalled without pulling > half of KDE out? This is definitely not true. -- WBR, wRAR signature.asc Description: PGP signature
Re: The future of KDE in Debian?
On Mon, Jan 24, 2022 at 11:36:01PM +0100, Marco Valli wrote: > I sent the link to a news that appeared on a reputable, if not > authoritative, site. Phoronix is not that. -- WBR, wRAR signature.asc Description: PGP signature
Re: Bluetooth headset "protocol not available". (Bug#998220)
On Wed, Nov 10, 2021 at 01:07:33PM +0900, Norbert Preining wrote: > I think "someone" should recommend libspa-0.2-bluetooth, maybe pipewire > itself. Note that pulseaudio-module-bluetooth isn't recommended by pulseaudio either. -- WBR, wRAR signature.asc Description: PGP signature
Re: KDE/Plasma/Wayland v5.23 and SDDM delay on reboot/restart
On Sun, Oct 17, 2021 at 08:44:28AM +0200, Sedat Dilek wrote: > To confirm that this is an issue with *** KDE/Plasma + Wayland ***... > I logged into a *** KDE/Plasma + X11 *** session and then rebooted. > There was no 90 seconds delay. I'm always getting 90 seconds delays on reboot and I use X11. -- WBR, wRAR signature.asc Description: PGP signature
Re: Re: Plasma 5.23 25th Annivery Release coming to unstable
On Fri, Oct 15, 2021 at 12:31:55PM +0200, Eric Valette wrote: > > IME it's *rarely* needed. > > Normally aptitude safe-upgrade installs and removes packages as needed. > > I beg to disagree. Here you speak about *aptitude* which is a tool that is > not the plain apt tool itself. You could also say things for dselect, > synaptic, discover... > > With apt-get, you have to use dist-upgrade quite often because as other have > pointed out, you cannot add or remove packages without dist-upgrade. > > Clearly to install libkdecorations2-5v5, you will need apt-get dist-upgrade. > And the libkdecorations2-5v5 that was wrongly put in experimental does break > the unstable version... apt upgrade, as opposed to apt-get upgrade, can install new packages. -- WBR, wRAR signature.asc Description: PGP signature
Re: Plasma 5.21 in Debian Bullseye ?
On Sun, Jun 27, 2021 at 02:27:11PM +, Atlantis wrote: > Hello, i love Debian and KDE ! Thanks you for your work. > > I have a question about Debian 11 Bullseye. > Do you think that the version 5.21 of KDE Plasma will move to Debian Bullseye > ? No, bullseye is frozen since last year. -- WBR, wRAR signature.asc Description: PGP signature
Re: Wohooo! Plasma 5.20 and KF 5.77 coming to unstable
I've just updated (the packages from experimental were installed before) and so far it works perfectly. -- WBR, wRAR signature.asc Description: PGP signature
Re: Upgrade fwupd fwupd-amd64-signed broke plasma-nm (5.19.5-3)
On Tue, Dec 22, 2020 at 08:41:20AM +0100, Héctor Sales Llamas wrote: > Hi, this morning I updated my system (Testing) and when upgrade the > packages fwupd fwupd-amd64-signed, they remove among other packages > this: plasma-nm > (plasma-nm [4:5.19.5-3]) > > My question someone knows why ? Because you allowed that. plasma-nm Depends on libopenconnect5 which Depends on libtss2-esys0 in testing but the new fwupd Depends on libtss2-esys-3.0.2-0. libopenconnect5 that Depends on libtss2-esys-3.0.2-0 can't currently migrate: https://qa.debian.org/excuses.php?package=openconnect So your `apt full-upgrade` proposed removing it and you agreed. -- WBR, wRAR signature.asc Description: PGP signature
Re: KDE Plasma LTS for Debian stable
On Thu, Dec 10, 2020 at 12:12:53PM -0500, Joe McEntire wrote: > > On Thursday, December 10, 2020 11:08:59 AM EST you wrote: > > On Thu, Dec 10, 2020 at 07:20:18PM +0330, peylight wrote: > > > Hi Andy, > > > You are talking about freeze timeline and policies. > > > Please look at this document for that: > > > https://release.debian.org/buster/freeze_policy.html > > > The time and date is defined and any programmer can planning for it. > > > I check the LTS versions of KDE and what can i see Debian choose is v5.14, > > > that is not the LTS version. > > > How ever Debian could choose v5.12 LTS or even v5.8 LTS for bug fixes and > > > security issues. > > > I think Debian should be change the approach for more KDE Desktop > > > stability > > > as for the kernel has taken this approach. > > > > If Debian keeps years-old KDE in unstable I'll stop using it, tbh. > > I don't know where this information is coming from This suggestion comes from the email I was replying to. -- WBR, wRAR signature.asc Description: PGP signature
Re: KDE Plasma LTS for Debian stable
On Thu, Dec 10, 2020 at 07:20:18PM +0330, peylight wrote: > Hi Andy, > You are talking about freeze timeline and policies. > Please look at this document for that: > https://release.debian.org/buster/freeze_policy.html > The time and date is defined and any programmer can planning for it. > I check the LTS versions of KDE and what can i see Debian choose is v5.14, > that is not the LTS version. > How ever Debian could choose v5.12 LTS or even v5.8 LTS for bug fixes and > security issues. > I think Debian should be change the approach for more KDE Desktop stability > as for the kernel has taken this approach. If Debian keeps years-old KDE in unstable I'll stop using it, tbh. -- WBR, wRAR signature.asc Description: PGP signature
Re: Understanding apt-autoremovable KDE packages
On Sat, Jun 20, 2020 at 11:18:53AM +0200, Sedat Dilek wrote: > I can NOT follow this removal suggestions. > > Both kmag and kmousetool work in my environment. You may be misunderstanding what does autoremove do. It's simply removes packages that are not marked as installed manually and are not dependencies of other installed packages. It doesn't mean those packages don't work or are useless. -- WBR, wRAR signature.asc Description: PGP signature
Re: Removing and reinstalling all KDE packages
On Mon, May 18, 2020 at 11:05:02PM -0700, Marco Paolieri wrote: > Is there a different way I should remove the libkf5ldap5 package? Try dpkg -r. Though if something depends on it, and it probably does, you'll need either ask dpkg to ignore deps, or remove all deps too. > On Mon, May 18, 2020 at 11:03 PM Marco Paolieri wrote: > > > Thank you very much for the suggestion... What I get is: > > > > $ LANG=C sudo apt-get remove libkf5ldap5 > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > You might want to run 'apt --fix-broken install' to correct these. > > The following packages have unmet dependencies: > > accountwizard : Depends: libkf5pimcommon5-19.08 > > Depends: libkf5pimcommon5abi2 (>= 4:19.08.3) but it is not > > going to be installed > > akonadiconsole : Depends: libkf5akonadisearchcore5 (>= 4:19.08.3) but > > 4:17.12.3-1 is to be installed > > ... > > E: Unmet dependencies. Try 'apt --fix-broken install' with no packages > > (or specify a solution). > > > > $ LANG=C sudo apt --fix-broken install > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > Correcting dependencies... Done > > The following additional packages will be installed: > > kaddressbook kde-standard kdepim-addons kdepim-themeeditors kdiff3 > > kf5-kdepim-apps-libs-data kgpg kmail libkf5akonadisearch-bin > > libkf5akonadisearch-plugins libkf5akonadisearchcore5 > > libkf5akonadisearchxapian5 libkf5akonadixml5 libkf5alarmcalendar-data > > libkf5alarmcalendar5abi1 libkf5eventviews5abi1 libkf5followupreminder5 > > libkf5gravatar5abi2 libkf5imap-data > > libkf5incidenceeditor-data libkf5kaddressbookimportexport5 > > libkf5ldap-data libkf5mailcommon-data libkf5mailcommon5abi2 > > libkf5mailimporter5 libkf5mailimporterakonadi5 > > libkf5messagecomposer5abi1 libkf5messagecore5abi1 libkf5messagelist5abi1 > > libkf5messageviewer5abi1 libkf5mimetreeparser5abi1 libkf5pimcommon-data > > libkf5pimcommon5abi2 > > libkf5pimcommonakonadi5abi1 libkf5sendlater5 libkf5syndication5abi1 > > libkf5templateparser5 libkf5tnef5 libkf5webengineviewer5abi1 > > libkpimgapi-data libkpimgapicore5abi1 > > libkpimimportwizard5 libkpimitinerary-data libkpimitinerary5 > > libkpimkdav-data libkpimkdav5abi2 libkpimpkpass5 libkpimsmtp5abi1 > > libphonenumber7 libprotobuf22 libqt5networkauth5 > > libreoffice-kde5 libreoffice-kf5 libreoffice-plasma libreoffice-qt5 > > libsasl2-modules-kdexoauth2 mbox-importer mysql-server-5.7 > > pim-data-exporter pim-sieve-editor qtgstreamer-plugins-qt5 > > task-desktop task-italian task-italian-desktop task-italian-kde-desktop > > task-kde-desktop task-ssh-server tasksel tasksel-data > > Suggested packages: > > skanlite kopete clamav procmail spamassassin | bogofilter | spambayes | > > bsfilter | crm114 tinyca > > Recommended packages: > > fonts-symbola kde-l10n-it orca libreoffice libreoffice-help-en-us > > The following packages will be REMOVED: > > libkfilemetadata4 libkjsapi4 libkjsembed4 libkldap4 libkmime4 > > libknewstuff2-4 libknotifyconfig4 libkntlm4 libkpimgapicore5 > > libkpimkdav5abi1 libkpty4 libkresources4 libkrosscore4 > > libnepomuk4 libnepomukquery4a libntrack-qt4-1 libphonon4 libpolkit-qt-1-1 > > libqca2 libqca2-plugins libqimageblitz4 libqjson0 libqt4-dbus > > libqt4-declarative libqt4-designer libqt4-network > > libqt4-opengl libqt4-qt3support libqt4-script libqt4-sql > > libqt4-sql-sqlite libqt4-svg libqt4-xml libqt4-xmlpatterns libqtdbus4 > > libqtgui4 libqtwebkit4 libsolid4 libsoprano4 > > libthreadweaver4 phonon phonon-backend-vlc qdbus qt-at-spi soprano-daemon > > The following NEW packages will be installed: > > kaddressbook kde-standard kdepim-addons kdepim-themeeditors kmail > > libkf5alarmcalendar-data libkf5alarmcalendar5abi1 libkf5eventviews5abi1 > > libkf5followupreminder5 libkf5gravatar5abi2 > > libkf5imap-data libkf5ldap-data libkf5mailcommon5abi2 > > libkf5messagecomposer5abi1 libkf5messagecore5abi1 libkf5messagelist5abi1 > > libkf5messageviewer5abi1 libkf5mimetreeparser5abi1 > > libkf5pimcommon5abi2 libkf5pimcommonakonadi5abi1 libkf5sendlater5 > > libkf5syndication5abi1 libkf5templateparser5 libkf5tnef5 > > libkf5webengineviewer5abi1 libkpimgapicore5abi1 > > libkpimimportwizard5 libkpimitinerary-data libkpimitinerary5 > > libkpimkdav5abi2 libkpimpkpass5 libkpimsmtp5abi1 libphonenumber7 > > libprotobuf22 libqt5networkauth5 libreoffice-kde5 > > libreoffice-kf5 libreoffice-plasma libreoffice-qt5 > > libsasl2-modules-kdexoauth2 mbox-importer pim-data-exporter > > qtgstreamer-plugins-qt5 > > The following packages will be upgraded: > > kdiff3 kf5-kdepim-apps-libs-data kgpg libkf5akonadisearch-bin > > libkf5akonadisearch-plugins libkf5akonadisearchcore5 > > libkf5akonadisearchxapian5 libkf5akonadixml5 > > libkf5incidenceeditor-data libkf5kaddressbookimportexport5 > > libkf5mailcommon-data libkf5mailimporter5 libkf5mailimporterakonadi5 > > libkf5pimcommon-data libkpim
Re: Removing and reinstalling all KDE packages
On Mon, May 18, 2020 at 05:18:54PM -0700, Marco Paolieri wrote: > dpkg: errore nell'elaborare l'archivio > /var/cache/apt/archives/libkf5ldap-data_19.08.3-1_all.deb (--unpack): > tentata sovrascrittura di "/usr/share/locale/ar/LC_MESSAGES/libkldap5.mo" > presente anche nel pacchetto libkf5ldap5:amd64 17.12.3-1 Remove libkf5ldap5 and try again. Also, when you are asking for help, consider running your commands with LANG=C to privde logs in English. -- WBR, wRAR signature.asc Description: PGP signature
Re: Okular slow search in PDF contents
On Wed, May 13, 2020 at 10:13:16AM +0200, Frank Mehnert wrote: > Try this manual instead: > > https://developer.arm.com/docs/ddi0487/latest/arm-architecture-reference-manual-armv8-for-armv8-a-architecture-profile https://static.docs.arm.com/ddi0487/fb/DDI0487F_b_armv8_arm.pdf is the direct link to the doc. > Go to the Contents search bar and enter > > esr > > With okular 4:20.04.0-1 it takes more than 20 seconds on my Skylake > T470p (24GB RAM) until the search bar is responsible again and the 4 > entries are found. 26s to get the results. For the first 11s only the "e" letter is displayed in the input box. The okular process used 100% of one core the whole time I think. i5-7400, 4:20.04.0-1 -- WBR, wRAR signature.asc Description: PGP signature
Re: digiKam 6.4.0
On Mon, Feb 17, 2020 at 12:05:01PM +0100, Luigi Toscano wrote: > Also, please note that they have been kept around after digikam totally > dropped them just for compatibility purpose, but they are basically replaced > by the Purpose framework also in the other projects. See also: > > https://mail.kde.org/pipermail/release-team/2019-April/011316.html > https://phabricator.kde.org/T10525 Thank you, this answers my question from the previous email. -- WBR, wRAR signature.asc Description: PGP signature
Re: digiKam 6.4.0
On Mon, Feb 17, 2020 at 10:55:27AM +, Brad Rogers wrote: > You don't need kipi-plugins any more, also, kipi-plugins-common can go, > too. In fact, upgrading (here, at least) required its removal. A log > out and back in and all the export options still exist. Do you mean one should install digikam instead of kipi-plugins now if they need export from KDE apps? -- WBR, wRAR signature.asc Description: PGP signature
Re: digiKam 6.4.0
On Mon, Feb 17, 2020 at 11:30:12AM +0100, Michal BULIK wrote: > > 6.4.0 has entered testing. What about kipi-plugins ? Has it disappeared ? > Or has it been replaced by something else ? Separate kipi-plugins 4:19.12.2-1 source package is in NEW. -- WBR, wRAR signature.asc Description: PGP signature
Re: phonon-backend-gstreamer-common has been kept back
On Wed, Nov 13, 2019 at 12:01:51AM +0100, Diederik de Haas wrote:
> I don't know if "Debian Package Tracker" is a Web Shortcuts which is part of
> a
> normal installation or if I have added it manually myself.
> The "Shortcut URL:" is "https://tracker.debian.org/pkg/\{@}";
>
> Using that, you can easily select each package name and then look it up in
> "tracker.debian.org" and see what the status is. If you see "Removed
>
> from unstable" and/or " REMOVED from testing", then you should get
> rid of it in most cases.
Just use apt-show-versions, filtering by "No available version in archive".
--
WBR, wRAR
signature.asc
Description: PGP signature
Re: Some information about the removal of Qt 4 and remaining KDE SC 4.14
On Mon, Aug 26, 2019 at 09:19:49AM +0200, Martin Steigerwald wrote: > Also most of the stuff above is RM'd from Debian archive already and *won't* > receive any security updates from now on anymore. As usual, you can find such packages with $ apt-show-versions | fgrep 'No available' -- WBR, wRAR signature.asc Description: PGP signature
Re: bug reports / powerdevil/upower
On Mon, Jul 01, 2019 at 01:42:36PM +0200, Xavier Brochard wrote: > In your case, libssl has nothing to do with powerdevil ; libssl is for > securing network communications It definitely *does* have something to do with powerdevil, please read the bug report, the part about upowerd failing to start. -- WBR, wRAR signature.asc Description: PGP signature
Re: digiKam 6.0.0
On Fri, Mar 01, 2019 at 11:33:08AM +0100, Dietz Proepper wrote: > Hi, > > a humble question - digiKam 6.0.0 is out some weeks now. Are there plans to > package it? We are currently frozen, by the way. -- WBR, wRAR signature.asc Description: PGP signature
Re: Buster: Has anyone been able to run an app as root in KDE?
On Wed, Oct 03, 2018 at 08:56:51AM +0200, local10 wrote: > Now when I try to run Kwrite as root (just for test purposes) it no longer > hangs but immediately fails with the following error message: > > KDEInit could not launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu' Install kde-cli-tools. -- WBR, wRAR signature.asc Description: PGP signature
Re: systemctl restart sddm
On Mon, Jul 23, 2018 at 01:33:46AM +0200, inkbottle wrote: > No I was rather meaning, where, during the boot process, it is invoked. It is a service so it is invoked by the init system. -- WBR, wRAR signature.asc Description: PGP signature
Re: systemctl restart sddm
On Sun, Jul 22, 2018 at 11:42:32PM +0200, inkbottle wrote: > As some of you already know, since *completely uneventful* upgrade of Friday, > July 20, 2018, "sddm" does not start automatically anymore, whether because > something goes wrong at some point or because it doesn't start at all, > meaning > it is not even invoked in the first place, that I know not ;) > > Anyway, I'm not so unfortunate, because "startx", invoked as simple user in a > "tty" is working fine, and it is my workaround for the present, and will be > until I can find enough time to deal with it properly, and not simply trying > to worsen the situation. > > So, in my to-do list, first thing is: why should "sddm" start, at all, at > boot > time? Are you asking what is the purpose of sddm? -- WBR, wRAR signature.asc Description: PGP signature
Re: Update removal package
On Fri, Jun 29, 2018 at 03:11:17PM +0200, Luigi Toscano wrote: > > plasma-netbook (4:4.11.22-3) > PS. Regardless of any update, you can remove plasma-netbook: it's an old > package and not used anymore. It's also not in the archive and I find useful to run apt-show-versions |fgrep avail from time to time to find such packages (aptitude and synaptic have similar filters built in, I think).. -- WBR, wRAR signature.asc Description: PGP signature
Re: Switch User Broken
On Mon, Jun 11, 2018 at 04:55:36PM +0200, Klaus Becker wrote: > I use > > alias switch-user='dm-tool switch-to-greeter' > > In ~/.bashrc. > > But I cannot find the package I installed for 'dm-tool switch-to-greeter' lightdm Are you using it instead of sddm? -- WBR, wRAR signature.asc Description: PGP signature
Re: okular "cannot find latex executable"
On Wed, Apr 18, 2018 at 04:07:21AM +0200, inkbottle wrote: > But then, what happens for me, even though I've installed the "suggested" > texlive-binaries, and rebooted in between, is that I get a message saying > "cannot find latex executable". Well, texlive-binaries doesn't install latex. You probably need texlive-latex-base. -- WBR, wRAR signature.asc Description: PGP signature
Re: Amarok disappeared from testing. Wait or install from stable or unstable?
On Sun, Oct 22, 2017 at 05:52:18PM -0400, Robert van den Berg wrote: > Amarok stopped working (it would load, but wouldn't play anything anymore) > for > me under testing after a complex update. I tried to remove and reinstall > Amarok, only to find that Amarok is currently not present in testing. > > I was wondering if I'm better of to wait for the unstable version to arrive > in > testing. The version currently present in unstable will never migrate. The only way for Amarok to return into testing is someone packaging the Qt5 version which at this point is not even guaranteed. > Alternatives are to install it from unstable or from stable. However, I'm not > sure if I'll run into dependency issues. You may try to install it but it's only a temporary solution even if it will work. Qt4 will soon be dropped. -- WBR, wRAR signature.asc Description: PGP signature
Re: Problems with keyboard after upgrade to Plasma >5.6
On Sat, Sep 16, 2017 at 10:30:14AM -0300, Claudio Ferreira wrote: > I'm a old user of kde and unstable debian and I was a happy user until kde > 5.8. > > Since the upgrade to 5.8 and beyond, my keyboard works "slow". A example: > when I press Alt+F2, and shows the runner, I type any thing and not > happens. Some time ago, appears one or other letter typed. I started having such problems from time to time recently. I have not tried debugging that (apart from changing the keyboard batteries to fresh ones which didn't help). -- WBR, wRAR signature.asc Description: PGP signature
Re: libblockdev-part2
On Thu, Aug 31, 2017 at 06:23:43PM -0700, Jimmy Johnson wrote: > > > As you can probably see, I'm trying to figure what is stopping > > > libblockdev-part2 from being upgraded.. > > But it's clear: > > > > The following packages have unmet dependencies: > > libblockdev-part2 : Depends: sgdisk (>= 0.8.6) but it is not installable > It some how became upgradable by it's self? No, it was updated. -- WBR, wRAR signature.asc Description: PGP signature
Re: libblockdev-part2
On Thu, Aug 31, 2017 at 10:25:23AM -0700, Jimmy Johnson wrote: > As you can probably see, I'm trying to figure what is stopping > libblockdev-part2 from being upgraded.. But it's clear: The following packages have unmet dependencies: libblockdev-part2 : Depends: sgdisk (>= 0.8.6) but it is not installable -- WBR, wRAR signature.asc Description: PGP signature
Re: libblockdev-part2
On Thu, Aug 31, 2017 at 09:57:50AM -0700, Jimmy Johnson wrote: > > > libblockdev-part2 requires libparted2-v3.1 > > It doesn' > > Depends: libblockdev-part-err2, libblockdev-utils2, libc6 (>= 2.4), > > libglib2.0-0 (>= 2.42.2), libparted2 (>= 3.1) > > Current libparted2 is >(3.2) and as both you and I see it requires (3.1) > What am I not understanding here? That ">=" means "greater or equal". -- WBR, wRAR signature.asc Description: PGP signature
Re: libblockdev-part2
On Thu, Aug 31, 2017 at 09:04:28AM -0700, Jimmy Johnson wrote: > libblockdev-part2 requires libparted2-v3.1 It doesn't. Depends: libblockdev-part-err2, libblockdev-utils2, libc6 (>= 2.4), libglib2.0-0 (>= 2.42.2), libparted2 (>= 3.1) -- WBR, wRAR signature.asc Description: PGP signature
Re: Warning! Current udisks2 in Sid is broken
On Wed, Aug 30, 2017 at 07:52:06PM +0500, Andrey Rahmatullin wrote: > On Wed, Aug 30, 2017 at 07:48:52AM -0700, Jimmy Johnson wrote: > > > > > > No, it's not fixed, current dist-upgrade orphans gdisk and plasma > > > > > > will not > > > > > > start. > > > > > But are you sure you have udisks2 2.7.2-2? > > > > No, I have Sid version udisks2 2.7.2-1, why would I have a higher > > > > version? > > > Because the bug is present in 2.7.2-1 and fixed in 2.7.2-2, and you > > > commented on the message about the uploaded fix. > > I see, but the higher version is not in the repos, so it's not fixed!?! > It is fixed, but not in repos yet. It's now available, at least on my mirror. -- WBR, wRAR signature.asc Description: PGP signature
Re: Warning! Current udisks2 in Sid is broken
On Wed, Aug 30, 2017 at 07:48:52AM -0700, Jimmy Johnson wrote: > > > > > No, it's not fixed, current dist-upgrade orphans gdisk and plasma > > > > > will not > > > > > start. > > > > But are you sure you have udisks2 2.7.2-2? > > > No, I have Sid version udisks2 2.7.2-1, why would I have a higher version? > > Because the bug is present in 2.7.2-1 and fixed in 2.7.2-2, and you > > commented on the message about the uploaded fix. > I see, but the higher version is not in the repos, so it's not fixed!?! It is fixed, but not in repos yet. -- WBR, wRAR signature.asc Description: PGP signature
Re: Warning! Current udisks2 in Sid is broken
On Wed, Aug 30, 2017 at 07:41:59AM -0700, Jimmy Johnson wrote: > > > No, it's not fixed, current dist-upgrade orphans gdisk and plasma will not > > > start. > > But are you sure you have udisks2 2.7.2-2? > No, I have Sid version udisks2 2.7.2-1, why would I have a higher version? Because the bug is present in 2.7.2-1 and fixed in 2.7.2-2, and you commented on the message about the uploaded fix. -- WBR, wRAR signature.asc Description: PGP signature
Re: Warning! Current udisks2 in Sid is broken
On Wed, Aug 30, 2017 at 06:56:09AM -0700, Jimmy Johnson wrote: > No, it's not fixed, current dist-upgrade orphans gdisk and plasma will not > start. But are you sure you have udisks2 2.7.2-2? -- WBR, wRAR signature.asc Description: PGP signature
Re: udisks2 upgrade brakes plasma
On Wed, Aug 30, 2017 at 10:06:03AM +0200, Martin Steigerwald wrote: > > > > > do not upgrade to udisk2 2.7.2 > > > > > > > > > > It breaks plasma > > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873627 > > > > > > > > As the bug is RC it is enough to install apt-listbugs. > > > > > > It wasn´t initially. > > > > But it was when this warning was sent. > > Mind you, I don´t check the status of the bug report *every* minute. It was a > window of about maybe 5 minutes between I experienced issue and sent the > warning. > > And even it is was, my warning doesn´t hurt any one, or does it? I was not commenting on *your* warning. -- WBR, wRAR signature.asc Description: PGP signature
Re: udisks2 upgrade brakes plasma
On Wed, Aug 30, 2017 at 09:33:04AM +0200, Martin Steigerwald wrote: > > > do not upgrade to udisk2 2.7.2 > > > > > > It breaks plasma > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873627 > > > > As the bug is RC it is enough to install apt-listbugs. > > It wasn´t initially. But it was when this warning was sent. -- WBR, wRAR signature.asc Description: PGP signature
Re: Warning! Current udisks2 in Sid is broken
On Wed, Aug 30, 2017 at 09:07:05AM +0200, Martin Steigerwald wrote: > Hello. > > Put the package on hold. > > I wonder why this bug wasn´t set to a severity that makes it show up in apt- > listchanges. ITYM apt-listbugs. And it *is* currently set to grave, though it wasn't when the bug report was filed. -- WBR, wRAR signature.asc Description: PGP signature
Re: udisks2 upgrade brakes plasma
On Wed, Aug 30, 2017 at 08:44:15AM +0200, Libor Klepáč wrote: > Hi, > do not upgrade to udisk2 2.7.2 > > It breaks plasma > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873627 As the bug is RC it is enough to install apt-listbugs. -- WBR, wRAR signature.asc Description: PGP signature
Re: plasma-discover-updater not available in stretch but available in sid
On Sun, Feb 19, 2017 at 11:26:42PM +0200, Nikolaos Pantazis wrote: > Hi, > I run stretch. I have no system tray update notifier in kde plasma. bug > #797886 told me to install plasma-discover-updater witch is not available > in stretch but is available in sid. It's not available in sid either (if you don't count obsolete packages in kfreebsd-*). From the 5.7.0-2 changelog: "Drop plasma-discover-updater, no longer needed". -- WBR, wRAR signature.asc Description: PGP signature
Re: konsole --version crashes
On Thu, Dec 29, 2016 at 11:59:07AM +0500, Andrey Rahmatullin wrote: > On Thu, Dec 29, 2016 at 01:52:20AM -0500, kamaraju kusumanchi wrote: > > Is the above link up to date? I ask because > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Debian > > says that there are -dbg packages that I should install to get > > backtrace. But I do not see any packages such as konsole-dbg or > > libqt5dbus5-dbg in the archive. > They are now konsole-dbgsym and libqt5dbus5-dbgsym. For other packages the > names may differ. You also need to enable the debug repo, see https://wiki.debian.org/AutomaticDebugPackages -- WBR, wRAR signature.asc Description: PGP signature
Re: konsole --version crashes
On Thu, Dec 29, 2016 at 01:52:20AM -0500, kamaraju kusumanchi wrote: > Is the above link up to date? I ask because > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Debian > says that there are -dbg packages that I should install to get > backtrace. But I do not see any packages such as konsole-dbg or > libqt5dbus5-dbg in the archive. They are now konsole-dbgsym and libqt5dbus5-dbgsym. For other packages the names may differ. -- WBR, wRAR signature.asc Description: PGP signature
Re: konsole --version crashes
On Wed, Dec 28, 2016 at 03:18:56PM -0500, kamaraju kusumanchi wrote: > Thanks Andrey and solitone. I guess I am the chosen one ;) Any ideas > how to narrow down the problem? Debug the crash. -- WBR, wRAR signature.asc Description: PGP signature
Re: konsole --version crashes
On Wed, Dec 28, 2016 at 12:05:43PM -0500, kamaraju kusumanchi wrote: > Can someone reproduce the problem in testing and/or know how to fix it? Works for me on testing. -- WBR, wRAR signature.asc Description: PGP signature
Re: KDE Frameworks 5.28.0
On Sun, Nov 20, 2016 at 10:28:29AM +0100, Luc Castermans wrote: > > > > 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! > > It's the same as `apt upgrade`. > in contrast to ¨ aptitude dist-upgrade; which will upgrade all No, there is `aptitude full-upgrade` which is the same as `apt dist-upgrade`. -- WBR, wRAR signature.asc Description: PGP signature
Re: KDE Frameworks 5.28.0
On Sun, Nov 20, 2016 at 11:11:12AM +0200, David Baron wrote: > > 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! It's the same as `apt upgrade`. -- WBR, wRAR signature.asc Description: PGP signature
Re: use apt-listbugs (was: Re: Some problems with the last updates)
On Sun, Nov 06, 2016 at 12:32:56AM +0100, Martin Steigerwald wrote: > One tip for such cases: > > Use apt-listbugs. This wouldn't help, of course, as there was no bug. -- WBR, wRAR signature.asc Description: PGP signature
Re: Some problems with the last updates
On Sat, Nov 05, 2016 at 01:56:38PM +0100, Diederik de Haas wrote: > Did you do 'apt-get dist-upgrade'? > 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 I can confirm downgrading qt5 to testing solves the problem. -- WBR, wRAR signature.asc Description: PGP signature
Re: Some problems with the last updates
On Sat, Nov 05, 2016 at 01:56:38PM +0100, Diederik de Haas wrote: > On zaterdag 5 november 2016 09:08:36 CET Valerio Passini wrote: > > 2 - My plasma session is damaged. Don't know exactly what it's missing but > > plasmashell crashes on login leaving a black screen and the applications > > launched in the previous session (luckily konsole). > > Please, can you tell me some fixes? > > Did you do 'apt-get dist-upgrade'? > 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 I wonder if rebuilding some packages locally is easier than downgrading a lot of packages? If yes, which ones? -- WBR, wRAR signature.asc Description: PGP signature
Re: Some problems with the last updates
On Sat, Nov 05, 2016 at 03:37:02PM +0500, Andrey Rahmatullin wrote: > > > 2 - My plasma session is damaged. Don't know exactly what it's missing but > > > plasmashell crashes on login leaving a black screen and the applications > > > launched in the previous session (luckily konsole). > > > Please, can you tell me some fixes? > > Same here unfortunately. > > (gdb) bt > #0 0x72ff5f37 in QObject::setProperty(char const*, QVariant const&) > (this=0x0, name=name@entry=0x7fff3010b468 "initialPositionSet", value=...) at > kernel/qobject.cpp:3848 > #1 0x7fff301053ad in NotificationsHelper::addNotificationPopup(QObject*) > (this=0x1654af0, win=) at > ./applets/notifications/plugin/notificationshelper.cpp:81 > #2 0x7fff3010b044 in NotificationsHelper::qt_static_metacall(QObject*, > QMetaObject::Call, int, void**) (_o=_o@entry=0x1654af0, > _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=6, > _a=_a@entry=0x7fff4c20) > at > ./obj-x86_64-linux-gnu/applets/notifications/plugin/moc_notificationshelper.cpp:155 Looks like https://phabricator.kde.org/D3051 And I indeed have 20 or so errors regarding loading various QML files before the crash. -- WBR, wRAR signature.asc Description: PGP signature
Re: Some problems with the last updates
On Sat, Nov 05, 2016 at 03:32:19PM +0500, Andrey Rahmatullin wrote: > On Sat, Nov 05, 2016 at 09:08:36AM +0100, Valerio Passini wrote: > > 2 - My plasma session is damaged. Don't know exactly what it's missing but > > plasmashell crashes on login leaving a black screen and the applications > > launched in the previous session (luckily konsole). > > Please, can you tell me some fixes? > Same here unfortunately. (gdb) bt #0 0x72ff5f37 in QObject::setProperty(char const*, QVariant const&) (this=0x0, name=name@entry=0x7fff3010b468 "initialPositionSet", value=...) at kernel/qobject.cpp:3848 #1 0x7fff301053ad in NotificationsHelper::addNotificationPopup(QObject*) (this=0x1654af0, win=) at ./applets/notifications/plugin/notificationshelper.cpp:81 #2 0x7fff3010b044 in NotificationsHelper::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=_o@entry=0x1654af0, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=6, _a=_a@entry=0x7fff4c20) at ./obj-x86_64-linux-gnu/applets/notifications/plugin/moc_notificationshelper.cpp:155 #3 0x7fff3010b2c8 in NotificationsHelper::qt_metacall(QMetaObject::Call, int, void**) (this=0x1654af0, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0x7fff4c20) at ./obj-x86_64-linux-gnu/applets/notifications/plugin/moc_notificationshelper.cpp:220 #4 0x7563d519 in QQmlObjectOrGadget::metacall(QMetaObject::Call, int, void**) const (this=this@entry=0x7fff4fc0, type=type@entry=QMetaObject::InvokeMetaMethod, index=, index@entry=11, argv=) at qml/qqmlpropertycache.cpp:1547 #5 0x755cc0f4 in CallMethod(QQmlObjectOrGadget const&, int, int, int, int*, QV4::ExecutionEngine*, QV4::CallData*) (object=..., index=, returnType=returnType@entry=43, argCount=, argTypes=, engine=engine@entry=0x852930, callArgs=) at jsruntime/qv4qobjectwrapper.cpp:1137 #6 0x755cd1c8 in CallPrecise(QQmlObjectOrGadget const&, QQmlPropertyData const&, QV4::ExecutionEngine*, QV4::CallData*) (object=..., data=..., engine=engine@entry=0x852930, callArgs=callArgs@entry=0x7fffd3000558) at jsruntime/qv4qobjectwrapper.cpp:1388 #7 0x755cda65 in QV4::QObjectMethod::callInternal(QV4::CallData*) const (this=, callData=) at jsruntime/qv4qobjectwrapper.cpp:1871 #8 0x755e31c1 in QV4::Runtime::callProperty(QV4::ExecutionEngine*, int, QV4::CallData*) (d=0x7fffd3000558, this=) at jsruntime/qv4object_p.h:332 #9 0x755e31c1 in QV4::Runtime::callProperty(QV4::ExecutionEngine*, int, QV4::CallData*) (engine=0x852930, nameIndex=, callData=0x7fffd3000558) at jsruntime/qv4runtime.cpp:1030 #10 0x7fff300fed32 in () #11 0x0001 in () #12 0x77dea6b4 in _dl_name_match_p (name=0x7fff5200 "H\004", name@entry=0x7fffeeb40090 "libicudata.so.57", map=map@entry=0x7fffd30004c8) at dl-misc.c:295 #13 0x77de2429 in _dl_map_object (loader=0x7fffd3000598, name=0x7fffeeb40090 "libicudata.so.57", type=32767, trace_mode=-754973624, mode=0, nsid=0) at dl-load.c:2186 #14 0x0001000100010001 in () #15 0x0001000100010001 in () #16 0x0001000100010001 in () #17 0x0001000100010001 in () #18 0x0001000100010001 in () #19 0x0001000100010001 in () #20 0x0001000100010001 in () #21 0x000100010001 in () #22 0x77de7caf in _dl_map_object_deps (map=, preloads=, npreloads=, trace_mode=, open_mode=) at dl-deps.c:611 -- WBR, wRAR signature.asc Description: PGP signature
Re: Some problems with the last updates
On Sat, Nov 05, 2016 at 09:08:36AM +0100, Valerio Passini wrote: > 2 - My plasma session is damaged. Don't know exactly what it's missing but > plasmashell crashes on login leaving a black screen and the applications > launched in the previous session (luckily konsole). > Please, can you tell me some fixes? Same here unfortunately. -- WBR, wRAR signature.asc Description: PGP signature
Re: HIDPI insanity
On Wed, Sep 21, 2016 at 09:38:47AM +0200, Thom Castermans wrote: > This changed at some point - I think when Plasma 5.6 rolled around, but not > exactly sure. Anyway, what I did was switching my scaling (System Settings > > > Display and Monitor > Display Configuration > Scale Display) back to 1, so > not > scaling up. On the other hand I set my font DPI (System Settings > Font > > Fonts > > Force fonts DPI) to 96 (after ticking the box of course). Since that > version > of Plasma, all interfaces appear to scale nicely in response to this. > Firefox > and Chrome apparently respect that setting too (although I may have played > around a bit with settings there, cannot remember). I couldn't get Chrome to behave sanely on my 13" 1920x1080 laptop without setting scaling globally. I don't want that scaling because everything else except Chrome is OK. The preinstalled Win10 has global scaling set to 1.5 though. -- WBR, wRAR signature.asc Description: PGP signature
Re: spectacle and online services
On Fri, Sep 02, 2016 at 06:42:04PM +0200, trinques laurent wrote: > Le vendredi 2 septembre 2016, 16:11:28 CEST Andrey Rahmatullin a écrit : > > ksnapshot supported uploading images online via kipi-plugins. I don't see > > this feature in current kde-spectacle. Google shows that there should be > > an "Online Services" menu folder in the Exort button but I don't have it. > > My gwenview still has a set of online export plugins in its plugin menu. > > In settings you could choose a remote folder, but not work for me with sftp/ > fish File Transfer Protocol. Remote folders are not the same as online services. -- WBR, wRAR signature.asc Description: PGP signature
spectacle and online services
ksnapshot supported uploading images online via kipi-plugins. I don't see this feature in current kde-spectacle. Google shows that there should be an "Online Services" menu folder in the Exort button but I don't have it. My gwenview still has a set of online export plugins in its plugin menu. -- WBR, wRAR signature.asc Description: PGP signature
Re: digikam 5: then ksnapshot is removed
On Sun, Aug 14, 2016 at 04:43:22PM +0200, Luigi Toscano wrote: > spectacle should carry the proper configuration to allow the snapshot with the > Print button. khotkeys was even changed to not hardcode ksnapshot: > https://git.reviewboard.kde.org/r/126091/ I've checked my two other KDE systems (not on current sid) and both of them don't launch ksnapshot on PrtSc. > Did you restart the Plasma session completely (including all the background > services) after installing kde-spectacle *and* removing ksnapshot? No. -- WBR, wRAR signature.asc Description: PGP signature
Re: digikam 5: then ksnapshot is removed
On Sun, Aug 14, 2016 at 03:19:01PM +0100, Brad Rogers wrote: > >in the KDE Daemon global hotkey section and it doesn't launch spectacle. > Delete ksnapshot, enter spectacle, hit 'Apply'. I didn't understand what do you mean but I've found that it's not a builting hotkey (unfortunately for a DE) but one manually configured via kmenuedit. -- WBR, wRAR signature.asc Description: PGP signature
Re: digikam 5: then ksnapshot is removed
On Sun, Aug 14, 2016 at 08:37:38AM +0200, Pino Toscano wrote: > Yes, the kdegraphics metapackage needs to switch from ksnapshot to > kde-spectacle. As people pointed out already, ksnapshot is no more > developed, and instead there's spectacle (called kde-spectacle in Debian > for naming issues) which does what ksnapshot did and more. How do I set them to be launched by PrtSc? There is a print screen action in the KDE Daemon global hotkey section and it doesn't launch spectacle. -- WBR, wRAR signature.asc Description: PGP signature
Re: Debug symbols of Qt5
On Mon, Jun 06, 2016 at 06:14:08PM +0200, Frank Mehnert wrote: > I'm running Debian/Sid up-to-date. Are the debug symbols for the Qt5 libraries > available? qtbase5-dbg, I guess. > "apt-file search libQt5Gui.so" doesn't show a except for the normal > binaries. This is expected as -dbg packages built with debhelper compat level 9 don't use original file names. -- WBR, wRAR signature.asc Description: PGP signature
Re: KDE catastrophe after June 5 dist-upgrade
On Mon, Jun 06, 2016 at 09:01:12AM +0200, Holger Schramm wrote: > First i would reinstall all autoremoved packages especially the libkf5* > ones and the sddm as mentioned before. I don't think one should ever install library packages manually, otherwise there are wrong dependencies listed somewhere. -- WBR, wRAR signature.asc Description: PGP signature
Re: Wife's sid box still wants to deinstall on dist-upgrade
On Thu, Sep 17, 2015 at 12:39:36PM -0700, Jimmy Johnson wrote: > Brad I'm just going to look at your apps and I see gimp & digikam, in Sid > both are installable gimp yes, digikam no. > what I did was run package 'upgrade-system' and let it have its way with > my system and it showed me what a mess I was running That sounds like overstatement. > On Sept 15th Debian reported everybody upstream should be able to have a > clean updated system and they are on spot as far as I can see. Huh? -- WBR, wRAR signature.asc Description: Digital signature
Re: Any idea when plasma desktop will be working?
On Thu, Sep 17, 2015 at 11:59:43AM -0400, Gary Dale wrote: > It's been a couple of weeks now since it broke. I'm continuing to do > upgrades daily and see some progress in other tools (e.g. aptitude is back) > but the plasma desktop remains unusable. Does anyone how fixing it is > progressing? It is usable here, what dou you mean? -- WBR, wRAR signature.asc Description: Digital signature
Re: qdbus commands in 64-bit jessie?
On Thu, Sep 03, 2015 at 06:28:35PM -0600, D. R. Evans wrote: > Following my recent upgrade to jessie, the same command produces: > > > > qdbus: could not exec '/usr/lib/i386-linux-gnu/qt4/bin/qdbus': No such file or > directory dpkg -l qdbus -- WBR, wRAR signature.asc Description: Digital signature
Re: Plasma desktop unusable in stretch
On Thu, Sep 03, 2015 at 03:03:35PM -0400, Gary Dale wrote: > Sorry, but before releasing a major package to "testing", shouldn't it be > tested against the "testing" environment? No, we don't do this. -- WBR, wRAR signature.asc Description: Digital signature
Re: Plasma desktop unusable in stretch
On Thu, Sep 03, 2015 at 06:16:53PM +0100, Brad Rogers wrote: > >allotted time, the package transitions to testing. > I was surprised to see that "allotted time" can be as little as two > days. Which doesn't give unstable users a lot of time to discover any > real nasties. Urgencies higher than medium are used only in special cases. > For most packages, transition time is ten days, as I'm sure most people > know. Five. https://lists.debian.org/debian-devel-announce/2013/11/msg7.html -- WBR, wRAR signature.asc Description: Digital signature
Re: Plasma desktop unusable in stretch
On Thu, Sep 03, 2015 at 06:30:13PM +0200, Matthias Bodenbinder wrote: > Am 03.09.2015 um 18:12 schrieb Martin Steigerwald: > >> Packages from Debian Unstable enter the next-stable testing distribution > >> automatically, when a list of requirements is fulfilled: [...] The package > >> does not introduce new release critical bugs. > > > > So and now *who* reports these? > > > > Then rethink from there. > > Well, I would expect a minimum of testing from the package maintainers even > before a package is uploaded to unstable. I assume for the case at hand that > the package maintainers were pretty much aware about the broken KDE desktop. The maintainers are well aware that packages may behave badly during large transitions and that shouldn't stop them from uploading, as it's the only way forward. -- WBR, wRAR signature.asc Description: Digital signature
Re: Plasma desktop unusable in stretch
On Thu, Sep 03, 2015 at 12:03:04PM -0400, Gary Dale wrote: > I've tended to view "testing" as a rolling release That's the main misunderstanding. We had several tries to design and/or create a rolling Debian distro but there is nothing currently existing AFAIK. And it takes a lot more effort than is currently spent on unstable and testing (which is already a lot). -- WBR, wRAR signature.asc Description: Digital signature
Re: Plasma desktop unusable in stretch
On Thu, Sep 03, 2015 at 12:43:37PM +0200, Christian Hilberg wrote: > "It's all automatic" is the bit I missed. I was under the impression > that this would be true for experimental->unstable only experimental->unstable is fully manual (even requiring a new upload). -- WBR, wRAR signature.asc Description: Digital signature
Re: Plasma desktop unusable in stretch
On Wed, Sep 02, 2015 at 10:21:47AM -0400, Gary Dale wrote: > I thought testing was supposed to be where packages were mainly working and > the sid and experimental where were packages were tested to make sure they > actually worked. Not really. "The testing distribution is generated automatically by taking packages from unstable if they satisfy certain criteria. Those criteria should ensure a good quality for packages within testing." [0] That doesn't guarantee the testing is usable at any single point of time, and the packages can even be temporarily removed from testing. This only guarantees that packages in testing are not RC-buggy and pass other technical checks. Packages in Debian are not "tested to make sure they actually worked" other than by the users. So, during large transitions both unstable and testing may be temporarily unusable. Users who want continuously working systems should use stable (or expect to make efforts to deal with problems that happen in testing and unstable). [0]: https://www.debian.org/doc/manuals/developers-reference/ch04.en.html#sec-dists -- WBR, wRAR signature.asc Description: Digital signature
Re: Inkscape 0.48.4 for Debian
On Thu, May 02, 2013 at 11:07:35AM -0400, john Culleton wrote: > Trying to get a working copy of Inkscape 0.48.4 without getting too > deep into library hell. Does Wheezy have this version? Alternatively > will a version intended for Ubuntu also work on Debian? Squeeze only > has 0.47. > > I am a Debian novice, but a Linux user since about 1996. $ rmadison inkscape inkscape | 0.47.0-2 | squeeze | source inkscape | 0.47.0-2+b1 | squeeze | amd64, armel, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc inkscape | 0.48.3.1-1.3 | wheezy | source, amd64, armel, armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc inkscape | 0.48.3.1-1.3 | sid | source, amd64, armel, armhf, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc inkscape | 0.48.4-0.1 | experimental | source, amd64, armel, armhf, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc -- WBR, wRAR signature.asc Description: Digital signature
Re: Deebian 7.0 needs to support MTP (for Android), else it will lose relevance
On Sat, Feb 09, 2013 at 09:24:32AM +1100, Scott Ferguson wrote: > I strongly agree and suggest that we represent the silent majority of > long term Debian users. You cannot introduce packages that have only > been around for a year or two into Stable without diluting what Stable > means. Please don't. That's strongly offtopic here, but you don't seem to understand how does stable get created. In other words, we introduce packages that have been around for only half a year to each stable. -- WBR, wRAR signature.asc Description: Digital signature
Re: Deebian 7.0 needs to support MTP (for Android), else it will lose relevance
On Fri, Feb 08, 2013 at 05:21:19PM +0300, Pavel Mihaduk wrote: > The problem is that you take exactly the same position, _demanding_ KDE > 4.10 in wheezy just because _you_ consider MTP support a must-have. Please show where I demanded that. -- WBR, wRAR signature.asc Description: Digital signature
Re: Deebian 7.0 needs to support MTP (for Android), else it will lose relevance
On Fri, Feb 08, 2013 at 11:55:14AM +0300, Pavel Mihaduk wrote: > Andrey, > > Have you ever tried to read what other people wrote? There's a package > freeze policy Have *you* tried to read what other people wrote and notice *who* writes *what*? > which defines the procedures quite clearly; besides, > Qt-KDE team is not that big and it's hardly possible they'll manage to > package and push KDE 4.10 till wheezy release. I know. I just don't like when people write silly and/or wrong things on matters they do not understand. And while "we are frozen and you may wait for a backport" is a valid argument, "I didn't see such devices so I think you are wrong" or "I am not convinced that MTP as a protocol is useful" are not. > On Fri, 8 Feb 2013 00:33:35 +0600 > Andrey Rahmatullin wrote: > > > On Thu, Feb 07, 2013 at 06:46:24PM +0100, Martin Steigerwald wrote: > > > > > > Debian 7.0 (upcoming "Wheezy") needs MTP support in it's KDE > > > > > > in order to be relevant. > > > > > Honestly: I don´t care. > > > > > > > > > > I understand the sense behind MTP in not having to *mount* a > > > > > device. But from what I have seen regarding MTP I am not very > > > > > convinced about it. > > > > > > > > How is this opinion relevant here? It's the only option. > > > > > > Aha. > > > > > > Even if you state your oppinion as a matter fact here, it is still > > > just an oppinion. Cause you didn´t state and prove any facts in > > > this thread so far. > > > > > > So how is your oppinion relevant here? > > > > > > I tried to explain you something. I got the impression you didn´t > > > even listen. > > > > > > I do not see a reason to waste another second of my life on this. > > > > > > Thread set to ignore. > > Typical. > > > > -- WBR, wRAR signature.asc Description: Digital signature
Re: Deebian 7.0 needs to support MTP (for Android), else it will lose relevance
On Fri, Feb 08, 2013 at 02:12:42PM +0100, Mirosław Zalewski wrote: > > Galaxy Nexus was released with 4.0 more than year ago. It doesn't support > > UMS. > But, as David pointed out, there are bunch of new devices that DOES support > UMS. > > So maybe you should just choose your smartphone more carefully? It's nothing > new that before buying new device, Linux users should check if it will work > with their OS. Spending half an hour doing research may spare you much > trouble > later. Yeah, this is an option, though it is sad that people are forced to choose a phone based on (lack of) Linux support of a protocol that exists for a long time, instead of actual technical properties. There are also people with existing devices who try to start using Linux, but I'm not sure anymore that we try to support those. -- WBR, wRAR signature.asc Description: Digital signature
Re: Deebian 7.0 needs to support MTP (for Android), else it will lose relevance
On Fri, Feb 08, 2013 at 07:56:23PM +0800, David Smith wrote: > > The result: > > Google decided to remove USB Mass Storage from Android 4.x devices. > > Newer Android devices support MTP-only. > I don't believe that is accurate as my HP tablet running Cyanogenmod9 with > Android 4.0.4, my Motorola Razor cell phone with Android 4.0.4, and my > girlfriend's HTC One X with Android 4.1.1 work just fine with Debian > Wheezy + KDE 4.8.4. I can send and receive files between devices with zero > issues, and these devices are all "up-to-date" with the latest stable > android available for the devices. > > I assume you mean the more bleeding edge android 4.2 or 4.3 which is > currently only supported on a handful of devices, removed USB mass > storage? If so, I just won't upgrade my devices as the upgrade is always > optional. Galaxy Nexus was released with 4.0 more than year ago. It doesn't support UMS. > You should be able to flash an older version of android on your > devices that you already purchased if you accidently upgraded to MTP-only, That's a funny suggestion. -- WBR, wRAR signature.asc Description: Digital signature
Re: Deebian 7.0 needs to support MTP (for Android), else it will lose relevance
On Thu, Feb 07, 2013 at 06:46:24PM +0100, Martin Steigerwald wrote: > > > > Debian 7.0 (upcoming "Wheezy") needs MTP support in it's KDE in order > > > > to be relevant. > > > Honestly: I don´t care. > > > > > > I understand the sense behind MTP in not having to *mount* a device. > > > But from what I have seen regarding MTP I am not very convinced about > > > it. > > > > How is this opinion relevant here? It's the only option. > > Aha. > > Even if you state your oppinion as a matter fact here, it is still just an > oppinion. Cause you didn´t state and prove any facts in this thread so far. > > So how is your oppinion relevant here? > > I tried to explain you something. I got the impression you didn´t even > listen. > > I do not see a reason to waste another second of my life on this. > > Thread set to ignore. Typical. -- WBR, wRAR signature.asc Description: Digital signature
Re: Deebian 7.0 needs to support MTP (for Android), else it will lose relevance
On Thu, Feb 07, 2013 at 11:05:40AM +0100, Martin Steigerwald wrote: > > Debian 7.0 (upcoming "Wheezy") needs MTP support in it's KDE in order > > to be relevant. > > Honestly: I don´t care. > > I understand the sense behind MTP in not having to *mount* a device. But > from what I have seen regarding MTP I am not very convinced about it. How is this opinion relevant here? It's the only option. -- WBR, wRAR signature.asc Description: Digital signature
Re: Deebian 7.0 needs to support MTP (for Android), else it will lose relevance
On Wed, Feb 06, 2013 at 07:58:17PM +0100, Leopold Palomo Avellaneda 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. > > I have Android 4.x with MSC. However is not the default. Are you sure you > didn't have it? It is supported only by some devices. -- WBR, wRAR signature.asc Description: Digital signature
Re: Deebian 7.0 needs to support MTP (for Android), else it will lose relevance
On Wed, Feb 06, 2013 at 07:57:45PM +0200, David Baron wrote: > These are excerpted from ~$ locate mtp | grep usr mtpfs doesn't work (#654939) and when it does it's too unreliable. Command-line tools are not an option because in this case you can just use adb. kio_kamera is read-only and unreliable. I think this also applies to GVFS gphoto2:// and probably other libgphoto2 users. gvfs-mtp is not packaged. -- WBR, wRAR signature.asc Description: Digital signature
Re: Deebian 7.0 needs to support MTP (for Android), else it will lose relevance
On Wed, Feb 06, 2013 at 06:13:26PM +0100, Leopold Palomo-Avellaneda wrote: > I think that yo are a bit dramatic. Just to configure your android device to > use usb as msc It is just not possible with certain newer devices. -- WBR, wRAR signature.asc Description: Digital signature
Re: Re: Re: NVidia drivers in KDE
On Sat, Jul 28, 2012 at 06:47:47PM +0100, Grześ Andruszkiewicz wrote: > What is the best way to downgrade cairo? debsnap -- WBR, wRAR signature.asc Description: Digital signature
Re: Re: NVidia drivers in KDE
On Mon, Jul 23, 2012 at 02:38:16PM +0100, Grześ Andruszkiewicz wrote: > Hi, > > Marco, > I did the change, but I haven't observed any difference... > > Marek, > I can confirm that it does work for Chrome but it breaks Iceweasel > (the performance drops in a very similar level to Chrome at different > settings) > > Do you know if all nVidia cards have these issues? I was planning to > upgrade, but the situation makes me wonder if it is worth sticking > with nVidia... As nobody seems to know whether it's a cairo bug, nvidia driver bug or something else, nobody can tell you which configurations are affected, but downgrading cairo to 1.10 semms to fix the problem for everyone. -- WBR, wRAR signature.asc Description: Digital signature
Re: Suspend to memory in KDE
On Wed, Apr 13, 2011 at 09:45:48PM +0530, Ritesh Raj Sarraf wrote: > > KDE uses pm-suspend, which does more than just echo "mem" > > > /sys/power/state. Though I think Gnome uses it too. Do you use KDE 4.4 or > > 4.6? > I had been trying to look for this. Can you suggest where to look on how > kde calls/depends on pm-suspend? Does it rely on dbus for it? > > My intent is to see if I can replace that with small helper scripts. > Currently, if you uninstall pm-utils, you will lose suspend/hibernate > functionality. Before 4.5 KDE used hal, now it uses upower. Via dbus in both cases. -- WBR, wRAR signature.asc Description: Digital signature
Re: KDM doesn't work
On Fri, Apr 08, 2011 at 10:07:37PM +0200, Torquil Macdonald Sørensen wrote: > I have installed the KDE 4.6.1 from http://qt-kde.debian.net/ onto my Sid. > > However, kdm will not start. After booting, when X is started, I'm simply > dropped back into text mode. > > In /var/log/syslog I found the following error message: > > Apr 8 21:20:51 asus kdm: :0[1839]: Received unknown or unexpected command -2 > from greeter > Apr 8 21:20:51 asus kdm: :0[1839]: Abnormal termination of greeter for > display :0, code 1, signal 0 > > Any ideas? Meanwhile I'm using XDM as a substitute. /var/log/kdm.log -- WBR, wRAR signature.asc Description: Digital signature
Re: Suspend to memory in KDE
On Sat, Apr 09, 2011 at 12:32:35PM +0800, Liang Guo wrote: > I'm using a HP 6515b laptop, when I use K Menu -> Leave -> Sleep(Suspend to > memory) to suspend my laptop, I need wait more than 1 minutes(some time about > 5 > minutes) before suspend complete. How can I trace this problem? KDE uses pm-suspend, which does more than just echo "mem" > /sys/power/state. Though I think Gnome uses it too. Do you use KDE 4.4 or 4.6? -- WBR, wRAR signature.asc Description: Digital signature
pinentry-qt4 doesn't use the system style on 4.6
After upgrading to 4.6 pinentry-qt4 uses some non-default style (Motif or Windows, can't determine) while the Qt4 and KDE themes are set to QtCurve. System is Sid. -- WBR, wRAR signature.asc Description: Digital signature
Re: knetworkmanager interface regression in 4.5.1
On Tue, Sep 14, 2010 at 05:45:26PM +0600, Andrey Rahmatullin wrote: > > Try using plasma-widget-networkmanagement instead of the > > knetworkmanager tray icon. > It doesn't show any connections in the right part of the popup window and > it even doesn't automatically connect to a wifi network which has "Connect > automatically" property set. That was fixed by one more reboot. -- WBR, wRAR (ALT Linux Team) signature.asc Description: Digital signature
Re: knetworkmanager interface regression in 4.5.1
On Tue, Sep 14, 2010 at 11:28:05AM +0300, George Kiagiadakis wrote: > > After upgrading to 4.5.1 I've noticed that network entries in the > > knetworkmanager tray icon menu are shown as empty lines. Connections > > confiured to start automatically are still started, but I can't do > > anything with the menu entries: they don't have tooltips and nothing > > happens when I click on them (so I can't establish a non-automatic > > connection). > > It's a sid system updated from qt-kde.d.o. > Try using plasma-widget-networkmanagement instead of the > knetworkmanager tray icon. It doesn't show any connections in the right part of the popup window and it even doesn't automatically connect to a wifi network which has "Connect automatically" property set. -- WBR, wRAR (ALT Linux Team) signature.asc Description: Digital signature
knetworkmanager interface regression in 4.5.1
After upgrading to 4.5.1 I've noticed that network entries in the knetworkmanager tray icon menu are shown as empty lines. Connections confiured to start automatically are still started, but I can't do anything with the menu entries: they don't have tooltips and nothing happens when I click on them (so I can't establish a non-automatic connection). It's a sid system updated from qt-kde.d.o. -- WBR, wRAR (ALT Linux Team) signature.asc Description: Digital signature
Re: How to improve font-using in KDE4?
On Tue, May 18, 2010 at 07:01:23PM +0200, Dirk Salva wrote: > im comparison to another computer, working still with Lenny, the > display of fonts in Konsole is bad:-( > Without antialiasing on Squeeze (as in Lenny) the fonts are angular, > with activated antialiasing the fonts are too spongy. So, where do I > have to search to resolve this problem? On my Lenny-Desktop font in > Konsole without antialiasing looks perfect. In Squeeze not:-( Something has changed in Qt 4.6. There are even some bug reports in Qt tracker, such as http://bugreports.qt.nokia.com/browse/QTBUG-7011 -- WBR, wRAR (ALT Linux Team) signature.asc Description: Digital signature
