1 user browsing Discussion: funkyass | 2 guests | 1 bot  
Main » Discussion » (Mis)adventures on Debian ((old)stable|testing|aghmyballs)
Pages: First Previous 1 2 3 4 5 6
Posted on 19-10-02, 00:18
Full mod

Post: #353 of 418
Since: 10-30-18

Last post: 4 days
Last view: 56 min.
User is online
Recently, Debian Testing finally updated to gnome-terminal 3.34, in which they finally got around to making all the various menu-options accessible from title-bar controls, so you can use them even when the menu-bar is hidden. For a straight-up GNOME 3 desktop, that's an improvement.

For people using gnome-terminal on a non-GNOME 3 desktop, it can be a drawback. Title-bar controls mean a client-drawn title-bar, so window-managers that actually manage windows (like i3, dwm or awesome) now have extra, redundant title-bars hanging around eating up space.

I'm not angry, because it's reasonable for the GNOME people to make gnome-terminal better for GNOME at the expense of other environments, but I'm now in the market for an alternative, visually-lighter-weight terminal emulator. Unfortunately, it seems that gnome-terminal is absolutely the most polished terminal emulator around, and everything else is a step down.

My current shortlist of alternatives is:

- xterm is a bit primitive, but rock-solid, and I already have it configured to my liking.
- pterm is a straight-up port of PuTTY to POSIX, and it feels a bit weird to use it as a local terminal
- QTerminal feels weird because it's Qt-based, and sometimes it lays out Unicode text oddly

I'm definitely not interested in:

- st, because I don't want anything to do with the suckless "community"
- kitty, because I'm not interested in managing Yet Another Config File
- alacritty, ditto

The ending of the words is ALMSIVI.
Posted on 19-10-02, 04:04 (revision 1)
Custom title here

Post: #722 of 929
Since: 10-30-18

Last post: 4 days
Last view: 6 hours
Xterm also has ths advantage of trying to actually emulate the terminals it claims to emulate, instead of claiming to be a specific DEC terminal and then behaving wildly diffrently.

On the other hand, something libvte-based will probably be better-behaved with newer software because of the nesticle effect.

--- In UTF-16, where available. ---
Posted on 19-10-02, 04:14
Not from my cellphone

Post: #566 of 779
Since: 10-30-18

Last post: 2 days
Last view: 15 hours
Been using xterm since I got bored of konsole/gnome-terminal (too much stuff for my liking), even back when DEs weren't braindamaged. Normally I dislike minimalism, but come on, it's a terminal, you should not get in the way! ("tabbed terminals"? Dude, windows are free!)

I haven't even touched my xterm settings - I use whatever defaults are shipped by my distro of choice.

Yes, I know xterm has a menu. No, I've never used it intentionally.

Licensed Pirate® since 2006, 100% Buttcoin™-free
Posted on 20-05-30, 19:27
Not from my cellphone

Post: #718 of 779
Since: 10-30-18

Last post: 2 days
Last view: 15 hours
As per this comment on the related Ubuntu bugreport, adding iommu=soft seems to silence the endless stream of swiotlb bullshittery on systems using Broadcom 4401 NICs, like my Inspiron 6400.

No other side effects have been noticed so far. Unfortunately, outside the Ubuntu bugreport all reports related to this stupid bug have been stalled (or even closed), as nobody seems to care about old computers anymore, and this comes out from the OS that supports pretty much every Network Interface Chipset known to mankind...

Licensed Pirate® since 2006, 100% Buttcoin™-free
Posted on 20-09-13, 02:00 (revision 2)
Not from my cellphone

Post: #771 of 779
Since: 10-30-18

Last post: 2 days
Last view: 15 hours
In one of those very, VERY rare times when I have unrestricted/unmetered access to the Internet (not thanks to CANTV!), I managed to install nearly a year of pending updates across my active Debian fleet. I did a full "apt-get -t buster-backports dist-upgrade" to nicely bridge the gap between ol' stale Stable and the party zone at Testing. Among other things, this meant all my machines got the latest kernel on Debian, which unsurprisingly is the already-EOL 5.7 branch.

No incidents to report... except for THIS.
Those came from my oldest active Buster setup, the IBM TV box with its patched-up ATi RV630 (HD2600 in marketingspeak). Apparently the new kernel hates my card, but only in X11 - KMS framebuffer console is spotless. The wallpaper is fine, but everything else renders with that kind of corruption! Even weirder: if you look at the last screenshot, videos and 3D workloads are corruption-free - it's only things like window borders, widgets, icons and everything with which you interact with your PC! (I'm quite surprised the corruption could be captured on an ordinary screenshot - no blurrycams needed!) Needless to say, this is no bueno - this is MALO, MUCHO MUY MALO!

Things used to work fine with kernel 5.3, and indeed if I reboot to that kernel, display works flawlessly. I tried installing every linux-image release on Backports, and every since kernel starting with 5.4 exhibits the very same symptoms: consoles and 3D/videos are fine, desktop is corrupted, so it's clearly not a Mesa or Xorg bug. However, there is another workaround which I found the only one to bring some sanity back: disable KMS. With no modesetting (radeon.modeset=0), X11 is once again corruption-free, but as you already know, this kills hi-rez consoles, bootsplashes, and in general modern kernels and GPU drivers don't really like it that much (I even got the DRM bits yelling at me at the kernel log that "UMS is not compiled-in on this module" or something down these lines!). Of course this could imply that the next Debian release (Bullseye) would be a dud for this specific configuration, which would be a shame as it feels quite speedy with a half-decent GPU and plenty of RAM!

Unfortunately, while I've got some good material for a bugreport, why even bother filing a report!? To keep it languishing aside the other couple reports I've filed on kernel bugs that hit me with ZERO ACKNOWLEDGEMENT AT ALL, not even basic triaging?! Yeah, now that upstream is seriously thinking about killing AGP support I guess the only answer I would get nowadays is a "sucks to be you", not even "have this virtual money and go buy a virtual video card that won't even fit on your dinosaur" :/

Licensed Pirate® since 2006, 100% Buttcoin™-free
Posted on 20-09-13, 08:14
Post: #148 of 148
Since: 11-24-18

Last post: 5 days
Last view: 5 days
Posted by tomman

No incidents to report... except for THIS.


Oh, wow... Time to get a few used RX 550 cards?
Posted on 20-09-15, 21:49

Post: #88 of 88
Since: 11-13-19

Last post: 2 days
Last view: 7 hours
Posted by wertigon
Posted by tomman

No incidents to report... except for THIS.


Oh, wow... Time to get a few used RX 550 cards?

They make RX 550 cards in AGP form factor?
Posted on 20-09-15, 23:42 (revision 1)
Not from my cellphone

Post: #779 of 779
Since: 10-30-18

Last post: 2 days
Last view: 15 hours
Posted by kode54
Posted by wertigon
Posted by tomman

No incidents to report... except for THIS.


Oh, wow... Time to get a few used RX 550 cards?

They make RX 550 cards in AGP form factor?


Most likely this also hits the native PCIe versions of those R600 cards, and who knows what else (as ATi/AMD maintainers are focused on recent hardware nowadays). Disabling KMS fixes desktop, but kills framebuffer consoles (and I'm unsure if UVD/VDPAU/VA-API still works without KMS)

Another feature killed by recent updates: being able to use dumbphones with ModemManager: my ol' trusty (and now headless) RAZR V9x no longer gets recognized by ModemManager - not that it ever worked with it: MM always died trying to use my 3G connection (it sent some AT command related to APNs, the phone returned some empty response, MM went ballistic and segfaulted - the same phone works just fine with pon/poff and nearly every other modem dialer), SMS support was spotty (with ModemManager-GUI I wasn't even able to READ messages until a 2018 update or so, and even then it would WIPE the phone storage every time I pulled the messages out of the phone, unlike most Windows tools and Wammu). Ah well, I guess only dinosaurs use dumbphones, even if you're forced to interact with them through a PC because noone repairs broken flex cables on flip phones anymore. At least I learned how to use USSD codes via AT commands (AT+CUSD=1,"*144#") since that's the only way you can check your prepaid balance on Movistar phones over here, and even THAT was broken on ModemManager too!

The Broadcom NIC on my Dell still causes the kernel to complain, but iommu=soft still keeps things under control - that's yet another bug noone cares about fixing anytime soon (on that related Ubuntu bugreport, people hasn't had the same luck as me with this workaround, but it's fine - who uses wired NICs nowadays?).

I had finally to bite another bullet and install VirtualBox from official upstream .DEBs since the packages on Sid are too new for Buster, and the old Sid version I had installed now has an incompatible kernel module which breaks your setup on anything past 5.4 - great, more bloody red Orrible® branding on my desktop. Guess next time I have unmetered access I'll play a bit with KVM/QEMU and friends, as VirtualBox is slowly earning a place into my shitlist :/

Licensed Pirate® since 2006, 100% Buttcoin™-free
Pages: First Previous 1 2 3 4 5 6
Main » Discussion » (Mis)adventures on Debian ((old)stable|testing|aghmyballs)
Yes, it's an ad.