[dolphin] [Bug 412618] Crash when copying directory with the same name

2019-12-24 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=412618

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #15 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 412618] Crash when copying directory with the same name

2019-12-09 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=412618

--- Comment #14 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 412618] Crash when copying directory with the same name

2019-11-25 Thread Julian Schraner
https://bugs.kde.org/show_bug.cgi?id=412618

--- Comment #13 from Julian Schraner  ---
(In reply to pac.dlfisher from comment #12)
> THAT, that's 19illionth times better than the initial response I got about
> checking with the community with the information I gave. THANK YOU!!!
> 
> Just for clarification. The KDE backports refer to the older versions and
> not the current stable release?
> 
> How do I verify that I'm not using "KDE packports PPA"?

If you don't know whether you are using the backports PPA or not, you most
likely don't use it. (You could check this by looking at the output of `sudo
apt update` - if ppa.launchpad.net/kubuntu-ppa/[...] is in there, the
repository is enabled). The PPA
(https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/backports) is to allow
users on Kubuntu to get newer versions of KDE software. This would be important
because if you had a newer version of KIO, you would also need a newer
kio-dbgsym package.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 412618] Crash when copying directory with the same name

2019-11-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=412618

--- Comment #12 from pac.dlfis...@gmail.com ---
THAT, that's 19illionth times better than the initial response I got about
checking with the community with the information I gave. THANK YOU!!!

Just for clarification. The KDE backports refer to the older versions and not
the current stable release?

How do I verify that I'm not using "KDE packports PPA"?

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 412618] Crash when copying directory with the same name

2019-11-25 Thread Julian Schraner
https://bugs.kde.org/show_bug.cgi?id=412618

Julian Schraner  changed:

   What|Removed |Added

 CC||m...@xyquadrat.ch

--- Comment #11 from Julian Schraner  ---
Huh, for some reason Ubuntu doesn't publish kio-dbgsym in the newer repos
anymore... Anyways, you should be able to download the .deb package from
launchpad: https://launchpad.net/ubuntu/disco/amd64/kio-dbgsym/5.56.0-0ubuntu1.
If you do not use a KDE backports PPA, this one should be the correct version.
Theoretically the backtrace should then be complete.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 412618] Crash when copying directory with the same name

2019-11-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=412618

--- Comment #10 from pac.dlfis...@gmail.com ---
And I feel as if I've been very clear in my "I can't figure how to get what you
need and shown the steps I have taken to try and find what it is you need"

For reference:
https://packages.ubuntu.com/search?keywords=kio=names=disco=all

even instructions on a different solution path would be viable. But instead, I
get told to check with the community about it. (A different repo, a direct
download, etc)

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 412618] Crash when copying directory with the same name

2019-11-24 Thread Elvis Angelaccio
https://bugs.kde.org/show_bug.cgi?id=412618

--- Comment #9 from Elvis Angelaccio  ---
We do care, but as already said we need a stacktrace with debug symbols
enabled, otherwise there is nothing we can do.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 412618] Crash when copying directory with the same name

2019-11-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=412618

--- Comment #8 from pac.dlfis...@gmail.com ---
A few things -- I thought I was being clear in the fact that I did look and
that I was asking someone who might know or perhaps somewhere where an
alternative link could be provided to the package.
I'm able to reproduce it consistently on different hardware running the current
version kubuntu - I did that BEFORE bothering to report.

I realize that everyone that contributes or works on fixing these bugs has a
life but so do the people who report them and I waited over two weeks just to
be told that I need to try and find a better solution to the problem that isn't
actually the one I'm reporting so you can have a more detailed report.

Just close the ticket at this point since nobody cares about this issue or can
identify where it is coming from.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 412618] Crash when copying directory with the same name

2019-11-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=412618

--- Comment #7 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 412618] Crash when copying directory with the same name

2019-11-03 Thread Elvis Angelaccio
https://bugs.kde.org/show_bug.cgi?id=412618

Elvis Angelaccio  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #6 from Elvis Angelaccio  ---
(In reply to pac.dlfisher from comment #3)
> Not sure which package actually contains kio.

Should be kio-dbgsym, but please ask in the Ubuntu support channels to be sure.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 412618] Crash when copying directory with the same name

2019-10-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=412618

pac.dlfis...@gmail.com changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|BACKTRACE   |---

--- Comment #5 from pac.dlfis...@gmail.com ---
Update status comment requirement message fulfillment center. How may I direct
your call?

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 412618] Crash when copying directory with the same name

2019-10-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=412618

pac.dlfis...@gmail.com changed:

   What|Removed |Added

 Attachment #123020|0   |1
is obsolete||

--- Comment #4 from pac.dlfis...@gmail.com ---
Created attachment 123371
  --> https://bugs.kde.org/attachment.cgi?id=123371=edit
Useless bug report

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 412618] Crash when copying directory with the same name

2019-10-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=412618

--- Comment #3 from pac.dlfis...@gmail.com ---
Not sure which package actually contains kio. I went with kdelibs5-dbg. I
should also add that the ubuntu repo only had kdelibs5 and libqt4 in the repo.

The generated bug report has some extra fun "this bug report is probably not
useful, 1 star of 3" stuff to it that I think is kinda cool! Maybe I missed
that before.

The packages containing debug information for the following application and
libraries are missing:
/usr/bin/dolphin
/lib/x86_64-linux/libQt5Widgets.so.5
/lib/x86_64-linux/libkdeinti5_dolphin.so
/lib/x86_64-linux/libKF5CoreAddons.so.5
/lib/x86_64-linux/libKF5KIOCore.so.5
/lib/x86_64-linux/libQt5Core.so.5

Unmodified repo file from minimum kubuntu install with closed source driver
support

$ apt search dolphin-*
> dolphin-dev

$ apt search libkdeinit
> pkg-kde-tools [installed

$ apt search libkf5coreaddons
> *-data [installed]
> *-dev
> *-dev-bin
> *-doc
> *5 [installed]
> qml-module-org-kde-kcoreaddons [installed]

$ apt search libKF5KIO
> *-dev
> *-doc
> *filewidgets5 [installed]
> *ntlm5 [installed]
> *widgets5 [installed]

$ apt search libqt5core
> *5a [installed]


---
And I realize this is VERY off topic but there is ABSOLUTELY no way I would go
about making a bug report for something I can't reliably reproduce nor would
have any idea where to start looking for a backtrace.
When I have Kate focused, the computer will randomly lock up and I'm forced to
power cycle the PC. If you happen to know what files might be of use, I can
take a gander and make an educated decision on making a bug report for this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 412618] Crash when copying directory with the same name

2019-10-20 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=412618

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 412618] Crash when copying directory with the same name

2019-10-06 Thread Elvis Angelaccio
https://bugs.kde.org/show_bug.cgi?id=412618

Elvis Angelaccio  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|REPORTED|NEEDSINFO
 CC||elvis.angelac...@kde.org

--- Comment #1 from Elvis Angelaccio  ---
Please install debug symbols for kio and then post another backtrace.

-- 
You are receiving this mail because:
You are watching all bug changes.