[Bug 1523326] [NEW] K3B (growisofs) too many directories
Public bug reported: hello . . . I have successfully used K3B for many years doing monthly FULL backups to DVDs and then BDs except for this month. I tried to backup my system K3B 2.0.2 and received a few error messages primarily being told that K3B could not calculate the file size. I downloaded Kubuntu 15.10 with K3B 2.0.3 and using a USB stick began K3B. Same error message. I isolated the problem (maybe). growisofs generates an error telling me that my burn has "too many directories". The number 65535 (?) follows the message. This is the base error for all my other error messages. K3B cannot calculate the file size because not all the directories are calculated (?). I removed /usr (biggest number of directories) and the burn was successful. I used a DVD-DL to burn /usr and again successful. It looks like I have maxed out the limit on directories. Never thought that would happen. K3b Version 2.0.2 / 2.0.3 Using KDE Development Platform 4.14.13 and Kubuntu 15.10 downloaded 6Dec15. Hope this helps. ** Affects: k3b (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to k3b in Ubuntu. https://bugs.launchpad.net/bugs/1523326 Title: K3B (growisofs) too many directories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/k3b/+bug/1523326/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1510731] Re: Can't use crypto in manual disk setup Kubuntu 15.10
Have you tried with Ubuntu rather than Kubuntu? If not, you might want to try with Ubuntu, just to rule out whether this is a Kubuntu specific issue. Using the “something else” option presented during installation of Ubuntu 15.10 and Ubuntu 16.04 (onto a non-UEFI system with a gpt formatted drive), I have been able to create a LUKS-encrypted volume on sda2, and I have been able to install boot (/boot) into non-encrypted sda1, and root (/) into LUKS-encrypted sda2. I have noticed, however, that, after creating the LUKS-encrypted volume on sda2 (using the create the next partition as "physical volume for encryption" that you mention), I sometimes have to wait a bit (sometimes a minute or more) before "sda2_crypt" (or something like that, I don't recall the exact label) is created, into which I can install root. Maybe your installation hangs t this point? Although the above works for me, I have NOT been able to install boot (/boot) into non-encrypted sda1, root (/) into LUKS-encrypted sda2, and home (/home) into into LUKS-encrypted sda3. Rather, although I am able to create all of the LUKS-encrypted volumes, the installer hangs during installation when the following is displayed: “Creating ext4 system for /home in partition #1 of Encrypted volume (sda3_crypt)...” See https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1523194 for the issue that I'm describing. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to ubiquity in Ubuntu. https://bugs.launchpad.net/bugs/1510731 Title: Can't use crypto in manual disk setup Kubuntu 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1510731/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 56369]
*** Bug 353607 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdepim in Ubuntu. https://bugs.launchpad.net/bugs/56369 Title: akregator is not crash proof To manage notifications about this bug go to: https://bugs.launchpad.net/kdepim/+bug/56369/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1523364] Re: Workarounding screen edge test breaks xrandr test
** Description changed: Workarounding bug #1522466 in a test (a problem with screen edges without XRandr) unfortunately breaks another test that was passing without the workaround: --- 17/18 Test #17: kwin-testXRandRScreens ...***Exception: Other 1.23 sec * Start testing of TestXRandRScreens * Config: Using QtTest library 5.5.1, Qt 5.5.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.2.1 20151129) QFATAL : TestXRandRScreens::initTestCase() Received signal 11 FAIL! : TestXRandRScreens::initTestCase() Received a fatal error. Loc: [Unknown file(0)] Totals: 0 passed, 1 failed, 0 skipped, 0 blacklisted * Finished testing of TestXRandRScreens * --- - This should be fixed. One option is to wait for the real upstream fix - for bug #1522466 and remove the workaround at that point. The workaround - itself is harmless since only test setup is changed. + This should be fixed. One option is to wait for the real Qt upstream fix + for the bug #1522466 (screen edges without xrandr) and remove the + workaround at that point. The workaround itself is harmless since only + test setup is changed. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwin in Ubuntu. https://bugs.launchpad.net/bugs/1523364 Title: Workarounding screen edge test breaks xrandr test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1523364/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1523364] [NEW] Workarounding screen edge test breaks xrandr test
Public bug reported: Workarounding bug #1522466 in a test (a problem with screen edges without XRandr) unfortunately breaks another test that was passing without the workaround: --- 17/18 Test #17: kwin-testXRandRScreens ...***Exception: Other 1.23 sec * Start testing of TestXRandRScreens * Config: Using QtTest library 5.5.1, Qt 5.5.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.2.1 20151129) QFATAL : TestXRandRScreens::initTestCase() Received signal 11 FAIL! : TestXRandRScreens::initTestCase() Received a fatal error. Loc: [Unknown file(0)] Totals: 0 passed, 1 failed, 0 skipped, 0 blacklisted * Finished testing of TestXRandRScreens * --- This should be fixed. One option is to wait for the real Qt upstream fix for the bug #1522466 (screen edges without xrandr) and remove the workaround at that point. The workaround itself is harmless since only test setup is changed. ** Affects: kwin (Ubuntu) Importance: Undecided Status: New ** Tags: qt5.5 ** Description changed: - Workarounding bug #1522466 (a problem with screen edges without XRandr) - unfortunately breaks another test that was passing without the - workaround: + Workarounding bug #1522466 in a test (a problem with screen edges + without XRandr) unfortunately breaks another test that was passing + without the workaround: --- 17/18 Test #17: kwin-testXRandRScreens ...***Exception: Other 1.23 sec * Start testing of TestXRandRScreens * Config: Using QtTest library 5.5.1, Qt 5.5.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.2.1 20151129) QFATAL : TestXRandRScreens::initTestCase() Received signal 11 FAIL! : TestXRandRScreens::initTestCase() Received a fatal error. -Loc: [Unknown file(0)] + Loc: [Unknown file(0)] Totals: 0 passed, 1 failed, 0 skipped, 0 blacklisted * Finished testing of TestXRandRScreens * --- This should be fixed. One option is to wait for the real upstream fix for bug #1522466 and remove the workaround at that point. ** Description changed: Workarounding bug #1522466 in a test (a problem with screen edges without XRandr) unfortunately breaks another test that was passing without the workaround: --- 17/18 Test #17: kwin-testXRandRScreens ...***Exception: Other 1.23 sec * Start testing of TestXRandRScreens * Config: Using QtTest library 5.5.1, Qt 5.5.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.2.1 20151129) QFATAL : TestXRandRScreens::initTestCase() Received signal 11 FAIL! : TestXRandRScreens::initTestCase() Received a fatal error. Loc: [Unknown file(0)] Totals: 0 passed, 1 failed, 0 skipped, 0 blacklisted * Finished testing of TestXRandRScreens * --- This should be fixed. One option is to wait for the real upstream fix - for bug #1522466 and remove the workaround at that point. + for bug #1522466 and remove the workaround at that point. The workaround + itself is harmless since only test setup is changed. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwin in Ubuntu. https://bugs.launchpad.net/bugs/1523364 Title: Workarounding screen edge test breaks xrandr test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1523364/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1258422] Re: Maximized windows go under panel if panel attached to screen edge between two monitors
Thank you for this "tint2" workaround. Now I can do my work. As a bonus, I used the clock provided by it, because in Plasma 5 the time format can't be customized anymore. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1258422 Title: Maximized windows go under panel if panel attached to screen edge between two monitors To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1258422/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
