google
[Bug]: undefined reference to `testing::internal::MakeAndRegisterTestInfo
Describe the issue
undefined reference to `testing::internal::MakeAndRegisterTestInfo(std::__cxx11::basic_string<char, std::char_traits
Steps to reproduce the problem
normal TEST() method
What version of GoogleTest are you using?
googletest_1.14.0
What operating system and version are you using?
UNNTU 22
What compiler and version are you using?
GCC
What build system are you using?
cmake
Additional context
No response
Same problem, but Ive got just server error instead of TLS. But it was working fine at beginning.
@aizerin Nope, Prusa Connect is having issues right now in general, not just on the printer.
I do have the same issue with prints that use a lot of arc moves (G2/G3).
I also noticed that the response of the UI on the printer can feel sluggish at times during those prints.
I provided ulab with a test print. I will provide the same file along with a 3MF with the settings used here so people can troubleshoot. The files come with a CC BY-NC-ND 4.0 license. If Prusa or others wish to use this for troubleshooting this issue you can use it even though that might normally be considered "Commercial use" consider this a written exception for that specific case.
Related reddit post: https://www.reddit.com/r/prusa3d/comments/1kf9rv8/prusa_support_is_amazing_that_hasnt_exactly_been/
Same issues here - sometimes CoreOne Loses Connection to PrusaConnect…
Issue exists on every printer. CPU gets overloaded and doesn't have enough cycles to do networking as kinematics take priority. You should also notice that the printer UI becomes noticeably laggy when this happens.
All we can really do at this point is wait for @Prusa-Support to fix it through firmware or make some kind of new board with more CPU power. I opened a ticket about this about a month and a half ago that is still open.
Wow, i spoke to support 2 nights in a row and they acted like this has never happened before. We can do more than just wait. This was my first prusa, but it's getting refunded for a bambu. i wanted to believe in prusa, but i'll just buy a working printer instead
This is not an airport. You don't have to announce your departure. Good luck with your new machine.
This is not an airport. You don't have to announce your departure. Good luck with your new machine.
did you think of that yourself, or is it about a 5 year old joke now?
I want others who find this thread to realize that prusa has a 60 day refund policy, and i encourage anyone reading this to vote with their wallet. a product in this price class should ship complete. my flashforge 5M base model is more functional than my prusa, because i can remove the USB stick and prepare the next print while there's a job in progress. i can't even get p link to stay connected on my machine on wifi or wired, despite the fact that i can ping it on my network
This is not an airport. You don't have to announce your departure. Good luck with your new machine.
did you think of that yourself, or is it about a 5 year old joke now?
I want others who find this thread to realize that prusa has a 60 day refund policy, and i encourage anyone reading this to vote with their wallet. a product in this price class should ship complete. my flashforge 5M base model is more functional than my prusa, because i can remove the USB stick and prepare the next print while there's a job in progress. i can't even get p link to stay connected on my machine on wifi or wired, despite the fact that i can ping it on my network
I got this reply from Prusa support. So they are actively working on it and they have acknowledged it. These things take time to diagnose and fix. I'm also frustrated it has taken a while don't get me wrong. But I still much prefer my Prusa over the Flashforge I've tried and the quality is generally better than my Bambu printer.
Thank you for your detailed follow-up and for the time and effort you've dedicated to replicating and analyzing this issue. I completely understand your frustration, and I’m truly sorry that your experience so far has not lived up to expectations, especially given the time you've invested and the premium nature of the product.
I want to assure you that our development team is actively investigating this matter. We've reviewed the behavior you're reporting, particularly the UI slowdowns, networking dropouts, and overall performance degradation when printing complex models, and we recognize that this issue affects all Core One units under similar conditions. Your GitHub report and community coordination have been extremely helpful and are genuinely appreciated.
I'm glad to let you know that the root of the issue has been identified, and a fix is planned to be included in the next firmware version. The team is currently finalizing and testing this update to ensure it addresses the overload symptoms without introducing regressions elsewhere.
While we understand the delay has been frustrating, firmware-level optimizations of this nature require careful implementation and verification. That said, your case has been flagged for internal priority, and we will notify you as soon as the update is available for download.
Thank you again for your patience and for offering to assist further.
Thanks for adding that. Maybe there's something else wrong with mine because i lose prusa connect even when nothing is printing. I'd prefer the prusa as well, that's why this is frustrating. when it does print, the results are fantastic. having no network and a captive USB doesn't really work for me, though
It might be. If your printer is connected via wifi that connection could just be unstable. I haven't experienced any issues with connect whilst not printing.
On Sun, May 25, 2025 at 05:56 Groucho83 @.***> wrote:
Groucho83 left a comment (prusa3d/Prusa-Firmware-Buddy#4636) https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/4636#issuecomment-2907592003
Thanks for adding that. Maybe there's something else wrong with mine because i lose prusa connect even when nothing is printing
— Reply to this email directly, view it on GitHub https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/4636#issuecomment-2907592003, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAL2FL57KLY55JFAFGM3SD33AE5PFAVCNFSM6AAAAAB364UF76VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMBXGU4TEMBQGM . You are receiving this because you are subscribed to this thread.Message ID: @.***>
I want others who find this thread to realize that prusa has a 60 day refund policy, and i encourage anyone reading this to vote with their wallet.
And I would love for you to realize that this is not a discussion forum or social media. An issue tracker is meant to report and fix problems. You venting, threatening to leave or telling people to buy something else does not help with anything.
If you want to rant, go to Facebook, Reddit or even the Prusa Forum, but please keep it on topic here.
Sick, i've got the same problem, only i'm having issued with a wired connection and while not printing. There's my report on this forum post that has been open for a month with no assignee but the dev team is working on. I'm happy to report p link does work after another FW reset
So todays Firmware did not fixed this.
@Prusa-Support Any ETA on this ? My Buddycam is useless with that error ....
There's a PR #4342 already for those having issues with half-duplex instead of full-duplex, which can also cause some timeouts or transfer errors on some network configurations. I haven't had any TLS error so far or any disconnects. However will have a closer look on mine and if it happens, I'm going to debug it.
Ive had this a couple of times, usually dies halfway through a code transfer and pauses the print halfway through.
Ive found going to network and swapping from WiFi to ethernet and back again (give it a couple seconds on ethernet) gets it to reconnect.
The issue in the two comments above seem unrelated to this one...
On Wed, May 28, 2025 at 15:12 koombot @.***> wrote:
koombot left a comment (prusa3d/Prusa-Firmware-Buddy#4636) https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/4636#issuecomment-2916285215
Ive had this a couple of times, usually dies halfway through a code transfer and pauses the print halfway through.
Ive found going to network and swapping from WiFi to ethernet and back again (give it a couple seconds on ethernet) gets it to reconnect.
— Reply to this email directly, view it on GitHub https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/4636#issuecomment-2916285215, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAL2FL73FQEZZGINPF6S2JL3AWY4VAVCNFSM6AAAAAB364UF76VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMJWGI4DKMRRGU . You are receiving this because you are subscribed to this thread.Message ID: @.***>
The issue in the two comments above seem unrelated to this one... …
Actually that's a behaviour I saw on mk4s as well and it was gone after the network patch due to switch to full-duplex as number of dropped packets was much lower (and dropped packets leading to dhcp failures and aborted downloads). Regarding the tls issue, that's totally unrelated as it seems to be a Prusa Server issue. On switching to wifi and back to eth, the init function is called which restarts the network stack leading to a new negotiation.
i just finished speaking with prusa support. i don't think they're working on this
If this is a "CPU running out of cycles issue" as we theorize this issue might have the same root cause as this one https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/4573#issuecomment-2925280482 given the comments of Prusa support.
This is really frustrating. It's still happening on Firmware 6.3.3. Hopefully it can be fixed with the next update.
It's only during "complex" prints, Prusa supports told me. Printing a plate with "simple" boxes, it stays connected.
When printing a "complex" object, like this Skeleton T-Rex in 150%, the connection to Connect is lost when it's at ~2%:
Worst of all, when the printer is disconnected, you cannot check the camera feed to see if the print isn't making any spaghetti!!!
Super frustrating! I know Prusa Support has to prioritize all the reported issues and not all can be fixed immediately... But in my eyes you're paying premium price and you'd expected more about these (in my eyes) basic stuff....
Extra addition, see some of the printers:
Kwik is printing the cases and is connected. Kwek and Kwak is printing those Skeleton T-rex and are now at 50-ish percent (I can check in Home Assistant):
And yes, the names Kwik, Kwek & Kwak is Dutch for Huey Dewey and Louie :)
Having same issue on newest Core One firmware. Disconnecting Prusa Connect after 40-50 minutes of printing. On LCD there is TLS Error in Prusa Connect section. No matter if connected by WiFi or Ethernet.
This makes Buddy3D Camera unusable as it doesn’t support local streaming or PrusaLink snapshots. Very annoying!
Indeed! The camera is not accessible via local network or PrusaLink. PrusaLink works as it is local. The integration in Home Assistant works, so there's a workaround. Now I want local access to the camera's.
I've bought 3 camera's (€44 each) and are quite useless as I cannot watch/check the prints remotely :(
I'm having the same problem. I bought the camera to be able to monitor print while I'm away and cancel objects if something detaches from plate. But Core One keeps disconnecting from Prusa Connect shortly after print start, making the camera useless.
Meanwhile, a MK4 stays connected all the time, and it is on the same wifi (standing right next to the Core One), so it's definitely not wifi issue.
Same problem here when printing a print consisting of only arcs it never stays connected the whole print and the whole UI is really laggy as well.
