tde-users May 2018

users@trinitydesktop.org

33 participants
51 discussions

[ Re-send ] Explaining the process of adding bugs to next TDE release

by Michele Calgaro

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Dear all, re-sending without autocrypt option. There has been some reports of problems with SPAM filters discarding the previous email. If you already received the first message yesterday, please ignore this one and accept our apologies for the double sending. If you didn't get the original email, please read below. Cheers Michele, Slavek - -------------------- Dear all, we would like to explain the process of how bug reports get added to the next release bug list. As many of you probably know, there are some bug reports (that we call meta bugs) that serve as an index for bugs to fix or already fixed for the next maintenance and minor release. For example bug 2247 for R14.1.0, bug 2696 for R14.0.5 and bug 2885 for R14.0.6. These meta bugs are intended to list bugs that have been selected by the developers for the mentioned coming release, so we would like to invite all of you to refrain from directly adding bugs to those lists on your own. Instead you should first discuss with one of the developers (say Tim, Slavek or Michele) and if agreed, you can then add the bug to the discussed list. The reason for this logic (and limitation) is that if anyone just add bugs indiscriminately based on their own needs, those lists would grow out of control and out of what is physically possible to achieve with the development workforce that TDE has at the moment. We encourage all of you to participate in making TDE better, but please take note of the above procedure and try sticking to it as much as possible. On a side note, R14.0.5 bug list has been frozen and no other bugs will go into it unless critical of blockers. Of course, if a working patch is provided before the release of R14.0.5, we will consider that for inclusion. Feel free to provide your feedback on the process explain above Cheers Michele, Slavek -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAlsD2uwACgkQKnW3yore 1c9tjw/9GTvzkZULvstj5VBBWjdJgfbkFQ+hDq8c7cRleKDqDwwK89uSdWshe6G7 VU5fwH82CScdF4itYr8GxZvwmZPcLtPvy83WLsEPL4pvC8oNoUZtHkqNniL8CP14 wfiUZcFuQvMa251i2KP0a1QBREd8xJhbj09obfz8YFa9sRQq0cauMgMDqxVOR+6U 0MU8CgTNplh49XWAjX9e5upwsgvqEb58e53h0XsYOn9aM+tvUOnCaKA83eIlICUe R6qt5807sKPbd2fXlpSNmtprPllwo/OKse/KUrCq0a3hifG64xapwub/S+ylGFpf Q2RfHxvKVUnSOyElNe7wYYjVhBv5qCcGO4mE7uR8TwsN3ta2vL226aw5rNv8Oarb nNKrjBO5Ey3F4wxhFI5ZNOmQqU6eqSvqwiT2lN2nVZ0CCuXGDScXcHo8gLM3j6la 9hSE/R8KouLtef2NyrFB1ObWtn2p4geAbQKVTyr9sQyS2K07Fyub2qeamdJeOyEV 1HtCzK+ot3QwD+jrTfQEigJGUitW4DPfy6iVLHBJz+B5kkOspYJq8Ks9EQh/Zya0 BNRKpqettm6RlOchuNHa7NWuPOyQUyyPnBI371+EsBAohZdgm0Nuis9RYVnoXII0 YO9F31g8dfY9rCTJ9CkFV4GpA6879uswTcxEf/AEod/m4ZdhnR8= =lSLn -----END PGP SIGNATURE-----

6 years, 7 months

a miracle has happened!

by dep

the final part of my upgrade saga was installation of new nvidia drivers, which has in the past taken at least two days and required anguish, blood sacrifices to unknown demons, and angry outburts at anyone who encounters me. but i just now installed the nvisia drivers for ubuntu-16.04 and they . . . just worked! (the act of writing my particular configuration, primaty monitor below secondary monitor, won't write to the x.org configuration file, so i have to redo it on every reboot, but that's as it has always been.) now if i could cook up the mouse cursor i've wanted ever since i switched from OS/2 to linux. there was an OS/2 utility that allowed one to write one's own mouse (and other) cursors, and i got it and used it and loved it because it was possible to make a pointer arrow that was the reverse of whatever it was over -- black on white, white on black, blue on red, etc., to the point of even being half one color and half the other when it rested on an edge. this made it manifestly visible, always. linux has nothing to match it and i intend to undertake a course of study that will result in its being replicated for linux. i'll send postcards. -- dep Sent with ProtonMail Secure Email. Because privacy matters.

6 years, 7 months

Explaining the process of adding bugs to next TDE release

by Michele Calgaro

Dear all, we would like to explain the process of how bug reports get added to the next release bug list. As many of you probably know, there are some bug reports (that we call meta bugs) that serve as an index for bugs to fix or already fixed for the next maintenance and minor release. For example bug 2247 for R14.1.0, bug 2696 for R14.0.5 and bug 2885 for R14.0.6. These meta bugs are intended to list bugs that have been selected by the developers for the mentioned coming release, so we would like to invite all of you to refrain from directly adding bugs to those lists on your own. Instead you should first discuss with one of the developers (say Tim, Slavek or Michele) and if agreed, you can then add the bug to the discussed list. The reason for this logic (and limitation) is that if anyone just add bugs indiscriminately based on their own needs, those lists would grow out of control and out of what is physically possible to achieve with the development workforce that TDE has at the moment. We encourage all of you to participate in making TDE better, but please take note of the above procedure and try sticking to it as much as possible. On a side note, R14.0.5 bug list has been frozen and no other bugs will go into it unless critical of blockers. Of course, if a working patch is provided before the release of R14.0.5, we will consider that for inclusion. Feel free to provide your feedback on the process explain above Cheers Michele, Slavek

6 years, 7 months

but now no scrollbars in gnome apps

by dep

i used only a few gnome apps, the most indespensible of which id gthumb. i just opened it for the first time since the upgrade and found navigation impossible: there are no scrollbars! might anyone here know the package that contains the scrollbars? -- dep Sent with ProtonMail Secure Email. Because privacy matters.

6 years, 7 months

ha!

by dep

still haven't fixed artsd -- what package is it in, that i might try to reinstall or something? -- but i am writing this on trinity's kmail, through the protonmail bridge, which encrypts it and sends it down the pipe to their server, which sends it out in whatever form the list receives it. which i suspect is a first. a minor first to be sure, but a first. -- dep Sent with ProtonMail Secure Email. Because privacy matters.

6 years, 7 months

make ot stop, part II

by dep

so when i logged back in to tde, there was a box asking if i had noticed that artsd had been having a tantrum and was i tired of hearing from it. i clicked on "hell yes, where were you five minutes ago" and am in without issue. now. how might i sort this and fix it? anybody know? dep Sent with [ProtonMail](https://protonmail.com/) Secure Email. Because privacy matters.

6 years, 7 months

make it stop!

by dep

well, things went *mostly* well with the upgrade. but this evening a started getting *many* segfaults re. artsd, at the rate of one every few seconds. each throws a window that grabs focus, making impossible even to see what's going on. we're talking hundreds of them. i can't even logout! HELP!!!! Thanks in advance. dep Sent with [ProtonMail](https://protonmail.com/) Secure Email. Because privacy matters.

6 years, 7 months

user-dependent compose combinations

by D. R. Evans

Does anyone have instructions as to how to add compose key combinations for an individual user? I have seen quite several mutually-exclusive methods that are purported to work, but I haven't had any success here. Here is the current situation (which does not work): $ locale LANG=en_US.UTF-8 Following the man page for Compose, I have the following ~/.XCompose file, which should (according to the man page) import the system-wide Compose file for my locale, and add one extra entry (for testing purposes): ---- include "%L" # import the default Compose file for your locale <Multi_key> <asterisk> <asterisk> : "⁂" asterism # ASTERISM ---- But when I try to enter a compose sequence, it seems that only the ones in the system-wide file are used. For example, the system file /usr/share/X11/locale/en_US.UTF-8/Compose has the following lines: ---- <Multi_key> <asterisk> <0> : "°" degree # DEGREE SIGN <Multi_key> <0> <asterisk> : "°" degree # DEGREE SIGN ---- if, in this e-mail, I type the sequence: compose * 0 then, as expected, I see: ° but if I similarly type the sequence: compose * * I see: [i.e., nothing] I've probably done something stupid, like made a typing error somewhere, but I've stared at the files, and re-read the man page multiple times, and I just don't see why what I've done doesn't work. I have rebooted, just to make sure that the files are read correctly; to no avail. (Probably just a restart of the X server is needed [if that], but rebooting seemed more certain.) Doc PS I am on debian stable, fully up to date. -- Web: http://enginehousebooks.com/drevans

6 years, 7 months

trying now to solve a kmail puzzle

by dep

hi, everybody . . . after a little research, and spurred by that pile of stuff that wanted to be autoremoved, i went ahead last night and changed my sources.list to reflect Ubuntu-16.04-LTS and Preliminary Stable and did apt-get update and apt-get dist-upgrade. (ubuntu has traditionally supported LTS-to-LTS upgrades, which makes sense.) and so far, fingers crossed, everything is working. now comes the part that largely sparked all this upgrade frenzy (though the gemini project has figured in, too, this is now about my desktop machine): getting kmail to work with protonmail. i seem to have all the pieces installed. but there are some configuration issues that i cannot sort -- i simply don't know that much about the mechanics of email. i have the beta of the protonmail bridge, which is alleged to allow use of a local mail client in linux rather than being tied to protonmail's admittedly very nice webmail. the only configuration example they give, though, is thunderbird. might someone who knows mail well look through here and give me a sense of the analogs in kmail? most of it i can sort out, but such as the "IMAP exception" confounds me, as does where i'm supposed to tell kmail about 127.0.0.1:1143 and 127.0.0.1:1025. i know the numbers after the colons are the port, but no idea about the 127.0.0.1. there are a couple of other things that also puzzle me. the instructions, for thunderbird, are here: https://protonmail.com/bridge/thunderbird#1 that failing, does anyone know of a good way to export vast kmail message archives to thunderbird? dep Sent with [ProtonMail](https://protonmail.com/) Secure Email. Because privacy matters.

6 years, 7 months

have i wrecked everything here?

by dep

evening, folks . . . i just attempted to install a deb package, which failed for the lack of some qt5 widgets. so i ran apt-get -f install, and after it ran it informed me of this: The following packages were automatically installed and are no longer required: acpi amarok-common-trinity amarok-engine-xine-trinity amarok-trinity arts-trinity bluetooth bluez-utils crystalcursors desktop-effects-tde-trinity dmz-cursor-theme fonts-arabeyes foo2zjs fortune-mod fortunes-min fotoxx-common gir1.2-ges-1.0 gir1.2-gst-plugins-base-0.10 gir1.2-gst-plugins-base-1.0 gir1.2-gstreamer-0.10 gir1.2-gstreamer-1.0 gstreamer1.0-gnonlin gtk-qt-engine-trinity gtk3-tqt-engine-trinity gwenview-trinity kaffeine-trinity karm-trinity katapult-trinity kbstate-trinity kdbusnotification-trinity keep-trinity kmag-trinity kmailcvt-trinity kmousetool-trinity kmplayer-base-trinity kmplayer-konq-plugins-trinity konversation-trinity kopete-trinity kpf-trinity kppp-trinity krdc-trinity krfb-trinity ksplash-engine-moodin-trinity ksystemlog-trinity ktorrent-trinity kubuntu-default-settings-trinity kubuntu-konqueror-shortcuts-trinity kvkbd-trinity landscape-client landscape-common lftp libavahi-tqt-1 libccfits0 libcfitsio3 libdbus-tqt-1-1c2 libges-1.0-0 libifp4 libjs-sphinxdoc libmp4v2-2 libnjb5 libqt5concurrent5 libraw9 librsync1 libscim8c2a min12xxw pnm2ppa powermanagement-interface pxljr python-gst-1.0 python-pylibacl python-pyxattr qt4-tqt-theme-engine rdesktop rdiff-backup scim-bridge-client-qt scim-im-agent scim-modules-socket screen speedcrunch splix strigi-daemon synaptic-trinity tqca-tls ttf-arabeyes ttf-arphic-ukai ttf-arphic-uming ttf-lao ttf-malayalam-fonts ttf-thai-tlwg ttf-unfonts-core now, clearly some of these i really do not need -- ttf-malayalam-fonts comes to mind -- but there's a lot of trinity stuff that is listed here. am i safe in telling it that, yes, it may autoremove these? it seems a little much. dep Sent with [ProtonMail](https://protonmail.com/) Secure Email. Because privacy matters.

6 years, 7 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

tde-users May 2018