[Bug 1114259] Re: Opening files on an MTP device doesn't work

2013-05-01 Thread hefeweiz3n
@H5N1: This ist not a KIO-MTP bug as it, as you put it, works if the access rights are correct. So you will have to look elsewhere. With regard to this bug: It has absolutely nothing to do with it. This error here was not caused by being denied access to a device (With KIO actually can't do

[Bug 1114259] Re: Opening files on an MTP device doesn't work

2013-03-19 Thread hefeweiz3n
** Changed in: kio-mtp (Ubuntu) Assignee: (unassigned) = hefeweiz3n (philschmidt) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1114259 Title: Opening files on an MTP device doesn't work

[Bug 1114259] Re: Opening files on an MTP device doesn't work

2013-03-19 Thread hefeweiz3n
** Changed in: kio-mtp (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1114259 Title: Opening files on an MTP device doesn't work To manage notifications

[Bug 1114259] Re: Opening files on an MTP device doesn't work

2013-03-15 Thread hefeweiz3n
I just fixed this in current git. Very stupid mistake this one :(. Fix can be backported since no strings are involved. I'll try to upload a *.patch tonight. Even better would be to get the current version included, but seems unlikely as raring is in feature freeze. -- You received this bug

[Bug 1114259] Re: Opening files on an MTP device doesn't work

2013-03-15 Thread hefeweiz3n
Applying https://projects.kde.org/projects/playground/base/kio- mtp/repository/revisions/1350841237002357ab5b7bc1ffb9ca139a85dfd2 should do the trick, however the line numbers may differ greatly. As there have been lots of other changes that affect stability greatly a complete reimport would

[Bug 1000506] Re: plasma-widget-menubar crashes plasma-desktop frequently

2012-12-04 Thread hefeweiz3n
A Rebuild should fix this. I just build and installed Menubar 0.1.17 under Arch wich KDE 4.9.3 and it works. So please someone do that for Kubuntu to verify. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 485755] Re: openoffice.org-kde : Drag and Drop to not visible Area = Crash

2010-01-04 Thread hefeweiz3n
I can confirm now that the Bug is in fact an Upstream bug. Archlinux with KDE 4.3 and Openoffice 3.1 with KDE Integration (Same as under 9.10 with Kubuntu Backports PPA). -- openoffice.org-kde : Drag and Drop to not visible Area = Crash https://bugs.launchpad.net/bugs/485755 You received this

[Bug 485755] [NEW] openoffice.org-kde : Drag and Drop to not visible Area = Crash

2009-11-20 Thread hefeweiz3n
Public bug reported: Binary package hint: openoffice.org When trying to DragDrop Text from an area in a Document to an area that is not yet visible Openoffice crashes as soon as it should begin to scroll down. According to another user this Problem is confined to the KDE- Integration.

[Bug 485755] Re: openoffice.org-kde : Drag and Drop to not visible Area = Crash

2009-11-20 Thread hefeweiz3n
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/35878585/Dependencies.txt -- openoffice.org-kde : Drag and Drop to not visible Area = Crash https://bugs.launchpad.net/bugs/485755 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 462039] [NEW] File-Browser Progress bar gets stuck at 100%, Busy-Cursor also doesn't disappear

2009-10-27 Thread hefeweiz3n
Public bug reported: Binary package hint: k3b Ubuntu Karmic RC using KDE 4.3.2 When browsing files in the integrated File browser the Progress bar in the bottom left corner gest stuck at 100%. The Cursor also remains in the Busy-State, no matter what action is taken. Problem is probably due to

[Bug 352916] Re: plasma crashed with SIGSEGV

2009-04-02 Thread hefeweiz3n
Ok, I hope that this is the right file, it's the only one i could find. ** Attachment added: _usr_bin_plasma.1000.crash http://launchpadlibrarian.net/24667207/_usr_bin_plasma.1000.crash -- plasma crashed with SIGSEGV https://bugs.launchpad.net/bugs/352916 You received this bug notification

[Bug 352916] Re: plasma crashed with SIGSEGV

2009-04-01 Thread hefeweiz3n
** Attachment added: CoreDump.gz http://launchpadlibrarian.net/24620027/CoreDump.gz ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/24620028/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/24620029/ProcMaps.txt ** Attachment added:

[Bug 352490] Re: plasma crashed with SIGSEGV

2009-03-31 Thread hefeweiz3n
** Attachment added: CoreDump.gz http://launchpadlibrarian.net/24576403/CoreDump.gz ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/24576404/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/24576405/ProcMaps.txt ** Attachment added:

[Bug 282151] Re: kontact crashed with SIGSEGV

2008-10-25 Thread hefeweiz3n
I have not been able to reproduce this Bug, which obviously is a good thing. Sadly I dont know after which update this was no longer the Case, but the Bug can be closed. If I encounter it again, i will post again. -- kontact crashed with SIGSEGV https://bugs.launchpad.net/bugs/282151 You

[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk

2008-10-17 Thread hefeweiz3n
For your Information: Launchpad is NOT a support forum, in future situations please refer to the forums. As for your Problem: The driver is fixed in the current kernel-release, but as the live-cd still ships with the old kernel, networking is of course disabled with this card. I recommend waiting

[Bug 212388] Re: python2.5 crashed with DBusException in call_blocking()

2008-09-27 Thread hefeweiz3n
I confirm that I also occasionally get this message using Kubuntu Intrepid. I get this message usually just after logging in. Same here. -- python2.5 crashed with DBusException in call_blocking() https://bugs.launchpad.net/bugs/212388 You received this bug notification because you are a member