Re: akonadi-kde-resource-googledata: still working for anyone?
On Friday 03 June 2011 18:56:40 Lisandro Damián Nicanor Pérez Meyer wrote: > On Lun 30 May 2011 07:15:45 Michael Schuerig escribió: > [snip] > > It seems to work for me now, too. It is not enough, to restart the > > Akdonadi Server or the KDE session. The respective resources have to be > > removed and added again to make it work. > > Indeed, I had to remove them and re add them. > > Regards, Lisandro. > > Hi, Calendar works ok for me but contacts don't. It seg faults every time. Application: Akonadi Resource (akonadi_googledata_resource), signal: Segmentation fault [KCrash Handler] #6 __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:32 #7 0x7fbef4479095 in qstrlen (str=, size=) at ../../include/QtCore/../../src/corelib/tools/qbytearray.h:68 #8 QString::fromUtf8 (str=, size=) at tools/qstring.cpp:3938 #9 0x00419880 in _start () -- Sami signature.asc Description: This is a digitally signed message part.
Re: Can't connect to msn server with kopete
Hi, The reason might be that Microsoft is closing Live chat and migrating to Skype. On 30 August 2013 21:51, Diederik de Haas wrote: > Hi, > > In the last week I've been trying to connect to MSN with kopete, but I keep > getting the error: > "Cannot connect with the instant messaging server or peers" > > Is anyone else seeing this and is there a fix for it? > > Is kde-telepathy a proper replacement? > I noticed that the kde-telepathy(-minimal) is at version 0.4.0-1, while > most > other kde-telepathy packages are at version 0.6.3-1. > Why is that? > > Cheers, > Diederik > > -- > GPG: 0x138E41915C7EFED6
Re: Milou in Experimental
On 14 June 2015 at 15:33, Lorenzo Bettini wrote: > On 13/06/2015 12:42, Volker Wysk wrote: > > Am Samstag, 13. Juni 2015, 11:05:52 schrieb Lorenzo Bettini: > > > >> On 12/06/2015 21:30, Volker Wysk wrote: > > > >> > Hi! > > > >> > > > > >> > > > > >> > > > > >> > I just want to notice, that I have found Milou in Experimental, but it > > > >> > doesn't work for me. There doesn't appear any plasmoid named "milou" > in > > > >> > the "add plasmoid" (Miniprogramme hinzufügen) list. > > > >> > > > >> Hi > > > >> > > > >> I think that the corresponding Plasmoid is called simply "Search". > > > > > > > > Thanx, but I don't have this either. > > > > So you installed milou packages but you don't see any widget that > contains "Search"? > > I don't think that Milou works on plasma 4 and needs the full plasma 5 desktop. We'll have to still wait for some time to get all the plasma 5 packages to experimental. They are waiting for approval in the NEW queue ( https://ftp-master.debian.org/new.html).
Re: So I have a Plasma 5 desktop!
On 13 July 2015 at 08:34, Jimmy Johnson wrote: > On 07/12/2015 09:17 PM, Michael Schuerig wrote: > >> On Sunday 12 July 2015 19:06:55 Jimmy Johnson wrote: >> > > I'm waiting for some things I see missing before I upgrade >>> "plasma-desktop". What I see missing are "showdesktop and "klipper", >>> I've been using them for many years and would hate to loose them. Also >>> I know once I remove a KDE-4 package there is no looking back and you >>> can loose the functions of your desktop. Once I find my missing >>> packages I will be extremely happy! So far so good.. >>> >> >> Klipper is there already. "Showdesktop"? A widget to hide all windows >> and show the desktop underneath? That's there, too. >> > > > Michael, I'm not seeing what you are seeing..I'm not seeing showdesktop at > all..and klipper is version KDE-4 and if I install plasma-desktop KDE-4 > klipper will be gone with no replacement.. Klipper doesn't have its own package in KF5/Plasma 5. It's included in plasma-workspace (plasma-workspace 4:5.3.2-1 replaces klipper). Show Desktop -plasmoid is in plasma-widgets-addons (4:5.3.2-2) package. -- Sami
Re: Install on stretch : feedback
On 3 August 2015 at 19:10, Diederik de Haas wrote: > On Monday 03 August 2015 17:26:44 Michal BULIK wrote: > > - kdeconnect is working no more. I've installed the latest > >version from source but it does not work. I'll try to solve > >it with the kdeconnect team > > Could you report that back to this list as well and/or provide a link to > the > discussion? I really miss kdeconnect as it was just awesome. > > Cheers, > Diederik Hi, Kdeconnect in Debian is only for KDE4 and doesn't work with Plasma5/KF5. There is a git tree ( https://anonscm.debian.org/cgit/pkg-kde/kde-extras/kdeconnect-plasma.git/) for Plasma 5 but that hasn't been uploaded to Debian yet. I'm building Kdeconnect directly from the KDE git tree ( http://quickgit.kde.org/?p=kdeconnect-kde.git) and it's working on my Debian Plasma 5.
Re: Install on stretch : feedback
On 4 August 2015 at 17:24, Michal BULIK wrote: > Hi Sami, > > > > Kdeconnect in Debian is only for KDE4 and doesn't work with Plasma5/KF5. > There is a git tree ( > https://anonscm.debian.org/cgit/pkg-kde/kde-extras/kdeconnect-plasma.git/) > for Plasma 5 but that hasn't been uploaded to Debian yet. > > I'm building Kdeconnect directly from the KDE git tree ( > http://quickgit.kde.org/?p=kdeconnect-kde.git) and it's working on my > Debian Plasma 5. > > Can you share with us how you install it. I've compiled it with cmake, > make > & make install but I get the message "Process org.kde.kdeconnect received > signal 6" > > Thanks, > Michal > > Hi, Check that you have KDE_INSTALL_USE_QT_SYS_PATHS:BOOL=ON in CMakeCache.txt. Without it the 'make install' will install Kdeconnect to wrong directory (/usr/lib/[arch]/ instead of /usr/lib/[arch]/qt5/). You might want to 'make uninstall' before that change to uninstall the files from the wrong directory
Re: qdbus commands in 64-bit jessie?
On 4 September 2015 at 03:28, D. R. Evans wrote: > In wheezy, the following command worked correctly: > > > > qdbus org.kde.yakuake /yakuake/sessions runCommandInTerminal $SESSION_ID > "tmux" > > > > 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 > > > > The reference to i386 is a bit puzzling, since this is a 64-bit system. > Anyway, I discovered that all attempts to execute qdbus commands from the > command line produce the same error :-( > > What do I need to do to get my qdbus commands working again? > > Doc > > -- > Web: http://www.sff.net/people/N7DR > > > > Hi, Do you have package qdbus-qt5 installed? If not install that and try again.
Re: qdbus commands in 64-bit jessie?
On 8 September 2015 at 21:12, D. R. Evans wrote: > Am awaiting a response to the e-mail below; I executed the command as > requested, but don't know what I'm supposed to do now :-( > > Doc > > > > D. R. Evans wrote on 09/04/2015 11:17 AM: > > Andrey Rahmatullin wrote on 09/04/2015 09:59 AM: > >> 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 > >> > > > > > > > > root@homebrew:/home/n7dr# dpkg -l qdbus > > Desired=Unknown/Install/Remove/Purge/Hold > > | > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > > ||/ NameVersionArchitecture > Description > > > +++-===-==-==- > > ii qdbus 4:4.8.6+git64-g5dc amd64 Qt > 4 > > D-Bus tool > > root@homebrew:/home/n7dr# > > > > > > > > I don't understand it, but it doesn't look good. I didn't see any obvious > > complaints during the upgrade process, though (for this or any other > packages > > except db1.5-util, which was held back for some reason). > > > > Doc > > > > > -- > Web: http://www.sff.net/people/N7DR > > Hi, What terminal are you using? Is it i386 arch terminal or is qtchooser package arch i386? I'm no expert on multi-arch but those could be reasons why running qdbus wants to use i386 version. You can list all i386 packages with dpkg -l *:i386 64-bit qdbus is in /usr/lib/x86_64-linux-gnu/qt4/bin/qdbus
Re: qdbus commands in 64-bit jessie?
On 9 September 2015 at 17:21, D. R. Evans wrote: > Boris Pek wrote on 09/09/2015 02:09 AM: > > >>> I'm no expert on multi-arch but those could be reasons > >>> why running qdbus wants to use i386 version. > >> > >> This is a 64-bit system, so I am unclear why multi-arch is involved at > all. > >> Any non-64-bit programs were put there by the debian upgrade procedure, > not by me. > > > > This is not true. See below. > > It is true. But we are being dragged down a rabbit hole, and I don't see > the > point of arguing how various things got on my system. qdbus worked prior to > the upgrade, and now it doesn't, so the question remains: > > >>> What do I need to do to get my qdbus commands working again? > > The upgrade obviously broke something related to qdbus, but I don't > understand > at all how to fix it. > > Doc > > -- > Web: http://www.sff.net/people/N7DR > > On my system /usr/bin/qdbus is a link to qtchooser and as your qtchooser arch is i386 it will try to use i386 version of qdbus. Could you replace your qtchooser with a amd64 version.
Re: kde does not start normally
On 31 October 2015 at 16:30, Carlos Kosloff wrote: > If you follow this list you are aware of my efforts to get kde to start > normally. > I am aware that many of you have succeeded, maybe some did not, I am among > the latter. > Different systems and hardware react differently, I have a computer that > works fine with sddm, but in my main system sddm throws a black screen, and > both have similar configurations. > My question is: can somebody help with making kde start normally? > So far no dm has worked, I am forced to start kde with "startx startkde". > Thank you. > -- > Hi, Do you have a Nvidia card on the non-working computer? If you have and glx-alternatives is <0.6.1 you might be affected by this bug https://bugs.debian.org/799948
Re: kde does not start normally
On 31 October 2015 at 16:57, Carlos Kosloff wrote: > > Indeed, my card uses nvidia and glx-alternative-nvidia is 0.5.1. > So is glx-diversions and glx-alternative-mesa. > What to do? There is no upgrade for these packages in testing. > -- > On 10/31/2015 10:48 AM, Sami Erjomaa wrote: > > On 31 October 2015 at 16:30, Carlos Kosloff wrote: > >> If you follow this list you are aware of my efforts to get kde to start >> normally. >> I am aware that many of you have succeeded, maybe some did not, I am >> among the latter. >> Different systems and hardware react differently, I have a computer that >> works fine with sddm, but in my main system sddm throws a black screen, and >> both have similar configurations. >> My question is: can somebody help with making kde start normally? >> So far no dm has worked, I am forced to start kde with "startx startkde". >> Thank you. >> -- >> > Hi, > > Do you have a Nvidia card on the non-working computer? If you have and > glx-alternatives is <0.6.1 you might be affected by this bug > https://bugs.debian.org/799948 > > > I'm not sure if that bug is in 0.5.1. It was in 0.6.0. What worked for me was to add user sddm to video group in /etc/group
Re: kde does not start normally
On 31 October 2015 at 17:18, Carlos Kosloff wrote: > "I'm not sure if that bug is in 0.5.1. It was in 0.6.0. What worked for me > was to add user sddm to video group in /etc/group" > > Hmmm...I have this entry in /etc/group *sddm:x:131:* is this what you are > talking about? > Otherwise I could do *adduser sddm video* as root. > Also, without changing anything in my sources.list, I could download more > updated packages from unstable and install with dpkg. > What do you think? > Thank you. > I mean group *video:x:44:sddm,[my username]* in /etc/group. I still have this workaround enabled so I'm not 100% if updating the nvidia drivers from unstable fixes it. Actually I'm using nvidia drivers from experimental.
Re: Plasma 5.5.4 + KF 5.18 in experimental
There are few packages that won't become available before their build-deps are updated. At least kinfocenter, kwayland-integration and powerdevil don't build with kwayland-dev 4:5.4.3-1 but need 4:5.5.4-1 to build. On 28 January 2016 at 01:32, Diederik de Haas wrote: > On Wednesday 27 January 2016 23:30:36 Martin Steigerwald wrote: > > Anyone have a nice apt / aptitude mantra at hand to update just the > Plasma > > + KF packages to the experimental version without getting everything > else > > from it? > > > > Otherwise I´d try to go by some metapackages. > > That is going to be tricky. Especially as qt5.6-beta packages are also in > experimental. Anyway, here's a command I just put together: > > aptitude safe-upgrade '?narrow(~skde!~nlibreoffice,~i!~M)' -t experimental > > Which should upgrade packages from section kde which are not named > libreoffice > and are manually installed. > > You could also play with '~V5.16' but I _think_ the result will then be > that > automatically installed packages (mostly libraries) will then be marked as > manually installed and I personally don't like that. > > The following may also be useful: > aptitude safe-upgrade '?narrow(~i!~M, ~V4:5.4.*)' -t experimental > > HTH, > Diederik
Re: plasma 5.5 in experimental
On 16 February 2016 at 18:38, Marc Haber wrote: > Hi, > > I have tried plasma 5.5 from experimental and kwin-x11 crashes > immediately on login. This leaves me with unmovable undecorated > windows. Starting anther kwin instance from a shell doesn't work > either since some leftover from the dead kwin instance blocks access. > > Unfortunately, drkonqui doesn't start in that situation as well. > > Is that a known issue, and how can I assist in debugging? > > Greetings > Marc > > -- > > - > Marc Haber | "I don't trust Computers. They | Mailadresse im Header > Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 > Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421 > > Hi, Have you installed all the plasma and KF packages from experimental that you can? IIRC I had similar problem that was fixed when I installed qml-module-org-kde-* packages from experimental. the Plasma 5.5 and KF 5.18/19 isn't complete or possible to install from experimental since some of the packages are built with qt 5.5.1 from unstable and some are built with qt 5.6.0 beta from experimental making it impossible for the build system to build all the packages or install when they depend on different qt versions.
Re: plasma 5.5 in experimental
Hi, I don't think it's completely because of builder issue. If it is an issue in builders wouldn't all the packages in experimental be built with 5.6.0? Some of the packages in experimental are built with 5.5.1 and some are built with 5.6.0. examples: built with qt 5.5.1: bluez-qt, karchive built with qt 5.6.0: kwidgetsaddons, kcodecs, kconfig I can't see directly from the build dependencies what would make the builders choose 5.6.0 for some and 5.5.1 for some. karchive Build-Depends: cmake (>= 2.8.12), debhelper (>= 9), extra-cmake-modules (>= 5.19.0~), libbz2-dev, liblzma-dev, pkg-kde-tools (>= 0.15.16~), qtbase5-dev (>= 5.4), zlib1g-dev kconfig Build-Depends: cmake (>= 2.8.12), debhelper (>= 9), extra-cmake-modules (>= 5.19.0~), pkg-kde-tools (>= 0.15.15ubuntu1~), qtbase5-dev (>= 5.4), qttools5-dev (>= 5.4), qttools5-dev-tools (>= 5.4)
Re: kwalletmanager5 cannot open a wallet with experimental stuff installed
On 25 February 2016 at 15:36, Diederik de Haas wrote: > On Thursday 25 February 2016 14:29:18 Martin Steigerwald wrote: > > I solved this by upgrading kde-runtime 15.08 in unstable to 15.12.1 in > > experimental. > > > > Come on, stuff all the things into unstable already :) > > How did you 'overcome' https://bugs.debian.org/814526 ? > Did you force the installation of plasma-desktop-data? You don't have to 'overcome' that bug if you don't have any kde-l10n-* packages installed
Re: kwalletmanager5 cannot open a wallet with experimental stuff installed
On 25 February 2016 at 16:23, Diederik de Haas wrote: > On Thursday 25 February 2016 16:00:09 Sami Erjomaa wrote: > > > How did you 'overcome' https://bugs.debian.org/814526 ? > > > Did you force the installation of plasma-desktop-data? > > > > You don't have to 'overcome' that bug if you don't have any kde-l10n-* > > packages installed > > Damn, referenced the wrong bug. > I meant this one: https://bugs.debian.org/814152 > ([libkscreenlocker5] Conflict with plasma-workspace) update plasma-workspace to 4:5.5.4-1
Re: Icons and screensavers
Hi, There's a bug for the icon issue #801992 Iceweasel icons (png) were generated during build from a svg file but due to a bug in librsvg they were cropped and not resized bugs.debian.org/cgi-bin/bugreport.cgi?bug=801992
Re: Nasty bug in qtdeclarative 5.6.1 (sid only)
Hi, Could these segfaults I get during system shutdown after display server has stopped be related to this bug? kernel: [ 523.653043] kactivitymanage[2231]: segfault at 7f5c90507cd0 ip 7f5c800d7301 sp 7ffc83c58008 error 4 in libQt5Sql.so.5.6.1[7f5c800c1000+45000] kernel: [ 523.656887] QDBusConnection[2363]: segfault at 7f038007d1b0 ip 7f03928c9517 sp 7f037bdf49a0 error 4 in libQt5Core.so.5.6.1[7f0392617000+4c] On 16 June 2016 at 17:31, Lisandro Damián Nicanor Pérez < perezme...@gmail.com> wrote: > If you are running sid be sure to update your system in ~8hs fron now. I > have > just uploaded qtdeclarative again with a patch for a nasty crash. > > > > -- > firmaware: soft cuya licencia pagas enviando un autografo > StucKman en #grulic, irc.freenode.net > > Lisandro Damián Nicanor Pérez Meyer > http://perezmeyer.com.ar/ > http://perezmeyer.blogspot.com/ > -- Sami Erjomaa <https://www.google.com/profiles/sami.erjomaa> <https://twitter.com/Erjomaa><https://www.linkedin.com/in/erjomaa>
Re: ksystraycmd missing
Hi, ksystraycmd is in package kde-workspace-bin On 18 June 2016 at 15:29, MERLIN Philippe wrote: > Help, > > With the recent update in SID AMD64 i have this message : impossible to > start ksystraycmd or Plasma message say "impossible to open library > libkdeinit5_ksystraycmd and its seems normal an apt-file search find > libkdeinit5 does not show any libkdeini5_ksystraycmd. > > What can I do ? is a problem with the comming of new Kde Frameworks ? > > Cheers. > > Philippe Merlin > > > -- Sami Erjomaa <https://www.google.com/profiles/sami.erjomaa> <https://twitter.com/Erjomaa><https://www.linkedin.com/in/erjomaa>
Re: ksystraycmd missing
On 18 June 2016 at 16:35, MERLIN Philippe wrote: > > > Help, > > > > > > > > With the recent update in SID AMD64 i have this message : impossible to > > > > start ksystraycmd or Plasma message say "impossible to open library > > > > libkdeinit5_ksystraycmd and its seems normal an apt-file search find > > > > libkdeinit5 does not show any libkdeini5_ksystraycmd. > > > > > > > > What can I do ? is a problem with the comming of new Kde Frameworks ? > > > > > > > > Cheers. > > > > > > > > Philippe Merlin > > Thank you, but i can't install kde-workspace-bin > > LANG=C apt-get install kde-workspace-bin > Reading package lists... Done > Building dependency tree > Reading state information... Done > Package kde-workspace-bin is not available, but is referred to by another > package. > This may mean that the package is missing, has been obsoleted, or > is only available from another source > However the following packages replace it: > plasma-workspace:i386 plasma-desktop:i386 plasma-workspace > plasma-desktop-data plasma-desktop > kde-runtime-data > > E: Package 'kde-workspace-bin' has no installation candidate > Cheers. > What application are you trying to start that uses ksystraycmd? The systray system changed and that command is not available anymore. Plasma-workspace includes xembedsniproxy that enables old system tray icons. https://lists.debian.org/debian-kde/2016/06/msg00087.html -- Sami Erjomaa
Re: ksystraycmd missing
On 18 June 2016 at 19:16, MERLIN Philippewrote: > > What application are you trying to start that uses ksystraycmd? The > systray > > > system changed and that command is not available anymore. > Plasma-workspace > > > includes xembedsniproxy that enables old system tray icons. > > > > > > https://lists.debian.org/debian-kde/2016/06/msg00087.html > > > > > > -- > > > Sami Erjomaa > > thanks : > > applications : Kontact when i want to open an link which open firefox and > if i want to open firefox by a kde menu. > Firefox 47.0-1 from Debian unstable doesn't do that for me. Maybe you have some extensions or add-ons that use the old system tray or you have installed some other version of firefox that uses the old system tray. -- Sami Erjomaa
Re: multi screen handling definately better now
On 21 June 2016 at 14:08, Kai Michael Hamich wrote: > Hi, > > my experience is, that after i send my pc to hibernate or reboot the screen > settings get sometimes lost (like every second reboot). > > Then i have to re-arrange the positions of the two screens again on first > login. > > Has anyone else the same experience? > Yes. I believe that is this upstream bug https://bugs.kde.org/show_bug.cgi?id=346961 I'm going to test if removing the write access to the kscreen config file works as a workaround. Other workaround I've seen is to configure your displays in Xorg. -- Sami Erjomaa <https://www.google.com/profiles/sami.erjomaa> <https://twitter.com/Erjomaa><https://www.linkedin.com/in/erjomaa>
Re: KDE Connect media player issue
On 27 July 2016 at 13:43, Valerio Passini wrote: > I've recently discovered this application and it's really amazing and > useful. > What is working not so good is the media remote control plugin, because > it's > not able to automatically detected if you are using a compatible media > player > like amarok or vlc (this should be documented somewhere). I've found a > workaround that consists in tinkering with KDE Connect options in > systemsettings: you need to disable and to enable multimedia control > receiver, > than on the smartphone app the media player will show and will be working. > I'm > guessing if this is a problem on the app side or on the KDE side, what I > know > it's that the app is complaining about the KDE counterpart being older. > > Valerio > > Hi, This is a bug in the computer side of the application. https://bugs.kde.org/show_bug.cgi?id=352529 The application doesn't detect when a media player is started, only those that are running when the plugin is loaded. This is fixed in the 1.0 version that was released 4 days ago in the kde git. The 1.0 version source isn't released yet in http://download.kde.org/unstable/kdeconnect/. When it's released there it can be packaged for Debian. -- Sami
Re: digikam 5: then ksnapshot is removed
On 14 August 2016 at 16:56, Martin Steigerwald wrote: > Am Sonntag, 14. August 2016, 08:37:38 CEST schrieb Pino Toscano: >> Hi, >> >> In data sabato 13 agosto 2016 20:08:01 CEST, Luc Castermans ha scritto: >> > Indeed installing Digikam 5 forces to remove kdegraphics package. I think >> > >> > I can miss a few, except for ksnapshot. Is this a wrong dependency? >> >> 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. >> >> I'm going to upload soon a new version of meta-kde, so the update won't >> cause the packages to be uninstalled. > > The only thing I miss from kde-spectacle is simply numbering screenshots. It > has placeholders for date and time which is pointless for me to have in the > filename, as its in the filesystem metadata and the image metadata already. It > does not seem to have any placeholder for numbering them. > > But I will report this upstream as this is no Debian issue. > > -- > Martin > The Spectacle preferences says "If a file with this name already exists, a serial number will be appended to the filename. For example, if the filename is "Screenshot", and "Screenshot.png" already exist, the image will be saved as "Screenshot-1.png". -- Sami Erjomaa
Re: Up to date information on plasma versions in testing?
On 22 October 2016 at 13:45, Shawn Sörbom wrote: > Hi folks, > Just wondering where one can find up to date information on the plasma > versions currently in stretch? the obvious answer would be to check > individual > packages of course, but I find that they often have confusing (and > conflicting) version numbers. Is a package like Kwin a good overall > progress > indicator for the state of which version is (mostly) being used? > Thanks, > --Shawn > > This page has all the packages and their versions in different releases maintained by the qt-kde team https://qa.debian.org/developer.php?login=debian-qt-...@lists.debian.org -- Sami Erjomaa
Re: Plasma 5.23 upload to unstable is complete
On Sun, 17 Oct 2021 at 01:25, Patrick Franz wrote: > Hi all, > > the upload of Plasma 5.23 to unstable is complete and it should be safe > to upgrade. > > Just a couple of notes: > * When you upgrade, make sure to upgrade all packages to 5.23. > * ksysguard has been removed and when upgrading, make sure that the > packages get removed e.g. by using "dist-upgrade". > * A minor hiccup seems to be that the keybinding for KRunner (Alt+F2/ > Alt+Space) seems to have been lost as the option appears twice in > systemsettings. But you can easily restore the default setting for the > keybinding in the settings. > > Have fun. > > > -- > Med vänliga hälsningar > > Patrick Franz > > > Hi, Thank You all (Kde/QT Team). Is ksysguard package deprecated upstream since that hasn't been updated yet? https://tracker.debian.org/pkg/ksysguardhttps://tracker.debian.org/pkg/ksysguard If it is deprecated it should be removed from plasma-desktop recommendations. For me the Alt+F2 and Alt+Space work as they should. -- Sami Erjomaa
Re: Unable to access plasma desktop after nvidia drive upgrade on testing
On Tue, 19 Oct 2021 at 11:46, Marc Bres Gil wrote: > Good Morning, > > Yesterday I've did a apt upgrade which upgraded the nvidia-driver to 470 > on my debian testing system. > After the corresponding reboot, SDDM starts ok, but when I input my > credentials plasma desktop hangs on the splash screen. > > Now I've installed cinnamon DE (a lot uglier btw) which works, so seems > some problem between plasma and new nvidia-driver. > I've created a new user from scratch to check if there are some problems > with user profile customizations, but got the same behavior, after entering > the credentials on sddm, plasma hangs on the splash screen. > > I've checked the xorg.0.log, and seen nothing there. > Anyone has the same problem? > Can you guide me on which logs I have to check to find the problem? > > Thank you > > -- > Marc Bres Gil > m...@bres.cat > marc.b...@gmail.com > Hi, Downgrade libkdecorations2-5v5 to version 5.21.5-2 -- Sami Erjomaa linktr.ee/erjomaa
Re: KDE Frameworks 5.90 coming to unstable
> > > It appears to me that it is complete already. > > Frameworkintegration hasn't been built since it depends on knewstuff that's in the "NEW" queue. Rest of the Frameworks 5.90 can be installed. -- Sami Erjomaa
Re: Bookwork KDE task switchers
On Sun, 24 Apr 2022 at 10:08, luca.pedrielli wrote: > Il 24/04/22 06:58, local10 ha scritto: > > Hi, > > After migrating from Bullseye to Bookworm, it appears that the only task > switchers available to me in Bookworm are "Breeze", "Breeze Dark" and "Breeze > Twilight", no other task switchers are available. > > Currently I use Breeze, which works but I would prefer to get the "Flip > Switch" back that I used to use in Bullseye. Not sure why other task > switchers have disappeared, maybe I'm missing a package or maybe the KDE > compositor crashed? Had a similar issue some years back when the KDE > compositor crashed and KDE disabled it afterwards, resulting in the loss of > some task switchers, IIRC. > > Any ideas? Thanks > > > some effects where dropped > >- > >coverswitch >- > >cube >- > >cubeslide >- > >flipswitch > > > :( > > -- > Saluti, Luca Pedrielli > > Hi, I have Compact, Cover Switch, Flip Switch, Grid, Informative, Large Icons and Small Icons + the 3 Breeze Those other switchers come in the kwin-addons package -- Sami Erjomaa linktr.ee/erjomaa
Re: Plasma 6 coming to unstable
On Thu, 28 Nov 2024 at 15:47, Matthieu Gallien wrote: > > I cannot get links to open when using Nextcloud client (web login page > into your browser or local folders) or I just tested with this command: > > xdg-open /home//Téléchargements > > This has no effect and I am unsure how best to debug this. > Any clue would be appreciated (even it it means reaching out to KDE > contributors) > > -- > Matthieu Hi, xdg-open in Debian (xdg-utils 1.1.3-4.1) doesn't support Plasma 6 (KDE6). It is fixed in xdg-utils upstream. The missing part is in commit https://cgit.freedesktop.org/xdg/xdg-utils/commit/scripts/xdg-open.in?id=c10cdaf8a03997cc18e51ee6299f0dcc02c34870 -- Sami Erjomaa
