Re: Replacing Pulseaudio with Alsa alone
On 2019-06-04 at 23:47, Joe Dennigan wrote: Dan Ritter writes: Kaj Persson wrote: I am running Debian 9 Stretch. After the OS install the Pulseaudio is by default the standard audio system with Alsa as the executor. Which is the best strategy to remove Pulseaudio and instead letting Alsa be the one and only audio system? Are there any serious disadvantages doing so? There is one serious disadvantage: Firefox doesn't support audio in any other way except PulseAudio. If you don't care about that, then you can certainly play music, record audio, and otherwise do normal audio-related things through ALSA. I got shot of PulseAudio more than a year ago because of serious sound latency issues (700-1200+ms in VirtualBox/WinXP for some old games I love). Using plain ALSA fixed that. I had already switched to Palemoon as a browser (other problems with Firefox - not audio relevant) at that point, and now also use Waterfox, and have not missed PulseAudio or Firefox at all. As I type this, I am listening to Saint-Saëns Symphony No 3 on YouTube using Waterfox with no problems whatsoever. I don't know of any other desktop applications that actually need PulseAudio and can't think of any disadvantage(s) to removing it. Regards, Joe Dennigan Thank you for all answers and advices. A silly question, perhaps: Do I need take any special steps for the transform, or is just e.g. apt-get --autoremove remove pulseaudio sufficient, and the system automaticly adapts to the new situation? /Kaj
Replacing Pulseaudio with Alsa alone
I am running Debian 9 Stretch. After the OS install the Pulseaudio is by default the standard audio system with Alsa as the executor. Which is the best strategy to remove Pulseaudio and instead letting Alsa be the one and only audio system? Are there any serious disadvantages doing so? /Kaj
Re: No sound
Den 2019-05-14 kl. 18:09, skrev Curt: On 2019-05-12, 70147pers...@telia.com <70147pers...@telia.com> wrote: I have no sound at all. By starting e.g. VLC or Audacity with a *.wav file I can see this executed, in Audacity also the wave form, but nothing from the loudspeaker. Since July, 2018? https://lists.debian.org/debian-user/2018/07/msg00424.html Have you tried running jack without realtime priorities? jackd -r & Are you (or Stretch by default) set up for realtime? (I don't know.) /etc/security/limits.d/99-realtime.conf @realtime - rtprio 99 @realtime - memlockunlimited sudo groupadd realtime sudo usermod -a -G realtime yourUserID Logout and back in. I didn't read through the thread with much care, so maybe I'm in left field (where I hope nobody pulls any line drives). Hi Curt! To your second question I say, I think so. Here is no group called realtime, and hence no file 99-realtime.conf in /etc/security/limits.d/. But there is a single file audio.conf and also a group audio, which I am a member of. The file contains the lines you mention, except the number 95 instead of 99, and "realtime" replaced with "audio". On the first question I must say: I do not know. I tested your proposed command and got as a result a printout from jackdmp, which looked like a help printout. Kaj
Re: No sound
Den 2019-05-12 kl. 19:30, skrev David Wright: On Sun 12 May 2019 at 13:08:33 (+0200), 70147pers...@telia.com wrote: Inxi is telling that the sound card, Device-1, is Intel 82801I HD Audio, and the driver: snd_hda_intel. This raises the question of what device 0 is, and whether the sound is being routed there. As a non-DE non-pulse user, I would run alsamixer, press F6 and select the device 1. Then work my way along the bars, raising levels with the arrows and unmuting with the M key. As some applications have their own volume controls that may or may not work, speaker-test is a useful command for a source. Cheers, David. Well David, I did not describe the content of the link, but in short one creates as Device-0, a virtual device called Loopback, which does what its name is saying, it loops back to jack what was transferred to Device-0, the default device. So programmes not adapted to run jack, gets its signal connected to jack and handled by this. OK, this is how I have understood it, my knowledge is not deep enough to exactly see what happens. Someone better skilled could perhaps give a better explanation. By using mate-volume-control I could see that this Loopback was created as the default Device-0. The card itself "HDA Intel" is there too. Kaj
Re: No sound
Den 2019-05-12 kl. 17:28, skrev Jonas Smedegaard: Quoting Hans (2019-05-12 17:12:13) Got in the same problem half a year ago. Some program was blocking the sounddevice. I remeber, there was a command. which shows, which application is just accessing the sound device (dev/snd). Maybe someone knows the command and can help here. I forgot the exact syntax. In my case it was the application "timidity", which I just deinstalled. Got no problems after it. Perhaps this: lsof /dev/snd - Jonas Thank you for the hint. I tested it and the result was an empty list. After that I made a purge of timidity. In /etc and all its subdirectories I removed every trace of "timidity". All files and directories containing "timidity" in its name were removed. All files containing the word were edited, and the word was removed. After that a cold start (power off), but no difference. The computer is silent as in the space around us, so no forward step so far. Kaj
Re: No sound
Den 2019-05-12 kl. 13:59, skrev arne: On Sun, 12 May 2019 13:08:33 +0200 (CEST) "70147pers...@telia.com" <70147pers...@telia.com> wrote: I have no sound at all. By starting e.g. VLC or Audacity with a *.wav file I can see this executed, in Audacity also the wave form, but nothing from the loudspeaker. Could you run alsa-info and choose: Automatically upload ALSA information to www.alsa-project.org? and post the result from: Your ALSA information is located at: http://alsa-project.org/db/?f on this list? Well Arne, a lot of info, which I have notyet been able to investigate fully. Here is the link: http://alsa-project.org/db/?f=d022b002500193f3df3710c5620b58d20ecc8f52 Thank you so far! Kaj
Re: No sound/audio
Den 2018-07-18 kl. 07:07, wrote deloptes: 70147pers...@telia.com wrote: Nothing else, I love Firefox, and appreciate really the work all these volunteers are doing, but if I cannot get sound from that programme the way I prefer, I feel I am forced to look for another browser. Anyone who knows a way to bypass the announced limitations? Hi, while I agree with you that we are left without a choice in cases such as firefox, I disagree that this is a firefox problem. The problem is definitely in timidity as it hooks I guess directly to alsa and blocks any other application. There were suggestions made to use jack and when working with music (timidity) you probably will have other benefits by using jack. As of your remark - you stopped timidity - did you disable autostart before rebooting. Chances are high you didn't and it autostarted blocking your device again. In /etc/default/timidity # uncomment to override enabling triggered by availability of timidity-deamon TIM_ALSASEQ=false regards No, certainly you are right. So far my knowledge did not reach. Well, I followed your instruction and made a reboot. And now the timidity daemon was not there, at least according to the command "ps -ef | grep timidity". Before the reboot it was. But the only result of this was that none of my programmes delivered any sound, not Frescobaldi and not Firefox. So what was the advantage? Is there no possibility to coexist with Timidity (and Jack)? Before my latest upgrade, I now use version 61 of Firefox, they worked fine together, at least from my point of view. I had sound in Firefox as well as Frescobaldi and Denemo (and Ardour). So from with my horizon all has been a deterioration, even if I of course does not realize all the difficulties you developers are meeting. On the other hand, Timidity is a so much appreciated software, that it should be a good thing learning to live together with it. A dialogue with the Timidity guys perhaps? Regarding Ardour and the other music software I can suspect it is not equally big, but we who use them will still continue to do so, and not lose them. Well Frescobaldi is working fine with Jack. Denemo seems to have its own method for producing sound, and is working fine also without Timidity. Regarding Ardour I do not know yet, I have not had the time to test. Kaj
Re: How to gain control over the system?
On 2017-07-12 at 03:49, Felix Miata wrote: Kaj Persson composed on 2017-07-11 22:29 (UTC+0200): ... ls -Al /home: drwxr-xr-x 39 kaj kaj 16384 jul 11 17:23 kaj OK... and from the command tree -qpadxugL 2 /home: /home ... │ ├── [drwxrwx--- root kaj ] DATA ... │ ├── [drwxrwx--- root kaj ] Hämtningar ... │ ├── [drwxrwx--- root kaj ] Musik │ ├── [drwxrwx--- root kaj ] Nedladd ... Definitely not OK, making one wonder what lurks deeper or elsewhere. and from tree -qpadxugL 3 /home/kaj/.config: OK only as deep as you went. ... I see nothing which gives me an idea of what is wrong. Are there any more files or directories to look at? In /etc perhaps? You're not done looking. Until you get all the way to the bottom, you can't know what else is wrong. You apparently need depth of at least 3 in the other hidden directories, at least 4 in .config, and probabliy 4 or more in all. Again: chown -R 1000:1000 /home/kaj/ as root should fix them all. If it doesn't, chown would seem to be broken. Maybe this in addition? chown -R 1000:1000 /home/kaj/.* Try MC in fullscreen mode. That way every listing you can see will display ownership. Some of you did react strongly on the ownership on some of the directories. They are owned by root and have group access by group kaj (1000). I tried to shortly explain why. They are mounted vfat partitions, and as far as I have succeeded to mount them, this is the result. I suppose that those people are purists with not too big experience of mixed environments. If I go solely with ext4 partitions, all this is much easier, but I have reasons to have at least half a window open towards the Microsoft world with common data, so that's it. Maybe ntfs is a better choice, and simpler to manage, but at that time, many years ago when I had to chose, the support for that file system was not sufficiently good, so my choice became vfat. As always only root can mount a file system. In the case vfat, which does not have an access system by its own, the owner of the mounted system will be root. According to "man mount" you could put the option uid=1000 (or any), and I do so in my fstab, but at least I have not got this to work. However gid=1000 works fine, and that way I get full access to the vfat partitions. I use umask=007. Possibly you could use 707, but this has not caused me any problems during all these years I have used this method. And these vfat partitions are used purely for user data: photos, documents, downloads etc. Unpacking the downloads are normally performed in an ext4 partition and run from there. Moreover chown has no impact on these mounts. The only way to change the ownership (which does not work) or group, is by umount and a new mount. Not even the option remount has any effect, at least according to my experience. Also, all files and all subdirectories inherit the owner and group properties from its parents all way up, so strictly it is sufficient to look at the top level of all mounts. In my case all mounts except /usr/local are mounted at subdirectories of /mnt. Then some of them have got an extra entry via mount --bind in $HOME, and it is those you see in the list with root as the owner. I have looked at all files down to the bottom of the tree, but this list is not suitable to present in this forum, much too long. Already the previous lists were too big, but I wanted you to see the principle. Nowhere in this huge list I can see an incorrect root influence. BUT! What I lack is power to arrange my desktop and panels. Isn't there some file somewhere in which I should be set access to these facilities, something like sudo access? Maybe a group I should belong to, or something like this? I do not have enough knowledge of all this, but I hope someone in the forum will have. /Kaj
Re: How to gain control over the system?
On 2017-07-10 at 01:36, Felix Miata wrote: Kaj Persson composed on 2017-07-09 14:54 (UTC+0200): * Regarding access to my user directory: During my search I did in fact find some files and directories owned by user root or group root. These are changed to be owned by my user id and group id, but this did not help. By the way, On this computer I have always had just one user, mine, and hence got the user id 1000 and group id 1000. This is the case now too. Are you 100% sure you found and corrected 100% of bad ones? Does 1000:1000 own $HOME? X session settings not saved is virtually always bad file permissions or errant ownership. Anything that got stolen by root:root via errant sudo or su will almost certainly have to be fixed as root, exception being via a superwizard who would unlikely ever have gotten into this trouble in the first place. You really don't need to hunt for any that are bad unless you care to know which are causing the trouble. Simply do as root: chown -R 1000:1000 /home/kaj/ using whatever your actual username is rather than kaj. Yes, I think so. Shouldn't I? All the commands in the following are given as user root. This is the output from the command ls -Al /home: drwxr-xr-x 39 kaj kaj 16384 jul 11 17:23 kaj drwx-- 2 root root 16384 sep 28 2016 lost+found drwx-- 4 root root 4096 okt 26 2016 .Trash-0 and from the command tree -qpadxugL 2 /home: /home ├── [drwxr-xr-x kaj kaj ] kaj │ ├── [drwx-- kaj kaj ] .alsaplayer │ ├── [drwxr-xr-x kaj kaj ] Bilder │ ├── [drwxr-xr-x kaj kaj ] bin │ ├── [drwx-- kaj kaj ] .cache │ ├── [drwxr-xr-x kaj kaj ] .config │ ├── [drwxrwx--- root kaj ] DATA │ ├── [drwxr-xr-x kaj kaj ] Dokument │ ├── [drwxr-xr-x kaj kaj ] dwhelper │ ├── [drwx-- kaj kaj ] .gconf │ ├── [drwx-- kaj kaj ] .gnome2 │ ├── [drwx-- kaj kaj ] .gnome2_private │ ├── [drwx-- kaj kaj ] .gnupg │ ├── [drwxrwx--- root kaj ] Hämtningar │ ├── [drwx-- kaj kaj ] .local │ ├── [drwx-- kaj kaj ] Mail │ ├── [drwxr-xr-x kaj kaj ] Mallar │ ├── [drwx-- kaj kaj ] .mozc │ ├── [drwx-- kaj kaj ] .mozilla │ ├── [drwxrwx--- root kaj ] Musik │ ├── [drwxrwx--- root kaj ] Nedladd │ ├── [drwxr-xr-x kaj kaj ] Publikt │ ├── [drwxr-xr-x kaj kaj ] Skrivbord │ ├── [drwx-- kaj kaj ] .thunderbird │ ├── [drwxr-xr-x kaj kaj ] Video ├── [drwx-- root root] lost+found └── [drwx-- root root] .Trash-0 ├── [drwx-- root root] files └── [drwx-- root root] info and from tree -qpadxugL 3 /home/kaj/.config: /home/kaj/.config ├── [drwxr-xr-x kaj kaj ] caja │ └── [drwxr-xr-x kaj kaj ] scripts ├── [drwx-- kaj kaj ] enchant ├── [drwx-- kaj kaj ] gtk-2.0 ├── [drwx-- kaj kaj ] gtk-3.0 ├── [drwx-- kaj kaj ] ibus │ └── [drwx-- kaj kaj ] bus ├── [drwxr-xr-x kaj kaj ] libreoffice │ └── [drwx-- kaj kaj ] 4 │ ├── [drwxr-xr-x kaj kaj ] cache │ └── [drwxr-xr-x kaj kaj ] user ├── [drwx-- kaj kaj ] mate │ ├── [drwx-- kaj kaj ] eom │ └── [drwx-- kaj kaj ] panel2.d │ └── [drwx-- kaj kaj ] default ├── [drwxr-xr-x kaj kaj ] mate-session │ └── [drwxr-xr-x kaj kaj ] saved-session ├── [drwx-- kaj kaj ] mc ├── [drwxr-xr-x kaj kaj ] pluma └── [drwxr-xr-x kaj kaj ] rncbc.org A few explanations: The names are partly in Swedish, but you might never the less understand them, I think. "Hämtningar" and "Nedladd" is Swedish for "Downloads". Those few directories owned by user root and group kaj are mounted file systems (FAT32) containing only user data. I have removed a few lines regarding installed programmes. I see nothing which gives me an idea of what is wrong. Are there any more files or directories to look at? In /etc perhaps? /Kaj
Re: How to gain control over the system?
Hi Jimmy, Well, I did not follow your suggestion exactly, but as people has said, the root account is already and always there, even it has not been assigned a password. So, against my real whish, not to activate the root account, I gave the command sudo passwd root, and entered a password. And now I suppose I have burned my ships and have no way back... But! Nothing has changed. I can still not enter program icons to the panel, and not define keyboard shortcuts. If I sort the icons on the desktop they still, after a cold start, come back in a completely other order, dispite I had marked "Keep ajusted" (right click on desktop). So...? /Kaj Den 2017-07-09 kl. 22:28, skrev Jimmy Johnson: On 07/08/2017 02:57 PM, Kaj Persson wrote: Hi all, So can someone help me get the command back, or do I have to make a new reinstall, hoping for better luck. Possibly setting a password on the Admin, hence activating that account, which I would prefer not having to. Thank you in advance Kaj Hi, Start the Stretch install cd/dvd in repair mode and when you get to where you can start a shell in the install at the prompt type:# passwd root and then enter the new root passwd and then reboot.
Re: How to gain control over the system?
Yes, a good try, but ... Owner and group for /home is root resp. root, and for /home/cookoo (to use your example) is the correct user name resp. group. I have also looked one level further, hence /home/cookoo/subdir/, and all directories on this level have the same ownership (=user name - group). Thank you for your efforts to help. /Kaj On 2017-07-09 at 19:21, Fungi4All wrote: I am interested in the owner of the file structure of /home/user Let's say your username is cookoo Is the owner of and its subdirectories and contents also cookoo? With your filemanager r-click properties and permissions to see owner and file access rights. If you see a number like 1008 instead of the username that is the problem. From: 70147pers...@telia.com To: debian-user@lists.debian.org Well, as I wrote my /home is an own partition, and so it has been for a long time. So it is not a new copy but a new mount. Certainly it therefore contains old config files that maybe ought to be removed. But on the other hand almost all of them are reused, since many of them belong to applications which I want to install also in the new system. Also, as I wrote, I did a test by moving all these config files into a new directory "hidden", itself not hidden despite the name, inside the home directory (and partition). /Kaj On 2017-07-09 at 15:38, Fungi4All wrote: Again, did you copy your /home from a previous system or is it a new configuration that locked your panels? UTC Time: July 9, 2017 12:54 PM From: 70147pers...@telia.com To: debian-user@lists.debian.org Thank you all for thoughts and viewpoints on what can be wrong in my installation of Debian 9. I have looked through places I might expect can contain some explanation, but so far I have not been able to exclaim an "Ah, that"s it!". Here are some of my observations: * First source of install: Well, I do know I wrote that used the live image, but to be honest, for now I am not sure, I do not remember. I had downloaded the live image as well as the install image, and most probable choice would be the later. But I do not know. Anyway the install process itself went without any problems. * At the install I made it fully new from the bottom. The only directory I kept unchanged was my home directory. This is situated on an own partition. All the others were reformatted: /, /boot, /usr, /var and /tmp. All these are on individual partitions while e.g. /etc is contained in the root partition. At earlier installations I have noticed that the home directory can contain wrong configuration files, so as a test I moved all hidden files i.e. files starting with a dot to a new created directory "hidden". This was however after the install. So at a subsequent cold start the system had no configuration files there but created new ones with default values. This however had no positive impact on my problem. * Configuring sudo? No I have not done that explicitly, not more than what the install program did itself. I have looked at /etc/sudoers and what I think the important lines are: # User privilege specification root ALL=(ALL:ALL) ALL # Allow members of group sudo to execute any command %sudo ALL=(ALL:ALL) ALL #includedir /etc/sudoers.d In /etc/sudoers.d there are no more files than README. There is no /etc/sudo.conf file. * Regarding access to my user directory: During my search I did in fact find some files and directories owned by user root or group root. These are changed to be owned by my user id and group id, but this did not help. By the way, On this computer I have always had just one user, mine, and hence got the user id 1000 and group id 1000. This is the case now too. uid 1000 is a member of the sudo group. * As I wrote I have always used this method of not setting any password to the root account, and this is for quite many years now. My Linux path has gone via Ubuntu, well to be honest a couple of years after the Microsoft era I ran in Suse, but was not fully satisfied. And when Ubuntu and Canonical introduced Unity, I left that ship for Linux Mint Debian edition (LMDE) until I took the last(?) step into Debian a couple of years ago where the entrance point was jessie. The empty root password has always worked fine until now. Possibly Ubuntu has patched the sudologin but should LMDE? And jessie? I do not think so. Hope someone can find something significant in this and give a hint on what to do. Kaj
Re: How to gain control over the system?
Well, as I wrote my /home is an own partition, and so it has been for a long time. So it is not a new copy but a new mount. Certainly it therefore contains old config files that maybe ought to be removed. But on the other hand almost all of them are reused, since many of them belong to applications which I want to install also in the new system. Also, as I wrote, I did a test by moving all these config files into a new directory "hidden", itself not hidden despite the name, inside the home directory (and partition). /Kaj On 2017-07-09 at 15:38, Fungi4All wrote: Again, did you copy your /home from a previous system or is it a new configuration that locked your panels? UTC Time: July 9, 2017 12:54 PM From: 70147pers...@telia.com To: debian-user@lists.debian.org Thank you all for thoughts and viewpoints on what can be wrong in my installation of Debian 9. I have looked through places I might expect can contain some explanation, but so far I have not been able to exclaim an "Ah, that"s it!". Here are some of my observations: * First source of install: Well, I do know I wrote that used the live image, but to be honest, for now I am not sure, I do not remember. I had downloaded the live image as well as the install image, and most probable choice would be the later. But I do not know. Anyway the install process itself went without any problems. * At the install I made it fully new from the bottom. The only directory I kept unchanged was my home directory. This is situated on an own partition. All the others were reformatted: /, /boot, /usr, /var and /tmp. All these are on individual partitions while e.g. /etc is contained in the root partition. At earlier installations I have noticed that the home directory can contain wrong configuration files, so as a test I moved all hidden files i.e. files starting with a dot to a new created directory "hidden". This was however after the install. So at a subsequent cold start the system had no configuration files there but created new ones with default values. This however had no positive impact on my problem. * Configuring sudo? No I have not done that explicitly, not more than what the install program did itself. I have looked at /etc/sudoers and what I think the important lines are: # User privilege specification root ALL=(ALL:ALL) ALL # Allow members of group sudo to execute any command %sudo ALL=(ALL:ALL) ALL #includedir /etc/sudoers.d In /etc/sudoers.d there are no more files than README. There is no /etc/sudo.conf file. * Regarding access to my user directory: During my search I did in fact find some files and directories owned by user root or group root. These are changed to be owned by my user id and group id, but this did not help. By the way, On this computer I have always had just one user, mine, and hence got the user id 1000 and group id 1000. This is the case now too. uid 1000 is a member of the sudo group. * As I wrote I have always used this method of not setting any password to the root account, and this is for quite many years now. My Linux path has gone via Ubuntu, well to be honest a couple of years after the Microsoft era I ran in Suse, but was not fully satisfied. And when Ubuntu and Canonical introduced Unity, I left that ship for Linux Mint Debian edition (LMDE) until I took the last(?) step into Debian a couple of years ago where the entrance point was jessie. The empty root password has always worked fine until now. Possibly Ubuntu has patched the sudologin but should LMDE? And jessie? I do not think so. Hope someone can find something significant in this and give a hint on what to do. Kaj
Re: How to gain control over the system?
Thank you all for thoughts and viewpoints on what can be wrong in my installation of Debian 9. I have looked through places I might expect can contain some explanation, but so far I have not been able to exclaim an "Ah, that's it!". Here are some of my observations: * First source of install: Well, I do know I wrote that used the live image, but to be honest, for now I am not sure, I do not remember. I had downloaded the live image as well as the install image, and most probable choice would be the later. But I do not know. Anyway the install process itself went without any problems. * At the install I made it fully new from the bottom. The only directory I kept unchanged was my home directory. This is situated on an own partition. All the others were reformatted: /, /boot, /usr, /var and /tmp. All these are on individual partitions while e.g. /etc is contained in the root partition. At earlier installations I have noticed that the home directory can contain wrong configuration files, so as a test I moved all hidden files i.e. files starting with a dot to a new created directory "hidden". This was however after the install. So at a subsequent cold start the system had no configuration files there but created new ones with default values. This however had no positive impact on my problem. * Configuring sudo? No I have not done that explicitly, not more than what the install program did itself. I have looked at /etc/sudoers and what I think the important lines are: # User privilege specification rootALL=(ALL:ALL) ALL # Allow members of group sudo to execute any command %sudo ALL=(ALL:ALL) ALL #includedir /etc/sudoers.d In /etc/sudoers.d there are no more files than README. There is no /etc/sudo.conf file. * Regarding access to my user directory: During my search I did in fact find some files and directories owned by user root or group root. These are changed to be owned by my user id and group id, but this did not help. By the way, On this computer I have always had just one user, mine, and hence got the user id 1000 and group id 1000. This is the case now too. uid 1000 is a member of the sudo group. * As I wrote I have always used this method of not setting any password to the root account, and this is for quite many years now. My Linux path has gone via Ubuntu, well to be honest a couple of years after the Microsoft era I ran in Suse, but was not fully satisfied. And when Ubuntu and Canonical introduced Unity, I left that ship for Linux Mint Debian edition (LMDE) until I took the last(?) step into Debian a couple of years ago where the entrance point was jessie. The empty root password has always worked fine until now. Possibly Ubuntu has patched the sudologin but should LMDE? And jessie? I do not think so. Hope someone can find something significant in this and give a hint on what to do. Kaj
How to gain control over the system?
Hi all,
Anyone having an idea how to get back the command over my desktop,
including the panels? Until two weeks ago I ran Debian 8 ("jessie"), but
after a unsuccessful clean-up operation the whole system became totally
corrupted, and I decided to to a complete new install of the new Debian
9 ("stretch") and Mate (which I was using in jessie too). I was using
the live DVD put on a memory stick. All went fine, and the system
started without problems. I was happy to notice that I could now use the
Nouveau driver for the screen. Until now I have had to use the nVidia
driver certainly without problems, but it is good being able to use free
software.
But now I discovered an issue, I cannot manage my desktop. I have always
at the previous installations, and they are quite many now, been advised
to, for security reason, leave the root password unset, which causes the
root account go passive, and for all tasks where I need root authority I
go via su/sudo. It has always worked fine, and this using su/sudo still
does. But I cannot control the panels, I have two of them, one on top
intended for icons of my most used programs, as a kind of favourite
menu, and one at bottom where the active programmes appear as buttons.
The bottom panel is working mostly as I want, but I cannot add new apps
to it, e.g. the window switch, I used to have. And I cannot add the
program icons to top panel. Via a right click on a program menu item I
have the option "Put this to the panel" (well, possibly not the correct
words, this is a home made translation from my Swedish version), but,
when trying to select that, nothing happens.
However the related options to save icon to the desktop works fine, and
I can also sort the icons to what I find useful, but it does not survive
a cold start. All the icons come back in some kind of default order,
which I have not been able found out. It is at least not alphabetic.
So can someone help me get the command back, or do I have to make a new
reinstall, hoping for better luck. Possibly setting a password on the
Admin, hence activating that account, which I would prefer not having to.
Thank you in advance
Kaj
