Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Search found 22 matches
- 2023-03-26 10:59
- Forum: Testing And Unstable
- Topic: [Testing - Bookworm] using twice the memory bullseye needed
- Replies: 12
- Views: 10150
Re: [Testing - Bookworm] using twice the memory bullseye needed
Thee have been changes to how free measures memory. Tx that could explain it (and i am seeing the same kind of increase for "top", too, which makes sense if both "free" and "top" rely on "libproc2") Here are my figures from a just logged-in plasma session: ve...
- 2023-03-25 18:46
- Forum: Testing And Unstable
- Topic: [Testing - Bookworm] sound not working anymore after upgrade from bullseye
- Replies: 12
- Views: 5339
Re: [Testing - Bookworm] sound not working anymore after upgrade from bullseye
Thanks for keeping at it, Frank ! After removing pulseaudio I now have sound in KDE settings, dolphin preview, smplayer and firefox. For deadbeef i am using the dev's static build and had to use a more recent one which has a pipewire plugin (1.9.5 i/o 1.8.8). For vlc i had to manually install vlc-pl...
- 2023-03-25 15:12
- Forum: Testing And Unstable
- Topic: [Testing - Bookworm] sound not working anymore after upgrade from bullseye
- Replies: 12
- Views: 5339
Re: [Testing - Bookworm] sound not working anymore after upgrade from bullseye
pactl works indeed , but i cannot play anything with vlc, smplayer, deadbeef ... and plasma sees no audio output device I see i have pipewire & pipewire-pulseaudio running, though ... baldyeti@gobogeg:Music$ pactl list Module #1 Name: libpipewire-module-rt Argument: { nice.level = -11 #rt.prio =...
- 2023-03-25 13:12
- Forum: Testing And Unstable
- Topic: [Testing - Bookworm] sound not working anymore after upgrade from bullseye
- Replies: 12
- Views: 5339
Re: [Testing - Bookworm] sound not working anymore after upgrade from bullseye
Thanks for the suggestion but i actually did and it produces the exact same output (except for the "connection error"). And of course i noticed the issue because i could not get sound from multimedia apps running under my regular account)
- 2023-03-25 12:52
- Forum: Testing And Unstable
- Topic: [Testing - Bookworm] sound not working anymore after upgrade from bullseye
- Replies: 12
- Views: 5339
[Testing - Bookworm] sound not working anymore after upgrade from bullseye
sound was previously working under bullseye but not since i upgraded to bookworm perhaps this has to do with pipewire vs pulseaudio ? here's what 'inxi -A" reports Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series H...
- 2023-03-25 12:25
- Forum: Testing And Unstable
- Topic: [Testing - Bookworm] using twice the memory bullseye needed
- Replies: 12
- Views: 10150
Re: [Testing - Bookworm] using twice the memory bullseye needed
1,1 GB on Plasma on a clean desktop sounds very heavy. I did a fresh Bullseye install a couple of days ago when changing SSD, and memory usage with Plasma was around 500 MB. That was about my expectation, too. Perhaps a little higher but not double the memory from previous version. I suspect this i...
- 2023-03-25 10:07
- Forum: Testing And Unstable
- Topic: [Testing - Bookworm] using twice the memory bullseye needed
- Replies: 12
- Views: 10150
Re: [Testing - Bookworm] using twice the memory bullseye needed
Saying your computer uses a lot of memory with Firefox running is like saying you car feels a bit heavy with an unspecified number of baby elephants sitting in the back. The figures i gave are straight after booting, running "free -h" either from a text console or konsole instance. The in...
- 2023-03-25 09:09
- Forum: Testing And Unstable
- Topic: [Testing - Bookworm] using twice the memory bullseye needed
- Replies: 12
- Views: 10150
[Testing - Bookworm] using twice the memory bullseye needed
Hello, i have recently upgraded a bullseye installation to bookworm. It mostly went well, but under debian 12 the same system is using about twice the memory it needed before. That is to say, about 550M in text mode and 1.1G under plasma. This is a 4th gen i3 system (and using Intel HD). CPU: dual c...
- 2021-02-07 14:29
- Forum: Graphical Environments & Desktops
- Topic: [SOLVED] buster/KDE: cannot unlock screen
- Replies: 8
- Views: 3230
Re: [SOLVED] buster/KDE: cannot unlock screen
Alright I agree changing group membership of /etc/shadow is a better solution (it was set to utmp).
No need to speak in minimalistic riddles, though ("read the logs", "re-read that post properly")
No need to speak in minimalistic riddles, though ("read the logs", "re-read that post properly")
- 2021-02-07 13:58
- Forum: Graphical Environments & Desktops
- Topic: [SOLVED] buster/KDE: cannot unlock screen
- Replies: 8
- Views: 3230
Re: buster/KDE: cannot unlock screen
looks like a bug was once opened against [libpam-modules-bin], only to be deemed "unreproducible".
- 2021-02-07 13:47
- Forum: Graphical Environments & Desktops
- Topic: [SOLVED] buster/KDE: cannot unlock screen
- Replies: 8
- Views: 3230
Re: buster/KDE: cannot unlock screen
Found the following suggestion on reddit:
This works but i have no idea how these permissions changed on my system and why so very few other users seem affected..
Code: Select all
chmod 4755 /sbin/unix_chkpwd
- 2021-02-07 13:22
- Forum: Graphical Environments & Desktops
- Topic: [SOLVED] buster/KDE: cannot unlock screen
- Replies: 8
- Views: 3230
Re: buster/KDE: cannot unlock screen
I forgot to mention I can unlock from a console using "loginctl unlock-session n" , just not from the graphical dialog.
- 2021-02-07 13:19
- Forum: Graphical Environments & Desktops
- Topic: [SOLVED] buster/KDE: cannot unlock screen
- Replies: 8
- Views: 3230
Re: buster/KDE: cannot unlock screen
from /var/log/auth.log: Feb 7 14:02:43 shoggoth unix_chkpwd[12355]: check pass; user unknown Feb 7 14:02:43 shoggoth unix_chkpwd[12355]: password check failed for user (baldyeti) Feb 7 14:02:43 shoggoth kcheckpass[12344]: pam_unix(kde:auth): authentication failure; logname= uid=1000 euid=1000 tty=:0...
- 2021-02-07 12:12
- Forum: Graphical Environments & Desktops
- Topic: [SOLVED] buster/KDE: cannot unlock screen
- Replies: 8
- Views: 3230
[SOLVED] buster/KDE: cannot unlock screen
On a buster system running plasma, the unlock screen dialog does not work. i can see (by making the typed characters visible) that the keyboard layout is correct and the proper password typed, but all i get is "unlocking failed". I have had this problem forever (probably already when the v...
- 2019-01-23 17:49
- Forum: Installation
- Topic: failed upgrade stretch -> testing/buster
- Replies: 15
- Views: 11368
Re: failed upgrade stretch -> testing/buster
Hello, after i purged the system of all neptuneOS packages, i managed to upgrade to buster, then installed kde-plasma-desktop. It wasn't all smooth sailing and i had to resort to "aptitude -f" and remove va-driver-all. Apt (and apt-get) do not complain anymore at all but for some reason ap...
- 2019-01-19 16:40
- Forum: Installation
- Topic: failed upgrade stretch -> testing/buster
- Replies: 15
- Views: 11368
Re: failed upgrade stretch -> testing/buster
Thanks for all suggestions. I am in no hurry and was curious to try KDE 5.14. I will purge the system from its non-debian packages and try again but that may not be before another week or so.
- 2019-01-19 16:40
- Forum: Installation
- Topic: failed upgrade stretch -> testing/buster
- Replies: 15
- Views: 11368
Re: failed upgrade stretch -> testing/buster
Alright, that clarifies your 1st post - hence my other question: when would be a better time and is there another (sub)forum where the current state of release upgrades is more specifically discussed ?llivv wrote:Upgrade stable to testing is hard enough (A T M) that seasoned users are having issues.
- 2019-01-19 16:34
- Forum: Installation
- Topic: failed upgrade stretch -> testing/buster
- Replies: 15
- Views: 11368
Re: failed upgrade stretch -> testing/buster
SOunds about bassackwards to me. At what point did you remove the third party? 1st second or fourth? weeks ago - kde 5.12 works real fine and i was barely getting any more updates for it, so i removed the adhoc source I know adding non-official sources is unsupported, which is why i l mentioned it ...
- 2019-01-19 13:44
- Forum: Installation
- Topic: failed upgrade stretch -> testing/buster
- Replies: 15
- Views: 11368
Re: failed upgrade stretch -> testing/buster
are you saying there are known problems with upgrading atm and suhggesting i retry a little later ?llivv wrote:unlike the present condition of the dist-upgrade
is there another place (newsgroup, perhaps ?) where the matter is discussed ?
- 2019-01-19 13:30
- Forum: Installation
- Topic: failed upgrade stretch -> testing/buster
- Replies: 15
- Views: 11368
Re: failed upgrade stretch -> testing/buster
I have backups. This is a partition i can easily overwrite with a copy of my "real" stretch, but where i wanted to test upgrading.