Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kotatogram cannot connecting using system proxy while web login success and QWidget::render don't work well #390

Open
Thesoul20 opened this issue Sep 6, 2022 · 1 comment
Labels

Comments

@Thesoul20
Copy link

Steps to reproduce

I use a proxy to use telegram, I can login telegram web, but not Kotatogram.
When i open the Kotatogram app, it always show connecting as this(as the same time, telegram web can open normally)

image

When i open Kotatogram in terminal and give sudo to it, it shows
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QPainter::begin: Paint device returned engine == 0, type: 3
QWidget::render: Cannot render with an inactive painter

And I'm not sure it's my own problem.

Expected behaviour

Connecting well and show the login QR code.

Actual behaviour

connecting false.

Operating system

Ubuntu 20.04

Version of Kotatogram Desktop

1.4.8

Installation source

Static binary from official website

Logs

sudo ./Kotatogram
[sudo] password: 
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QPainter::begin: Paint device returned engine == 0, type: 3
QWidget::render: Cannot render with an inactive painter
QPainter::begin: Paint device returned engine == 0, type: 3
QWidget::render: Cannot render with an inactive painter
Copy link
Contributor

github-actions bot commented Jul 1, 2024

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

@github-actions github-actions bot added the stale label Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant