Description of problem: This problem is similar to the one described in Bug 20182 except that I do not use GPT or UEFI. I've used dropbox without problems on MGA4 and MGA5. With a full install of MGA6+Plasma (preserving my home partition), I'm not able to install dropbox from their site. Always segfault. I contacted dropbox support and they replied that Mageia is not supported. After reading bug 20182 report, I decided to install on another laptop (still no UEFI and GPT) using the Mageia packages: - dropbox (non-free) + libnotify_0.7.7-1 + python-gpgme_0.3.10 - dropservicemenu + kdialog-16.12.3-2 + python-m2crypto_0.23.0-1 After installation, I clicked on dropbox icon is menu. It downloaded the proprietary daemon from dropbox site and created the ~/.dropbox directory. Then every attempt to start dropbox fails without message but "dropbox status" reports "Dropbox isn't running!" To summarize: - installation from dropbox website do not work (SEGV during install) - installation from Mageia packages do not work - installations on 2 different machines. Both are using Plasma - UEFI and GPT identified in bug 20182 are not used in my case A strace file is available Version-Release number of selected component (if applicable): Mageia6 (official)
Created attachment 9723 [details] strace file
(In reply to Gilles Allard from comment #1) > Created attachment 9723 [details] > strace file Assigning to all packagers collectively and CC'ing kde team because you're using Plasma. I hope one of them can read the strace file, identify the problem and assign to the package that's the culprit. Changing status from UNCONFIRMED to NEW, because the reporter reproduced the issue on two different machines. (In reply to Gilles Allard from comment #0) > Description of problem: > This problem is similar to the one described in Bug 20182 except that I do > not use GPT or UEFI. I doubt using GPT or UEFI matters, so this might be the same issue. A strace file from bug #20182 can be found here https://bugs.mageia.org/attachment.cgi?id=8899
Summary: dropbox do not run on MGA6 => dropbox does not run on MGA6 (Plasma)Assignee: bugsquad => pkg-bugsCC: (none) => kde, marja11See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=20182Status: UNCONFIRMED => NEWEver confirmed: 0 => 1
One user in blogdrake report that deleting the file ~/.dropbox-dist/dropbox-lnx.x86_64-41.4.80/PyQt5.QtDBus.so make works the dropbox installed from repositories
CC: (none) => j.alberto.vc
Another file some of us have removed to get it working: ~/.dropbox-dist/dropbox-lnx.*/libdrm.so.2 https://bugs.mageia.org/show_bug.cgi?id=20182#c50 https://forums.mageia.org/en/viewtopic.php?f=7&t=11571&p=71338&hilit=dropbox#p71125
CC: (none) => fri
I see this thing download and unzip some python modules (and the libdrm library) that exists in Mageia, but with some changes in the name of the .so files python-cryptography dropbox name cryptography.hazmat.bindings._constant_time.so mageia name cryptography/hazmat/bindings/_constant_time.so dropbox name cryptography.hazmat.bindings._openssl.so mageia name cryptography/hazmat/bindings/_openssl.so etc python-psutil python-tornado python-qt5-webkit python-qt5-core python-qt5-network python-qt5-gui python-qt5-webkitwidgets python-qt5-widgets python-qt5-printsupport python-qt5-dbus I don't found equivalent to linuxffi.pthread._linuxffi_pthread.so cpuid.compiled._cpuid.so linuxffi.resolv.compiled._linuxffi_resolv.so posixffi.libc._posixffi_libc.so librsyncffi.compiled._librsyncffi.so linuxffi.sys.compiled._linuxffi_sys.so Also note that dropbox report dropbox: running python 2.7.11 while python in mageia 6 is 2.7.13 Maybe would be a good thing make works this with local modules instead of with the ones that the application download because if more than one user in the system use dropbox then the modules will be downloaded more than one time
Keywords: (none) => IN_ERRATA6
Thank you for the Errata update, katanek :) I inserted a link to it in top of our wiki page https://wiki.mageia.org/en/Dropbox (rest of wiki page need be updated by someone - this is just a quick fix)
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 6's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Best regards, Aurélien Bugsquad Team
CC: (none) => ouaurelienStatus: NEW => RESOLVEDResolution: (none) => OLD