[partitionmanager] [Bug 370384] KDE Partition Manager crashes while starting up
https://bugs.kde.org/show_bug.cgi?id=370384 --- Comment #21 from Andrius Štikonas--- Just a small update: Looks like partitionmanager packaging repository disappeared, that's there were no newer snapshots of partitionmanager for a month... The reason for disappearance seems to be that debian removed their partitionmanager repo. You can see in https://packages.qa.debian.org/p/partitionmanager.html that partitionmanager was removed from testing... -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 371407] Unable to start KDE Partition Manager
https://bugs.kde.org/show_bug.cgi?id=371407 Andrius Štikonaschanged: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Andrius Štikonas --- That's due to ABI break in kpmcore and partition manager was not recompiled in neon. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370384] KDE Partition Manager crashes while starting up
https://bugs.kde.org/show_bug.cgi?id=370384 Andrius Štikonaschanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #20 from Andrius Štikonas --- Ok, I can see crash in neon myself now. Indeed as Vishal wrote earlier, crash is gone after rebuilding exactly the same source code. So I'm almost sure this bug is just due to ABI break in kpmcore and partition manager was not recompiled in neon dev edition... If that's not the case please reopen this bug once newer package reaches neon (I'm not sure when it will be though). -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370384] KDE Partition Manager crashes while starting up
https://bugs.kde.org/show_bug.cgi?id=370384 --- Comment #19 from Andrius Štikonas--- (In reply to Emre Unlu from comment #18) > I can reproduce this easily on KDE neon dev. ed. -stable and can get logs if > needed. dev stable edition has the same package as dev unstable (where kpmcore is newer than partitionmanager). But I think today there was a new build of partitionmanager, so it would be interesting to see if anything changes once it gets into neon repos. Unfortunately console output is not really useful... There isn't anything that could help to find this crash. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 371621] incorrect dimensions of swap partitions /used only/
https://bugs.kde.org/show_bug.cgi?id=371621 Andrius Štikonaschanged: What|Removed |Added Version Fixed In||3.0 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 371621] incorrect dimensions of swap partitions /used only/
https://bugs.kde.org/show_bug.cgi?id=371621 Andrius Štikonaschanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Andrius Štikonas --- I think this is dublicate. I recall fixing something like this. Before we just didn't have any code to read swap usage. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370384] KDE Partition Manager crashes while starting up
https://bugs.kde.org/show_bug.cgi?id=370384 --- Comment #15 from Andrius Štikonas--- (In reply to Vishal Rao from comment #13) > I should mention if I run my local build of partitionmanager/kpmcore it does > not crash, not sure if it's because I made a debug build. But when I run the > one that came installed in /usr/bin I get the previously posted stacktrace > crash during startup. Could it be you didn't build dummy backend in your local build? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370384] KDE Partition Manager crashes while starting up
https://bugs.kde.org/show_bug.cgi?id=370384 --- Comment #14 from Andrius Štikonas--- (In reply to Vishal Rao from comment #13) > I should mention if I run my local build of partitionmanager/kpmcore it does > not crash, not sure if it's because I made a debug build. But when I run the > one that came installed in /usr/bin I get the previously posted stacktrace > crash during startup. Thanks for slightly more detailed debug output. Let me look at the code and think what might be going wrong with the icon. But I am not sure if we will be able to test it if it doesn't crash with your local build. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370384] KDE Partition Manager crashes while starting up
https://bugs.kde.org/show_bug.cgi?id=370384 --- Comment #10 from Andrius Štikonas--- Hi Ben, Isn't m.2 drive nvme? I thought that's what nvme is... Backtrace points to line QListWidgetItem(QIcon::fromTheme(d.iconName()).pixmap(IconSize(KIconLoader::Desktop)), d.prettyName()) I wonder what might be going wrong here... icon Name should default to hard drive icon if icon is missing...maybe it's pretty name... -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370384] KDE Partition Manager crashes while starting up
https://bugs.kde.org/show_bug.cgi?id=370384 --- Comment #6 from Andrius Štikonas--- (In reply to Vishal Rao from comment #4) > Correction to my previous comment "was trying to format the pen drive when > came across this issue" - I didn't write correct - I meant to say I also > faced this issue during startup of partition manager, when it scans the > devices, it lists my devices and not sure if this is important but when it > reaches my /dev/nvme0n1 is when the crash happens. > > Any system info I can provide? What commands to run and post output that > would help? Ok, knowing it might crash on nvme might be useful. I'll try to think how I can reproduce it, need to find a way to add nvme device to virtual machine since I don't have any nvme devices. But I won't be able to find time for that till weekend at the very least... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370180] Widgets moved to secondary monitor upon reboot
https://bugs.kde.org/show_bug.cgi?id=370180 --- Comment #6 from Andrius Štikonas--- Plasma panel also jumps to the wrong screen when I run kquitapp5 plamashell && plasmashell -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370180] Widgets moved to secondary monitor upon reboot
https://bugs.kde.org/show_bug.cgi?id=370180 Andrius Štikonaschanged: What|Removed |Added CC||andr...@stikonas.eu Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #5 from Andrius Štikonas --- I think I have the same issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371196] Panel consistently appears on wrong monitor after reboot since 5.8
https://bugs.kde.org/show_bug.cgi?id=371196 Andrius Štikonaschanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||andr...@stikonas.eu Ever confirmed|0 |1 --- Comment #3 from Andrius Štikonas --- I can confirm this issue. I also waited till 5.8.2 but it wasn't fixed. Wanted to report a bug but looks like it is already reported. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370181] partitionmanager crashes while opening and scanning device /dev/sda
https://bugs.kde.org/show_bug.cgi?id=370181 --- Comment #6 from Andrius Štikonas--- No, I don't think we need any hard drive space except for tiny bit for storing settings. But I guess running out of space can make system perform unpredictably and something else goes wrong. I guess 20 seconds is still ok. It depends on the speed of drives. There might be some improvements in newer versions. Both Kubuntu and Mint ship not too new 1.2.1... -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370181] partitionmanager crashes while opening and scanning device /dev/sda
https://bugs.kde.org/show_bug.cgi?id=370181 --- Comment #4 from Andrius Štikonas--- What do you mean it started after waiting a while. Does it take very long? It takes some time to scan partitions and get all required info. So I guess it works for you on Kubuntu. Unfortunately I have no idea what causes std::bad_alloc. Google says it is usually thrown when you are out of memory but Partition Manager doesn't really use that much memory... -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370181] partitionmanager crashes while opening and scanning device /dev/sda
https://bugs.kde.org/show_bug.cgi?id=370181 --- Comment #1 from Andrius Štikonas--- I can't reproduce this crash with Mint 18. "QFileInfo::absolutePath: Constructed with empty filename" might be related to swap, there were some fixes for that in latest git version but it wasn't about crashes... Any more info about partitions and file systems? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370384] KDE Partition Manager crashes while starting up
https://bugs.kde.org/show_bug.cgi?id=370384 --- Comment #1 from Andrius Štikonas--- I can't reproduce this on Neon User Edition running on VirtualBox. Can you provide any more info? What devices or partitions are there? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370181] partitionmanager crashes while opening and scanning device /dev/sda
https://bugs.kde.org/show_bug.cgi?id=370181 Andrius Štikonaschanged: What|Removed |Added Summary|partiotionmanager crashes |partitionmanager crashes |while opening and scaning |while opening and scanning |device /dev/sda |device /dev/sda CC||andr...@stikonas.eu -- You are receiving this mail because: You are watching all bug changes.
[kteatime] [Bug 279222] icon of the progress of the system tray doesn't work
https://bugs.kde.org/show_bug.cgi?id=279222 Andrius Štikonaschanged: What|Removed |Added CC||luke-jr+kdeb...@utopios.org --- Comment #19 from Andrius Štikonas --- *** Bug 369588 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kteatime] [Bug 369588] 1.3.0: "Visualize progress in icon tray" non-functional
https://bugs.kde.org/show_bug.cgi?id=369588 Andrius Štikonaschanged: What|Removed |Added CC||andr...@stikonas.eu Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Andrius Štikonas --- *** This bug has been marked as a duplicate of bug 279222 *** -- You are receiving this mail because: You are watching all bug changes.
[kteatime] [Bug 279222] icon of the progress of the system tray doesn't work
https://bugs.kde.org/show_bug.cgi?id=279222 Andrius Štikonaschanged: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #18 from Andrius Štikonas --- Tomasz, I don't think kteatime is that well maintained, so you should probably try to do the change yourself otherwise nobody will do it... -- You are receiving this mail because: You are watching all bug changes.
[kdebugsettings] [Bug 356700] Segmentation fault after saving to a file and pressing OK
https://bugs.kde.org/show_bug.cgi?id=356700 --- Comment #3 from Andrius Štikonas--- In case or Partition Manager these crashes appeared after migration from QRegExp to QRegularExpression... And even replacing all QStringLiterals with QLatin1Strings -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 365882] Partition Manager shouldn't allow second instance to run
https://bugs.kde.org/show_bug.cgi?id=365882 Andrius Štikonaschanged: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #2 from Andrius Štikonas --- Unfortunately this introduces a regression in Wayland support. I'll revert the commit for now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365109] Konversation doesn't raise on Wayland
https://bugs.kde.org/show_bug.cgi?id=365109 --- Comment #2 from Andrius Štikonas--- This doesn't seem to be Konversation specific, I can't raise other windows, e.g. kgpg (frameworks branch) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365109] Konversation doesn't raise on Wayland
https://bugs.kde.org/show_bug.cgi?id=365109 Andrius Štikonaschanged: What|Removed |Added CC||andr...@stikonas.eu Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 368462] Add support for ECC keys (primary and subkeys)
https://bugs.kde.org/show_bug.cgi?id=368462 Andrius Štikonaschanged: What|Removed |Added Latest Commit||http://commits.kde.org/kgpg ||/65514177e6b9d096b5f6a822a1 ||699e474d791f03 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #8 from Andrius Štikonas --- Git commit 65514177e6b9d096b5f6a822a1699e474d791f03 by Andrius Štikonas. Committed on 01/10/2016 at 12:36. Pushed by stikonas into branch 'frameworks'. Fix compilation with older versions of gpgme. M +8-0core/convert.cpp http://commits.kde.org/kgpg/65514177e6b9d096b5f6a822a1699e474d791f03 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 342567] TLSv1.2 is not used on imap/smtp/managesieve
https://bugs.kde.org/show_bug.cgi?id=342567 Andrius Štikonaschanged: What|Removed |Added Version Fixed In||16.12 Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #21 from Andrius Štikonas --- All patches are not merged. Will be fixed in 16.12 with Frameworks 5.27. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 342567] TLSv1.2 is not used on imap/smtp/managesieve
https://bugs.kde.org/show_bug.cgi?id=342567 --- Comment #20 from Andrius Štikonas--- kio patch is now merged too, commit 8196a735bebc6fd5eaf9d293bd565c00ef98516b So SMTP should be working now. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 342567] TLSv1.2 is not used on imap/smtp/managesieve
https://bugs.kde.org/show_bug.cgi?id=342567 --- Comment #19 from Andrius Štikonas--- Ok, I've submitted 3 review requests to git.reviewboard.kde.org kmailtransport fix seems to be already in. kio: https://git.reviewboard.kde.org/r/129031/ kimap: https://git.reviewboard.kde.org/r/129030/ libksieve: https://git.reviewboard.kde.org/r/129029/ -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 369288] hfsplus-tools commands renamed in some distributions
https://bugs.kde.org/show_bug.cgi?id=369288 Andrius Štikonaschanged: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||http://commits.kde.org/kpmc ||ore/aa5daf03786a3eb2a8ca783 ||868f2d2ddd869e1ac --- Comment #3 from Andrius Štikonas --- Git commit aa5daf03786a3eb2a8ca783868f2d2ddd869e1ac by Andrius Štikonas. Committed on 24/09/2016 at 16:10. Pushed by stikonas into branch 'master'. Use symlinks to hfsplus (diskdev_cmds) commands. Some distributions rename those commands to mkfs.hfsplus and fsck.hfsplus. M +2-2src/fs/hfsplus.cpp http://commits.kde.org/kpmcore/aa5daf03786a3eb2a8ca783868f2d2ddd869e1ac -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 369288] hfsplus-tools commands renamed in some distributions
https://bugs.kde.org/show_bug.cgi?id=369288 --- Comment #2 from Andrius Štikonas--- Do you think make sense to switch HFS to the same utilities away from hfsutils? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 369288] hfsplus-tools commands renamed in some distributions
https://bugs.kde.org/show_bug.cgi?id=369288 Andrius Štikonaschanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED --- Comment #1 from Andrius Štikonas --- Yeah, I think I'll switch it so symlinks. I also didn't realize that other distributions just rename executables instead of using symlinks. Thanks for the report. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 369082] kded5 crashes on Plasma Wayland session
https://bugs.kde.org/show_bug.cgi?id=369082 Andrius Štikonaschanged: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #3 from Andrius Štikonas --- ok, looks like wacomtablet kcm was causing this crash. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 369082] kded5 crashes on Plasma Wayland session
https://bugs.kde.org/show_bug.cgi?id=369082 Andrius Štikonaschanged: What|Removed |Added Component|general |general Product|frameworks-knotifications |frameworks-kded Assignee|mklape...@kde.org |afies...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 369082] kded5 crashes on Plasma Wayland session
https://bugs.kde.org/show_bug.cgi?id=369082 --- Comment #2 from Andrius Štikonas--- So kded5 crashes when plasma wayland starts but I can start kded5 manually. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 369082] kded5 crashes on Plasma Wayland session
https://bugs.kde.org/show_bug.cgi?id=369082 Andrius Štikonaschanged: What|Removed |Added Summary|SNI system tray icons do|kded5 crashes on Plasma |not work in Plasma Wayland |Wayland session |session | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 369082] SNI system tray icons do not work in Plasma Wayland session
https://bugs.kde.org/show_bug.cgi?id=369082 --- Comment #1 from Andrius Štikonas--- Looks like org.kde.StatusNotifierWatcher interface is not present in my wayland session -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 369082] SNI system tray icons do not work in Plasma Wayland session
https://bugs.kde.org/show_bug.cgi?id=369082 Andrius Štikonaschanged: What|Removed |Added CC||kdelibs-b...@kde.org Assignee|kwin-bugs-n...@kde.org |mklape...@kde.org Product|kwin|frameworks-knotifications Version|5.7.95 |unspecified Component|wayland-generic |general -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 259678] Partitionmanager should not require root privileges to start.
https://bugs.kde.org/show_bug.cgi?id=259678 Andrius Štikonaschanged: What|Removed |Added CC||jodr...@live.com --- Comment #13 from Andrius Štikonas --- *** Bug 369144 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 369144] Partitionmanager lack of privilege under wayland.
https://bugs.kde.org/show_bug.cgi?id=369144 Andrius Štikonaschanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Andrius Štikonas --- Well, this is part of a wider problem. On wayland you can't easily run applications as root. They have to use KAuth to obtain privileges. But Partition Manager uses root A LOT, so porting everything to KAuth very non trivial. Will take some time... *** This bug has been marked as a duplicate of bug 259678 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368989] Alt+F4 shortcut works only with XWayland windows
https://bugs.kde.org/show_bug.cgi?id=368989 Andrius Štikonaschanged: What|Removed |Added CC||andr...@stikonas.eu -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 368982] Impossible to change screen resolution under Wayland
https://bugs.kde.org/show_bug.cgi?id=368982 Andrius Štikonaschanged: What|Removed |Added CC||andr...@stikonas.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 369082] New: SNI system tray icons do not work in Plasma Wayland session
https://bugs.kde.org/show_bug.cgi?id=369082 Bug ID: 369082 Summary: SNI system tray icons do not work in Plasma Wayland session Product: kwin Version: 5.7.95 Platform: Gentoo Packages URL: http://pastebin.com/8CpzEGdd OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: andr...@stikonas.eu I can't see any system tray icons when running Plasma on Wayland. Whenever I run program from terminal I get the following error message. org.kde.knotifications: service is "org.kde.StatusNotifierItem-3866-1" org.kde.kwindowsystem: Loaded plugin "/usr/lib64/qt5/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemKWaylandPlugin.so" for platform "wayland" org.kde.knotifications: Registering a client interface to the KStatusNotifierWatcher org.kde.knotifications: KStatusNotifierWatcher not reachable Reproducible: Always Steps to Reproduce: 1. Start Plasma Wayland sessions Actual Results: No system tray icons besides plasmoids. Expected Results: System tray works. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 368674] partition manager crashes while checking highly corrupted partition (memory leak)
https://bugs.kde.org/show_bug.cgi?id=368674 --- Comment #1 from Andrius Štikonas--- I think what happens is that output from e2fsck is stored in a variable in KPM. e2fsck keeps producing more and more output and uses more and more memory. We can already do command timeout but that will probably not work because some normal file system checks sometimes take a long time to happen, I saw one lasting about 50 minutes. One way to fix this might be to add a limit to stored output and exit with error when that limit is reached. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 368187] Outdated KPM 1.2.1 available in Discover
https://bugs.kde.org/show_bug.cgi?id=368187 --- Comment #3 from Andrius Štikonas--- Maybe try here: https://launchpad.net/ubuntu/+source/partitionmanager -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 368211] crashes after start
https://bugs.kde.org/show_bug.cgi?id=368211 Andrius Štikonaschanged: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Andrius Štikonas --- KDE Partition Manager 1.0.3 is simply too old (6 years since the release). Please upgrade to newer version, e.g. 2.2.1. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 368187] Outdated KPM 1.2.1 available in Discover
https://bugs.kde.org/show_bug.cgi?id=368187 Andrius Štikonaschanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Andrius Štikonas --- Yeah, unfortunately noone packages it for Kubuntu :(. Even older version is in Debian. 1.2.1 for Kubuntu was packaged by Jonathan Riddell but he now works on Neon (which by the way has much newer version of KDE Partition Manager). Try to report this bug to Kubuntu developers (probably on Launchpad)... -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 357114] Crash when trying to remove partition
https://bugs.kde.org/show_bug.cgi?id=357114 Andrius Štikonaschanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #4 from Andrius Štikonas --- I think crashes happen when trying to write to read-only device. So I'll mark this as duplicate of another similar bug. If that's not the case please reopen. *** This bug has been marked as a duplicate of bug 365872 *** -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 367473] Partition Manager seems to show swap partition is using more than its size
https://bugs.kde.org/show_bug.cgi?id=367473 Andrius Štikonaschanged: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kpmc ||ore/5ab60c6dfadd5cf2e941d01 ||05ff598092031f9b5 Status|CONFIRMED |RESOLVED --- Comment #6 from Andrius Štikonas --- Git commit 5ab60c6dfadd5cf2e941d0105ff598092031f9b5 by Andrius Štikonas. Committed on 29/08/2016 at 11:12. Pushed by stikonas into branch 'master'. Enable used space reporting for swap. M +5-0src/core/lvmdevice.cpp M +26 -5src/fs/linuxswap.cpp M +5-0src/fs/linuxswap.h M +4-0src/plugins/libparted/libpartedbackend.cpp http://commits.kde.org/kpmcore/5ab60c6dfadd5cf2e941d0105ff598092031f9b5 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 367473] Partition Manager seems to show swap partition is using more than its size
https://bugs.kde.org/show_bug.cgi?id=367473 --- Comment #5 from Andrius Štikonas--- We don't really have code to read swap usage. I guess one way to fix this bug is to add that code, e.g. check /proc/swaps like GParted does. The other is to simply do not report swap usage (since it is not really relevant for resizing, you can't resize active swap partition and inactive does not have any used space), but I guess the first option is nicer. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 367473] Partition Manager seems to show swap partition is using more than its size
https://bugs.kde.org/show_bug.cgi?id=367473 Andrius Štikonaschanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 179264] Wish: Add support for LVM in KDE Partition Manager
https://bugs.kde.org/show_bug.cgi?id=179264 Andrius Štikonaschanged: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #3 from Andrius Štikonas --- LVM support is now added to KDE Partition Manager. It's not "all the capabilities, past and present, of lvmtools." but basic stuff is working, e.g. creating/resizing LVM Physical Volumes, creating/resizing LVM Logical Volumes, adding/removing LVM PVs to/from LVM Volume groups. More advanced stuff may required using command line, just like with other partitioning tools, e.g. we don't support absolutely all features of ext4 or btrfs. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 364394] Managesieve is broken
https://bugs.kde.org/show_bug.cgi?id=364394 Andrius Štikonaschanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Andrius Štikonas --- Well, it works for me too. As original bug reporter I'll mark this as fixed then... -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 367577] [KGpg-frameworks] Hangs after rejecting the first assistant dialog
https://bugs.kde.org/show_bug.cgi?id=367577 Andrius Štikonaschanged: What|Removed |Added CC||andr...@stikonas.eu --- Comment #1 from Andrius Štikonas --- It doesn't hang here, it simply starts in the tray after clicking cancel. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 364394] Managesieve is broken
https://bugs.kde.org/show_bug.cgi?id=364394 --- Comment #1 from Andrius Štikonas--- wasn't this reverted with 16.04.3? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 366313] Used space of Fat32 partition is zero if partition is not mounted and the dirty bit is set.
https://bugs.kde.org/show_bug.cgi?id=366313 Andrius Štikonaschanged: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kpmc ||ore/ea99bcc76fd92d85182445c ||5a80eac2590e7c53a --- Comment #9 from Andrius Štikonas --- Git commit ea99bcc76fd92d85182445c5a80eac2590e7c53a by Andrius Štikonas. Committed on 02/08/2016 at 20:41. Pushed by stikonas into branch 'master'. Correctly report used space of FAT partitions whose dirty bit is set. M +1-1src/core/operationrunner.cpp M +1-1src/fs/fat16.cpp http://commits.kde.org/kpmcore/ea99bcc76fd92d85182445c5a80eac2590e7c53a -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 366313] Used space of Fat32 partition is zero if partition is not mounted and the dirty bit is set.
https://bugs.kde.org/show_bug.cgi?id=366313 Andrius Štikonaschanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #8 from Andrius Štikonas --- (In reply to sascha.zenglein from comment #6) > Done. fsck.msdos shows the correct size even with dirty bit set though. I > think there has to be some condition that decides to not show info if the > file system is corrupt, because if you just took the info of fsck.msdos then > the size would be correct either way. fsck.msdos returns exit status 1 when dirty bit is set, that's why code to read usage was not run. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 366313] Used space of Fat32 partition is zero if partition is not mounted and the dirty bit is set.
https://bugs.kde.org/show_bug.cgi?id=366313 --- Comment #7 from Andrius Štikonas--- Yeah, I'll try to look into it. Now that we know this is caused by dirty bit... -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 366313] Used space of Fat32 partition is zero if partition is not mounted.
https://bugs.kde.org/show_bug.cgi?id=366313 --- Comment #5 from Andrius Štikonas--- Well, we probably don't want to automatically run fsck that modifies file system. Maybe it would be nice to show some warning that file system is not clean. But without looking further into this I can't tell how easy is to add that. So I guess change the title and catetory to wishlist... -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 366313] Used space of Fat32 partition is zero if partition is not mounted.
https://bugs.kde.org/show_bug.cgi?id=366313 --- Comment #3 from Andrius Štikonas--- Strange, it seems to work for me. I've just looked at fat code in KPMcore, so used space is calculated by running fsck.msdos -n -v /dev/sdb2 and looking at cluster size in the output, e.g.: 4096 bytes per cluster as well as the number of used clusters, e.g /dev/sdb2: 2 files, 38401/1339843 clusters Can you check if you see these two lines if you run fsck.msdos manually Maybe something to do with fsck.msdos on your system, e.g. they changed something between versions... My version is fsck.fat 3.0.28 (2015-05-16) -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 366313] Used space is zero if partition is not mounted.
https://bugs.kde.org/show_bug.cgi?id=366313 --- Comment #1 from Andrius Štikonas--- Is it true with any file system? Or some particular file system, if so then which one are you using. (In reply to sascha.zenglein from comment #0) > Recovery partition of size 2.71GiB was shown as completely empty. Panicked > for a moment before checking that all the files were still there. Used space > was correct after the partition was mounted to /mnt. > > Reproducible: Always > > Steps to Reproduce: > 1. Have a partition that is not mounted and not empty > 2. Check the used space in partitionmanager > > Actual Results: > The used space of said partition is shown as zero. > > Expected Results: > The used space should be shown correctly or there should be a text saying it > can't be accessed. Thinking it's empty might lead someone to deleting it. > > It's the standard "Dell XPS 13 (2016) Developer Edition" recovery partition. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 259678] Partitionmanager should not require root privileges to start.
https://bugs.kde.org/show_bug.cgi?id=259678 --- Comment #12 from Andrius Štikonas--- This is now in progress. First bits of KAuth support landed in kpmcore master. However, root is required in lots and lots of places, so it will still need much more work and for now kdesu is still used. (partitionmanager --dontsu now mostly detects available devices and partitions) -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 365882] Partition Manager shouldn't allow second instance to run
https://bugs.kde.org/show_bug.cgi?id=365882 Andrius Štikonaschanged: What|Removed |Added Latest Commit||http://commits.kde.org/part ||itionmanager/71510d270950d0 ||5ddda5c81d938db7e5744650bc Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Andrius Štikonas --- Git commit 71510d270950d05ddda5c81d938db7e5744650bc by Andrius Štikonas. Committed on 20/07/2016 at 11:36. Pushed by stikonas into branch 'master'. Do not allow the second instance of Partition Manager M +1-0CMakeLists.txt M +1-0src/CMakeLists.txt M +3-0src/main.cpp http://commits.kde.org/partitionmanager/71510d270950d05ddda5c81d938db7e5744650bc -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 365872] Partition manager crash when try decrease partition
https://bugs.kde.org/show_bug.cgi?id=365872 --- Comment #2 from Andrius Štikonas--- Hmm, this crash in Partition::sectorsUsed() is probably the same as all these other crashes reported in bugzilla which I unfortunately hasn't been able to reproduce. I can try to see if locking sd card would help. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 365789] Add partition manager to system settings
https://bugs.kde.org/show_bug.cgi?id=365789 Andrius Štikonaschanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #2 from Andrius Štikonas --- The main reason why late Volker Lanz decided to remove KDE Partition Manager KCM module (i.e. systemsettings module) is that you can't easily make it have all same features as standalone application. And this confuses people a lot since they think that KCM module is the whole application. Root privileges is another problem. Hopefully KPM will not require root in the future but it is still quite some time in the future. In addition, writing KCM module would require to spend a lot of manpower (which we don't have that much and it is better spend on other things) on another UI which will only be useful to Plasma users. KDE Partition Manager is obviously a KDE project but it might be useful to other users too, it even has some features that Gparted lacks (vice versa too, gparted does some things we don't). -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 365791] New: Error when deleting private key with GnuPG 2.1
https://bugs.kde.org/show_bug.cgi?id=365791 Bug ID: 365791 Summary: Error when deleting private key with GnuPG 2.1 Product: kgpg Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@opensource.sf-tec.de Reporter: andr...@stikonas.eu Error status (TS_MSG_SEQUENCE) is returned when deleting private key. Compared to GnuPG 2.0, the new version requires additional new line input before printing [GNUPG:] GOT_IT Reproducible: Always gpg --delete-secret-and-public-key --status-fd=1 --command-fd=0 B47458AF3DF75D87 gpg (GnuPG) 2.1.12; Copyright (C) 2016 Free Software Foundation, Inc. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. sec rsa2048/3DF75D87 2016-07-17 testtest[GNUPG:] GET_BOOL delete_key.secret.okay y [GNUPG:] GOT_IT [GNUPG:] PINENTRY_LAUNCHED 26194 [GNUPG:] PINENTRY_LAUNCHED 26199 pub rsa2048/3DF75D87 2016-07-17 testtest [GNUPG:] GET_BOOL delete_key.okay [GNUPG:] GOT_IT -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 364233] Request to switch to hfsplus-tools
https://bugs.kde.org/show_bug.cgi?id=364233 Andrius Štikonaschanged: What|Removed |Added Version Fixed In|2.3 |2.2.1 --- Comment #3 from Andrius Štikonas --- Hi, I've now released 2.2.1 with this change. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 364889] KDE Partition Manager 1.2.1 doesn't ask for root privileges on KDE Neon 5.6.5
https://bugs.kde.org/show_bug.cgi?id=364889 Andrius Štikonaschanged: What|Removed |Added CC||andr...@stikonas.eu --- Comment #2 from Andrius Štikonas --- It looks like this is caused by a combination of 2 things: kf5 based kdesu is not in $PATH kde partition manager in neon is too old (only 2.0.1 and later can find kdesu in libexec folder) -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 364863] Crash when trying to grow partition
https://bugs.kde.org/show_bug.cgi?id=364863 --- Comment #1 from Andrius Štikonas--- Hi, could you tell which filesystem was that? I'm having trouble reproducing that, so maybe you know any other info that might be relevant. E.g. does it happen every time, or maybe this has something to do with sector size... -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 364645] Partitionmanager crashs when trying to import partition table
https://bugs.kde.org/show_bug.cgi?id=364645 --- Comment #2 from Andrius Štikonas--- Hi, did you use localized or English version of KDE Partition Manager? There might be one issue caused by translated strings? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 179264] Wish: Add support for LVM in KDE Partition Manager
https://bugs.kde.org/show_bug.cgi?id=179264 Andrius Štikonaschanged: What|Removed |Added Assignee|v...@fidra.de |tith.chant...@gmail.com CC||andr...@stikonas.eu Status|CONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 364648] New: Import/Export partition table does not work for non English locales
https://bugs.kde.org/show_bug.cgi?id=364648 Bug ID: 364648 Summary: Import/Export partition table does not work for non English locales Product: partitionmanager Version: 2.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: andr...@stikonas.eu Import/Export partition table does not work for non English locales when "primary" or "extended" in PartitionRole, etc are translated. Reproducible: Always Steps to Reproduce: 1. Export partition table Actual Results: It contains translated version of "primary" -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 357114] Crash when trying to remove partition
https://bugs.kde.org/show_bug.cgi?id=357114 --- Comment #3 from Andrius Štikonas--- This is a possible duplicate of bug #306476 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 357114] Crash when trying to remove partition
https://bugs.kde.org/show_bug.cgi?id=357114 Andrius Štikonaschanged: What|Removed |Added CC||tonym...@gmail.com --- Comment #2 from Andrius Štikonas --- *** Bug 364645 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 364645] Partitionmanager crashs when trying to import partition table
https://bugs.kde.org/show_bug.cgi?id=364645 Andrius Štikonaschanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Andrius Štikonas --- *** This bug has been marked as a duplicate of bug 357114 *** -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 364476] partitionmanager can't identify iso9660 partition
https://bugs.kde.org/show_bug.cgi?id=364476 Andrius Štikonaschanged: What|Removed |Added Severity|normal |wishlist Priority|NOR |LO --- Comment #1 from Andrius Štikonas --- Changing to wishlist. Detection support might be nice but I don't think anything else would be possible (e.g. resize). Looks like Gparted also doesn't support it. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 342567] TLSv1.2 is not used on imap/smtp/managesieve
https://bugs.kde.org/show_bug.cgi?id=342567 Andrius Štikonaschanged: What|Removed |Added Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #16 from Andrius Štikonas --- Still not working for me with 16.04.2 (KF5 5.21) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 364394] New: Managesieve is broken
https://bugs.kde.org/show_bug.cgi?id=364394 Bug ID: 364394 Summary: Managesieve is broken Product: kmail2 Version: 5.1.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: sieve Assignee: kdepim-b...@kde.org Reporter: andr...@stikonas.eu When I try to open managesieve dialog it shows an error: Sieve operation failed. The server responded: require ["fileinto","imap4flags"]; Reproducible: Always Steps to Reproduce: 1. Try openning ManageSieve editor in KMail Actual Results: Error message shows the first line of my sieve script. I checked, this got broken with commit aa295b6cf15ee67a980b2858ccad6e6e8e769585 just before 16.04.1 version got released. Fix Bug 328246 - Manage Sieve scripts feature broken FIXED-IN: 5.2.1 BUG: 328246 My IMAP server is Dovecot 2.2.19 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 364284] Cannot edit “More...“ mount options - OK / Apply button missing
https://bugs.kde.org/show_bug.cgi?id=364284 --- Comment #2 from Andrius Štikonas--- Also added placeholder text to guide user. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 364284] Cannot edit “More...“ mount options - OK / Apply button missing
https://bugs.kde.org/show_bug.cgi?id=364284 Andrius Štikonaschanged: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/part ||itionmanager/af140882a7a65c ||1d38869c2aff9f8ccb5fa95eb5 Status|CONFIRMED |RESOLVED --- Comment #1 from Andrius Štikonas --- Git commit af140882a7a65c1d38869c2aff9f8ccb5fa95eb5 by Andrius Štikonas. Committed on 15/06/2016 at 13:35. Pushed by stikonas into branch 'master'. Add Ok/Cancel buttons to EditMountPointOptionsDialog. M +8-0src/gui/editmountoptionsdialog.cpp http://commits.kde.org/partitionmanager/af140882a7a65c1d38869c2aff9f8ccb5fa95eb5 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 364284] Cannot edit “More...“ mount options - OK / Apply button missing
https://bugs.kde.org/show_bug.cgi?id=364284 Andrius Štikonaschanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 364233] Request to switch to hfsplus-tools
https://bugs.kde.org/show_bug.cgi?id=364233 Andrius Štikonaschanged: What|Removed |Added Status|ASSIGNED|RESOLVED Version Fixed In||2.3 Resolution|--- |FIXED Latest Commit||2514f7d8f4aea875e0777ee2a77 ||c1902c880e1ab --- Comment #2 from Andrius Štikonas --- Fixed in http://commits.kde.org/kpmcore/2514f7d8f4aea875e0777ee2a77c1902c880e1ab -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 364233] Request to switch to hfsplus-tools
https://bugs.kde.org/show_bug.cgi?id=364233 Andrius Štikonaschanged: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Andrius Štikonas --- Will do for the next version. Thanks for reporting this. I was not aware of those hfsplus-tools (although, they are called diskdev_cmds in Gentoo, took me some time to realize). -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 363294] KDE Partition Manager crashes on exit if QFileDialog is used
https://bugs.kde.org/show_bug.cgi?id=363294 --- Comment #2 from Andrius Štikonas--- The same thing happens in kjumpingcube if linking to KDELibs4Support is removed. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 314294] W95 FAT32 (LBA) partition: "No valid partition table was found on this device."
https://bugs.kde.org/show_bug.cgi?id=314294 Andrius Štikonaschanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||andr...@stikonas.eu Resolution|--- |WORKSFORME --- Comment #2 from Andrius Štikonas --- I've tried this MBR dump on my 500 GB harddrive and it worked fine. But partition inside was actually a bit larger than 40 GB, so if harddrive was just 40 GB than that's the problem (partition larger than capacity of the harddrive). -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 363294] KDE Partition Manager crashes on exit if QFileDialog is used
https://bugs.kde.org/show_bug.cgi?id=363294 Andrius Štikonaschanged: What|Removed |Added Ever confirmed|0 |1 Version|Git |2.2 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 324772] partitionmanager deleted mounted partition table - Errors AFTER writing changes to disk
https://bugs.kde.org/show_bug.cgi?id=324772 Andrius Štikonaschanged: What|Removed |Added Resolution|--- |WONTFIX Status|CONFIRMED |RESOLVED --- Comment #2 from Andrius Štikonas --- I added some extra check when mounted partition is deleted. But it's not possible to check these things at job execution when partition table is created. Actually, gparted also throws an error very late if you mount partition without refreshing the status of the devices. It's just the way partition managers work, e.g. if I open partition manager and gparted at the same time, try to do some operations and then apply first one program and then another, the second program will also throw a lot of errors. So try to refresh partition manager status (e.g. F5 or from menu) if you do any changes externally. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 363393] No way to validate the "Edit mount point" GUI
https://bugs.kde.org/show_bug.cgi?id=363393 Andrius Štikonaschanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Andrius Štikonas --- Was already fixed in KDE Partition Manager 2.1 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 363294] KDE Partition Manager crashes on exit if QFileDialog is used
https://bugs.kde.org/show_bug.cgi?id=363294 --- Comment #1 from Andrius Štikonas--- Bug 356700 has very similar backtrace -- You are receiving this mail because: You are watching all bug changes.
[kdebugsettings] [Bug 356700] Segmentation fault after saving to a file and pressing OK
https://bugs.kde.org/show_bug.cgi?id=356700 Andrius Štikonaschanged: What|Removed |Added CC||andr...@stikonas.eu --- Comment #1 from Andrius Štikonas --- Note that this looks very similar to bug 363294 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 362314] crash after close
https://bugs.kde.org/show_bug.cgi?id=362314 --- Comment #2 from Andrius Štikonas--- Related KPM bug: 363294 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 362314] crash after close
https://bugs.kde.org/show_bug.cgi?id=362314 Andrius Štikonaschanged: What|Removed |Added CC||andr...@stikonas.eu --- Comment #1 from Andrius Štikonas --- Hmm, the same thing happens with KDE Partition Manager -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 363294] New: KDE Partition Manager crashes on exit if QFileDialog is used
https://bugs.kde.org/show_bug.cgi?id=363294 Bug ID: 363294 Summary: KDE Partition Manager crashes on exit if QFileDialog is used Product: partitionmanager Version: Git Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: andr...@stikonas.eu KDE Partition Manager crashes on exit if QFileDialog with most themes (e.g. Breeze or Oxygen but not with GTK+ theme). Reproducible: Always Steps to Reproduce: 1. Open KDE Partition Manager 2. Menu->Device->Export Partition Table 3. Click cancel 4. Quit KDE Partition Manager Actual Results: Application: partitionmanager (partitionmanager), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 QGenericAtomicOps>::load (_q_value=@0x7f8bb58b2720: ) at ../../include/QtCore/../../src/corelib/thread/qgenericatomic.h:90 #7 QBasicAtomicInteger::load (this=0x7f8bb58b2720) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:118 #8 QtPrivate::RefCount::deref (this=0x7f8bb58b2720) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:60 #9 QString::~QString (this=0x2acea00, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qstring.h:1053 #10 QRegExpEngineKey::~QRegExpEngineKey (this=, __in_chrg=) at tools/qregexp.cpp:866 #11 QHashNode ::Node>::~QHashNode (this=, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qhash.h:237 #12 QHash ::Node>::deleteNode2 (node=0x2ace9f0) at ../../include/QtCore/../../src/corelib/tools/qhash.h:585 #13 0x7f8bcd8aad69 in QHashData::free_helper (this=0x2562fd0, node_delete=0x7f8bcd8cc890 ::Node>::deleteNode2(QHashData::Node*)>) at tools/qhash.cpp:491 #14 0x7f8bcd8c44d4 in QHash ::Node>::freeData (this=, x=) at ../../include/QtCore/../../src/corelib/tools/qhash.h:621 #15 QHash ::Node>::~QHash (this=, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qhash.h:342 #16 QHash ::Node>::clear (this=0x7f8bcdc2cdb0 <(anonymous namespace)::Q_QGS_globalEngineCache::innerFunction()::holder+16>) at ../../include/QtCore/../../src/corelib/tools/qhash.h:627 #17 QCache ::clear (this=0x7f8bcdc2cda0 <(anonymous namespace)::Q_QGS_globalEngineCache::innerFunction()::holder>) at tools/qcache.h:119 #18 QCache ::~QCache (this=0x7f8bcdc2cda0 <(anonymous namespace)::Q_QGS_globalEngineCache::innerFunction()::holder>, __in_chrg=) at tools/qcache.h:87 #19 (anonymous namespace)::Q_QGS_globalEngineCache::Holder::~Holder (this=0x7f8bcdc2cda0 <(anonymous namespace)::Q_QGS_globalEngineCache::innerFunction()::holder>, __in_chrg=) at tools/qregexp.cpp:3820 #20 0x7f8bccb48cd8 in __run_exit_handlers (status=0, listp=0x7f8bccea9618 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 #21 0x7f8bccb48d25 in __GI_exit (status=) at exit.c:104 #22 0x7f8bccb335b7 in __libc_start_main (main=0x41bff1 , argc=2, argv=0x7ffe5cd73b28, init=, fini=, rtld_fini=, stack_end=0x7ffe5cd73b18) at libc-start.c:323 #23 0x0041bb79 in _start () -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 363216] Copying partition into another twice and creating a new partition table results in a crash
https://bugs.kde.org/show_bug.cgi?id=363216 Andrius Štikonaschanged: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kpmc ||ore/4278172f35af11eaf6efd87 ||2645ad8015cc79839 Status|CONFIRMED |RESOLVED --- Comment #1 from Andrius Štikonas --- Git commit 4278172f35af11eaf6efd872645ad8015cc79839 by Andrius Štikonas. Committed on 19/05/2016 at 15:40. Pushed by stikonas into branch 'master'. Iterate over operation stack backwards. M +10 -7src/core/operationstack.cpp http://commits.kde.org/kpmcore/4278172f35af11eaf6efd872645ad8015cc79839 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 363216] Copying partition into another twice and creating a new partition table results in a crash
https://bugs.kde.org/show_bug.cgi?id=363216 Andrius Štikonaschanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 362956] Copying partition into another partition returns an error
https://bugs.kde.org/show_bug.cgi?id=362956 Andrius Štikonaschanged: What|Removed |Added Latest Commit||http://commits.kde.org/kpmc ||ore/96eaf6abae7d53bde02316b ||b550f6b6154456a98 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Andrius Štikonas --- Git commit 96eaf6abae7d53bde02316bb550f6b6154456a98 by Andrius Štikonas. Committed on 19/05/2016 at 11:11. Pushed by stikonas into branch 'master'. Fix overwriting partitions. M +1-1src/ops/copyoperation.cpp http://commits.kde.org/kpmcore/96eaf6abae7d53bde02316bb550f6b6154456a98 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 360554] Cache / Save Pending Operations on Error
https://bugs.kde.org/show_bug.cgi?id=360554 Andrius Štikonaschanged: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #1 from Andrius Štikonas --- I don't think there is any easy way to do that. Please suggest if there is. After the error happens we must rescan existing partitions, otherwise data corruption might happen. And rescaning involves removing all operations from operations stack, the same happens even if you refresh before applying operations. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 324772] partitionmanager deleted mounted partition table - Errors AFTER writing changes to disk
https://bugs.kde.org/show_bug.cgi?id=324772 --- Comment #1 from Andrius Štikonas--- Hi bill, Actually KPM seems to disable creating a new partition table if there are mounted partitions. Did you mean mounting outside KPM without refreshing KPM? At least right now KPM always assumes that there were no changes made to the partitions since the last refresh. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 363216] New: Copying partition into another twice and creating a new partition table results in a crash
https://bugs.kde.org/show_bug.cgi?id=363216 Bug ID: 363216 Summary: Copying partition into another twice and creating a new partition table results in a crash Product: partitionmanager Version: Git Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: andr...@stikonas.eu Copying partition into another twice and creating a new partition table results in a crash. Reproducible: Always Steps to Reproduce: 1. Copy partition into another 2. Repeat step 1 with the same partitions 3. Create a new partition table Actual Results: Crash Expected Results: New empty partition table is created. Application: KDE Partition Manager (partitionmanager), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f37df679880 (LWP 18120))] Thread 2 (Thread 0x7f37b49f5700 (LWP 18274)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f37e708ba6a in g_cond_wait_until () from /usr/lib64/libglib-2.0.so.0 #2 0x7f37e701bbd9 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f37e701c1fb in g_async_queue_timeout_pop () from /usr/lib64/libglib-2.0.so.0 #4 0x7f37e706e2ca in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7f37e706d875 in ?? () from /usr/lib64/libglib-2.0.so.0 #6 0x7f37e84ea474 in start_thread (arg=0x7f37b49f5700) at pthread_create.c:334 #7 0x7f37ea82c6cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f37df679880 (LWP 18120)): [KCrash Handler] #6 0x7f37eee480c5 in Operation::insertPreviewPartition (this=0x27b16e0, device=..., p=...) at /home/andrius/repositories/kde/kpmcore/src/ops/operation.cpp:54 #7 0x7f37eee514cd in CopyOperation::undo (this=0x27b16e0) at /home/andrius/repositories/kde/kpmcore/src/ops/copyoperation.cpp:117 #8 0x00454c0e in MainWindow::onApplyAllOperations (this=0x21639b0) at /home/andrius/repositories/kde/partitionmanager/src/gui/mainwindow.cpp:722 #9 0x0048d680 in MainWindow::qt_static_metacall (_o=0x21639b0, _c=QMetaObject::InvokeMetaMethod, _id=20, _a=0x7ffdffd6bac0) at /home/andrius/repositories/kde/partitionmanager/build/src/moc_mainwindow.cpp:211 #10 0x7f37eb64fe1a in QMetaObject::activate (sender=0x238dd00, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3713 #11 0x7f37ebe05e02 in QAction::triggered(bool) () from /usr/lib64/libQt5Widgets.so.5 #12 0x7f37ebe08288 in QAction::activate(QAction::ActionEvent) () from /usr/lib64/libQt5Widgets.so.5 #13 0x7f37ebf0dfa0 in ?? () from /usr/lib64/libQt5Widgets.so.5 #14 0x7f37ebf0e0d4 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5 #15 0x7f37ebfd2b1a in QToolButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5 #16 0x7f37ebe52a98 in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #17 0x7f37ebfd2bf9 in QToolButton::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #18 0x7f37ebe0fa3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #19 0x7f37ebe155c9 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #20 0x7f37eb62803d in QCoreApplication::notifyInternal (this=0x7ffdffd6c8b0, receiver=0x23fa710, event=0x7ffdffd6bfd0) at kernel/qcoreapplication.cpp:965 #21 0x7f37ebe144c2 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /usr/lib64/libQt5Widgets.so.5 #22 0x7f37ebe6ceeb in ?? () from /usr/lib64/libQt5Widgets.so.5 #23 0x7f37ebe6f42b in ?? () from /usr/lib64/libQt5Widgets.so.5 #24 0x7f37ebe0fa3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #25 0x7f37ebe14ebe in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #26 0x7f37eb62803d in QCoreApplication::notifyInternal (this=0x7ffdffd6c8b0, receiver=0x240b8c0, event=0x7ffdffd6c3f0) at kernel/qcoreapplication.cpp:965 #27 0x7f37eb946c17 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib64/libQt5Gui.so.5 #28 0x7f37eb948a45 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib64/libQt5Gui.so.5 #29 0x7f37eb930bb8 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib64/libQt5Gui.so.5 #30 0x7f37d8f20160 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #31 0x7f37e7046f97 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #32 0x7f37e70471f0 in ?? () from /usr/lib64/libglib-2.0.so.0 #33 0x7f37e704729c in g_main_context_iteration () from
[partitionmanager] [Bug 363050] Respect minCapacity when creating new filesystems in small unformatted partitions
https://bugs.kde.org/show_bug.cgi?id=363050 Andrius Štikonaschanged: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/part ||itionmanager/65d80dd405ad40 ||fc029a05080baaf1bda4d74611 Status|UNCONFIRMED |RESOLVED --- Comment #1 from Andrius Štikonas --- Git commit 65d80dd405ad40fc029a05080baaf1bda4d74611 by Andrius Štikonas. Committed on 17/05/2016 at 18:33. Pushed by stikonas into branch 'master'. Respect minCapacity when creating new filesystem in small unallocated partition M +1-0src/gui/sizedialogbase.cpp http://commits.kde.org/partitionmanager/65d80dd405ad40fc029a05080baaf1bda4d74611 -- You are receiving this mail because: You are watching all bug changes.