Re: Capslock / Numlock indicator not work in KDE (& sddm)
On 11/28/19 2:05 AM, luca.pedrielli wrote: have rebuilded kguiaddons-5.62 on my pc. a kmodifierkey_xcb.so is genereted, but non included in the .deb, so I have copied it in /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/ and the error is gone. logout/login and the key indicator(in some way) works. pkg problem? Saluti, Luca Pedrielli Hi Luca, I upgraded to see the problem, and then downgraded 'libkf5guiaddons5' to buster, did a 'apt-mark hold' on the package and solved the problem. Now I guess we wait for this group calling itself debian "linux" to catch up. I run plasma5.17, framework5.64, qt5.12 on a couple other systems, never seen this problem before. Thanks for pointing to the problem. -- Jimmy Johnson 19.09.KDE5 - Intel i7-3540M - EXT4 at sda10 Registered Linux User #380263
Re: Capslock / Numlock indicator not work in KDE (& sddm)
On 11/26/19 4:06 PM, Franklin Weng wrote: Jimmy Johnson 於 2019/11/27 上午6:55 寫道: On 11/26/19 11:26 AM, Shai Berger wrote: For some reason, both Jimmy and Luca insist on connecting this to the wrong problem: On Tue, 26 Nov 2019 01:30:01 -0800 Jimmy Johnson wrote: On 11/25/19 7:10 AM, Franklin Weng wrote: luca.pedrielli 於 2019年11月25日 週一 22:44 Numlock problems had already been reported https://lists.debian.org/debian-kde/2019/09/msg00033.html Not sure, but it looks like not the same problem. My problem is about the indicator not the status itself. The NumLock/Capslock status is correct according to the xset -q. The settings for numlock have changed in testing kde5. I think the systemsettings, input device module is suppose to be handling numlock on/off at sddm start. And Luca, later: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941505 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940872 Everything Luca and Jimmy are mentioning is about the state of numlock when sddm or plasma start. This is *not* what Franklin or I are talking about. We are talking about Caps/Num Lock being at the state they should be, as set by pressing the relevant keys. It is only the visual indicators which are not working -- the systray icons in plasma, and the caps-is-on warning in the lock or login screen. Listen to me! Remove your numlockx software, https://i.imgur.com/G4hSFii.png go to /etc/sddm.conf and change it to on or off, https://i.imgur.com/c4k4yTd.png go to systemsettings and make sure keyboard, numlock is set to no change. https://i.imgur.com/c3x5oSt.png Do it and then come back https://i.imgur.com/EMjLxsy.jpg => Login screen (taken from my phone, after all the settings above were done of course), the CAPSLOCK warning is always shown https://i.imgur.com/saGAqD7.png => Status of Capslock is off, Numlock is on, but the indicator (red frame in left and bottom-right corner) shows nothing. Have you tried a different keyboard layout? Also I've seen a new a package named 'numlock', remove it if it's installed. and tell me I don't know what you're talking about. until then stuff a sock! You don't know what I'm talking about. So do I have to stuff a sock now? I don't know what you're doing. You look like a ms windows keyboard jockey in a gui environment. So until I know different, keep the sock stuffed. -- Jimmy Johnson Devuan Beowulf KDE5 - AMD A8-7600 - EXT4 at sda8 Registered Linux User #380263
Re: Capslock / Numlock indicator not work in KDE (& sddm)
On 11/26/19 11:26 AM, Shai Berger wrote: For some reason, both Jimmy and Luca insist on connecting this to the wrong problem: On Tue, 26 Nov 2019 01:30:01 -0800 Jimmy Johnson wrote: On 11/25/19 7:10 AM, Franklin Weng wrote: luca.pedrielli 於 2019年11月25日 週一 22:44 Numlock problems had already been reported https://lists.debian.org/debian-kde/2019/09/msg00033.html Not sure, but it looks like not the same problem. My problem is about the indicator not the status itself. The NumLock/Capslock status is correct according to the xset -q. The settings for numlock have changed in testing kde5. I think the systemsettings, input device module is suppose to be handling numlock on/off at sddm start. And Luca, later: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941505 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940872 Everything Luca and Jimmy are mentioning is about the state of numlock when sddm or plasma start. This is *not* what Franklin or I are talking about. We are talking about Caps/Num Lock being at the state they should be, as set by pressing the relevant keys. It is only the visual indicators which are not working -- the systray icons in plasma, and the caps-is-on warning in the lock or login screen. Listen to me! Remove your numlockx software, go to /etc/sddm.conf and change it to on or off, go to systemsettings and make sure keyboard, numlock is set to no change. Do it and then come back and tell me I don't know what you're talking about. until then stuff a sock! -- Jimmy Johnson Devuan Beowulf KDE5 - AMD A8-7600 - EXT4 at sda8 Registered Linux User #380263
Re: Capslock / Numlock indicator not work in KDE (& sddm)
On 11/25/19 7:10 AM, Franklin Weng wrote: luca.pedrielli 於 2019年11月25日 週一 22:44 寫道： Il 24/11/19 02:26, Franklin Weng ha scritto: Hi, I'm using Debian testing and run KDE Plasma 5 (Framework 5.62.0, Qt 5.12.5, xcb window system, Application 19.08.1, kde-plasma-desktop version 5:104). Originally the indicator worked: in sddm login screen it would show warning when Capslock is ON; after logging into Plasma session a small icon would show beside the system tray when Capslock is ON. However from some day it didn't work anymore. The current status of my system is: - In sddm login screen, the Capslock ON warning *always* shows. - In Plasma the keyboard indicator plasmoids (org.kde.plasma.keyboardindicator) shows nothing no matter what the capslock/numlock status is. - Using xset -q I can get *correct* Capslock/Numlock status. Using xev I can see events of Capslock key being pressed and released. It looks like no problem in X window level, but the status does not pass to sddm/plasma correctly. Any idea or suggestion for finding or fixing the problem? Regards, Franklin No suggestion, but I can confirm this behaviour. Numlock problems had already been reported https://lists.debian.org/debian-kde/2019/09/msg00033.html -- Saluti, Luca Pedrielli Not sure, but it looks like not the same problem. My problem is about the indicator not the status itself. The NumLock/Capslock status is correct according to the xset -q. I'm without systemd here, using sysvinit, so I was hesitant to speak up. The settings for numlock have changed in testing kde5. I think the systemsettings, input device module is suppose to be handling numlock on/off at sddm start. Go to "/etc/sddm.conf" and look for "Numlock=none" for me that was the default I found and I changed it to on. The options are none, off and on. I also go to systemsettings/input device just to make sure the settings say to leave numlock along. Now it comes on at boot and stays on without installing any extra numlock software. I hope that helps. -- Jimmy Johnson Slackware64 11.19.KDE5 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
Re: Cant create unique app launcher per activity in plasma 5.8 in debian stable
On 08/30/2018 07:49 PM, aprekates wrote: Ok. I discovered that in the first tab (General) of a launcher-edit window the name must be unique. In the third tab (Application) there is again a field for the app's name but that's not relevant to my issue. So if launcherA(right_click) -> General -> Appname=FOO launcherB(right_click) -> General -> Appname=FOO ..then you have one launcher (as we can see in /.local/share/applications) and whatever you change in the other tabs will eventually change the same file. Hope that will help anyone with the same issue. On 30/08/2018 11:41 μμ, aprekates wrote: in plasm 5.8 LTS used in debian stable i create a plasma widget and i put firefox (A) in it. I do the same in another activity (B). Now if i try to change the command line in firefox A the same change will happen to B. I want each activity to have its own custom firefox icon. Alexandros If I understand you? I do the same in a different way. I do a menu edit and add the app I want and then use a quicklaunch widget and add the app to it from the menu. -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda2 Registered Linux User #380263
Re: Update for i965-va-driver-shaders - Bug -
On 04/13/2018 10:45 AM, Martin Steigerwald wrote: Hi Jimmy. Jimmy Johnson - 13.04.18, 18:04: i965-va-driver-shaders in Sid, Buster and Ubuntu 18.04LTS has an upgrade, if applied will remove the i965-va-driver, the upgrades been there for a week. What's up with this? % apt changelog i965-va-driver-shaders […] [ Sebastian Ramacher ] * New upstream release. * debian/: - Revert the split and switch back to full driver. Thanks to Timo Aaltonen. This package now Conflicts+Replaces i965-va-driver. -- Sebastian Ramacher <[…]> Tue, 20 Mar 2018 21:49:53 +0100 If that's the case then we have a bug. Package details state "depends on 1965-driver" and "enhances i965-driver" Cheers, -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263
Re: A recent update messed up application preferences
On 04/03/2018 05:15 PM, Shai Berger wrote: Hi, I'm using Testing, and a recent update -- I'm not sure which, there seem to have been both a large KDE update and a large Gnome/Cinnamon update in the last few days -- have messed up my application preferences. Thus, I suddenly found Gimp as my default PDF reader (when it has been Okular ever since Okular was available in Debian), and a ".jpeg" image suddenly opened in ImageMagick instead of Gwenview in my mail application (Claws Mail), although Gwenview was still chosen by xdg-open. Can anyone give me some clue where to look for the culprit? It's easy to fix, choose open with, choose the application you want and check the box to remember, done. -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263
Re: Why is Konqueror part of `kde-baseapps`
On 03/03/2018 02:59 AM, Albin Otterhäll wrote: Hi! Why is `konqueror`, `kwrite` and `keditbookmarks` part of the metapackage `kde-baseapps`? This seems to be packages that nobody needs or uses, but is part of all predefined metapackages (by being part of `kde-baseapps`). I agree, unless you are planing on bringing back konqueror file-management, dump it, it's useless. Cheers, -- Jimmy Johnson Debian Buster - KDE Plasma 5.12.2 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
Re: Konqueror is hidden and can't be brought back, but is still running after "Quit"
On 01/25/2018 03:05 PM, Xavier Brochard wrote: Le jeudi 25 janvier 2018, 23:33:57 CET Nuno Oliveira a �crit : [ konqueror] I'm not sure if it is still (well) maintained or will be migrated at all to Qt5. Well Konqueror is more or less dead and should be soon replaced by Qupzilla as a KDE project. QupZilla is incubating as a KDE project since August under the new "*Falkon" *name See https://community.kde.org/Incubator/Projects/Falkon "During the Akademy 2017 Konqueror BoF, the ex-maintainer of Konqueror, David Faure, proposed to integrate QupZilla into KDE in order to replace the aging Konqueror. (His reasoning is that QupZilla is already much more advanced in terms of webbrowsing features, and there is almost nobody working in Konqueror, so there is no point in duplicating efforts). " Regards Xavier We have some problems here, KDE Dolphin is using SUDO User so viewing root files and as user it's more difficult for making systemsettings5 changes for root look and feel you need gksu to get oxygen icons in synaptic. With Konqueror you can still use SU and view root but not with Dolphin. As for browsing the web with a KDE app I've never done that and never will. Konq is a simple file manager that I've used for something like 20 years or more, getting the filter bar was a nice add-on. Cheers, -- Jimmy Johnson Ubuntu 18.04 LTS - KDE Plasma 5.11.4 - Intel Core i5-3320M - EXT4 at sda5 Registered Linux User #380263
Re: Konqueror is hidden and can't be brought back, but is still running after "Quit"
On 01/25/2018 05:32 AM, inkbottle wrote: Hi, You might want to try that: Open Konqueror check "ps -e|grep -i konqueror" Go in Konqueror menu and do "quit" check "ps -e|grep -i konqueror", for me it's still running From that point on, either from plasma menu, or from command line, I cannot bring back Konqueror window. If I kill it, then I can have it again though. I've got latest sid version I believe. I haven't searched for upstream bug yet. It seems it is reproducible for another user at least. Chris I've been seeing things too, but this Sid. So I switched to start with Empty Session and put what I want to start in Auto Start with no problem and I have now done this with all my systems. Why you did not use KSysGuard to kill the app is beyond me. -- Jimmy Johnson Ubuntu 18.04 LTS - KDE Plasma 5.11.4 - Intel Core i5-3320M - EXT4 at sda5 Registered Linux User #380263
Re: Plasma 5.11 in experimental
On 01/26/2018 07:46 AM, Martin Steigerwald wrote: Hello. I just got aware of it and its actually installable. Did not see many visible changes so far. Systemsettings has been revamped, but as I read one can also go to back to the old look. Thanks, In systemsettings click on configure or the wrench in the upper left corner depending on your current view, we've been using the icon view as default. -- Jimmy Johnson Ubuntu 18.04 LTS - KDE Plasma 5.11.4 - Intel Core i5-3320M - EXT4 at sda5 Registered Linux User #380263
Re: New bug for i965/960M
On 11/18/2017 11:40 PM, NIkitushkin Andrey wrote: Hello! 1. I have new bug for i965/960M chipset. 2. I see: I see https://lists.debian.org/debian-user/2017/02/msg00800.html . After use new kernel 4.9 from Debian repositories my system not halt. Thanks! ))) 3. Oh! After enables xtables modules for Debian Linux kernel 4.9 my system halt again (stop error on booting). Please inspect this bug and fix! 4. You not answer on my bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844460 of last ONE YEAR!!! Please see this my links for detail information about this bug for i960M chipset. 5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100. Best regards, Nikitushkin Andrey. Suggestions, if you are using ext4 make sure you have e2fsprogs and its recommends/suggest installed. Make sure you have all linux firmware and drivers installed or you are going to have problems, it may not boot at all. Cheers, -- Jimmy Johnson Buster - KDE Plasma 5.10.5 - Intel T5250 - GM965/GL960 - EXT4 at sda7 Registered Linux User #380263
Re: Plasma and qt apps broken after upgrade in Testing
On 10/17/2017 06:58 AM, devfra wrote: On marted� 17 ottobre 2017 13:18:25 CEST Andy G Wood wrote: The nvidia driver update was also in my list of upgrades for the day. For me version 375.82-5 is also working fine now. I reinstalled the nvidia driver and nothing broke. Evidently there was a dependency issue with other packages during the upgrade. I updated another machine with Testing without nvidia driver and the issue didn't appear. So everything is ok now! My problem was also the nvidia driver install, I took your approach and removed nvidia and did a full upgrade and then reinstalled nvidia and all is well. I find it interesting that we where able to reinstall and not have any leftover pieces. :) 5.10.5 on Buster now, woot! -- Jimmy Johnson Debian Buster - KDE Plasma 5.10.5 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
Re: Plasma and qt apps broken after upgrade in Testing
On 10/17/2017 03:14 AM, devfra wrote: Hi list I upgraded Testing this morning and now Plasma 5 and all the qt applications are broken. Sddm does not work, it just shows me a black screen and the mouse cursor. I am also unable to start Plasma with another display manager (lightdm in my case). I am now in an xfce session, all the qt applications do not work and give me always the same error: kcalc: symbol lookup error: /usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current transmission-qt: symbol lookup error: /usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current kwrite: symbol lookup error: /usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current I tried to downgrade the liblgl1 and libglx0 packages to a previous version from debian snapshot but the problem remains. This [0] is the list of the packages upgraded this morning. Thanks in advance for any help. [0] https://paste.debian.net/hidden/938ee68a/ Thinks for the heads up, plasma-workspace is currently broken and of course that will break the whole kde-plasma-desktop and will get fixed soon, I hope, trust, etc. :) Thanks, -- Jimmy Johnson Debian Buster - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
bugs.debian.bug=851175
"Debian Bug report logs - #851175 plasma-workspace - All shell packages missing. This is an installation issue, please contact your distribution - missing dependency on plasma-desktop-data" I got hit with this one "All shell packages missing." while updating a Buster install today, it started with dpkg not being able to overwrite package "desktop-profiles" so instead of doing a force install I chose to purge the package and completed the update then reinstalled desktop-profiles, on reboot, after login is when I got hit with "All shell packages missing." and plasma would not start and it seems to be ambiguous from what I get searching the net, in my case the problem was package "desktop-profiles" being installed and purging desktop-profiles solved the problem and Plasma starts fine now. Why would "desktop-profiles" being installed keep plasma from starting? Upgrade-system said the system was completely updated and clean with no orphaned packages before I rebooted. -- Jimmy Johnson Debian Buster - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
Re: Plasma 5.10 in Testing?
On 10/12/2017 04:26 AM, Libor Klepáč wrote: Hi, I see those sometimes, starting few minutes after resume. It's fixable by `kquitapp plasmashell` & run it again from krunner. I don't know when it started, i have to candidates: 1) after upgrading to Plasma 5.10 2) after enabling GPU accel in firefox My GPU is VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) BTW: is it safe to upgrade to latest MESA, pulling in libegl1? Last time i tried, it broke GPU acceleration and also video acceleration. There are still some bug reports opened againts MESA. I have two Buster systems on my Haswell fully upgraded, I did have a update problem with dpkg not over writing package desktop-profiles so I purged desktop-profiles, completed the update and then reinstalled desktop-profiles. After reboot I could not start plasma with Error (All shell packages missing.), I could not repair the problem and then got the idea that maybe re-purging desktop-profiles may fix the problem and it did, so now I have two buster systems completely updated working fine. So I do have the latest mesa in buster and all is well, but I never have had a problem with this Haswell. Good luck, -- Jimmy Johnson Debian Buster - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda7 Registered Linux User #380263
Re: Bug#1 Freeze - Re: Intel i965
On 02/10/2017 06:58 PM, Jimmy Johnson wrote: On 02/10/2017 07:54 AM, debian-kde@lists.debian.org wrote: "Re: Bug#1 Freeze" Jimmy Johnson doc "Mine is an Intel Mobile GM965/GL960 Integrated Graphics and it's now working swell with the Sid 4.8.0-2 kernel but not as quick to load as the 4.7.0-1 kernel which works with no problem. In Stretch the 4.8.0-2 kernel is freezing the system, 4.7.0-1 kernel works swell - Intel Mobile GM965/GL960 Integrated Graphics. Plasma and SDDM." Here's an update for the i965, the linux-image-4.7 is no longer in the reposes, but is still on my laptop. linux-image-4.8 and 4.9 work only if I keep pressing ctrl+alt+F1, F2, F7, etc., way to much regression. Sometimes it will do a first boot without assistance from me but on the reboot will lockup without assistance. I'm being forced to use the linux-image from Jessie(works swell) in order to get updates. jessie-backports 4.8 and 4.9 do not work with plasma on the i965. If you need testing of assistance let me know. Hello, Here's an update, testing current kernels for Stretch 4.9.0-3, Buster 4.12.0-2 and Sid/Testing 4.13.0-1 they are all working swell, as for the regression, as long as I don't look there is none. As far as I'm concerned we can close this bug. Thank you, great job! -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.10.5 - Intel Core 2 Duo T5250 - EXT4 at sda8 Registered Linux User #380263
KDE Plasma Date & Time Format
In KDE4 I use the long date with the short day: "Mon, September 19, 2017". Is there an easy way to do this in Plasma5? Even better would be long date with short day and short month: "Mon, Sep 19, 2017" Is there a config file I can edit? I have spent my day looking at locals, etc until I have a headache and have made no headway with this at all. Thanks, -- Jimmy Johnson Debian Stretch - KDE Plasma 5.8.6 - AMD A8-7600 - EXT4 at sda6 Registered Linux User #380263
Re: Spectacle
On 09/16/2017 03:08 PM, Jimmy Johnson wrote: While taking a timed snapshot I notice I could not access the panel or tray, they seemed to be locked, after the shot was taken access to panel and tray was restored, but spectacle was of no use for the timed snapshot I wanted to take. Is this a bug or by design? Plasma Unstable. Thanks for all the responses. I have made a discovery, I use the Qt-Curve widget style. On a system that was still using the Oxygen widget style, normally I only use the oxygen icons, but while using the oxygen widget the panel and tray where behaving erratic/jumpy/fuzzy while taking a timed-snapshot with spectacle. I had already done the same on some other systems using stretch, buster and sid, so I changed the setting to use the qt-curve widget and the change was amazing and all was extremely stable and now spectacle is stable on all my plasma-5 systems using qt-curve while taking a timed-snapshot using spectacle. Cheers, -- Jimmy Johnson Debian Stretch - KDE Plasma 5.8.6 - AMD A8-7600 - EXT4 at sda6 Registered Linux User #380263
Re: Spectacle
On 09/17/2017 01:59 AM, Martin Steigerwald wrote: Hello Jimmy. Jimmy Johnson - 16.09.17, 15:08: While taking a timed snapshot I notice I could not access the panel or tray, they seemed to be locked, after the shot was taken access to panel and tray was restored, but spectacle was of no use for the timed snapshot I wanted to take. Is this a bug or by design? Plasma Unstable. Hmmm, I can reproduce when snapshotting the whole screen. However when I set snapshotting the active window and select the tray / panel which still slides out from its hidden position just fine it doesn�t appear on the resulting screenshot. But I think that may be by design. When I select window under mousepointer I am able to snapshot the control panel with systray just fine with a timed snapshot. However this all is with kde-spectable package 17.08.1-1 from experimental. Thanks, It will probably be fixed with the next release or the one after..A lot of things don't get fixed until after release too and the reason us old farts use old systems for our day to day. -- Jimmy Johnson Ubuntu 12.04 LTS - KDE Plasma 4.8.5 - EXT4 at sda5 Registered Linux User #380263
Re: Spectacle
On 09/17/2017 02:00 AM, Martin Steigerwald wrote: Jimmy Johnson - 16.09.17, 15:08: Ubuntu 12.04 LTS - KDE Plasma 4.8.5 - EXT4 at sda5 Registered Linux User #380263 By the way, there are different channels for Ubuntu support. But I bet you do not use this old KDE Plasma 4.8.5 version anymore as… well back then it was still ksnapshot. That's my sig file martin and has nothing to to do with Debian Unstable and what I was reporting. Ubuntu 12.04 LTS is far from being unstable and what I use day to day, other systems I use day to day are 14.04 LTS it's my main system on all computers and 16.04 LTS is what I use for my multimedia system, I love using old systems, they just work after setup and normally only need to be setup once. :) I also have Jessie, Stretch, Buster and Sid installed, all of these plus more are installed on many computers here, you may see most anything in my sig file, it's there for my reference and your amusement. What you don't see are other peoples sig files, you know the ones who are running Windows, you know the ones who hate Linux and are working hard at destroying Linux. Maybe you should worry more about what you can't see than harmless things you can see. I'm good with old systems until the year 2025 before I have to worry about using the unstable stuff I'm testing today. And Ksnapshot does NOT have the problem I saw with Spectacle, I use Ksnapshot in Plasma 5.8.7 and anything older. Does anybody know why we are using Spectacle and not Ksnapshot? A good reason and not just because it's the default. -- Jimmy Johnson Ubuntu 12.04 LTS - KDE Plasma 4.8.5 - EXT4 at sda5 Registered Linux User #380263
Spectacle
While taking a timed snapshot I notice I could not access the panel or tray, they seemed to be locked, after the shot was taken access to panel and tray was restored, but spectacle was of no use for the timed snapshot I wanted to take. Is this a bug or by design? Plasma Unstable. -- Jimmy Johnson Ubuntu 12.04 LTS - KDE Plasma 4.8.5 - EXT4 at sda5 Registered Linux User #380263
Re: Problems with keyboard after upgrade to Plasma >5.6
On 09/16/2017 06:30 AM, Claudio Ferreira wrote: Hi 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 prepared a USB with a live debian and tried again. When I try to do the test, works fine. How my language is brazilian portuguese and my keyboard is a US layout, I select US with dead keys. The simple question to select a keyboard, starts my problem. Without this, works fine. Some idea or suggestion? I haven't idea of how to debug this problem. What can I send to give a better idea? Since now, thanks by any help. Regards, Claudio Ferreira I'm thinking 'search folder updater', 'background services' in systemsettings5 maybe the slow down, maybe try un-checking/disable it to see if that helps0. Also you may want to disable Search in systemsettings5. I don't think they have anything to to do with kfind and you will still be able to search for things and start things with the runner. -- Jimmy Johnson Ubuntu 12.04 LTS - KDE Plasma 4.8.5 - EXT4 at sda5 Registered Linux User #380263
Re: Plasma 5.10.5 coming to unstable
On 09/12/2017 12:45 PM, Martin Steigerwald wrote: Hello. As subject says. I also see some more KDE Application 17.08 packages uploaded to experimental, like Qt5 based Konqueror (yay!) So far Konqueror File Management is still qt4 and working. As far is I'm concerned that's not a bad thing, if we upgrade to qt5 can we keep File Management is what I'm concerned with. as well as Dolphin and Konsole. KDEPIM 17.08 does not yet appear to be fully build in experimental yet. I hope to see it soon. Thanks, Cheers! -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.10.5 - AMD A8-7600 - EXT4 at sda8 Registered Linux User #380263
Re: libblockdev-part2
On 08/31/2017 10:58 AM, Andrey Rahmatullin wrote: 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 It some how became upgradable by it's self? By just clicking on the package I was able to upgrade it with no change to gdisk and no new sgdisk. There was some other libblock* upgrades but I did not click on them, yet libblockdev-part2 upgrade was now installable. Confused. -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda1 Registered Linux User #380263
Re: libblockdev-part2
On 08/31/2017 12:28 PM, Martin Steigerwald wrote: Jimmy Johnson - 31.08.17, 12:16: On 08/31/2017 11:15 AM, Diederik de Haas wrote: On donderdag 31 augustus 2017 10:25:23 CEST Jimmy Johnson wrote: As you can probably see, I'm trying to figure what is stopping libblockdev-part2 from being upgraded.. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873748 But it has been fixed now, so the updated binaries shouldn't take long to arrive in the archives and thereby resolve the dependency issue. Thank you, Is it safe to assume that sgdisk will replace gdisk? If so, will it be a drop-in replacement or more complicated? sgdisk *is* in the gdisk package and is used for scripting purpose. Just view manpage of it. I recommend to use either fdisk or cfdisk from util-linux meanwhile. They both are based on the same partitionining code meanwhile and support GPT. Or parted if you prefer that. Just look at the output of "apt changelog gdisk" to see how dated the Debian package for gdisk is. The upstream webpage has a newer version, but it is not yet packaged in Debian archive. So or so… this is off-topic here. So I suggest to ask partitioning related questions on debian-user instead. Martin, you can nicely share or keep quit, you insist on being my personal thorn since I posted to a thread more than two years ago, I'm attempting to learn the movement of a package here and not something about partitioning, maybe you are more dense than me, but from the start you have been a thorn. If you want to continue your argument you are welcome to post to me personal, I will not block you and I will be truthful. By the way I have never learned a thing from you except not to post to you, you only irritate the hell out of me. regards, -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda1 Registered Linux User #380263
Re: libblockdev-part2
On 08/31/2017 11:15 AM, Diederik de Haas wrote: On donderdag 31 augustus 2017 10:25:23 CEST Jimmy Johnson wrote: As you can probably see, I'm trying to figure what is stopping libblockdev-part2 from being upgraded.. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873748 But it has been fixed now, so the updated binaries shouldn't take long to arrive in the archives and thereby resolve the dependency issue. Thank you, Is it safe to assume that sgdisk will replace gdisk? If so, will it be a drop-in replacement or more complicated? -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda1 Registered Linux User #380263
Re: libblockdev-part2
On 08/31/2017 10:02 AM, Andrey Rahmatullin wrote: 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". Oh! 3.1 or better. As you can probably see, I'm trying to figure what is stopping libblockdev-part2 from being upgraded.. Thank you for your patience with me. -- Jimmy Johnson Ubuntu 14.04 LTS - KDE 4.13.2 - AMD A8-7600 - EXT4 at sda1 Registered Linux User #380263
Re: libblockdev-part2
On 08/31/2017 09:23 AM, Andrey Rahmatullin wrote: On Thu, Aug 31, 2017 at 09:04:28AM -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? -- Jimmy Johnson Ubuntu 14.04 LTS - KDE 4.13.2 - AMD A8-7600 - EXT4 at sda1 Registered Linux User #380263
libblockdev-part2
libblockdev-part2 requires libparted2-v3.1, current libparted2 is v3.2. How is this fixed? Thank you and cheers! -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda1 Registered Linux User #380263
Re: Qt 5.7.1 => 5.9.1
On 08/30/2017 11:40 AM, Jimmy Johnson wrote: On 08/30/2017 10:46 AM, Lisandro Damián Nicanor Pérez Meyer wrote: On 30 August 2017 at 11:49, Boris Pek <tehnic...@yandex.ru> wrote: I have just rebuild plasma-integration with Qt 5.9.1 in my system and this have solved the problem for me. So when binNMU'ed packages will arrive archive the issue will gone. This should be the case already. It happens that qt (upstream) had some symbols wrongly marked (fixed in 5.9) and some packages where missing binNMUs. Plasma-integration upgrade is in the repos now, what where the missing packages I should look for? I had wrong icons on one system, reset them and the icons where fixed. Good job, it's great to have things work! Thank you and cheers! -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda1 Registered Linux User #380263
Re: Qt 5.7.1 => 5.9.1
On 08/30/2017 10:46 AM, Lisandro Damián Nicanor Pérez Meyer wrote: On 30 August 2017 at 11:49, Boris Pek <tehnic...@yandex.ru> wrote: I have just rebuild plasma-integration with Qt 5.9.1 in my system and this have solved the problem for me. So when binNMU'ed packages will arrive archive the issue will gone. This should be the case already. It happens that qt (upstream) had some symbols wrongly marked (fixed in 5.9) and some packages where missing binNMUs. Plasma-integration upgrade is in the repos now, what where the missing packages I should look for? -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda1 Registered Linux User #380263
Re: Warning! Current udisks2 in Sid is broken
On 08/30/2017 10:56 AM, Andrey Rahmatullin wrote: 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. I got it and did another upgrade on another system, gdisk was orphaned after the dist-upgrade, so I removed it, more to see what would happen and only part of the desktop would work, so I apt install gdisk and reboot, gdisk was no longer orphaned and desktop came up complete. So even if we don't do text mode partitioning gdisk is still needed to complete the system. -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda1 Registered Linux User #380263
Re: Warning! Current udisks2 in Sid is broken
On 08/30/2017 07:52 AM, 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. Thank you Andrey, I just want people to know what you say and that is the needed package/s are not yet in the repos and that it should be fixed soon. -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda1 Registered Linux User #380263
Re: Qt 5.7.1 => 5.9.1
On 08/30/2017 07:49 AM, Boris Pek wrote: I have just rebuild plasma-integration with Qt 5.9.1 in my system and this have solved the problem for me. So when binNMU'ed packages will arrive archive the issue will gone. Boris, is that something I can do too? Do you have a recipe for the rebuild? In my system it was just: dget -d http://deb.debian.org/debian/pool/main/p/plasma-integration/plasma-integration_5.8.6-1.dsc sudo cowbuilder --update sudo cowbuilder --build plasma-integration_5.8.6-1.dsc | tee build.log sudo dpkg -i /opt/pbuilder/result/plasma-integration_5.8.6-1_amd64.deb If you really want to rebuild this package in your system you need to install and properly setup pbuilder or cowbuilder first. I would need to add source packages too? But I recommend you just wait until updated package (5.8.6-1+b1) will arrive into the mirror of Debian repo which you use. I will wait, maybe tonight I will give it a go. Best wishes, Boris Thank you Boris, I'm always willing to try something new and building a package is something I have not tried yet. :) -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda1 Registered Linux User #380263
Re: Warning! Current udisks2 in Sid is broken
On 08/30/2017 07:44 AM, Andrey Rahmatullin wrote: 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. I see, but the higher version is not in the repos, so it's not fixed!?! -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda1 Registered Linux User #380263
Re: Warning! Current udisks2 in Sid is broken
On 08/30/2017 07:00 AM, Andrey Rahmatullin wrote: 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? No, I have Sid version udisks2 2.7.2-1, why would I have a higher version? -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda1 Registered Linux User #380263
Re: Qt 5.7.1 => 5.9.1
On 08/30/2017 05:15 AM, Boris Pek wrote: I may add that usage of XDG_CURRENT_DESKTOP environment variable is broken now in KDE applications from Sid, and because of it they look very ugly when launched outside plasmashell or via `ssh -X ..`. For example, dolphin lacks all file icons and icons at toolbar and menus. Plus it uses some strange theme (not breeze). Dolpin looks normal in my install. Have you tried to launch it in openbox session or via ssh? `export XDG_CURRENT_DESKTOP=KDE` for applying proper Qt settings does not work anymore. I have just found my old email [1] and looking at [2] I hope that this problem will be fixed soon. [1] https://lists.debian.org/debian-kde/2016/06/msg00034.html [2] https://buildd.debian.org/status/package.php?p=plasma-integration=unstable I have just rebuild plasma-integration with Qt 5.9.1 in my system and this have solved the problem for me. So when binNMU'ed packages will arrive archive the issue will gone. Boris, is that something I can do too? Do you have a recipe for the rebuild? Best wishes, Boris Cheers, -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda1 Registered Linux User #380263
Re: Warning! Current udisks2 in Sid is broken
On 08/30/2017 02:21 AM, Martin Steigerwald wrote: Martin Steigerwald - 30.08.17, 09:07: Put the package on hold. I wonder why this bug wasn�t set to a severity that makes it show up in apt- listchanges. #873627 udisks2 in sid apparently left me with a borked system in plasma(?) https://bugs.debian.org/873627 Andreas, the maintainer of the package, just uploaded an update to fix this issue. Thanks, No, it's not fixed, current dist-upgrade orphans gdisk and plasma will not start. But if you install these packages, libblockdev-fs2 libblockdev-part2 libblockdev-mdraid2 libblockdev-crypto2 libblockdev-loop2 libblockdev-swap2 gdisk and you will be up and running again. -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda1 Registered Linux User #380263
Re: Qt 5.7.1 => 5.9.1
On 08/27/2017 03:39 PM, Rubin Abdi wrote: Just did a safe-upgrade. Everything seems to be working ok (though something is a little slow with Chrome unstable). The only issue I've noticed is widget style is stuck on Breeze. Selecting any other styles seems to not be respected. Yes, I have seen this too. So far I have been able to work around, I use Oxygen theme and apply settings as Root too. Sometimes just reapplying the settings as User will work too. Also today I send a letter to the creator of kwin crystal theme, I pray the crystal look in plasma5 will be coming. Cheers, -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda1 Registered Linux User #380263
Re: Qt 5.7.1 => 5.9.1
On 08/24/2017 05:12 PM, Jimmy Johnson wrote: On 08/24/2017 10:03 AM, Lisandro Damián Nicanor Pérez Meyer wrote: On jueves, 24 de agosto de 2017 15:58:42 -03 inkbottle wrote: On Wednesday, August 16, 2017 8:56:52 AM CEST Martin Steigerwald wrote: Hello. Qt 5.9.1 hits unstable. Please be careful to wait till its complete. Even though <https://release.debian.org/transitions/html/qtbase-abi-5-9-0.html> and <https://release.debian.org/transitions/html/qtdeclarative-5-9-1.html> still says "partial", it appears those packages do exist for AMD64, and upgrade seems possible, as of right now... Chris Except for some KDE stuff like akonadi, so depending on what you have installed apt might want to remove stuff. We are working on it. I held 3 libc packages, everything else is cleanly upgraded. Thank you. I have 3 extra libc6 i386 packages on this system (libc6-dev-amd64:i386, libc6-i686:i386, libc6-xen:i386) They are not on any other of my four Sid/Testing systems, they are not installed but are reported to be in my repos. Why do they not show on the other systems? I can't seem to be rid of them and they are outdated too. But now all 4 systems are up to date. -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda1 Registered Linux User #380263
Re: Qt 5.7.1 => 5.9.1
On 08/24/2017 10:03 AM, Lisandro Damián Nicanor Pérez Meyer wrote: On jueves, 24 de agosto de 2017 15:58:42 -03 inkbottle wrote: On Wednesday, August 16, 2017 8:56:52 AM CEST Martin Steigerwald wrote: Hello. Qt 5.9.1 hits unstable. Please be careful to wait till its complete. Even though <https://release.debian.org/transitions/html/qtbase-abi-5-9-0.html> and <https://release.debian.org/transitions/html/qtdeclarative-5-9-1.html> still says "partial", it appears those packages do exist for AMD64, and upgrade seems possible, as of right now... Chris Except for some KDE stuff like akonadi, so depending on what you have installed apt might want to remove stuff. We are working on it. I held 3 libc packages, everything else is cleanly upgraded. Thank you. -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda1 Registered Linux User #380263
Re: jessie upgrade deemed very difficult + there is no simple way not to install konqueror
On 06/20/2017 01:26 PM, Shawn Sörbom wrote: On Monday, June 19, 2017 11:24:59 PM PDT inkbottle wrote: task-kde-desktop depends on kde-standard which depends on plasma-desktop which depends on kde-baseapps which depends on konqueror which depends on tons of difficult to understand seemingly outdated dependencies. The upgrade is very difficult In fact I give up the upgrade altogether. I'll have to come to it through another angle: There are tons of packages which I deem old and unnecessary, and I find no simple way not to install them. And there is no simple way not to install konqueror. Chris PS: Also aptitude put all automatically installed packages to satisfy dependencies in manually installed: hundreds of them. It is a very difficult upgrade. If you download the meta-package source for kde-baseapps, you could remove the konqueror dependency from the control file, bump the version number, and repack it. I know this isn't ideal, but if you are willing to invest time in the task, it is doable. Good luck, --Shawn In Synaptic this is a very easy problem to solve, in auto-remove select all packages and go to menu, package and uncheck auto-installed packages. I then run upgrade-system(uses deborphan) in the konsole to clean the mess up. Cheers, -- Jimmy Johnson Debian Sid/Testing - KDE Plasma 5.8.7 - Linux 4.9 - EXT4 at sda15 Registered Linux User #380263
Re: jessie upgrade deemed very difficult + there is no simple way not to install konqueror
On 06/19/2017 02:24 PM, inkbottle wrote: task-kde-desktop depends on kde-standard which depends on plasma-desktop which depends on kde-baseapps which depends on konqueror which depends on tons of difficult to understand seemingly outdated dependencies. The upgrade is very difficult If you are installing task-kde-desktop then of course it depends on most everything, if you want it slimmed down remove what you don't want or maybe you need help with that? In fact I give up the upgrade altogether. Bye. I'll have to come to it through another angle: There are tons of packages which I deem old and unnecessary, and I find no simple way not to install them. And there is no simple way not to install konqueror. You still here.. There are many other ways and DM's to install and no Konq to deal with, easy. Chris PS: Also aptitude put all automatically installed packages to satisfy dependencies in manually installed: hundreds of them. It is a very difficult upgrade. Only for someone who is difficult, no knowledge and obviously no fun. Cheers, -- Jimmy Johnson Debian Buster - Plasma Version 5.8.6 - EXT4 at sda17 Registered Linux User #380263
Re: improving the UX with the default KDE installation
On 05/18/2017 10:45 AM, Shawn Sörbom wrote: On Saturday, April 22, 2017 1:07:09 PM PDT fradev wrote: Hi everyone On 25/03/17 18:50:08 CEST, fradev wrote: Here are the dependencies of task-kde-desktop, on the right my suggestions. task-kde-desktop Depends: tasksel Depends: task-desktop Depends: kde-standard Depends: sddm Recommends: kdeaccessibility--> change to: Suggests Recommends: gnome-orca --> change to: Suggests Recommends: k3b --> change to: Suggests Recommends: k3b-i18n--> change to: Suggests Recommends: plasma-nm Recommends: kdesudo Recommends: libreoffice-kde Recommends: apper --> substitute with: synaptic Recommends: gimp Recommends: firefox-esr Recommends: libreoffice Recommends: libreoffice-help-en-us Recommends: mythes-en-us Recommends: hunspell-en-us Recommends: hyphen-en-us Recommends: system-config-printer Recommends: dragonplayer--> substitute with: vlc ..and I use Amarok and Kaffeine, I also install Gstreamer while removing all of VLC. On some systems where they lately require VLC to be installed to get Kaffeine I install SMplayer. -- Jimmy Johnson Debian Wheezy - KDE 4.8.4 - Intel G3220 - EXT4 at sda7 Registered Linux User #380263
Re: improving the UX with the default KDE installation
On 03/30/2017 08:37 AM, fradev wrote: If someone is still interested in the topic, here it is the list of dependencies required by the meta-package *kde-standard* (a dependency of *task-kde-desktop*) with my suggestions on the right. kde-standard Depends: akregator--> change to: Suggests Depends: ark Depends: dragonplayer --> substitute with: vlc Depends: gwenview Depends: juk --> change to: Suggests Depends: kaddressbook --> change to: Suggests Depends: kate --> change to: Suggests Depends: kcalc Depends: kde-plasma-desktop Depends: khelpcenter Depends: kmail--> change to: Suggests Depends: knotes --> change to: Suggests Depends: kopete --> change to: Suggests Depends: korganizer --> change to: Suggests Depends: kde-spectacle Depends: kwalletmanager Depends: okular Depends: plasma-dataengines-addons Depends: plasma-pa Depends: plasma-runners-addons Depends: plasma-wallpapers-addons Depends: plasma-widgets-addons Depends: polkit-kde-agent-1 Depends: sweeper --> change to: Suggests Breaks: Recommends: konq-plugins --> REMOVE Recommends: plasma-nm --> change to: Depends Suggests: Suggests: skanlite Comments and suggestions are welcome. I'm planning to submit a bug report (as a wishlist item) in the next days to see if the issue can be discussed with the maintainers and if something can be done in time for the release of Stretch. Francesco Hi, kde-standard installs more than 130 packages that I do not have on any of my more than 30 installed kde-plasma-desktop's, it's something I will not install for anybody, kmail along makes no sense, to me it should be a stand-along application including it's wizards without pulling in everything PIM. So to me it's not a usable mail client unless someone wants all of PIM. Another thing, on installing kmail it will ask where you want your folders. WHY? Why don't it have defaults and then if the user wants to move the stuff let them. To me KDE PIM is a big mess and always has been, but I never was an evolution user either. I won't use dolphin unless I'm forced to use it and konq-plugins is a needed package for konqueror. No auto-updating for me and sweeper over bleachbit is a haha. I'm no longer a business person, I just make text notes and copy to text a new recipe once in a while. I haven't needed office in a longtime, but when office is needed I think open software can't be beat, but is it needed on every computer? It's fine for kde-standard. When I started this, I wanted a small list of packages that will work when installed, kde-connect, bluetooth, wireless. I go to linux conference and deb.org person after deb.org person can not configure wireless and these things just need to work. KDE does somethings I think are totally WTF, like making oxygen-cursor mandatory, no matter how many different colors it has, it still has balls. I guess every version has to have a WTF or it would not be KDE. I hope you're having a great day! regards, -- Jimmy Johnson Debian Stretch - Plasma 5.8.6 - EXT4 at sda11 Registered Linux User #380263
Re: improving the UX with the default KDE installation
On 03/20/2017 06:41 AM, rhkra...@gmail.com wrote: On Monday, March 20, 2017 01:26:28 AM Jimmy Johnson wrote: On 03/17/2017 02:44 AM, fradev wrote: On 15/03/17 13:34:38 CET, Jimmy Johnson wrote: As for the rest of your post I agree and what we need is a "debian-plasma-desktop meta package" where it's tested and working including kconnect, wireless, bluetooth, vlc, pulse, etc. and keep pim to the minimal so the kitchen sink is not added but hardware is working the way it should be. That's the idea, a functional setup without redundant software. But is it possible to discuss such a proposal with the KDE team? Should I submit a bug report? Office= okular Hmm, somehow I don't think okular fulfills all the needs of office, in my mind being at least: word processor, spreadsheet, (simple) database, slide maker (ala powerpoint). So, I suggest, if you're going to mention / include Firefox (which you did) that you should also include Libre Office (or the other version of Libre Office--don't remember the name--does that still exist?) Well for one thing, someone wanting *office will be able to click install office, if you want it in you may as well put a typing tutor in there too. But kpat, frozen-bubble or texas-holdem would get more use from the average user. If we think positive some educational programs could be added, maybe somethings from child's play or a beginners coding app, it getting to some family member who has the yearn to be creative and productive would be a blessing. Maybe you don't know it, but the average user does not know how to use a keyboard, like putting your index fingers on the f and j keys, basic typing. -- Jimmy Johnson Debian Stretch - Plasma 5.8.4 - EXT4 at sda11 Registered Linux User #380263
Re: improving the UX with the default KDE installation
On 03/17/2017 02:48 AM, Martin Steigerwald wrote: Am Mittwoch, 15. März 2017, 19:01:16 CET schrieb fradev: The default KDE/Plasma 5 installation in Stretch, via task-kde-desktop, in my opinion doesn't provide the best user experience because of the many applications installed by default. While the experience with the Plasma desktop is pretty good, the same cannot be said for some KDE applications. To improve the situation, at least for me, in different occasions I had to: - manually install only the required KDE applications in a minimal Debian setup; - or manually remove all the unwanted KDE applications in the default KDE installation (and break meta-packages). There are metapackages of finer granularity available like kde-standard, kdegraphics, kdemultimedia. I'm looking at it from the eyes of an average computer user, what they expect and what to do if something is not there that they expect(synaptic), fixing users problems. kde-plasma-desktop covers most, no PIM, that is a personal choice, like you say,install kde-standard if you want PIM, the average user don't even know how to use a keyboard like we do, less a personal information manager. They want to play dvd's, cd's, watch youtube, play internet games and do Facebook, but with a lot of them even Facebook is over their head. "Point-N-Click or Tap" is all they want to do. The average user is not being creative or productive while using the computer nor on this list. regards, -- Jimmy Johnson Debian Sid/Testing - Plasma 5.8.6 - EXT4 at sda15 Registered Linux User #380263
Re: improving the UX with the default KDE installation
On 03/17/2017 02:44 AM, fradev wrote: On 15/03/17 13:34:38 CET, Jimmy Johnson wrote: As for the rest of your post I agree and what we need is a "debian-plasma-desktop meta package" where it's tested and working including kconnect, wireless, bluetooth, vlc, pulse, etc. and keep pim to the minimal so the kitchen sink is not added but hardware is working the way it should be. That's the idea, a functional setup without redundant software. But is it possible to discuss such a proposal with the KDE team? Should I submit a bug report? Francesco Hello, Francesco, I was thinking as Users we could discuss the options here first and then make a proposal of the "debian-plasma-desktop" to the KDE team. Utilities= ark, kcalc, kwrite, spectacle. System= bleachbit, kinfo, partition-manager or gparted, konsole, kwalletmanager, synaptic, dolphin. Personally I prefer konqueror and kdf over dolphin, maybe just because I've been using konq and kdf, it seems like forever. Settings= systemsettings Office= okular Multimedia= vlc, k3b Internet= firefox, kget Graphics= gwenview Things like sddm, plasma-networkmanager, kdeconnect, bluetooth and wireless should just work. -- Jimmy Johnson Debian Sid/Testing - Plasma 5.8.6 - EXT4 at sda15 Registered Linux User #380263
Re: improving the UX with the default KDE installation
On 03/15/2017 11:20 AM, fradev wrote: Hi everyone The default KDE/Plasma 5 installation in Stretch, via task-kde-desktop, in my opinion doesn't provide the best user experience because of the many applications installed by default. While the experience with the Plasma desktop is pretty good, the same cannot be said for some KDE applications. To improve the situation, at least for me, in different occasions I had to: - manually install only the required KDE applications in a minimal Debian setup; - or manually remove all the unwanted KDE applications in the default KDE installation (and break meta-packages). The main issue is that, in some cases, the applications required recursively by the package task-kde-desktop are obsolete, bugged and/or are useless redundancies. I'll make some examples at the end of this e-mail to better explain my point of view. I don't know if there are other users considering this as a usability issue but, in case, and if it is still possible to do something given the freeze of Stretch, it could be solved by changing the applications listed as dependencies and recommended by the meta-packages used in the default KDE installation in Stretch. I'm working just for myself on a list of packages that can be omitted or substituted and if someone is interested I can continue in this discussion. Regards Francesco EXAMPLES Let's start with Konqueror, installed by default in the case discussed above. Despite its history and how interesting it is, we all know that Konqueror nowadays lacks developer manpower. Its web engines are obsolete and probably not suitable anymore for a safe web surfing. Surely many of us will not suggest its usage, especially to newcomers. Firefox and Chromium are far superior web browsers and, besides, Firefox is recommended by task-kde-desktop and it is installed in the default KDE installation. Konqueror can also be used as a file manager but we already have Dolphin, that I'm sure is considered the de facto file manager in the Plasma desktop, installed along with it. Konqueror therefore is pretty much useless and redundant in a standard installation. If it so, why install it by default? Same story with some of the KDEPIM applications installed by task-kde-desktop/kde-standard. I'm a Kmail user but like many others I know that Kmail can be a difficult beast to handle, it has its bugs, akonadi could be a pain sometimes, and it lacks developer manpower too (and maybe it will be replaced by Kube in the future). Despite I'm using Kmail I will probably suggest to other users and newcomers to try Icedove/Thunderbird instead, or simply use their e-mail accounts via web browser if it is too much for them. In my opinion Kmail and friends should not be installed by default. There are other cases like that or minor redundancies, such as Kate and Kwrite installed altogether. Why install them both? I agree that konqueror is not needee as a web browser but it's great as a file manager and I think that dolphin is trying to do to much and is not neeed, konq was here first and is the KDE mascot on top of that. As for the rest of your post I agree and what we need is a "debian-plasma-desktop meta package" where it's tested and working including kconnect, wireless, bluetooth, vlc, pulse, etc. and keep pim to the minimal so the kitchen sink is not added but hardware is working the way it should be. Take a look at "neon-plasma-desktop meta package" and you will see what I'm talking about. And I was just thinking about this yesterday. -- Jimmy Johnson KDE Neon - Plasma 5.9.3 - EXT4 at sda7 Registered Linux User #380263
Re: plasma-discover-updater not available in stretch but available in sid
On 02/19/2017 01:26 PM, 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. Don't know how to solve this problem. Thank you for your work in debian and kde. You must be mistaken, I cannot currently find plasma-discover-updater in Sid or Stretch and this is the first time I've heard of the package. Ah, I see what the problem is, https://packages.debian.org/sid/kde/plasma-discover-updater if you scroll to the bottom of the page you'll see it's only available for kfreebsd. regards, -- Jimmy Johnson Debian Sid/Testing - Plasma Version 5.8.4 - EXT4 at sda17 Registered Linux User #380263
Re: Bug#1 Freeze - Re: Intel i965
On 02/19/2017 07:53 AM, Jimmy Johnson wrote: On 02/10/2017 06:58 PM, Jimmy Johnson wrote: On 02/10/2017 07:54 AM, debian-kde@lists.debian.org wrote: "Re: Bug#1 Freeze" Jimmy Johnson doc "Mine is an Intel Mobile GM965/GL960 Integrated Graphics and it's now working swell with the Sid 4.8.0-2 kernel but not as quick to load as the 4.7.0-1 kernel which works with no problem. In Stretch the 4.8.0-2 kernel is freezing the system, 4.7.0-1 kernel works swell - Intel Mobile GM965/GL960 Integrated Graphics. Plasma and SDDM." Here's an update for the i965, the linux-image-4.7 is no longer in the reposes, but is still on my laptop. linux-image-4.8 and 4.9 work only if I keep pressing ctrl+alt+F1, F2, F7, etc., way to much regression. Sometimes it will do a first boot without assistance from me but on the reboot will lockup without assistance. I'm being forced to use the linux-image from Jessie(works swell) in order to get updates. jessie-backports 4.8 and 4.9 do not work with plasma on the i965. If you need testing of assistance let me know. Hello, Update, linux-image-4.9.0-2-amd64 now in Sid is working with i965. regards, So.. I installed linux-image-4.9.0-2-amd64 to Stretch and it did not work, never got to sddm, just loads a black screen and then freeze/lockup/quits/dies/kaput. Also I worth mentioning, the regression while booting Sid makes it painful to watch it boot, but it will get to the plasma desktop. 4.7.0-1-amd64 is still installed and quick too, works swell. regards, -- Jimmy Johnson Debian St etch - Plasma 5.8.2 - Intel Mobile 965 - EXT4 at sda6 Registered Linux User #380263
Re: Bug#1 Freeze - Re: Intel i965
On 02/10/2017 06:58 PM, Jimmy Johnson wrote: On 02/10/2017 07:54 AM, debian-kde@lists.debian.org wrote: "Re: Bug#1 Freeze" Jimmy Johnson doc "Mine is an Intel Mobile GM965/GL960 Integrated Graphics and it's now working swell with the Sid 4.8.0-2 kernel but not as quick to load as the 4.7.0-1 kernel which works with no problem. In Stretch the 4.8.0-2 kernel is freezing the system, 4.7.0-1 kernel works swell - Intel Mobile GM965/GL960 Integrated Graphics. Plasma and SDDM." Here's an update for the i965, the linux-image-4.7 is no longer in the reposes, but is still on my laptop. linux-image-4.8 and 4.9 work only if I keep pressing ctrl+alt+F1, F2, F7, etc., way to much regression. Sometimes it will do a first boot without assistance from me but on the reboot will lockup without assistance. I'm being forced to use the linux-image from Jessie(works swell) in order to get updates. jessie-backports 4.8 and 4.9 do not work with plasma on the i965. If you need testing of assistance let me know. Hello, Update, linux-image-4.9.0-2-amd64 now in Sid is working with i965. regards, -- Jimmy Johnson Debian Sid/Testing - Plasma 5.8.4 - AMD64 - EXT4 at sda9 Registered Linux User #380263
Re: Bug#1 Freeze - Re: Intel i965
On 02/10/2017 07:54 AM, debian-kde@lists.debian.org wrote: "Re: Bug#1 Freeze" Jimmy Johnson doc "Mine is an Intel Mobile GM965/GL960 Integrated Graphics and it's now working swell with the Sid 4.8.0-2 kernel but not as quick to load as the 4.7.0-1 kernel which works with no problem. In Stretch the 4.8.0-2 kernel is freezing the system, 4.7.0-1 kernel works swell - Intel Mobile GM965/GL960 Integrated Graphics. Plasma and SDDM." Here's an update for the i965, the linux-image-4.7 is no longer in the reposes, but is still on my laptop. linux-image-4.8 and 4.9 work only if I keep pressing ctrl+alt+F1, F2, F7, etc., way to much regression. Sometimes it will do a first boot without assistance from me but on the reboot will lockup without assistance. I'm being forced to use the linux-image from Jessie(works swell) in order to get updates. jessie-backports 4.8 and 4.9 do not work with plasma on the i965. If you need testing of assistance let me know. -- Jimmy Johnson Debian Stretch - Plasma 5.8.4 - EXT4 at sda11 Registered Linux User #380263
Re: linux-image-4.9.0-1-amd64 + nvidia-legacy-304xx-driver + xserver-xorg-video-nouveau
On 01/23/2017 11:54 PM, David Baron wrote: On יום שני, 23 בינואר 2017 21:14:58 IST Jimmy Johnson wrote: On 01/14/2017 02:26 PM, Jimmy Johnson wrote: I'm happy to report linux-image-4.9.0-1-amd64 + nvidia-legacy-304xx-driver are currently working swell together. I just updated, rebooted. See no change. Window decorations still missing, both in openGL and Xrender. Yes, Plasma defaults to OpenGL 2.0 and it's not good that it's not working, you have to use XRender, but compositing is working. Once you switch to XRender you need to logout/login to see the change. -- Jimmy Johnson Debian Sid/Testing - Plasma Version 5.8.4 - EXT4 at sda17 Registered Linux User #380263
Re: linux-image-4.9.0-1-amd64 + nvidia-legacy-304xx-driver + xserver-xorg-video-nouveau
On 01/14/2017 02:26 PM, Jimmy Johnson wrote: And it still works. I updated Sid/testing a couple days ago and retested current drivers, "nouveau" is working with sddm okay but froze with plasma(colorful lighting bolts). Current nvidia-legacy-304xx is working with XRender and compositing enabled and I'm good with that, tested on Stretch too, now I can do clean upgrades and I'm happy. Thank you Debian! linux-image-4.9.0-1-amd64 is behaving like image-4.8 used to behave nouveau froze with plasma(colorful lighting bolts). Debian's nvidia-legacy-304xx-driver is freezing with plasma start. On first boot plasma loaded the vga driver giving me the wrong screen size and did not load the installed nvidia driver at all. Booting linux-image-4.9.0-1-amd64 and reinstalling nvidia-legacy-304xx-driver crashed plasma and so did nouveau. I'm back to using nvidia-legacy-304xx-driver and linux-image-4.8.0-2-amd64 with XRender and compositing enabled. I'm happy to report linux-image-4.9.0-1-amd64 + nvidia-legacy-304xx-driver are currently working swell together. Thank you Debian! -- Jimmy Johnson Debian Sid/Testing - Plasma 5.8.4 - AMD64 - EXT4 at sda9 Registered Linux User #380263
Re: linux-image-4.9.0-1-amd64 + nvidia-legacy-304xx-driver + xserver-xorg-video-nouveau
On 01/15/2017 10:48 AM, Felix Miata wrote: Jimmy Johnson composed on 2017-01-15 10:24 (UTC-0800): This is Nvidia GeForce7025 using nvidia-legacy-304xx-driver using the 4.8.0-2 kernel because it's the only thing I've found to work. I'm also using an Intel desktop with ATI Radeon 9550 graphics and an Intel Laptop with Intel 965 graphics and this my main desktop is Nvidia with Nvidia GeForce7025 graphics. They all have some kind of problem with Sid/testing and Stretch Plasma. They all have many systems installed and are ready to test suggestions. 965 is too old for Xorg's modesetting driver support. About the 9550 I don't know because I don't have its rv number or know the rv number breakpoint, but suspect it might be supported, as the next rv group is supported. NAICT your 7025 should be new enough to use it. The 965 is only using "ro", the 4.8 and 4.9 kernel are installed but not working. The 4.7.0-1 kernel works swell, if the newer kernel's are not working later on I will do something else, like import another kernel that will be updated. The ATI is basically working with the 4.8.0-2 kernel and with the 4.9 kernel if I assist it by pressing key's on the keyboard or it dies and it's just using "ro". The Nvidia has to use "ro nomodeset nouveau.modeset=0" and is working swell with the 4.8.0-2 kernel but dies with the 4.9 kernel. -- Jimmy Johnson Debian Sid/Testing - Plasma 5.8.4 - EXT4 at sda15 Registered Linux User #380263
Re: linux-image-4.9.0-1-amd64 + nvidia-legacy-304xx-driver + xserver-xorg-video-nouveau
On 01/14/2017 09:51 PM, Felix Miata wrote: Jimmy Johnson composed on 2017-01-14 20:37 (UTC-0800): Is something missing in the kernel, maybe a module? Which gfxchip do you have? This is Nvidia GeForce7025 using nvidia-legacy-304xx-driver using the 4.8.0-2 kernel because it's the only thing I've found to work. Did you miss that the _preferred_ FOSS video driver in Sid, modesetting, is integrated into the xerver and you haven't tried it? It might be your solution. If you purge nouveau and nvidia drivers modesetting should be used automatically unless your gfxchip is outside support scope. I don't know whether there actually has been an announcement for NVidia, but NAICT it did happen for Intel: http://www.phoronix.com/scan.php?page=news_item=Fedora-Xorg-Intel-DDX-Switch http://www.phoronix.com/scan.php?page=article=intel-modesetting-2017=1 http://www.phoronix.com/scan.php?page=news_item=Ubuntu-Debian-Abandon-Intel-DDX I'm also using an Intel desktop with ATI Radeon 9550 graphics and an Intel Laptop with Intel 965 graphics and this my main desktop is Nvidia with Nvidia GeForce7025 graphics. They all have some kind of problem with Sid/testing and Stretch Plasma. They all have many systems installed and are ready to test suggestions. -- Jimmy Johnson Debian Sid/Testing - Plasma Version 5.8.4 - EXT4 at sda17 Registered Linux User #380263
Re: linux-image-4.9.0-1-amd64 + nvidia-legacy-304xx-driver + xserver-xorg-video-nouveau
On 01/14/2017 02:26 PM, Jimmy Johnson wrote:
And it still works.
I updated Sid/testing a couple days ago and retested current drivers,
"nouveau" is working with sddm okay but froze with plasma(colorful
lighting bolts). Current nvidia-legacy-304xx is working with XRender
and compositing enabled and I'm good with that, tested on Stretch too,
now I can do clean upgrades and I'm happy. Thank you Debian!
linux-image-4.9.0-1-amd64 is behaving like image-4.8 used to behave
nouveau froze with plasma(colorful lighting bolts). Debian's
nvidia-legacy-304xx-driver is freezing with plasma start.
On first boot plasma loaded the vga driver giving me the wrong screen
size and did not load the installed nvidia driver at all. Booting
linux-image-4.9.0-1-amd64 and reinstalling nvidia-legacy-304xx-driver
crashed plasma and so did nouveau. I'm back to using
nvidia-legacy-304xx-driver and linux-image-4.8.0-2-amd64 with XRender
and compositing enabled.
Here are some bits from log files:
Kernel log:
[0.888338] rtc_cmos 00:02: alarms up to one year, y3k, 242 bytes
nvram, hpet irqs
System log:
[0.888542] rtc_cmos 00:02: alarms up to one year, y3k, 242 bytes
nvram, hpet irqs
First boot with new kernel:
1/14/17 7:51 PM jimmy-1 kernel [ 39.088148] NVRM: Your system is not
currently configured to drive a VGA console
1/14/17 7:51 PM jimmy-1 kernel [ 39.088157] NVRM: on the primary VGA
device. The NVIDIA Linux graphics driver
1/14/17 7:51 PM jimmy-1 kernel [ 39.088160] NVRM: requires the use of
a text-mode VGA console. Use of other console
1/14/17 7:51 PM jimmy-1 kernel [ 39.088162] NVRM: drivers including,
but not limited to, vesafb, may result in
1/14/17 7:51 PM jimmy-1 kernel [ 39.088164] NVRM: corruption and
stability problems, and is not supported.
1/14/17 7:51 PM jimmy-1 sddm[595] Running display setup script
"/usr/share/sddm/scripts/Xsetup"
1/14/17 7:51 PM jimmy-1 sddm[595] Display server started.
1/14/17 7:51 PM jimmy-1 sddm[595] Socket server starting...
1/14/17 7:51 PM jimmy-1 sddm[595] Socket server started.
1/14/17 7:51 PM jimmy-1 sddm[595] Greeter starting...
1/14/17 7:51 PM jimmy-1 sddm[595] Adding cookie to
"/var/run/sddm/{f73eabcb-08df-499d-83bc-90cf9a367ba1}"
NVRM: DRM init failed
Is something missing in the kernel, maybe a module?
--
Jimmy Johnson
Debian Sid/Testing - Plasma Version 5.8.4 - EXT4 at sda17
Registered Linux User #380263
linux-image-4.9.0-1-amd64 + nvidia-legacy-304xx-driver + xserver-xorg-video-nouveau
And it still works. I updated Sid/testing a couple days ago and retested current drivers, "nouveau" is working with sddm okay but froze with plasma(colorful lighting bolts). Current nvidia-legacy-304xx is working with XRender and compositing enabled and I'm good with that, tested on Stretch too, now I can do clean upgrades and I'm happy. Thank you Debian! linux-image-4.9.0-1-amd64 is behaving like image-4.8 used to behave nouveau froze with plasma(colorful lighting bolts). Debian's nvidia-legacy-304xx-driver is freezing with plasma start. On first boot plasma loaded the vga driver giving me the wrong screen size and did not load the installed nvidia driver at all. Booting linux-image-4.9.0-1-amd64 and reinstalling nvidia-legacy-304xx-driver crashed plasma and so did nouveau. I'm back to using nvidia-legacy-304xx-driver and linux-image-4.8.0-2-amd64 with XRender and compositing enabled. -- Jimmy Johnson Debian Sid/testing - Plasma 5.8.4 - nvidia-legacy-304xx - EXT4 at sda14 Registered Linux User #380263
Re: Is anyone else experiencing intermittent Plasma freezes as of very recently?
On 01/10/2017 08:10 AM, newbee...@nativobject.net wrote: Le 10/01/2017 à 00:29, fra...@inventati.org a écrit : Hi I'm on Debian Stretch but I'm not experiencing the issues you're discussing here. However I remember to have had similar issues with Plasma 5 and Intel drivers. As a workaround I used this /etc/X11/xorg.conf.d/20-intel.conf: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "sna" Option "TearFree""true" Option "DRI""3" EndSection Given also the previous messages about this topic, enabling DRI3 indeed seems to solve the problem. Anyhow, I discovered that the problem was with the i8xx i9xx display driver, provided by the automatically installed xserver-xorg-video-intel package, which could be not required by new hardware as reported in the description: This package provides the driver for the Intel i8xx and i9xx family of chipsets [...] The use of this driver is discouraged if your hw is new enough (ca. 2007 and newer). You can try uninstalling this driver and let the server use it's builtin modesetting driver instead. I tried to uninstall this package as suggested and the problem was solved: sudo rm /etc/X11/xorg.conf.d/20-intel.conf sudo apt purge xserver-xorg-video-intel && sudo reboot Ciao Francesco Hi, I'm currently testing it and no crash since 3h... But it couldn't work with my desktop which is using nouveau driver on an nvidia graphic card... Regards Mourad Yes, the symptoms are the same. For the Intel I use the old linux-image-4.7.0-1 with no problem. -- Jimmy Johnson Debian Sid/testing - Plasma 5.8.4 - AMD64 - EXT4 at sda9 Registered Linux User #380263
Re: Compositing Problem
On 01/07/2017 11:12 AM, David Baron wrote: On יום שבת, 7 בינואר 2017 4:36:59 IST Jimmy Johnson wrote: On 10/19/2016 11:33 PM, Jimmy Johnson wrote: On 10/12/2016 12:10 PM, David Baron wrote: Running must recent kwin, etc., with Sid nvidia-legacy-304xx driver. Window decorations slow or do not show on non-KDE windows. If they do not show, one can pretend they are there and do everything. Effects all compositing options. Where to file bug? Quick fix? Quick fix, force install all your 'nvidia' and 'glx' installed packages back to 'Jessie-backports' and then 'lock-them' works, maybe 20-24 packages that you will be locking, varies a little with my installs, some I had not upgraded and I only had to lock the packages. I used synaptic while in xfce4 and all your kde apps work from xfce4 too as a side note. Note no problem with upgrades and those files being locked, at this time anyways. hehe There's a lot noise out there about fix's, I found nothing works for me. I came up with this fix and it works. While gtk works with the upgrade, plasma don't, it's a problem with plasma, you can't blame nvidia and say they are not doing their part, this is a problem debian plasma, I'm sure they are working on it. Seems to affect only 'legacy-304' and could be a simple code error. With the Debian-nvidia driver: Plasma is unable to start as it could not correctly use OpenGL2. Note dialog is working, sound is working, no plasma. With the Debian-free driver, computer freeze with colorful squiggly lines and I have to push the power button and repair the file system. David, do you have a better fix than down-grading the packages? And I may not need to down grade as many packages as I do, but it works. I updated Sid/testing a couple days ago and retested current drivers, "nouveau" is working with sddm okay but froze with plasma(colorful lighting bolts). Current nvidia-legacy-304xx is working with XRender and compositing enabled and I'm good with that, tested on Stretch too, now I can do clean upgrades and I'm happy. Thank you Debian! Mine does NOT work with xrender I'm sorry to hear that, I have XRender with compositing enabled on four Stretch systems and four Sid/testing systems using current nvidia-legacy-304xx. What are you doing as a work-around? -- Jimmy Johnson Debian Stretch - Plasma 5.8.2 at sda13 Registered Linux User #380263
Re: Compositing Problem
On 10/19/2016 11:33 PM, Jimmy Johnson wrote: On 10/12/2016 12:10 PM, David Baron wrote: Running must recent kwin, etc., with Sid nvidia-legacy-304xx driver. Window decorations slow or do not show on non-KDE windows. If they do not show, one can pretend they are there and do everything. Effects all compositing options. Where to file bug? Quick fix? Quick fix, force install all your 'nvidia' and 'glx' installed packages back to 'Jessie-backports' and then 'lock-them' works, maybe 20-24 packages that you will be locking, varies a little with my installs, some I had not upgraded and I only had to lock the packages. I used synaptic while in xfce4 and all your kde apps work from xfce4 too as a side note. Note no problem with upgrades and those files being locked, at this time anyways. hehe There's a lot noise out there about fix's, I found nothing works for me. I came up with this fix and it works. While gtk works with the upgrade, plasma don't, it's a problem with plasma, you can't blame nvidia and say they are not doing their part, this is a problem debian plasma, I'm sure they are working on it. Seems to affect only 'legacy-304' and could be a simple code error. With the Debian-nvidia driver: Plasma is unable to start as it could not correctly use OpenGL2. Note dialog is working, sound is working, no plasma. With the Debian-free driver, computer freeze with colorful squiggly lines and I have to push the power button and repair the file system. David, do you have a better fix than down-grading the packages? And I may not need to down grade as many packages as I do, but it works. I updated Sid/testing a couple days ago and retested current drivers, "nouveau" is working with sddm okay but froze with plasma(colorful lighting bolts). Current nvidia-legacy-304xx is working with XRender and compositing enabled and I'm good with that, tested on Stretch too, now I can do clean upgrades and I'm happy. Thank you Debian! -- Jimmy Johnson Debian Stretch - Plasma 5.8.2 - nvidia-legacy-304xx - EXT4 at sda14 Registered Linux User #380263
Re: Bug#1 Freeze
On 11/09/2016 12:20 AM, newbee...@nativobject.net wrote: Le 09/11/2016 à 04:14, Jimmy Johnson a écrit : On 11/07/2016 04:44 AM, Tim Ruehsen wrote: With latest updates made today: From time to time, KDE freezes. Any idea ? Hi, If it's an Intel video card and the kernel is 4.8 downgrade the kernel to 4.7 and it will take care of the problem. Same here ! Regards Mourad Mine is an Intel Mobile GM965/GL960 Integrated Graphics and it's now working swell with the Sid 4.8.0-2 kernel but not as quick to load as the 4.7.0-1 kernel which works with no problem. In Stretch the 4.8.0-2 kernel is freezing the system, 4.7.0-1 kernel works swell - Intel Mobile GM965/GL960 Integrated Graphics. Plasma and SDDM. -- Jimmy Johnson Ubuntu 16.04 LTS - Plasma 5.8.4 - AMD64 - EXT4 at sda22 Registered Linux User #380263
Re: Bug#1 Freeze
On 11/07/2016 04:44 AM, Tim Ruehsen wrote: With latest updates made today: From time to time, KDE freezes. Any idea ? Hi, If it's an Intel video card and the kernel is 4.8 downgrade the kernel to 4.7 and it will take care of the problem. -- Jimmy Johnson "Debian Wheezy" - KDE 4.8.4 - AMD64 - EXT4 at sda5 Registered Linux User #380263
Re: Compositing Problem
On 10/27/2016 02:51 AM, Diederik de Haas wrote: On donderdag 27 oktober 2016 02:38:10 CEST Jimmy Johnson wrote: Downgrading to Jessie-backports works, but cause package management problems. I wonder if backporting the free driver would work too. Not likely. It would only work if both nouveau and nvidia had a working driver and both introduced a bug around the same time which made it not work. It can happen, but statistically highly unlikely. The jessie-backports workaround was just to get back to an older known working driver and apparently ppl found that easier then using snapshot.debian.org. When you're using testing or sid, I highly recommend getting familiar with snapshot.debian.org as it allows you to downgrade to any version that was released to debian. Yep, Nouveau didn't work, this time it locked up with black and white squiggle lines shaped like lightning bolts. Installed Nvidia-304, downgraded 22 packages and back in business again. This was on a new install. -- Jimmy Johnson Debian Sid/Testing - Plasma Version 5.8.2 - EXT4 at sda24 Registered Linux User #380263
Re: Compositing Problem
On 10/22/2016 10:49 AM, David Baron wrote: Just maybe it be time that plasma worked correctly with Nouveau. Nouveau is beautiful for everything else. At least, Debian folks are maintaining that, not dependent on Nvidia to maintain for legacy devices they would rather forget. As I have already reported, the Debian free driver(Nouveau) freezes the system with colorful squiggly lines and I have to push and hold the power button to turn the computer off and then repair the file system. I'm waiting to hear from upstream for suggestions on what I may test to help fix the plasma nvidia problem. Downgrading to Jessie-backports works, but cause package management problems. I wonder if backporting the free driver would work too. -- Jimmy Johnson Debian Wheezy - KDE 4.8.4 - AMD64 - EXT4 at sda1 Registered Linux User #380263
Bug#841242: Compositing Problem
On 10/20/2016 02:10 AM, Jimmy Johnson wrote: On 10/20/2016 12:22 AM, Maximiliano Curia wrote: Control: tag -1 + help �Hola NVIDIA Maintainers! It seems that the new plasma version has some kind of incompatibility with the nvidia-legacy-304xx packages in sid. The following mail reports that using the nvidia packages from backports works as expected. Yes! Jessie-backports are the same version as Sid's old version before the upgrade. Why upgraded, I have no idea. In the kde team we are not using nvidia cards, so we can't reproduce/test this. And frankly, this might be way out of our league. :( Thus the request for help. I have been testing, I have 7 installs on this machine, if someone wants me to try a fix I can try. 2 plasma installs on my Intel laptop and the laptop is loving plasma, my second desktop is ATI and Intel and no problem with the display, but has a couple other problems I'm working on due to a quick upgrade to plasma from wheezy. Is this issue known to you? Should this bug be reassigned to the nvidia packages? Can you reproduce it? If so, can you point us to what the problem might be? Happy hacking, El 2016-10-19 a las 23:33 -0700, Jimmy Johnson escribi�: On 10/12/2016 12:10 PM, David Baron wrote: Running must recent kwin, etc., with Sid nvidia-legacy-304xx driver. Window decorations slow or do not show on non-KDE windows. If they do not show, one can pretend they are there and do everything. Effects all compositing options. Where to file bug? Quick fix? Quick fix, force install all your 'nvidia' and 'glx' installed packages back to 'Jessie-backports' and then 'lock-them' works, maybe 20-24 packages that you will be locking, varies a little with my installs, some I had not upgraded and I only had to lock the packages. I used synaptic while in xfce4 and all your kde apps work from xfce4 too as a side note. Note no problem with upgrades and those files being locked, at this time anyways. hehe There's a lot noise out there about fix's, I found nothing works for me. I came up with this fix and it works. While gtk works with the upgrade, plasma don't, it's a problem with plasma, you can't blame nvidia and say they are not doing their part, this is a problem debian plasma, I'm sure they are working on it. Seems to affect only 'legacy-304' and could be a simple code error. With the Debian-nvidia driver: Plasma is unable to start as it could not correctly use OpenGL2. Note dialog is working, sound is working, no plasma. With the Debian-free driver, computer freeze with colorful squiggly lines and I have to push the power button and repair the file system. David, do you have a better fix than down-grading the packages? And I may not need to down grade as many packages as I do, but it works. I unlocked 'libgl1-mesa-glx' so I could upgrade the 3 'mesa' packages of same version, with no ill effects and got a full, clean upgrade. Currently I have 23 nvidia+glx packages locked and all is well. -- Jimmy Johnson Debian Sid/Testing - KDE Plasma Version 5.8.2 - EXT4 at sda18 Registered Linux User #380263
Re: Compositing Problem
On 10/20/2016 02:10 AM, Jimmy Johnson wrote: On 10/20/2016 12:22 AM, Maximiliano Curia wrote: Control: tag -1 + help �Hola NVIDIA Maintainers! It seems that the new plasma version has some kind of incompatibility with the nvidia-legacy-304xx packages in sid. The following mail reports that using the nvidia packages from backports works as expected. Yes! Jessie-backports are the same version as Sid's old version before the upgrade. Why upgraded, I have no idea. In the kde team we are not using nvidia cards, so we can't reproduce/test this. And frankly, this might be way out of our league. :( Thus the request for help. I have been testing, I have 7 installs on this machine, if someone wants me to try a fix I can try. 2 plasma installs on my Intel laptop and the laptop is loving plasma, my second desktop is ATI and Intel and no problem with the display, but has a couple other problems I'm working on due to a quick upgrade to plasma from wheezy. Is this issue known to you? Should this bug be reassigned to the nvidia packages? Can you reproduce it? If so, can you point us to what the problem might be? Happy hacking, El 2016-10-19 a las 23:33 -0700, Jimmy Johnson escribi�: On 10/12/2016 12:10 PM, David Baron wrote: Running must recent kwin, etc., with Sid nvidia-legacy-304xx driver. Window decorations slow or do not show on non-KDE windows. If they do not show, one can pretend they are there and do everything. Effects all compositing options. Where to file bug? Quick fix? Quick fix, force install all your 'nvidia' and 'glx' installed packages back to 'Jessie-backports' and then 'lock-them' works, maybe 20-24 packages that you will be locking, varies a little with my installs, some I had not upgraded and I only had to lock the packages. I used synaptic while in xfce4 and all your kde apps work from xfce4 too as a side note. Note no problem with upgrades and those files being locked, at this time anyways. hehe There's a lot noise out there about fix's, I found nothing works for me. I came up with this fix and it works. While gtk works with the upgrade, plasma don't, it's a problem with plasma, you can't blame nvidia and say they are not doing their part, this is a problem debian plasma, I'm sure they are working on it. Seems to affect only 'legacy-304' and could be a simple code error. With the Debian-nvidia driver: Plasma is unable to start as it could not correctly use OpenGL2. Note dialog is working, sound is working, no plasma. With the Debian-free driver, computer freeze with colorful squiggly lines and I have to push the power button and repair the file system. David, do you have a better fix than down-grading the packages? And I may not need to down grade as many packages as I do, but it works. I unlocked 'libgl1-mesa-glx' so I could upgrade the 3 'mesa' packages of same version, with no ill effects and got a full, clean upgrade. Currently I have 23 nvidia+glx packages locked and all is well. -- Jimmy Johnson Debian Sid/Testing - KDE Plasma Version 5.8.2 - EXT4 at sda18 Registered Linux User #380263
Re: Compositing Problem
On 10/19/2016 11:53 PM, Thom Castermans wrote: This may be something you already tried, but a friend of mine had this issue so I am suggesting it anyway. Are you sure you need the 304.x version of the drivers? If you have a newer graphics card, then using this older driver may cause problems. You can check this by running nvidia-debugdump --list to see your device name and then searching for it in this list <http://www.nvidia.com/object/IO_32667.html>, or, probably easier, selecting it on this page <http://www.nvidia.com/Download/index.aspx?lang=en-us>. You can then search for the Debian package matching the suggested version. Good luck, video drivers tend to be finicky... Thom Complying to check for proper driver. jimmy@jimmy-1:~$ nvidia-detect Detected NVIDIA GPUs: 00:0d.0 VGA compatible controller [0300]: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) Checking card: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] (rev a2) Your card is only supported up to the 304 legacy drivers series. It is recommended to install the nvidia-legacy-304xx-driver package. jimmy@jimmy-1:~$ Thanks. -- Jimmy Johnson Debian Sid/Testing - XFCE4 - AMD64 - EXT4 at sda24 Registered Linux User #380263
Re: Compositing Problem
On 10/20/2016 01:04 AM, David Baron wrote: On יום חמישי, 20 באוקטובר 2016 9:22:29 IDT Maximiliano Curia wrote: Control: tag -1 + help ¡Hola NVIDIA Maintainers! It seems that the new plasma version has some kind of incompatibility with the nvidia-legacy-304xx packages in sid. The following mail reports that using the nvidia packages from backports works as expected. In the kde team we are not using nvidia cards, so we can't reproduce/test this. And frankly, this might be way out of our league. :( Thus the request for help. Is this issue known to you? Should this bug be reassigned to the nvidia packages? Can you reproduce it? If so, can you point us to what the problem might be? Happy hacking, El 2016-10-19 a las 23:33 -0700, Jimmy Johnson escribió: On 10/12/2016 12:10 PM, David Baron wrote: Running must recent kwin, etc., with Sid nvidia-legacy-304xx driver. Window decorations slow or do not show on non-KDE windows. If they do not show, one can pretend they are there and do everything. Effects all compositing options. Where to file bug? Quick fix? Quick fix, force install all your 'nvidia' and 'glx' installed packages back to 'Jessie-backports' and then 'lock-them' works, maybe 20-24 packages that you will be locking, varies a little with my installs, some I had not upgraded and I only had to lock the packages. I used synaptic while in xfce4 and all your kde apps work from xfce4 too as a side note. Note no problem with upgrades and those files being locked, at this time anyways. hehe 4. If downgrading 304xx be the only way now, please give me step by step how to do this since testing packages are broken. Using dkms. Add 'deb http://ftp.us.debian.org/debian/ jessie-backports non-free contrib main' to your sources.list and start downgrading nvidia and glx. In synaptic use the menu, package, force install. -- Jimmy Johnson Debian Sid/Testing - KDE Plasma Version 5.8.2 - EXT4 at sda15 Registered Linux User #380263
Bug#841242: Compositing Problem
On 10/20/2016 12:22 AM, Maximiliano Curia wrote: Control: tag -1 + help �Hola NVIDIA Maintainers! It seems that the new plasma version has some kind of incompatibility with the nvidia-legacy-304xx packages in sid. The following mail reports that using the nvidia packages from backports works as expected. Yes! Jessie-backports are the same version as Sid's old version before the upgrade. Why upgraded, I have no idea. In the kde team we are not using nvidia cards, so we can't reproduce/test this. And frankly, this might be way out of our league. :( Thus the request for help. I have been testing, I have 7 installs on this machine, if someone wants me to try a fix I can try. 2 plasma installs on my Intel laptop and the laptop is loving plasma, my second desktop is ATI and Intel and no problem with the display, but has a couple other problems I'm working on due to a quick upgrade to plasma from wheezy. Is this issue known to you? Should this bug be reassigned to the nvidia packages? Can you reproduce it? If so, can you point us to what the problem might be? Happy hacking, El 2016-10-19 a las 23:33 -0700, Jimmy Johnson escribi�: On 10/12/2016 12:10 PM, David Baron wrote: Running must recent kwin, etc., with Sid nvidia-legacy-304xx driver. Window decorations slow or do not show on non-KDE windows. If they do not show, one can pretend they are there and do everything. Effects all compositing options. Where to file bug? Quick fix? Quick fix, force install all your 'nvidia' and 'glx' installed packages back to 'Jessie-backports' and then 'lock-them' works, maybe 20-24 packages that you will be locking, varies a little with my installs, some I had not upgraded and I only had to lock the packages. I used synaptic while in xfce4 and all your kde apps work from xfce4 too as a side note. Note no problem with upgrades and those files being locked, at this time anyways. hehe There's a lot noise out there about fix's, I found nothing works for me. I came up with this fix and it works. While gtk works with the upgrade, plasma don't, it's a problem with plasma, you can't blame nvidia and say they are not doing their part, this is a problem debian plasma, I'm sure they are working on it. Seems to affect only 'legacy-304' and could be a simple code error. With the Debian-nvidia driver: Plasma is unable to start as it could not correctly use OpenGL2. Note dialog is working, sound is working, no plasma. With the Debian-free driver, computer freeze with colorful squiggly lines and I have to push the power button and repair the file system. David, do you have a better fix than down-grading the packages? And I may not need to down grade as many packages as I do, but it works. -- Jimmy Johnson Debian Sid/Testing - KDE Plasma Version 5.8.2 - EXT4 at sda15 Registered Linux User #380263
Re: Compositing Problem
On 10/20/2016 12:22 AM, Maximiliano Curia wrote: Control: tag -1 + help �Hola NVIDIA Maintainers! It seems that the new plasma version has some kind of incompatibility with the nvidia-legacy-304xx packages in sid. The following mail reports that using the nvidia packages from backports works as expected. Yes! Jessie-backports are the same version as Sid's old version before the upgrade. Why upgraded, I have no idea. In the kde team we are not using nvidia cards, so we can't reproduce/test this. And frankly, this might be way out of our league. :( Thus the request for help. I have been testing, I have 7 installs on this machine, if someone wants me to try a fix I can try. 2 plasma installs on my Intel laptop and the laptop is loving plasma, my second desktop is ATI and Intel and no problem with the display, but has a couple other problems I'm working on due to a quick upgrade to plasma from wheezy. Is this issue known to you? Should this bug be reassigned to the nvidia packages? Can you reproduce it? If so, can you point us to what the problem might be? Happy hacking, El 2016-10-19 a las 23:33 -0700, Jimmy Johnson escribi�: On 10/12/2016 12:10 PM, David Baron wrote: Running must recent kwin, etc., with Sid nvidia-legacy-304xx driver. Window decorations slow or do not show on non-KDE windows. If they do not show, one can pretend they are there and do everything. Effects all compositing options. Where to file bug? Quick fix? Quick fix, force install all your 'nvidia' and 'glx' installed packages back to 'Jessie-backports' and then 'lock-them' works, maybe 20-24 packages that you will be locking, varies a little with my installs, some I had not upgraded and I only had to lock the packages. I used synaptic while in xfce4 and all your kde apps work from xfce4 too as a side note. Note no problem with upgrades and those files being locked, at this time anyways. hehe There's a lot noise out there about fix's, I found nothing works for me. I came up with this fix and it works. While gtk works with the upgrade, plasma don't, it's a problem with plasma, you can't blame nvidia and say they are not doing their part, this is a problem debian plasma, I'm sure they are working on it. Seems to affect only 'legacy-304' and could be a simple code error. With the Debian-nvidia driver: Plasma is unable to start as it could not correctly use OpenGL2. Note dialog is working, sound is working, no plasma. With the Debian-free driver, computer freeze with colorful squiggly lines and I have to push the power button and repair the file system. David, do you have a better fix than down-grading the packages? And I may not need to down grade as many packages as I do, but it works. -- Jimmy Johnson Debian Sid/Testing - KDE Plasma Version 5.8.2 - EXT4 at sda15 Registered Linux User #380263
Re: Compositing Problem
On 10/12/2016 12:10 PM, David Baron wrote: Running must recent kwin, etc., with Sid nvidia-legacy-304xx driver. Window decorations slow or do not show on non-KDE windows. If they do not show, one can pretend they are there and do everything. Effects all compositing options. Where to file bug? Quick fix? Quick fix, force install all your 'nvidia' and 'glx' installed packages back to 'Jessie-backports' and then 'lock-them' works, maybe 20-24 packages that you will be locking, varies a little with my installs, some I had not upgraded and I only had to lock the packages. I used synaptic while in xfce4 and all your kde apps work from xfce4 too as a side note. Note no problem with upgrades and those files being locked, at this time anyways. hehe There's a lot noise out there about fix's, I found nothing works for me. I came up with this fix and it works. While gtk works with the upgrade, plasma don't, it's a problem with plasma, you can't blame nvidia and say they are not doing their part, this is a problem debian plasma, I'm sure they are working on it. Seems to affect only 'legacy-304' and could be a simple code error. With the Debian-nvidia driver: Plasma is unable to start as it could not correctly use OpenGL2. Note dialog is working, sound is working, no plasma. With the Debian-free driver, computer freeze with colorful squiggly lines and I have to push the power button and repair the file system. David, do you have a better fix than down-grading the packages? And I may not need to down grade as many packages as I do, but it works. -- Jimmy Johnson Debian Sid/Testing - KDE Plasma Version 5.8.2 - EXT4 at sda15 Registered Linux User #380263
Re: Testing/Unstable Synaptic broken again.
On 09/01/2016 08:51 AM, Jimmy Johnson wrote: The latest upgrades have broken Synaptic, unable to use Menus or right click and Search is affected too. Thank you upstream developing and packaging team for replacing the effected packages. Yay! These packages have now been upgraded in Sid, 'gir1.2-gtk-3.0, libgtk-3-0. libgtk-3-bin. libgtk-3-common' if you have been using testing and where effected you can temp add Sid repos and upgrade the effected packages, it will pull in a few more packages, but it is fixed. -- Jimmy Johnson Debian Stretch - Plasma 5.7.4 - AMD 64 - EXT4 at sda11 Registered Linux User #380263
Re: Btrfs & Dolphin
On 09/11/2016 09:42 AM, Gary Dale wrote: I've been considering switching from Ext4 for a while but don't have any compelling reasons to do so.. Why? It's still in development was the last I heard. When I build my new computer next year to use the latest peripherals devices, I'm thinking about using ZFS, it's fast and requires good hardware and ECC RAM. https://github.com/zfsonlinux/zfs/wiki/HOWTO-install-Debian-GNU-Linux-to-a-Native-ZFS-Root-Filesystem Until then EXT is the Holy Grail of Linux file systems, self healing, no compatibility problems and fast too. -- Jimmy Johnson Debian Sid - KDE-Plasma 5.7.4 - AMD64 - EXT4 at sda14 Registered Linux User #380263
Testing/Unstable Synaptic broken again.
The latest upgrades have broken Synaptic, unable to use Menus or right click and Search is affected too. -- Jimmy Johnson Debian Stretch - KDE-Plasma-Desktop 5.7.4 - EXT4 - AMD64 at sda12 Registered Linux User #380263
Re: KDE catastrophe after June 5 dist-upgrade
On 06/05/2016 08:00 PM, Allen James wrote:
Dear maintainers,
I use Debian Testing. Before today, my previous dist-upgrade was on May 28, at
which points all packages were up to date and KDE 5.4 was running smoothly.
Today (June 5) I again dist-upgrade my laptop and now KDE is very broken.
The following is a list of many of the KDE-related packages upgraded today
(others not related to KDE/Qt/KF5/etc were removed to the best of my ability):
Now, after reboot, Plasma does not start ("Plasma Cannot Start. All shell
packages missing."), I cannot connect to the internet, there is no krunner, etc,
basically huge problems. Concerned about this because I had maintained my laptop
on Debian Testing using KDE for almost 3 years without any major issue. Is there
a way to restore what I previously had, or is there any advice regarding this?
snip <
Thank you.
Allen J
Hi Allen! I don't know how long you've been running testing but for the
time being you may find less problems by using both testing and unstable
repos, at some point testing will become stable and then you will no
longer need the unstable repos, but that is far away. Currently while
using both repos, things are looking pretty good. :)
--
Jimmy Johnson
Plasma-5 - Where's my Quick-Launch?
Registered Linux User #380263
Re: KDE catastrophe after June 5 dist-upgrade
On 06/05/2016 08:00 PM, Allen James wrote:
Dear maintainers,
I use Debian Testing. Before today, my previous dist-upgrade was on May 28, at
which points all packages were up to date and KDE 5.4 was running smoothly.
Today (June 5) I again dist-upgrade my laptop and now KDE is very broken.
The following is a list of many of the KDE-related packages upgraded today
(others not related to KDE/Qt/KF5/etc were removed to the best of my ability):
Now, after reboot, Plasma does not start ("Plasma Cannot Start. All shell
packages missing."), I cannot connect to the internet, there is no krunner, etc,
basically huge problems. Concerned about this because I had maintained my laptop
on Debian Testing using KDE for almost 3 years without any major issue. Is there
a way to restore what I previously had, or is there any advice regarding this?
snip <
Thank you.
Allen J
Hi Allen! I don't know how long you've been running testing but for the
time being you may find less problems by using both testing and unstable
repos, at some point testing will become stable and then you will no
longer need the unstable repos, but that is far away. Currently while
using both repos, things are looking pretty good. :)
--
Jimmy Johnson
Plasma-5 - Where's my Quick-Launch?
Registered Linux User #380263
Re: iceweasel locking up under KDE, fine under Xfce
On 12/16/2015 03:34 PM, Arthur Marsh wrote: Arthur Marsh wrote on 15/12/15 16:18: and the problem seems to have gone away with the upgrade of packages based on kde4libs from 4:4.14.14-1 to 4:4.14.14-1+b1 Arthur. Back again with a vengeance, I can't even bring up iceweasel in gdb under KDE without it locking up. I can run iceweasel xfce alright though. Arthur. Besides XFCE4 I'm also looking at the "Trinity Desktop" ported to Debian, currently I have both Jessie and Stretch installed with Trinity, but I'm taking it slow, it's still a longtime before Stretch goes finial, but it has been disturbing me with all the auto-stuff that's being installed and working in the background, but I'm sure there will be a lot of people who will love their new system, but it just don't fell like a Debian System to me. -- Debian Jessie - KDE 4.14.2 - EXT4 - AMD64 at sda10 Registered Linux User #380263
Re: iceweasel locking up under KDE, fine under Xfce
On 12/12/2015 11:52 PM, Luc Castermans wrote: Op 13-12-15 om 04:25 schreef Jimmy Johnson: I always had bad experience with the free nvidia drivers. I always used the drivers from nvidia. Thanks for getting me to try the driver again, it's working with xrender, but sddm is being weird, it's losing mouse focus, I have to click in the box to enter my password, I didn't have to do that with the debian driver. At the moment I have a Radeon HD 8670D card in my PC. Also I need to click to enter a password. I believe (1) this behaviour should not depend on the driver and (2) this is the default behaviour of SDDM Yes you are right it should have nothing to do with the driver you have installed, but since testing plasma it has so far been the case, there is a big difference if you have the 'Nouveau' or 'Nvidia' driver installed with the Nouveau driver SDDM dose not lose focus and I do not have to click in the box to enter my password, this I have tested on 2 Stretch and my other Sid system and loosing mouse focus has not been a problem with SDDM, I have 4 upstream plasma systems. Currently I'm going to keep the Nvidia Driver installed on the one Sid system because outside of loosing focus on SDDM it other wise seems to be working, but I need to spend more time with it. -- Jimmy Johnson Debian Sid - KDE-Plasma 5.4.1 - AMD64 - EXT4 at sda14 Registered Linux User #380263
Re: iceweasel locking up under KDE, fine under Xfce
On 12/14/2015 10:16 AM, Jimmy Johnson wrote: On 12/12/2015 11:52 PM, Luc Castermans wrote: Op 13-12-15 om 04:25 schreef Jimmy Johnson: I always had bad experience with the free nvidia drivers. I always used the drivers from nvidia. Thanks for getting me to try the driver again, it's working with xrender, but sddm is being weird, it's losing mouse focus, I have to click in the box to enter my password, I didn't have to do that with the debian driver. At the moment I have a Radeon HD 8670D card in my PC. Also I need to click to enter a password. I believe (1) this behaviour should not depend on the driver and (2) this is the default behaviour of SDDM Yes you are right it should have nothing to do with the driver you have installed, but since testing plasma it has so far been the case, there is a big difference if you have the 'Nouveau' or 'Nvidia' driver installed with the Nouveau driver SDDM dose not lose focus and I do not have to click in the box to enter my password, this I have tested on 2 Stretch and my other Sid system and loosing mouse focus has not been a problem with SDDM, I have 4 upstream plasma systems. Currently I'm going to keep the Nvidia Driver installed on the one Sid system because outside of loosing focus on SDDM it other wise seems to be working, but I need to spend more time with it. I'm already back to using the nouveau driver..The Nvidia driver or the Debian Nvidia driver do not work with the new kernel, on the plus side SDDM is now working and not loosing focus. Plasma still crashes for no apparent reason. -- Jimmy Johnson Debian Sid - KDE Plasma 5.4.3 - AMD64 - EXT4 at sda15 Registered Linux User #380263
Re: iceweasel locking up under KDE, fine under Xfce
On 12/12/2015 03:59 AM, Luc Castermans wrote: Op 12-12-15 om 01:09 schreef Jimmy Johnson: On 12/11/2015 01:30 PM, Arthur Marsh wrote: Arthur Marsh wrote on 03/12/15 23:23: This seems to be an issue related to the graphics card used. Maybe, but I don't know how it all fits as I'm using Nvidia card and the free driver from the Debian repos..What happens to me is I get a Notice that plasma has crashed and sure enough the panel has crashed, I close the the Notice and go back to what I was doing and then it will crash again..If I don't acknowledge the Notice the system/computer will Freeze causing Plasma to be useless as a system and me doing a Hard-Shutdown.. I'm willing to do testing if someone wants to fix the problem.. I always had bad experience with the free nvidia drivers. I always used the drivers from nvidia. Luc Thanks for getting me to try the driver again, it's working with xrender, but sddm is being weird, it's losing mouse focus, I have to click in the box to enter my password, I didn't have to do that with the debian driver. -- Jimmy Johnson Debian Sid - KDE Plasma 5.4.3 - AMD64 - EXT4 at sda15 Registered Linux User #380263
Re: iceweasel locking up under KDE, fine under Xfce
On 12/11/2015 01:30 PM, Arthur Marsh wrote: Arthur Marsh wrote on 03/12/15 23:23: With an update to KDE from unstable, iceweasel from unstable locked up every time until I upgraded iceweasel to experimental. Now iceweasel runs fine under KDE. As previously mentioned running with Radeon 3200HD (RS780) and vdpau libraries installed. Arthur. I had one lock-up after installing the latest Linus' git head kernel with some Radeon-specic updates but did not lock up on a second attempt. This seems to be an issue related to the graphics card used. Arthur. Maybe, but I don't know how it all fits as I'm using Nvidia card and the free driver from the Debian repos..What happens to me is I get a Notice that plasma has crashed and sure enough the panel has crashed, I close the the Notice and go back to what I was doing and then it will crash again..If I don't acknowledge the Notice the system/computer will Freeze causing Plasma to be useless as a system and me doing a Hard-Shutdown.. I'm willing to do testing if someone wants to fix the problem.. -- Debian Jessie - KDE 4.14.2 - EXT4 - AMD64 at sda10 Registered Linux User #380263
Re: Safe to upgrade?
On 12/10/2015 02:38 PM, Martin Steigerwald wrote: martin@merkaba:~> uptime 23:34:54 up 4 days, 11:08, 0 users, load average: 1,22, 1,61, 1,58 with several suspend and several hibernation cycles in between, cause I never it it running through the night. No issue. Just works. Even with two Plasma sessions. One private one and one for work. Just sometimes I have it that Plasma session is not locked properly, and then doesn�t respond to mouse clicks at all. I did not wait for more than a few minutes so far for it to respond again and just "killall -u" it. But it happens quite rarely. Debian Sid, with self-compiled KF5 and KDEPIM, but Plasma from Debian packages. Thanks, All four of my Plasma systems crash, just setting there or maybe I'll be playing Kpat, it's been the case for along time now. While Xfce is as stable as stable can be. By the way it's 140 packages and 225MB if you want to install Kpat on an Xfce system. Thanks, -- Jimmy Johnson Debian Stretch - Xfce 4.12 - AMD64 - EXT4 at sda13 Registered Linux User #380263
Re: dist-upgrade still failing
On 10/30/2015 04:50 PM, Carlos Kosloff wrote: Thanks for all answers, this is my report. This is the list of commands I tried: as root: apt-get update && apt-get dist-upgrade, 0 packages apt-get purge lightdm apt-get autoremove --purge apt-get install --reinstall kdm apt-get install kde-full apt-get install task-kde-desktop reboot I still get the lightdm greeter and it fails to start back to the console systemctl stop kdm.service systemctl start kdm.service systemctl stop lightdm.service, not loaded as user startx, still the lightdm screen, no desktop back to console as user startx startkde, kde starts as an xterm session Problem I see is that even grub now has the lightdm screen, I cannot understand how that happens since I completely purged lightdm. So as root apt-get install grub-efi-amd64 apt-get install --reinstall grub-common still SOL, startx startkde is my only option so far. Where is Lisandro when you need him? If anybody wants to troubleshoot logs, I am of course willing to paste. Did you run 'dpkg-reconfigure kdm' after installing kdm? -- Kali Linux - KDE 4.14.2 - EXT4 - AMD64 at sda10 Registered Linux User #380263
Re: Why changing the volume when restoring the session ?
On 10/21/2015 03:03 AM, newbee...@nativobject.net wrote: Hi, I have a question of a useless behaviour. Everytime I restore my plasma5 session from standby mode the sound volume is put to 100% ! Is it possible to disable that foolish feature ? It seem to be a regression of that bug : https://bugs.kde.org/show_bug.cgi?id=324975 Regards Mourad I went to 'System Tray Settings'(right click on the tray) and unchecked 'Audio Volume', plus some others I did not need or want. I now use Kmix with no problem. -- Jimmy Johnson Debian Sid - KDE-Plasma 5.4.1 - AMD64 - EXT4 at sda13 Registered Linux User #380263
Konqueror file-management problem.
Konqueror file-management is only working in file-size, we had this problem once before when dolphin was not installable, but dolphin seems to be okay. -- Jimmy Johnson Debian Sid - KDE Plasma 5.4.1 - AMD64 - EXT4 at sda15 Registered Linux User #380263
Re: Can't start Kuser
On 09/26/2015 10:42 AM, Brad Rogers wrote: Hello All, A strange one, this; I'm trying to start Kuser from the KDE menu, but it refuses to accept the root password. I know the password to be correct (it's accepted by everything else). I can start it from the konsole with 'sudo kuser', and it works as expected. So, I've got a workaround, but it would be nice to get things going properly. Error report is; Permission denied. Possibly incorrect password, please try again. On some systems, you need to be in a special group (often: wheel) to use this program Weirdly, on another machine, Kuser works fine. So it would appear there's something odd about the particular setup on this machine. Searching the internet has proved fruitless. Maybe my search-foo isn't up to the task. Any help greatly appreciated. Sorry for your problems Brad, no problems here with kuser on any of my 5 Sid systems. -- Jimmy Johnson Debian Sid - KDE Plasma 5.4.1 - AMD64 - EXT4 at sda15 Registered Linux User #380263
Re: Wife's sid box still wants to deinstall on dist-upgrade
On 09/17/2015 12:44 PM, Andrey Rahmatullin wrote: 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. Then your system is dirty and you should listen to what I'm saying or not, up to you. But tell me what is the worst that can happen? 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 5 systems and one of the systems, this one, I have been running the same Sid for more than 10 years, I know what I'm doing, maybe you don't. 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? That should have read KDE announce. -- Jimmy Johnson Debian Sid - KDE Plasma 5.4.1 - AMD64 - EXT4 at sda15 Registered Linux User #380263
Re: Wife's sid box still wants to deinstall on dist-upgrade
On 09/17/2015 01:14 PM, Jimmy Johnson wrote: On 09/17/2015 12:44 PM, Andrey Rahmatullin wrote: 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. Then your system is dirty and you should listen to what I'm saying or not, up to you. But tell me what is the worst that can happen? 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 5 systems and one of the systems, this one, I have been running the same Sid for more than 10 years, I know what I'm doing, maybe you don't. 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? That should have read KDE announce. I'm sorry Andrey, you are correct digikam is in fact not installable, please forgive me. -- Jimmy Johnson Debian Sid - KDE Plasma 5.4.1 - AMD64 - EXT4 at sda15 Registered Linux User #380263
Re: Dolphin request to run as root
On 09/14/2015 04:52 AM, Daniel Schröter wrote: On 09/14/2015 10:57 AM, Jimmy Johnson wrote: I would open the menu(right click the menu start button) with 'edit applications'/menu edit and check to see what command is being used I can't edit the icons. I can not see the command. Maybe I there is one packages missing. BUT I saw that there is a second icon available for dolphin and with this one I doesn't get the message :-D Thanks for this hint! Did you find the package? It's 'kmenuedit', it's a required package, but I'm not surprised it's not installed. -- Jimmy Johnson Debian Sid - KDE Plasma 5.4.1 - AMD64 - EXT4 at sda15 Registered Linux User #380263
Re: Dolphin request to run as root
On 09/14/2015 12:05 AM, Daniel Schröter wrote: Hello, I'm running Dolphin in version 4:15.04.3-1 Since upgrade to plasma 5: If I start Dolphin with the icon I get a message for kdesu requesting root privileges. (If I click "ignore" it runs fine). If I start Dolphin from the konsole it doesn't request root privileges. I would open the menu(right click the menu start button) with 'edit applications'/menu edit and check to see what command is being used and also check to see that 'run as different user' is not checked. -- Jimmy Johnson Debian - Wheezy - KDE 4.8.4 - AMD64 - EXT4 at sda1 Registered Linux User #380263
kwikdisk
kwikdisk is now restored to the system tray in Sid. yay! Thank you, -- Jimmy Johnson Debian Stretch - KDE-Plasma-Desktop 5.4.0 - EXT4 - AMD64 at sda13 Registered Linux User #380263
Dual monitor placement settings.
For the first time in Sid since plasma 5 my monitors are being place where I want them at startup. Thank you, -- Jimmy Johnson Debian Sid - KDE-Plasma 5.4.0 - AMD64 - EXT4 at sda13 Registered Linux User #380263
Gimp
I have 3 Sid systems 2 had gimp installed and one didn't, I was able to get a full upgrade on the one without gimp and then install gimp. On the systems with gimp I was not able to get a full upgrade, so I removed gimp and then did a full upgrade and then I was able to reinstall gimp. -- Jimmy Johnson Debian Sid - KDE-Plasma 5.4.0 - AMD64 - EXT4 at sda13 Registered Linux User #380263
Re: Gimp
On 09/07/2015 03:40 AM, MERLIN Philippe wrote:
Le lundi 7 septembre 2015, 02:29:31 Jimmy Johnson a écrit :
> I have 3 Sid systems 2 had gimp installed and one didn't, I was able to
> get a full upgrade on the one without gimp and then install gimp.
>
> On the systems with gimp I was not able to get a full upgrade, so I
> removed gimp and then did a full upgrade and then I was able to
> reinstall gimp.
Thank you for the information, it is very interesting and surprising, it
would be instructive to explain the whys and wherefores. Thus Gimp
deleted one time can be reinstalled after the big update.
It would be interesting to know if other packages can follow the same
method, I think of Filezilla, Digikam...
Philippe Merlin
Hi,
Filezilla is installable on my system, while digikam is not.
# aptitude install Digikam
The following NEW packages will be installed:
digikam digikam-data{a} digikam-private-libs{a} enblend{a} enfuse{a}
ffmpegthumbs{a} freeglut3{a} hugin{a}
hugin-data{a} hugin-tools{a} kipi-plugins{a} kipi-plugins-common{a}
libarchive-zip-perl{a} libastro1{a}
libboost-filesystem1.55.0{a} libboost-filesystem1.58.0{a}
libboost-system1.55.0{a} libgsl0ldbl{a} libgtkglext1{a}
libhdf5-8{a} libid3tag0{a} libimage-exiftool-perl{a}
libkdcraw-data{a} libkdcraw23{a} libksane-data{a} libksane0{a}
liblensfun-data{a} liblensfun0{a} libmarblewidget19{a}
libopencv-calib3d2.4{a} libopencv-contrib2.4{a}
libopencv-core2.4{a} libopencv-features2d2.4{a} libopencv-flann2.4{a}
libopencv-highgui2.4{a}
libopencv-imgproc2.4{a} libopencv-legacy2.4{a} libopencv-ml2.4{a}
libopencv-objdetect2.4{a} libopencv-video2.4{a}
libpangox-1.0-0{a} libpgf6{a} libqextserialport1{a}
libqtglib-2.0-0{a} libqtgstreamer-1.0-0{a}
libqtgstreamerutils-1.0-0{a} libqtlocation1{a} libquazip1{a}
libraw10{a} libshp2{a} libsqlite0{a} libtbb2{a}
libvigraimpex4{a} libwxbase3.0-0v5{a} libwxgtk3.0-0v5{a}
marble-data{a} marble-plugins{a} minidlna{a}
opencv-data{a}
0 packages upgraded, 59 newly installed, 0 to remove and 0 not upgraded.
Need to get 77.9 MB of archives. After unpacking 263 MB will be used.
The following packages have unmet dependencies:
libstdc++6 : Breaks: digikam-private-libs (<= 4:4.4.0-1.1+b2) but
4:4.4.0-1.1+b2 is to be installed.
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) digikam [Not Installed]
2) digikam-private-libs [Not Installed]
3) kipi-plugins [Not Installed]
Accept this solution? [Y/n/q/?] q
--
Jimmy Johnson
Debian Sid - KDE-Plasma 5.4.0 - AMD64 - EXT4 at sda13
Registered Linux User #380263
Re: Plasma past G++ transition
On 09/03/2015 09:20 AM, Martin Steigerwald wrote: Luc you could try install task-kde-desktop or install kde-plasma-desktop, thats in testing. In Sid, bits are still broken like not being able to install Gimp and/or you can't do a dist-upgrade but you can do an aptitude safe-upgrade and that is what I recommend for both testing and unstable. Yes you can. Well at least I could. Calligra (including Krita) and Digikam are not there yet. Amarok, KMyMoney, kde-full all there and working. Be prepared that you may have to do the dist-upgrade in several steps, and possibly partly from a tty, cause I had to. Martin you do know that 'aptitude safe-upgrade' adds and removes packages as needed, don't you? If you are not comfortable with this, wait and install some lxde or other desktop for the time being. If you can. Been using Debian for more than 20 yrs. I've seen many systems break and I fix them all, yes, I'm comfortable, thanks to Debian and my study of package management. -- Jimmy Johnson Debian - Wheezy - KDE 4.8.4 - AMD64 - EXT4 at sda1 Registered Linux User #380263
Re: Plasma past G++ transition
On 09/02/2015 01:46 AM, Luc Castermans wrote: this is very nice news! However I tried to make fresh install from Testing last weekend, and then get many dependency conflicts as soon as I issue a "aptitide install kde-full". In summary: I installed a fresh Testing (base system), then do "aptitude install kde-full". Should I add unstable to sources.list, then do "aptitude install -t sid kde-full", or even from experimental? Regards Luc Luc you could try install task-kde-desktop or install kde-plasma-desktop, thats in testing. In Sid, bits are still broken like not being able to install Gimp and/or you can't do a dist-upgrade but you can do an aptitude safe-upgrade and that is what I recommend for both testing and unstable. -- Debian Jessie - KDE 4.14.2 - EXT4 - AMD64 at sda10 Registered Linux User #380263
Re: Plasma 5 wont starting
On 08/24/2015 11:44 AM, akhilkrishnans. wrote: 2015-08-22 9:35 GMT+05:30 Jimmy Johnson field.engin...@gmail.com mailto:field.engin...@gmail.com: A problem in packages libkf5windowsystem* was fixed two days ago. What you post sounds like you need to install/upgrade package 'plasma-desktop'. Updated and everything works fine except Dolphin, shows some 'Windows Server' like menus. No 'Plasma-Style' graphics there. And still KDM Login page have Gnome like Watchdial Pointer. In Sid/Unstable kde-plasma-desktop can be installed now and should complete your kde setup, also task-kde-desktop can be installed, it includes kde-standard, kde-plasma-desktop and plasma-desktop. All of the above is subject to change in the blink of an eye. -- Jimmy Johnson Debian Sid - KDE-Plasma 5.3.2 - AMD64 - EXT4 at sda13 Registered Linux User #380263
