Fosstodon

0 posts0 participants0 posts today

IPFire NewsFound a bug? Report it at <a href="https://bugzilla.ipfire.org/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://bugzilla.ipfire.org/</a> and help the making IPFire better! <a href="https://social.ipfire.org/tags/bugzilla" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bugzilla</a>

dusoftEnshittification you say? Well, Mozilla has got enough flak recently due to <a href="https://fosstodon.org/tags/AI" class="mention hashtag" rel="tag">#AI</a>. But basic stuff like file handling on <a href="https://fosstodon.org/tags/Firefox" class="mention hashtag" rel="tag">#Firefox</a> does not work properly as I have documented in this <a href="https://fosstodon.org/tags/bug" class="mention hashtag" rel="tag">#bug</a> report: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1956508" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://bugzilla.mozilla.org/show_bug.cgi?id=1956508</a> <a href="https://fosstodon.org/tags/bugzilla" class="mention hashtag" rel="tag">#bugzilla</a> <a href="https://fosstodon.org/tags/bugs" class="mention hashtag" rel="tag">#bugs</a> <a href="https://fosstodon.org/tags/ux" class="mention hashtag" rel="tag">#ux</a> <a href="https://fosstodon.org/tags/ui" class="mention hashtag" rel="tag">#ui</a>

Hacker NewsDigiCert: Threat of legal action to stifle Bugzilla discourse — <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1950144" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://bugzilla.mozilla.org/show_bug.cgi?id=1950144</a> <a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/DigiCert" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DigiCert</a> <a href="https://mastodon.social/tags/Bugzilla" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bugzilla</a> <a href="https://mastodon.social/tags/LegalAction" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LegalAction</a> <a href="https://mastodon.social/tags/Discourse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Discourse</a> <a href="https://mastodon.social/tags/Cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Cybersecurity</a> <a href="https://mastodon.social/tags/Mozilla" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mozilla</a>

Matěj Cepl 🇪🇺 🇨🇿 🇺🇦There is something sad about a project where blog posts start with “Surprise! <a href="https://en.osm.town/tags/Bugzilla" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bugzilla</a>’s not dead yet. :-)”<a href="https://www.bugzilla.org/blog/2022/12/13/upcoming-releases-and-more-fun-stuff/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.bugzilla.org/blog/2022/12/13/upcoming-releases-and-more-fun-stuff/</a>

Howard Chu @ Symas<a href="https://mastodon.social/@mhoye" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mhoye</a> <a href="https://mastodon.social/@gvwilson" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@gvwilson</a> that's why we run our own <a href="https://mastodon.social/tags/Bugzilla" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bugzilla</a> instance for <a href="https://mastodon.social/tags/OpenLDAP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenLDAP</a> and never use github's issue tracker. Always run your own infrastructure. We only mirror our code to github, nothing more.

Hessenhelden<a href="https://mastodon.world/@petsoi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@petsoi</a> Das Problem mit der GNOME-Fehlermeldungs-App ist, dass ich sie einfach nicht zum Laufen bekomme. Das bedeutet, ich kann darüber keine Fehler an Bugzilla melden, und ich habe keine Ahnung, woran es liegt. Vielen Dank für den Link zu den alternativen <a href="https://mastodon.social/tags/Trackern" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Trackern</a> – ich werde sie mir genauer ansehen!<a href="https://mastodon.social/tags/GNOME" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNOME</a> <a href="https://mastodon.social/tags/Bug" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bug</a> <a href="https://mastodon.social/tags/Bugzilla" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bugzilla</a> <a href="https://mastodon.social/tags/Fehlermeldung" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fehlermeldung</a>

HessenheldenBis <a href="https://mastodon.social/tags/Fedora" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fedora</a> 39 war es mir möglich, Fehler über den Bugtracker von <a href="https://mastodon.social/tags/GNOME" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNOME</a> zu melden. Doch seit der Neuinstallation von Fedora 40ff scheint meine Konfiguration nicht mehr akzeptiert zu werden. Die Optionen im GNOME Bugtracker sind begrenzt, so dass es kaum Spielraum für Fehler gibt – oder vielleicht entgeht mir einfach etwas.<a href="https://mastodon.social/tags/GNOME4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNOME4</a> <a href="https://mastodon.social/tags/GNOME47" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNOME47</a> <a href="https://mastodon.social/tags/Bug" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bug</a> <a href="https://mastodon.social/tags/Bucktracker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bucktracker</a> <a href="https://mastodon.social/tags/Fehlermeldung" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fehlermeldung</a> <a href="https://mastodon.social/tags/Bugzilla" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bugzilla</a>

mgorny-nyan (on) :autism:🙀🚂🐧Gdyby ktoś potrzebował zaktualizować tytuły setek zgłoszeń na Bugzilli z automatu, np. podmieniając starą nazwę paczki na nową, to proponuję mój nowy wynalazek… bugsed!<a href="https://github.com/projg2/bugsed" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/projg2/bugsed</a>A, i wszystkie paczki <a href="https://pol.social/tags/LLVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLVM</a> w <a href="https://pol.social/tags/Gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gentoo</a> są teraz w kategoriach llvm-*/.<a href="https://pol.social/tags/Bugzilla" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bugzilla</a>

mgorny-nyan (he) :autism:🙀🚂🐧Ever needed to update summaries of hundred of <a href="https://social.treehouse.systems/tags/Bugzilla" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bugzilla</a> bugs automatically, e.g. by updating the package name? I give you… bugsed!<a href="https://github.com/projg2/bugsed" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/projg2/bugsed</a>Oh, and all <a href="https://social.treehouse.systems/tags/LLVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLVM</a> packages in <a href="https://social.treehouse.systems/tags/Gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gentoo</a> are now in llvm-*/ categories.

Tcl/TkDid you know?In 1998, <a href="https://fosstodon.org/tags/Bugzilla" class="mention hashtag" rel="tag">#Bugzilla</a>, one of the first products of mozilla.org, was originally written in <a href="https://fosstodon.org/tags/Tcl" class="mention hashtag" rel="tag">#Tcl</a> by Terry Weissman for use at <a href="https://fosstodon.org/tags/mozilla" class="mention hashtag" rel="tag">#mozilla</a>.org (to replace the in-house system then in use at Netscape).It was then soon rewritten in Perl, though.

BugzillaIt's <a href="https://techhub.social/tags/GivingTuesday" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GivingTuesday</a> and what better time to give to <a href="https://techhub.social/tags/Bugzilla" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bugzilla</a> ? We have quite a ways to go to meet our goal of being able to hire a developer for the project to keep your updates coming faster, so won't you consider a recurring donation? Even a dollar or two per month would be fine because it all adds up. One time donations are accepted as well. <a href="https://bugzilla.org/donate" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://bugzilla.org/donate</a>

Nemo_bis 🌈<a href="https://tech.lgbt/@jinna" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jinna</a> Sorry for the frustrating experience. Personally I appreciate being able to change all fields in the bug report at the same time as I'm adding a comment, the way it works in <a href="https://mamot.fr/tags/bugzilla" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bugzilla</a>.

MediaWikiIt's a few days late, But this year is our 10th anniversary of the <a href="https://wikis.world/tags/WikimediaFoundation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WikimediaFoundation</a> started it's final steps in the <a href="https://wikis.world/tags/Bugzilla" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bugzilla</a> to <a href="https://wikis.world/tags/Phabricator" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Phabricator</a> migration, On the 2014-11-21 the import of the old Bugzilla archives into the Phabricator started, access to Phabricator to the public was reopened 2014-11-24.

justforfunLooks like I’ll be signing up for <a href="https://fosstodon.org/tags/bugzilla" class="mention hashtag" rel="tag">#bugzilla</a>, I was able to search through their reports and found this has been reported as recently as this May, but not reproduced. Once again, thank you <a href="https://mastodon.online/@thunderbird" class="u-url mention">@thunderbird</a> and a shoutout to <a href="https://layer8.space/@killyourfm" class="u-url mention">@killyourfm</a> who’s recent work and efforts on their marketing team got me to reinstall and make it my default client once again.

TomAoki<a href="https://soc.feditime.com/users/Tubsta" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Tubsta</a> You'd better posting the ports name, PR number (Bug *****) and/or its URL so that attracting eysballs of someone who can help you.😉 <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a> <a href="https://mastodon.bsd.cafe/tags/Bugzilla" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bugzilla</a>

Mehrad :kde: :emacs: :rstats:Everytime I want to file a bug for <a href="https://floss.social/@kde" class="u-url mention">@kde</a> I feel awkward and bad that I have to deal with bugzilla. I should say that KDE's bugzilla is more organized and clear than LibreOffice bugzilla, but nontheless, it is ugly, painful, weird, and overall unpleasant experience.<a href="https://fosstodon.org/tags/Bugzilla" class="mention hashtag" rel="tag">#Bugzilla</a> has some nice features compared to Github or Gitlab issues (e.g real-time search for similar issue, although it almost always give bad results), but this should not prevent us from criticizing the UX of this dated software.

Tixie SalanderTired of having fucking spammer on webkit bugzilla without no way to report and moderate them.Fuck it, I called out the problem on one of my ticket vastly followed, who juste have been one again vandalized.It's gonna send a notification to 65 persons even if it's not related to the original subject the ticket was about… but grmpfff the situation just gonna get worse and worse if nothing is made to fight enshittifier of the web<a href="https://mastodon.guerilla.studio/tags/Webkit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Webkit</a> <a href="https://mastodon.guerilla.studio/tags/Bugzilla" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bugzilla</a> <a href="https://mastodon.guerilla.studio/tags/WebDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebDev</a>

Erik van StratenAfter Gavin (<a href="https://fosstodon.org/@_calmdowndear" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@_calmdowndear</a> ) asked about password managers checking and warning for http connections, I did some tests; see <a href="https://infosec.exchange/@ErikvanStraten/113183533717083748" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://infosec.exchange/@ErikvanStraten/113183533717083748</a>.In addition to those and my original test, in the email to myself I replaced "example.com" by both:http:⧸⧸192.168.178.1 (*) and https:⧸⧸192.168.178.1 (*)(*) I'm using the Unicode '⧸' here instead of ASCII '/' to prevent Mastodon from hiding the protocol prefix (and turning it into a clickable link).If I follow the instructions in the email (fully close Firefox) and tap http:⧸⧸192.168.178.1 , then I (erroneously) get to see the padlock without strike through.I can then use the iOS autofill function to fill in the password without being warned that an http connection is being used. Even after autofilling the password, Firefox has not changed the padlock as can be seen in the left screenshot below.OTOH, if I follow the instructions in the mail but tap https:⧸⧸192.168.178.1 instead (and then tap "Advanced"), I *do* get warned because a self signed certificate is being used (see the screenshot at the right).<a href="https://chaos.social/@brahms" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@brahms</a> <a href="https://mozilla.social/@mozilla" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mozilla</a> <a href="https://infosec.exchange/tags/FirefoxIOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FirefoxIOS</a> <a href="https://infosec.exchange/tags/Vulnerability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Vulnerability</a> <a href="https://infosec.exchange/tags/Mozilla" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mozilla</a> <a href="https://infosec.exchange/tags/Bugzilla" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bugzilla</a> <a href="https://infosec.exchange/tags/FullDisclosure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FullDisclosure</a> <a href="https://infosec.exchange/tags/Padlock" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Padlock</a> <a href="https://infosec.exchange/tags/httpvshttps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#httpvshttps</a> <a href="https://infosec.exchange/tags/RFC1918" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC1918</a> <a href="https://infosec.exchange/tags/AVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AVM</a> <a href="https://infosec.exchange/tags/FritzBox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FritzBox</a> <a href="https://infosec.exchange/tags/HomeRouter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HomeRouter</a> <a href="https://infosec.exchange/tags/IOT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IOT</a>

Recent searches

Search options

Administered by:

Server stats:

#bugzilla