[gentoo-user] mail -s "IP address change" $EMAIL
echo "New IP address: $NEW_IP" | mail -s "IP address change" $EMAIL Doesn't work! -- Thelma
Re: [gentoo-user] using Wifi in a new machine : solved
After much investigation, I've finally got Wifi working in my new machine. There were 2 serious problems : the firmware had been updated to a new version number (7961 from 7921), which I was able to find in System Rescue /lib/firmware (it wasn't in the latest Gentoo firmware pkg). Then many tries failed to get Wpa-supplicant to start via RC : every time, it failed to start because it couldn't find an interface (the failure seems to be due to Udev/Dhcpcd/W-S tripping over one another). Finally, I removed it from the default runlevel & started it after boot + login via 'rc-service ... start'. There's a 15 sec delay, then 'ip a' shows carrier + IP numbers (it doesn't change the name from 'wlan0', but that doesn't matter). I've aliased the start command as 'wifi' in /root/.bashrc , which allows an easy start-up after every reboot (I insist on long-standing UNIX procedure & do all system management in a root console). The w-p conf file I'm using is as simple as cb , showing only SSID PSK priority . This is a desktop system in the basement of a downtown house : the Wifi server is upstairs over my head. FYI for anyone else who finds her/himself stuck in this way. -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] some help with wayland
Still some work to do, but much better now. In the sterr output when run as a new user where both screens are used, I saw Checking screens: available: (QScreen(0x55723012fa90, name="DVI-I-1"), QScreen(0x55723011a010, name="DVI-I-2")) redundant: QHash() fake: QSet() all: (QScreen(0x55723012fa90, name="DVI-I-1"), QScreen(0x55723011a010, name="DVI-I-2")) but run as my regular user, where wayland only finds one screen, I saw Checking screens: available: (QScreen(0x55ff257aaaf0, name="DVI-I-2")) redundant: QHash() fake: QSet() all: (QScreen(0x55ff257aaaf0, name="DVI-I-2")) After flailing about trying to figure out why one of the monitors didn't seem to be available, I found kscreen-doctor and I realized that I COULD select the "missing" monitor in the Display Settings and enable it. I'm still having problems getting that change and the relative positioning of the two monitors to stick across sessions, but at least I've now got stuff to work with. Thanks for the pointers.
Re: [gentoo-user] some help with wayland
On 2023.06.10 13:07, Michael wrote: On Saturday, 10 June 2023 18:00:34 BST Jack wrote: > I have also had odd behavior with X and two monitors, but I always > managed to get it working without excessive effort. My most persistent > problem was if the right monitor was plugged into the primary output, > reordering the monitors in the Display Settings would eventually get > lost and require me to do it again. At this point I can't remember why > I was so against just switching the cables. In my use case, it was related the user wanting a higher quality calibrated monitor on the right hand side to examine and process photographic samples of products, while the left was used to set up layouts and run usual productivity apps. > Final point - I still haven't found where the wayland log is when not > using sddm. > > Jack When you logout and return to the console from which you launched wayland, isn't there some output showing what was running and any problems with it? Nothing that (at the time) made any sense to me. What was happening is that I was inadvertently launching startplasma-wayland with xorg running, so I can see KWin getting confused. Now that I understand that, I can try again and see if the output actually gives any hint(s) I missed.
Re: [gentoo-user] Can't upgrade portage or update/install ebuilds
Nikolay Pulev schrieb am 10.06.23 um 11:47: Thank you Daniel. You suggestion got me going. You are welcome! I hope it was the only problem. If yes then installing from scratch would have been a waste of time. It is never wrong to get to know your system better. Then in most cases you can solve such things within minutes and you don't need the sledgehammer. -- Regards Daniel
Re: [gentoo-user] some help with wayland
On Saturday, 10 June 2023 18:00:34 BST Jack wrote: > I have also had odd behavior with X and two monitors, but I always > managed to get it working without excessive effort. My most persistent > problem was if the right monitor was plugged into the primary output, > reordering the monitors in the Display Settings would eventually get > lost and require me to do it again. At this point I can't remember why > I was so against just switching the cables. In my use case, it was related the user wanting a higher quality calibrated monitor on the right hand side to examine and process photographic samples of products, while the left was used to set up layouts and run usual productivity apps. > Final point - I still haven't found where the wayland log is when not > using sddm. > > Jack When you logout and return to the console from which you launched wayland, isn't there some output showing what was running and any problems with it? signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] some help with wayland
On 2023.06.10 04:44, Michael wrote: On Saturday, 10 June 2023 01:19:06 BST Jack wrote: I've been running xorg (KDE Plasma) for years, and have been perfectly happy, but every now and then I have tried wayland, with less or even less success. My recent attempts give me a plasma session in the upper 1024 x 768 of a monitor that does 1920x1080. It also doesn't recognize the second monitor at all. However, the mouse cursor moves freely across all of both monitors. Stating the obvious, but have you tried systemsettings to change the Display resolution? Logout, then login. Display Settings said that 1024x768 was the only available resolution. (see below) Also, have you tried dropping into a console and back again into the wayland desktop? Same behavior. I know some of the above sounds like cargo-culting, but I have found them to work with mixed results. I've seen stranger things work. I'm not sure what in your response that gave me a clue, but although I modified .xinitrc into .winitrc to use startplasma-wayland, I was still calling it with startx. DOH! So now, just running .winitrc gets me full resolution. However, running as a new user, it sees both monitors, but running as my existing user, it only sees one monitor. At least now I can start digging through changes in .login/.config between the two users. I've modified /etc/default/grub per the Wayland wiki page with no change. My main question right now is where to find any log of the wayland session. There is a KDE page which says where to look if you launch wayland from sddm, but I'm launching from a command line, using startx, with the last line in .winitrc (so I can also keep my original .xinitrc) of either "exec dbus-run-session startplasma-wayland" or "exec dbus-launch --sh-syntax --exit-with-session startplasma-wayland". Without sddm, you can run the startplasma-wayland stanza from a console, do your thing, logout and the console would have captured various logs - just as startx does. still didn't notice anything useful in the output, other than finally noticing that X was still starting when I least expected it. Alternatively, to check wayland or xwayland applications from within wayland, run in a terminal: I might still try that, but it's that basic system, not any particular application that was the issue. Thanks for the clue, or at least triggering me to find it. qdbus org.kde.KWin /KWin org.kde.KWin.showDebugConsole I moved to wayland 2-3 years ago for the opposite reasons to you. After the odd update(s) Xorg had started playing up with two monitors, causing the Plasma Task Manager to disappear, messing up the resolution, switching the primary monitor from left to right, and other problems I can't recall. Reconfiguring Plasma settings would not survive a reboot. I never bottomed out the causes of these problems (Plasma, Xorg video driver, mesa) and was about to give up on Plasma when I thought of trying out Wayland. Surprisingly Wayland provided a more stable desktop than Xorg had become! I have three systems running Wayland, all with radeon graphics. I don't know if Nvidia needs particular tweaking for NVENC, I've no experience with Nvidia in general. An intel laptop with Enlightenment works in Wayland, although the odd xwayland application fails to launch (e.g. Gkrellms). I have also had odd behavior with X and two monitors, but I always managed to get it working without excessive effort. My most persistent problem was if the right monitor was plugged into the primary output, reordering the monitors in the Display Settings would eventually get lost and require me to do it again. At this point I can't remember why I was so against just switching the cables. Final point - I still haven't found where the wayland log is when not using sddm. Jack
Re: [gentoo-user] blue screen / no signal detected
Sounds like the cable failed. Can you replace it or is it built in on one end? The change is probably because it's bent different. Sometimes failed cables sort of work when bent the right way, but not for long. --"Fascism begins the moment a ruling class, fearing the people may use their political democracy to gain economic democracy, begins to destroy political democracy in order to retain its power of exploitation and special privilege." Tommy Douglas Jun 10, 2023, 07:29 by the...@sys-concept.com: > My PC showing on my monitor blue screen. When I connect it to another > monitor I get no signal detected (using HDMI). > > I can log-in to that PC over network but get no signal detected on the > monitor. > > Did the video go? > > The card it has is: Nvidia TU117 [GeForce GTX 1650] > > -- > Thelma >
[gentoo-user] blue screen / no signal detected
My PC showing on my monitor blue screen. When I connect it to another monitor I get no signal detected (using HDMI). I can log-in to that PC over network but get no signal detected on the monitor. Did the video go? The card it has is: Nvidia TU117 [GeForce GTX 1650] -- Thelma
Re: [gentoo-user] KWallet refuses to auto open at login
Does a new user account work the way it is supposed to? On Sat, 10 Jun 2023, 07:33 Victor Ivanov, wrote: > Hello fellow penguins, > > I have to admit I'm at my wits' end with KWallet. This thing has been > driving me insane for the last couple of weeks, roughly since the > upgrade to Plasma 5.27 or shortly after. > > Every time I log in, it refuses to automatically open and prompts for > a password whenever an application wants to read secrets. Admittedly, > this is under Wayland which, following from recent news re this being > the Gentoo preference, I decided to give a try. But this also happens > under X11, so I doubt it's got anything to do with Wayland. > > I've tried everything I can think of: > - I've double checked the auto unlock guide in the Gentoo Wiki, made > sure PAM rules are in place and kwallet-pam is installed. Which should > be all good regardless, as it used to work just fine; > - I've also oneshot all of: kde-plasma/ , kde-frameworks/ , kde-apps/ > , and anything returned by "eix -I# pam", "eix -I# xdg", and "eix -I# > dbus" > - when the above failed to yield any meaningful resolution, I repeated > the one-shot step this time with "--noconfmem" and re-reviewed any > changes from the default configs; > - finally, I nuked all of my $HOME settings under ~/.config, ~/.cache, > and ~/.local and started from scratch; > - and yes, the KWallet was set up and re-setup (plenty of times) with > Blowfish with the same password as my login; > > The irony is, I have an equivalent Gentoo setup on a separate machine, > also moved to Wayland at the same time as I keep them both up to date > at the same intervals, and it works flawlessly. I've recursively > diff'd all config files under /etc between the two hosts and, other > than some minor, unrelated host-specific differences, everything is > identical, including configs under /etc/pam.d. > > I can get it to kind of work with a blank password, but that's not the > point and is not a viable "solution". Even then, it still doesn't auto > open, but at least it doesn't produce annoying prompts to open. > > I've always despised KWallet for its flaky behaviour but for the last > few years it hadn't given me any issues up until now. > > I'm truly bewildered. Is there anything I am missing? > > Best Regards, > Victor > >
[gentoo-user] KWallet refuses to auto open at login
Hello fellow penguins, I have to admit I'm at my wits' end with KWallet. This thing has been driving me insane for the last couple of weeks, roughly since the upgrade to Plasma 5.27 or shortly after. Every time I log in, it refuses to automatically open and prompts for a password whenever an application wants to read secrets. Admittedly, this is under Wayland which, following from recent news re this being the Gentoo preference, I decided to give a try. But this also happens under X11, so I doubt it's got anything to do with Wayland. I've tried everything I can think of: - I've double checked the auto unlock guide in the Gentoo Wiki, made sure PAM rules are in place and kwallet-pam is installed. Which should be all good regardless, as it used to work just fine; - I've also oneshot all of: kde-plasma/ , kde-frameworks/ , kde-apps/ , and anything returned by "eix -I# pam", "eix -I# xdg", and "eix -I# dbus" - when the above failed to yield any meaningful resolution, I repeated the one-shot step this time with "--noconfmem" and re-reviewed any changes from the default configs; - finally, I nuked all of my $HOME settings under ~/.config, ~/.cache, and ~/.local and started from scratch; - and yes, the KWallet was set up and re-setup (plenty of times) with Blowfish with the same password as my login; The irony is, I have an equivalent Gentoo setup on a separate machine, also moved to Wayland at the same time as I keep them both up to date at the same intervals, and it works flawlessly. I've recursively diff'd all config files under /etc between the two hosts and, other than some minor, unrelated host-specific differences, everything is identical, including configs under /etc/pam.d. I can get it to kind of work with a blank password, but that's not the point and is not a viable "solution". Even then, it still doesn't auto open, but at least it doesn't produce annoying prompts to open. I've always despised KWallet for its flaky behaviour but for the last few years it hadn't given me any issues up until now. I'm truly bewildered. Is there anything I am missing? Best Regards, Victor
Re: [gentoo-user] Can't upgrade portage or update/install ebuilds
Thank you Daniel. You suggestion got me going. Kind regards, Nikolay
Re: [gentoo-user] some help with wayland
On Saturday, 10 June 2023 01:19:06 BST Jack wrote: > I've been running xorg (KDE Plasma) for years, and have been perfectly > happy, but every now and then I have tried wayland, with less or even > less success. My recent attempts give me a plasma session in the upper > 1024 x 768 of a monitor that does 1920x1080. It also doesn't recognize > the second monitor at all. However, the mouse cursor moves freely > across all of both monitors. Stating the obvious, but have you tried systemsettings to change the Display resolution? Logout, then login. Also, have you tried dropping into a console and back again into the wayland desktop? I know some of the above sounds like cargo-culting, but I have found them to work with mixed results. > I've modified /etc/default/grub per the > Wayland wiki page with no change. My main question right now is where > to find any log of the wayland session. There is a KDE page which says > where to look if you launch wayland from sddm, but I'm launching from a > command line, using startx, with the last line in .winitrc (so I can > also keep my original .xinitrc) of either "exec dbus-run-session > startplasma-wayland" or "exec dbus-launch --sh-syntax > --exit-with-session startplasma-wayland". Without sddm, you can run the startplasma-wayland stanza from a console, do your thing, logout and the console would have captured various logs - just as startx does. Alternatively, to check wayland or xwayland applications from within wayland, run in a terminal: qdbus org.kde.KWin /KWin org.kde.KWin.showDebugConsole I moved to wayland 2-3 years ago for the opposite reasons to you. After the odd update(s) Xorg had started playing up with two monitors, causing the Plasma Task Manager to disappear, messing up the resolution, switching the primary monitor from left to right, and other problems I can't recall. Reconfiguring Plasma settings would not survive a reboot. I never bottomed out the causes of these problems (Plasma, Xorg video driver, mesa) and was about to give up on Plasma when I thought of trying out Wayland. Surprisingly Wayland provided a more stable desktop than Xorg had become! I have three systems running Wayland, all with radeon graphics. I don't know if Nvidia needs particular tweaking for NVENC, I've no experience with Nvidia in general. An intel laptop with Enlightenment works in Wayland, although the odd xwayland application fails to launch (e.g. Gkrellms). signature.asc Description: This is a digitally signed message part.
