Pesquisar

Search results for: bug

Fabio
6 meses atrás
#encripted #im #groupchat #kontalk @Gruppo Linux Como

Kontalk 4.0.0 - final group chat release

After a very long time... Compared to beta6.1, there are just a few bug fixes. For those coming from 3.1.10, here is a quick list of changes: group chats toggle encryption per chat internal logging system sticky conversations new app icon by Giovanni Lauricella organize preferences by category more reliable registration procedure Group chats work fine, but as a community project we always need your feedback for both bugs and improvements. Don't hesitate to open bugs at GitHub or discus...
Berlin
Tobias
6 meses atrás
Thank you all for working on ~friendica ~friendica <3 #ilovefs

Be it with code, documentation, bug reports or silly questions to the support forum! Thanks for all of that :-D

@Friendica Support
Rabuzarus
10 meses atrás
Yes I read it.
This is not a really a bug in the classical manner because the plan is to remove all tinymce (web-editor) code from frio.
- it's really hard to support both input methods (classical && web-editor) since they are working very differently
- the web-editor doesn't integrate very well in frio
- it also difficult in friendica core because at many places you have to respect 2 Editors (see autocompletion - the web does have it's own code for autocompletion). This makes future decisions really hard because you have always to respect the web-editor which behaves totally different

If it were up to me we would remove the web-editor completely and would rather focus on the standard editor and try to make this one more comfortable.

I know this answer is very disappointing for people who love the web-editor. Sry for that.
Fabio
10 meses atrás
#jolla

[release notes] 2.0.4/Fiskarsinjoki [released] - together.jolla.com

It took a long time before we delivered the previous update (2.0.2). Our goal now is to start providing updates in shorter intervals.
This update, 2.0.4 alias Fiskarsinjoki, introduces quite a few new features and bug fixes. One of the key new features is the option to save pictures and videos directly from the camera to the memory card. This helps to keep the Phone Memory from getting cluttered and in good shape. Another long-awaited new feature being introduced is conference calling. You can now rotate the device to landscape in Calculator to access the new scientific mode with support for high-precision, brackets and trigonometric and exponential operations. And, you can use Gallery edit options to adjust brightness and contrast of photos. You can also launch the synchronization of Calendar in the app itself, and share files from the File manager of Storage page (in Settings). Last but not least, we have upgraded the Browser engine.
Hypolite on Friendica
10 meses atrás
I have no trouble switching to pre-wrap as I didn't know it existed until now (thanks @Rabuzarus.

For better code display I use SyntaxHighlighter on my own website (example) for line-counting, but it doesn't wrap long lines and doesn't offer the raw source popup feature.

As for the original issue, @Tobias correctly identified that new lines have been eaten away between Hubzilla and Friendica, which is more a bug than the code block not wrapping long lines of text.
Michael Vogel
10 meses atrás
I would declare it as a bug.
Tobias
10 meses atrás
The bug is somewhere else - the line feeds are stripped away. When you have a look at the original, in front of every deb there has to be a new line.
Halle an der Saale
Steffen K9
10 meses atrás
Issue with long lines inside code blocks
Hello @Friendica Support and @Friendica Theme Developers
there is a visual problem with long lines inside codeblocks. I have this issue with frio and the latest develop code.
Imagem/foto

I also checked the issue with vier. Vier is using line breaks and the code block looks better.
Imagem/foto

Is this a bug? If so, I'll file a bug report on Github.

Have a nice Sunday!
Linux Walt
10 meses atrás de Friendica for Android
I believe Eugen said he's trying to follow actual written standards as much as possible. If there's a connection issue, one project or the other has a bug and it should be filed as such.
Fabio
11 meses atrás
I've done some checks.. my results:

- we fetch lrdd url with account uri without "acct:". I don't checked what webfinger specs says, but looks like Mastodont MUST receive accout prefixed by "acct:". If specs don't say that account uri MUST start with "acct:", Mastodont is too much strict. Anyway we could use "acct:" always

- Mastodont fill lrdd link rel="magic-public-key" href value without "data:". I think that is Mastodont bug in this side, because "href" should be an uri, and so must start with "data:".

I've patched Probe::detect() to always add "acct:" when fetching lrdd and Probe::ostatus() to accept base64 pubkey strings without "data:" , if you think it's worth.
Steffen K9
1 ano atrás
I would absolutely love to help with development but unfortunately I can't. Besides some basic bash scripting skills I'm an absolute noob when it comes to programming. :-) Some time ago I bought a book about HTML, CSS and PHP and I survived ;-) some web based tutorials about "programming". But I don't think that was helping much.
On the other hand I'm running a server on develop branch an I do a lot of testing. If I find a bug or bad usability I'm happy to report this and to open an Github issue.

we need to care not just implementing things but implement it in a good way

Yes, I'm completely on your side here. :-)
Tobias
1 ano atrás de open socialverse
prepare for my bug report, when my personal theme is not working on a node where it is not installed ;-)
Steffen K9
1 ano atrás
There was an issue with detecting feeds some days ago. A bug fix was released and I pulled the code from develop. So, it should work. Did you try this with ~friendica ~friendica or redredmatrix ^^
Sandro
1 ano atrás
For some reason I feel it the weight of filing it. Where would the bug be ? My vier is different from your vier ?
Fabio
1 ano atrás
looks like a bug..
Bordesholm
Tim Schlotfeldt
1 ano atrás
Endlich, mit den KDE Applications 16.04.1 ist endlich dieser nervige #Akonadi-Fehler behoben:


Bug 362559 – Regression since 5.0.2: Dragging addresses from kaddressbook to new message fails



@Arch Linux
Bordesholm
Tim Schlotfeldt
1 ano atrás
@Arch Linux (Repost)
Tim Schlotfeldt wrote the following post:
@Arch Linux Linux Aktuell gibt es einen auf Notebooks ärgerlichen Bug in #Network-Manager: [networkmanager]broken wifi-connection after upgrade to 1.0.12-1. Das war für mich Anlass, mich mit #ConnMan näher zu beschäftigen. Das Teil funktioniert gut. Nur #OpenVPN bekomme ich nicht ans laufen, speziell Einstellungen zu TUN und TAP.

Kennt sich da jemand aus?
Fabio
1 ano atrás
:-D It's my Jolla client that resize the image before upload it and remove exif tags. but a bug there is because I re-rotated the image via web interface but the miniature is still wrong...
Elena ``of Valhalla''
1 ano atrás
It seems you have been infected by the same photo rotation bug that plagues @Davide De Prisco :D
Bordesholm
Tim Schlotfeldt
1 ano atrás
@Arch Linux Aktuell gibt es einen auf Notebooks ärgerlichen Bug in #Network-Manager: [networkmanager]broken wifi-connection after upgrade to 1.0.12-1. Das war für mich Anlass, mich mit #ConnMan näher zu beschäftigen. Das Teil funktioniert gut. Nur #OpenVPN bekomme ich nicht ans laufen, speziell Einstellungen zu TUN und TAP.

Kennt sich da jemand aus?
Rabuzarus
1 ano atrás
Sure I always have a look at other design things. But march is full of doing stuff for university. So I will only have time to do small fixes.

And first I want to see what happens with https://github.com/friendica/friendica/pull/2328 because it is annoying to have always merge conflicts. And with such big commits I'm never sure if something is getting lost.

OT:
Yesterday I realized that there are some issues after https://github.com/friendica/friendica/pull/2370.
Go to edit contact and press the "update" link. It will redirect you to the wrong path. (https://github.com/friendica/friendica/blob/develop/mod/contacts.php#L375).

I would like to write a bug report but I don't know how to describe it in a good technical language.

In short: the redirection path is added to existing path and doesn't replace the existing path.
Result: https://friendica.domain.com/contacts/287/contacts/287
Tim Schlotfeldt
1 ano atrás
Ach ja, die Rewrite-Regel:

# Fix for KDE bug 355441
RewriteEngine On
RewriteRule "^(.*\.ics)(/)$" "$1"
Bordesholm
Tim Schlotfeldt
1 ano atrás
*seufz* Manchmal macht es #KDE einem nicht leicht, treu zu bleiben. #PIM ist sicherlich nicht nur für mich eine entscheidende Anwendungskategorie, und nun kann man auf einem #CalDav-Server kein Delete vornehmen, weil KIO http an jeder URL ein Slash dranhängt …

Bug 355441 – DAV Resource 15.12.0: Broken state, The item was not deleted on the server.

Sandro
2 anos atrás
I was notified about you commenting on your message. But I wasn't watching this post. Bug ?
Tim Schlotfeldt
2 anos atrás
I did just a short search on heise online about Lenovo and Thinkpads:

- Linux kills ThinkPad (an UEFI firmware bug), Feb. 2014
- Security desaster because of the preinstalled Adware „Superfish“, Feb. 2015
- Security related bug in Lenovo's System Update Service tool, May 2015

Bad track record :-/
David Benfell
2 anos atrás
As to the update, that might be. I'm not sure.

Here's what mysqltuner says. I've had trouble following its recommendations in the past so I'm not sure what to do now. The server in question is fairly hefty so I can probably tweak some variables:
mysqltuner: /usr/local/bin/mysqltuner /usr/ports/databases/mysqltuner
vegan# mysqltuner
Please enter your MySQL administrative login: root
Please enter your MySQL administrative password: >> MySQLTuner 1.6.0 - Major Hayden <major@mhtx.net>
>> Bug reports, feature requests, and downloads at http://mysqltuner.com/
>> Run with '--help' for additional options and output filtering
[--] Skipped version check for MySQLTuner script
[OK]Currently running supported MySQL version 5.5.47-MariaDB
[OK]Operating on 64-bit architecture

-------- Storage Engine Statistics -------------------------------------------
[--] Status: +Aria +CSV +InnoDB +MRG_MYISAM
[--] Data in MEMORY tables: 0B (Tables: 2)
[--] Data in MyISAM tables: 1G (Tables: 232)
[--] Data in InnoDB tables: 2G (Tables: 1077)
[!!] Total fragmented tables: 1091

-------- Security Recommendations -------------------------------------------
[OK]There is no anonymous account in all database users
[OK]All database users have passwords assigned
[!!] There is not basic password file list !

-------- Performance Metrics -------------------------------------------------
[--] Up for: 3d 12h 46m 22s (13M q [45.556 qps], 152K conn, TX: 248B, RX: 1B)
[--] Reads / Writes: 95% / 5%
[--] Binary logging is disabled
[--] Total buffers: 2.8G global + 21.6M per thread (512 max threads)
[OK]Maximum reached memory usage: 3.9G (24.68% of installed RAM)
[!!] Maximum possible memory usage: 13.6G (86.13% of installed RAM)
[OK]Slow queries: 0% (249/13M)
[OK]Highest usage of available connections: 10% (53/512)
[OK]Aborted connections: 0.00% (1/152718)
[OK]Query cache efficiency: 40.8% (6M cached / 16M selects)
[!!] Query cache prunes per day: 201366
[OK]Sorts requiring temporary tables: 0% (1K temp sorts / 592K sorts)
[!!] Joins performed without indexes: 37769
[!!] Temporary tables created on disk: 62% (241K on disk / 383K total)
[OK]Thread cache hit rate: 99% (1K created / 152K connections)
[!!] Table cache hit rate: 8% (1K open / 17K opened)
[OK]Open file limit used: 0% (535/465K)
[OK]Table locks acquired immediately: 99% (3M immediate / 3M locks)

-------- MyISAM Metrics -----------------------------------------------------
[OK]Key buffer used: 100.0% (8M used / 8M cache)
[OK]Key buffer size / total MyISAM indexes: 8.0M/400.0M
[OK]Read Key buffer hit rate: 98.1% (136M cached / 2M reads)
[!!] Write Key buffer hit rate: 33.6% (1M cached / 1M writes)

-------- InnoDB Metrics -----------------------------------------------------
[--] InnoDB is enabled.
[!!] InnoDB buffer pool / data size: 2.0G/2.1G
[!!] InnoDB buffer pool instances: 1
[OK]InnoDB Used buffer: 100.00% (131071 used/ 131071 total)
[OK]InnoDB Read buffer efficiency: 99.93% (498841994 hits/ 499170629 total)
[!!] InnoDB Write buffer efficiency: 0.00% (0 hits/ 1 total)
[OK]InnoDB log waits: 0.00% (0 waits / 258497 writes)

-------- AriaDB Metrics -----------------------------------------------------
[--] AriaDB is disabled.

-------- Replication Metrics -------------------------------------------------
[--] No replication slave(s) for this server.
[--] This is a standalone server..

-------- Recommendations -----------------------------------------------------
General recommendations:
Run OPTIMIZE TABLE to defragment tables for better performance
Reduce your overall MySQL memory footprint for system stability
Enable the slow query log to troubleshoot bad queries
Increasing the query_cache size over 128M may reduce performance
Adjust your join queries to always utilize indexes
Temporary table size is already large - reduce result set size
Reduce your SELECT DISTINCT queries without LIMIT clauses
Increase table_open_cache gradually to avoid file descriptor limits
Read this before increasing table_open_cache over 64: http://bit.ly/1mi7c4C
Beware that open_files_limit (465165) variable
should be greater than table_open_cache ( 4096)
Variables to adjust:
query_cache_size (> 128M) [see warning above]
join_buffer_size (> 16.0M, or always use indexes with joins)
table_open_cache (> 4096)
innodb_buffer_pool_size (>= 2G) if possible.
innodb_buffer_pool_instances(=2)


As to the performance on my network page:
Performance: Database: 0.184, Network: 0, Rendering: 0.033, Parser: 0, I/O: 0.02, Other: 0.142, Total: 0.379
Rabuzarus
2 anos atrás
@Friendica Developers
As you may know for some time I did a pull request concerning the implementation of a last_photos_widget. In this regard I came in several troubles about the permission part and reverted the commit. (link to the reverted PR: https://github.com/friendica/friendica/pull/2223 )

While working on the permission part I thought that it would be nice to have a universal function which could replace the permission code which looks similar at other places:




Permissions are no easy thing because of the fact that someone have to know the whole logic behind this code. And it's very easy to build regressions and security leaks.

While working on photo permissions I noticed that there seems to be a bug already in the code. Have a look at https://github.com/friendica/friendica/pull/2223 . $cid isn't defined somewhere. This would mean it would be always empty and so $visitor is always empty too.
If the visitor is a remote_user() and $vistior is empty (which it is always because $cid doesn't ever get a value)

To make it a little bit shorter. I don't dare to fix this because I don't know how the intended behavior should be.

So the question if someone more familiar could look at this.

A real goal would be to maybe slim the code and to make it reusable as a function for the parts I wrote above
Fabio
2 anos atrás
Tobias wrote the following post:

I <3 FreeSoftware Day

In the Free Software community, we exchange a lot of criticism. We write bug reports, tell others how they can improve the software, ask them for new features, and generally are not shy about criticising others. There is nothing wrong about that. It helps us to constantly improve. But sometimes we forget to show the hardworking people behind the software our appreciation. We should not underestimate the power of a simple "thank you" to motivate Free Software contributors in their important work for society. So say thank you on 14th February!

Imagem/foto

Início: Sábado Fevereiro 13, 2016 @ 23:00

Término: Domingo Fevereiro 14, 2016 @ 23:00

Tobias
2 anos atrás

I <3 FreeSoftware Day

In the Free Software community, we exchange a lot of criticism. We write bug reports, tell others how they can improve the software, ask them for new features, and generally are not shy about criticising others. There is nothing wrong about that. It helps us to constantly improve. But sometimes we forget to show the hardworking people behind the software our appreciation. We should not underestimate the power of a simple "thank you" to motivate Free Software contributors in their important work for society. So say thank you on 14th February!

Imagem/foto

Início: Sábado Fevereiro 13, 2016 @ 23:00

Término: Domingo Fevereiro 14, 2016 @ 23:00

Bordesholm
Tim Schlotfeldt
2 anos atrás
@Friendica Support Loading profile or network page needed a lot of time, up to 50 seconds. Turned out deleting some external links like to the ArchLinunx bug tracker solves the problem.
Rabuzarus
2 anos atrás
@Friendica Support @Friendica Developers @UX Watchdogs

After my work on unifying the contact templates and the work on different forum related things, I would suggest to add/sync the pdesc column to the the gcontact table.
But before I fill a bug report I want to have look if there are any concerns against it.

Why do I think, that it is useful?
Some account (which are not standard accounts - e.g. forums) use the pdesc as something like a short description. In contrast the about field have often much more data in it (people often write some sentences about the account).
I think we should strengthen the user behavior to use pdesc as a short description (a 3 - 4 words which summarize what the account is about).
Since pdesc should be very short we display it in serveral places, e.g. vcard and contactlist (in contrast to the about field, which we don't have integrated in the contact template because it could contain much information where we don't know how to display this mass of possible information).

Especially for non standard accounts (accounts which shouldn't represent a person - e.g. forums, information channels, accounts of organizations or companies) this could very useful because pdesc is presented (in the present behavior) right next to the account name.
To give an example. @UX Watchdogs would be.

UX Watchdogs (Forum)
ux-watchdogs@fc.oscp.info
Discuss Friendica User-Experience



This is a behavior which is already present. But only locally. If we would add pdesc to gcontacts this could be done for all friendica contacts
Fabio
2 anos atrás
Friendica 3.4.3 released
Tobias wrote the following post:
Friendica 3.4.3 released
Dear Federation,

we are happy to announce the release of Friendica 3.4.3, the last planed minor release of the <span>Lily of the valley</span> family before the release of Friendica 3.5 in spring 2016. As such version 3.4.3 bundles a couple bug fixes with a number of new features. For the full list, please read the CHANGELOG, but let me highlight some things from the long list.
  • Support to events attendance. Users can mark their participation to an event,
  • Private forums are mentioned automatically like community forums,
  • The UI in the aspects of dealing with contacts was streamlined,
  • The Forumlist widget moved from the addons into the core (you can just disable that addon),
  • Federation with Diaspora* and GNU Social was improved,
  • The API was improved, especially to fix some incompatibilities with the AndStatus clients.

And just a hint, in case you muss the little flag for language settings: have a look into the basic settings of your account, you will find the language settings there from now on.

How to Update?

If you have an installation using the git repository directly, all you have to do is a git pull in the friendica directory and the addons directory. That will fetch the new version from the master branch and you are ready to go. If you want to use the bleeding edge code from the development branch of Friendica 3.5 Asparagus, checkout the develop branch in your repository.

Alternatively you can find a zip file of the released version of friendica at github.com for download. Just unzip it on your local machine and replace the files on your server with the new files.

Friendica at the 32c3

Friendica will be present at the 32nd Chaos Communication Congress (32c3) on Day 2 (that is Monday, December 28) at the Assembly of the FSFE. Have a look at the congress wiki for details on the session. A great opportunity to meet some of the Friendica developers and other users in the real world.

Have a merry time!


@Friendica Developers @Friendica Support
@Gruppo Linux Como @Friendica Italia
Bordesholm
Tim Schlotfeldt
2 anos atrás
There it is, the next minor release of #friendica. Big thanks to the community and the developers!
Tobias wrote the following post:
Friendica 3.4.3 released
Dear Federation,

we are happy to announce the release of Friendica 3.4.3, the last planed minor release of the <span>Lily of the valley</span> family before the release of Friendica 3.5 in spring 2016. As such version 3.4.3 bundles a couple bug fixes with a number of new features. For the full list, please read the CHANGELOG, but let me highlight some things from the long list.
  • Support to events attendance. Users can mark their participation to an event,
  • Private forums are mentioned automatically like community forums,
  • The UI in the aspects of dealing with contacts was streamlined,
  • The Forumlist widget moved from the addons into the core (you can just disable that addon),
  • Federation with Diaspora* and GNU Social was improved,
  • The API was improved, especially to fix some incompatibilities with the AndStatus clients.


And just a hint, in case you muss the little flag for language settings: have a look into the basic settings of your account, you will find the language settings there from now on.

How to Update?

If you have an installation using the git repository directly, all you have to do is a git pull in the friendica directory and the addons directory. That will fetch the new version from the master branch and you are ready to go. If you want to use the bleeding edge code from the development branch of Friendica 3.5 Asparagus, checkout the develop branch in your repository.

Alternatively you can find a zip file of the released version of friendica at github.com for download. Just unzip it on your local machine and replace the files on your server with the new files.

Friendica at the 32c3

Friendica will be present at the 32nd Chaos Communication Congress (32c3) on Day 2 (that is Monday, December 28) at the Assembly of the FSFE. Have a look at the congress wiki for details on the session. A great opportunity to meet some of the Friendica developers and other users in the real world.

Have a merry time!
Tobias
2 anos atrás de Feed
Friendica 3.4.3 released
Dear Federation,

we are happy to announce the release of Friendica 3.4.3, the last planed minor release of the <span>Lily of the valley</span> family before the release of Friendica 3.5 in spring 2016. As such version 3.4.3 bundles a couple bug fixes with a number of new features. For the full list, please read the CHANGELOG, but let me highlight some things from the long list.
  • Support to events attendance. Users can mark their participation to an event,
  • Private forums are mentioned automatically like community forums,
  • The UI in the aspects of dealing with contacts was streamlined,
  • The Forumlist widget moved from the addons into the core (you can just disable that addon),
  • Federation with Diaspora* and GNU Social was improved,
  • The API was improved, especially to fix some incompatibilities with the AndStatus clients.

And just a hint, in case you muss the little flag for language settings: have a look into the basic settings of your account, you will find the language settings there from now on.

How to Update?

If you have an installation using the git repository directly, all you have to do is a git pull in the friendica directory and the addons directory. That will fetch the new version from the master branch and you are ready to go. If you want to use the bleeding edge code from the development branch of Friendica 3.5 Asparagus, checkout the develop branch in your repository.

Alternatively you can find a zip file of the released version of friendica at github.com for download. Just unzip it on your local machine and replace the files on your server with the new files.

Friendica at the 32c3

Friendica will be present at the 32nd Chaos Communication Congress (32c3) on Day 2 (that is Monday, December 28) at the Assembly of the FSFE. Have a look at the congress wiki for details on the session. A great opportunity to meet some of the Friendica developers and other users in the real world.

Have a merry time!
Michael Vogel
2 anos atrás
@Tobias @Fabio I guess we could clearly call this a "bug fix" and accept the pull request?
Rabuzarus
2 anos atrás
@Friendica Developers @Friendica Support

can someone please test?
In some special cases the notification menu seems not to appear in the top nav bar. I guess this bug appears when the nickname is to long.
Fabio
2 anos atrás
While http is quite simple, uploading files is a pile of hot crap....

You can upload a file using POST.
But, hey you need to use a multipart mime body to upload the file.
So you need to define "Content-Type" header as "multipart/form-data" with the boundary of each parts.

Passing values is easy (but I don't want to know what happens with non ascii chars..):
Content-Type: multypart/forms-data; boundary=MYBOUNDARY

--MYBOUNDARY
content-disposition: form-data; name="title'

A string
--MYBOUNDARY
content-disposition: form-data; name="body'

A multiline
string
--MYBOUNDARY--



Oh, hei, easy!

Now, let's add the file to upload, a photo in this case

Content-Type: multypart/forms-data; boundary=MYBOUNDARY

--MYBOUNDARY
content-disposition: form-data; name="title'

A string
--MYBOUNDARY
content-disposition: form-data; name="body'

A multiline
string
--MYBOUNDARY
content-disposition: form-data; name="media"; filename="photo.png"
Content-Type: image/png

..binary data of the file..
--MYBOUNDARY--



Wait! "binary data"? why.. how?.. what?

My client is written in javascript (QML), and I have some little problems to build a body text string with binary data in it.


Let's read the RFC 2388, section 4.3
While the HTTP protocol can transport arbitrary binary data, the
default for mail transport is the 7BIT encoding.

wtf..
The value supplied
for a part may need to be encoded and the "content-transfer-encoding"
header supplied if the value does not conform to the default
encoding.


Oh, ok!
So I can base64 encode the data, and set "content-transfer-encoding: base64" in my file part.

No.
Tried, php save the upload file encoded, ignoring the header.
But hey, the related bug it's only from 2009 and discussion stopped in 2010, so maybe php10 will support this.

Django 1.3 started to handle the header in 2012


At the end of this I think the only way I can upload a file is to dump JS and XMLHttpRequest and write some C++...
Or change Firendica code to handle base64 encoded file in some non-standard way...
Rebeka Catalina
2 anos atrás
Some bad news : it's not something permanent. What I mean is, that since a while now everything seems to be ok again - that means, that this bug for isn't easy to uncover :-/
Tobias
2 anos atrás de open socialverse
In the issue about the forumlist filtering @Rabuzarus mentioned it could well be a result from a bug in the filtering of the network stream, which is what groups do as well (more or less, but I don't know if it's done in the same place).

Replies to other peoples posting are not filtered out by the groups, but I think this is not the problem here - right? The top-level postings arrive in the wrong groups.
Fabio
2 anos atrás
Friendica 3.4.3-rc
@Friendica Support @Friendica Developers

Ladies and gentlemen,
we are now in feature-freeze pre-release bug-squashing state, on the road to release Friendica 3.4.3
A branch for the Release Candidate has been opened:
https://github.com/friendica/friendica/tree/release-3.4.3-rc

Developers, please open your bug-related pull requests against that branch.

Users, please switch to that branch and test!

Translators, please... translate :-)

Go on!
Tobias
2 anos atrás de open socialverse
@Steffen Krumbholz could you fetch again? @Michael Vogel had an loop not exited, but a patch for this was added this morning, so eventually you hit the sweet spot of the bug?
Fabio
2 anos atrás

Bug #1463112 “Cat sitting on keyboard crashes lightdm” : Bugs : unity package : Ubuntu

14.04, locked screen to go to lunch, upon return from lunch cat was sitting on keyboard, login screen was frozen & unresponsive.

To replicate: In unity hit ctrl-alt-l, place keyboard on chair. Sit on keyboard.

Resolution: Switched to virtual terminal, restarted lightdm, lost all open windows in X session.

What should have happened: lightdm not becoming unresponsive.


need cats for testing
Michael Vogel
2 anos atrás
Update: I found the bug. The pull request is done.
Michael Vogel
2 anos atrás
Using the item table generates too much load. I would prefer using "last-item". It can be called a bug that on forums this isn't updated.

$uid is used for the ID of the user. $cid would be for a contact. Since you are referring to a user, this $uid is correct.
Michael Vogel
2 anos atrás
Thing is: The description promises something that can't work. If I don't want to be found by others then I should hide my profile.

The only "bug" is the existance of the option. The whole implementation of the functionality doesn't fit to it. It's a wrong description and the implementation interferes with itself from the beginning.

If it really should work then it must be done in a completely different way. A profile could get an additional field that switches between "should I be suggested"/"Should I not be suggested" that had to be synchronized between the systems.

But: I really don't see any need for it. Even if enabled correctly, it won't prevent other people from browsing through the local or public directory and adding you. It wouldn't prevent you from being added by persons who saw your posts because they were repeated by others or by people who saw your comment on another persons post.

And it wouldn't prevent you from being suggested by "/match".

This option only adds more complexity but isn't a gain in privacy in any case.
Tobias
2 anos atrás de open socialverse
but it's 3 different things.

you want to be listed in the phoine book for your town?
for thw world?
may we introduce you to newcomers to town?

three things. three options. and if i dont want to be suggested, but the suggestor does so, then this is a bug.
Michael Vogel
2 anos atrás
Remove "Suggest me"?
@Friendica Developers While searching for a problem I discovered a bug in "poco" (pull request comes soon) and I was asking myself about the sense of the "Suggest me" option. It's the option called: "Allow us to suggest you as a potential friend to new members?"

In fact all this option is doing is publishing the contact under /poco (When you call it without a username).

Personally I think this option is redundant. There is already the option "Publish your default profile in your local site directory?" which - in my mind - is really similar. I would expect the same results when I call /poco or /directory

What do you mean?
Fred
2 anos atrás de Hubzilla
Solução (simples) pra quem não consegue entrar no SDDM após atualização do Debian Stretch
Quem usa Debian Stretch com a combinação KDE+Nvidia+SDDM teve uma infeliz surpresa após atualizar os drivers da Nvidia pra última versão e o pacote glx-diversions para a versão 0.6.0: o SDDM dá um erro (mais especificamente o erro é anunciado pelo sddm-greeter) e não aparece mais a tela de autenticação.

Depois de dar uma passeada na rede, achei uma solução bem simples e que resolve o problema: adicionar o usuário sddm ao grupo video. Parece que também é necessário adicionar o seu próprio usuário a esse grupo, mas como o meu já estava nesse grupo, foi só adicionar o sddm que tudo voltou a funcionar perfeitamente. Pra quem não lembra, pra adicionar o usuário ao grupo é só usar o comando abaixo (como root ou usando o sudo:
adduser sddm video
A dica veio desse bug aberto na Debian.
Berlin
Tobias
2 anos atrás de open socialverse
Mike Macgirvin wrote the following post:

Hubzilla (beta2)



Announce: Hubzilla 0.10 (public beta 2)

Lots of changes since 0.9. The most notable differences are delivery reports to verify message delivery and improved export/import/sync for channel migrations. There has also been a rework of the delivery and queue code to improve delivery reliability in hostile shared hosting environments and also improve delivery performance (this is tweakable so you can fine tune for your hardware and environment).

There have also been significant changes in dead site detection so that we can avoid wasting resources on sites that have shut down and the members migrated elsewhere.

The UI and theming has gone through additional work with an improved mail/PM interface and a new default schema which is easier to use on tablets and handhelds. As usual there were many bug fixes. A couple of these are high impact so we encourage all hubzilla sites to upgrade and keep current until our official launch; which is getting closer.

We encourage new site builders to use hubzilla and refrain from building any new redmatrix sites. There may still be a few issues in the new code, but the improvements are so extensive as to be a "no-brainer" at this point.
Fabio
2 anos atrás

Wine Staging

Wine Staging (formerly wine-compholio) is a special wine version containing bug fixes and features, which are not yet available in regular wine versions. The idea of Wine Staging is to provide new features faster to end users and to give developers the possibility to discuss and improve their patches before they are sent upstream. We also intend to...
antigo