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

couldnt launch (with workaround) #9937

Open
serj-kzv opened this Issue Nov 28, 2018 · 6 comments

Comments

Projects
None yet
3 participants
@serj-kzv

serj-kzv commented Nov 28, 2018

qBittorrent version and Operating System

qBittorrent 4.1.4 from Official PPA
Kubuntu 18.04.1 (with latest updates)

If on linux, libtorrent and Qt version

the same as in Kubuntu 18.04.1 (with latest updates)

What is the problem

could not launch

What is the expected behavior

normal execution

Steps to reproduce

Sometimes after trying to run

Extra info(if any)

Has some relation to bug 8263

user@user-PC:~$ qbittorrent
terminate called after throwing an instance of 'std::runtime_error'
  what():  Cannot write to torrent resume folder.


*************************************************************
Please file a bug report at http://bug.qbittorrent.org and provide the following information:

qBittorrent version: v4.1.4

Caught signal: SIGABRT
Stack trace:
  /lib/x86_64-linux-gnu/libc.so.6 : gsignal()+0xc7  [0x7f168b9c2e97]
  /lib/x86_64-linux-gnu/libc.so.6 : abort()+0x141  [0x7f168b9c4801]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x8c8b7  [0x7f168c3b78b7]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x92a06  [0x7f168c3bda06]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x92a41  [0x7f168c3bda41]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x92c74  [0x7f168c3bdc74]
  qbittorrent : BitTorrent::Session::initResumeFolder()+0x254  [0x55c2a55141c4]
  qbittorrent : BitTorrent::Session::Session(QObject*)+0x1c6c  [0x55c2a5515e9c]
  qbittorrent : BitTorrent::Session::initInstance()+0x37  [0x55c2a55181d7]
  qbittorrent : Application::exec(QStringList const&)+0x38  [0x55c2a54e2508]
  qbittorrent : main()+0x38f  [0x55c2a54d338f]
  /lib/x86_64-linux-gnu/libc.so.6 : __libc_start_main()+0xe7  [0x7f168b9a5b97]
  qbittorrent : _start()+0x2a  [0x55c2a54ddb1a]
Aborted

Workarounded by reinstalling with configuration cleaning

sudo apt purge qbittorrent
sudo rm -rf /home/<user_name>/.local/share/data
sudo rm -rf /home/<user_name>/.config/qBittorrent
sudo apt update && sudo apt install qbittorrent

@serj-kzv serj-kzv changed the title from couldnt launch to couldnt launch (with workaround) Nov 28, 2018

@sledgehammer999

This comment has been minimized.

Contributor

sledgehammer999 commented Nov 28, 2018

what(): Cannot write to torrent resume folder.

This is the real reason. For some reason qbt coulnd't write to ~/.local/share/data/qBittorrent/BT_backup
This is often due to wrong folder permissions.

@glassez should we reconsider this std::exception approach? Maybe catch it somewhere and present a dialog?

@glassez

This comment has been minimized.

Member

glassez commented Nov 28, 2018

Maybe catch it somewhere and present a dialog?

Apparently we should inform the user (and then abort anyway). But don't forget that it can be "nox" variant.

@glassez glassez closed this Nov 28, 2018

@glassez glassez reopened this Nov 28, 2018

@glassez

This comment has been minimized.

Member

glassez commented Nov 28, 2018

This is often due to wrong folder permissions.

Apparently, because of the playful hands of the user... How else can it happen?

@sledgehammer999

This comment has been minimized.

Contributor

sledgehammer999 commented Nov 28, 2018

Apparently, because of the playful hands of the user... How else can it happen?

Of course.

Apparently we should inform the user (and then abort anyway).

Yes. But abort normally, not with a crash/exception.

But don't forget that it can be "nox" variant.

Maybe in this case the std::exception is acceptable? Or an explicit error message in the terminal before exiting.

@serj-kzv

This comment has been minimized.

serj-kzv commented Nov 29, 2018

Apparently, because of the playful hands of the user... How else can it happen?

You're right. It's happened when I miss clicked in terminal and ran qbittorrent as the sudo user once. After that it's impossible to launch qbittorrent as the usual user.

@glassez

This comment has been minimized.

Member

glassez commented Nov 29, 2018

@sledgehammer999
Made some sketches. Not tested yet. See #9940.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment