KDE 5.8 Ordneransicht
Hallo, ich habe gerade wieder mal das aktuelle Testing installiert mit KDE 5.8. Dabei habe ich ein Problem: Wenn ich die Oberfläche auf Ordneransicht stelle bzw. wenn ich ein anderes Hintergrundbild wähle, wird das nach Abmelden bzw. Neustart auf die Originaleinstellungen zurückgesetzt. Andere Änderungen merkt er sich aber. Ich habe schon alles mögliche getestet, jedoch ohne Erfolg (plasma* gelöscht in .config/kde4, neues Profil, neuer Nutzer, Profil von einer anderen Installation - KDE 4.x übernommen). Zum Hintergrund: Ich nutze debian schon sein über 5 Jahren auf den verschiedensten Rechnern und mit KDE 4 klappt auch alles. Gruß Holger -- Holger Bachmann - computer & umwelt Fechnerstr. 19 - 10717 Berlin Telefon +49 30 789 589 67 Fax +49 30 789 586 57 email h...@bacu.de web www.bacu.de
Bug#841062: installation-reports
Package: installation-reports Boot method: ISO image Image version: http://cdimage.debian.org/mirror/cdimage/daily-builds/daily/current/ppc64el/iso-cd/debian-testing-ppc64el-netinst.iso Date: Mon Oct 17 00:44:56 2016 Machine: qemu VM / P8 baremetal / powerVM Processor: ppc64el Memory: 4Gb Partitions: /dev/sda1 JFS (more than 10Gb) /dev/sda3 swap Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[E] Overall install:[E] Comments/Problems: When partitionning the disk, I chose the guided partitionning to use the entire disk and one partition, then I changed the file system of the main partition to JFS instead of ext4. Everything went right until the grub installation. It failed with: Install the GRUB boot loader on a hard disk --- !! ERROR: Unable to install GRUB in /dev/sda1 Executing 'grub-install /dev/sda1' failed. This is a fatal error. from /var/log/syslog: Oct 17 00:51:19 grub-installer: info: Installing grub on '/dev/sda1' Oct 17 00:51:19 grub-installer: info: grub-install does not support --no-floppy Oct 17 00:51:19 grub-installer: info: Running chroot /target grub-install --force "/dev/sda1" Oct 17 00:51:19 grub-installer: Installing for powerpc-ieee1275 platform. Oct 17 00:51:20 grub-installer: grub-install: error: Oct 17 00:51:20 grub-installer: unknown filesystem. Oct 17 00:51:20 grub-installer: error: Running 'grub-install --force "/dev/sda1"' failed. Oct 17 01:09:20 main-menu[974]: (process:5214): File descriptor 3 (pipe:[9531]) leaked on lvdisplay invocation. Parent PID 5736: /bin/sh Oct 17 01:09:20 main-menu[974]: (process:5214): File descriptor 4 (/dev/pts/4) leaked on lvdisplay invocation. Parent PID 5736: /bin/sh Oct 17 01:09:20 main-menu[974]: (process:5214): File descriptor 5 (/dev/pts/4) leaked on lvdisplay invocation. Parent PID 5736: /bin/sh Oct 17 01:09:20 main-menu[974]: (process:5214): File descriptor 6 (/dev/pts/4) leaked on lvdisplay invocation. Parent PID 5736: /bin/sh Oct 17 01:09:20 main-menu[974]: (process:5214): Volume group "sda" not found Oct 17 01:09:20 main-menu[974]: (process:5214): Cannot process volume group sda Oct 17 01:09:20 main-menu[974]: WARNING **: Configuring 'grub-installer' failed with error code 1 Oct 17 01:09:20 main-menu[974]: WARNING **: Menu item 'grub-installer' failed.
Bug#841072: installation-report: failure to mount the EFI partition: IO charset ascii not found
Package: installation-reports Version: 2.62 Severity: important -- Package-specific info: Boot method: USB key Image version: http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso build of 2016-10-03 Date: 2016-10-17 Machine: Lenovo Thinkpad X260 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [X] Detect network card:[X] Configure network: [X] Detect CD: [X] Load installer modules: [X] Clock/timezone setup: [X] User/password setup:[X] Detect hard drives: [X] Partition hard drives: [E] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: I have booted the installer in UEFI mode and in the partitioning step, the installer fails to mount the EFI partition that it created: Oct 17 19:27:31 kernel: [ 325.233318] FAT-fs (sda1): IO charset ascii not found Oct 17 19:27:46 main-menu[406]: (process:6083): mount: mounting /dev/sda1 on /target/boot/efi failed: Invalid argument Oct 17 19:27:46 main-menu[406]: WARNING **: Configuring 'partman-base' failed with error code 2 Oct 17 19:27:46 main-menu[406]: WARNING **: Menu item 'partman-base' failed. In fact, I'm not even sure that it did format the partition that it created. I don't see anything like this in the syslog file. And looking in the partman log file it rather seems like that the EFI partition is created as ext2! I'm attaching the full log files of the installation attempt. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ install-x260.tar.gz Description: application/gzip
Bug#840400: Issue seems in nls_ascii module not available
Hi Thomas, Thomas Wuensche (2016-10-15): > I also had that problem and could work around by loading nls_ascii.ko > module manually. It turned out that the vfat mount to access the EFI > partition failed due to lack of ASCII IO charset. > > So I guess the reason for the bug is the lack of a loaded nls_ascii > module at the time when the partition should be prepared and mounted > during the install. That's tracked in #839552. KiBi. signature.asc Description: Digital signature
Bug#841072: installation-report: failure to mount the EFI partition: IO charset ascii not found
Raphael Hertzog (2016-10-17): > Package: installation-reports > Version: 2.62 > Severity: important > > -- Package-specific info: > > Boot method: USB key > Image version: > http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso > build of 2016-10-03 > Date: 2016-10-17 > > Machine: Lenovo Thinkpad X260 > > Base System Installation Checklist: > [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it > > Initial boot: [X] > Detect network card:[X] > Configure network: [X] > Detect CD: [X] > Load installer modules: [X] > Clock/timezone setup: [X] > User/password setup:[X] > Detect hard drives: [X] > Partition hard drives: [E] > Install base system:[ ] > Install tasks: [ ] > Install boot loader:[ ] > Overall install:[ ] > > Comments/Problems: > > I have booted the installer in UEFI mode and in the partitioning step, the > installer fails to mount the EFI partition that it created: > Oct 17 19:27:31 kernel: [ 325.233318] FAT-fs (sda1): IO charset ascii not > found > Oct 17 19:27:46 main-menu[406]: (process:6083): mount: mounting /dev/sda1 on > /target/boot/efi failed: Invalid argument > Oct 17 19:27:46 main-menu[406]: WARNING **: Configuring 'partman-base' failed > with error code 2 > Oct 17 19:27:46 main-menu[406]: WARNING **: Menu item 'partman-base' failed. #839552 KiBi. signature.asc Description: Digital signature
Re: Bug#840400: Issue seems in nls_ascii module not available
On Mon, Oct 17, 2016 at 02:33:34PM +0200, Cyril Brulebois wrote: > Thomas Wuensche (2016-10-15): > > I also had that problem and could work around by loading nls_ascii.ko > > module manually. It turned out that the vfat mount to access the EFI > > partition failed due to lack of ASCII IO charset. > That's tracked in #839552. I'm slightly surprised you didn't merge #839552, #840400 and #841072 then… (*) but I'd like to suggest forcemerge 839552 840400 841072 -- cheers, Holger (*) but I'm refraining from doing so myself for historic reasons. signature.asc Description: Digital signature
Bug#841072: installation-report: failure to mount the EFI partition: IO charset ascii not found
Raphael Hertzog (2016-10-17): > Package: installation-reports > Version: 2.62 > Severity: important > > -- Package-specific info: > > Boot method: USB key > Image version: > http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso > build of 2016-10-03 > Date: 2016-10-17 http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/ has builds dated from today, which should work since the linux bug has been fixed, and builds now work again (pettersson had issues past week). Please close this bug report if you confirm the fix. KiBi. signature.asc Description: Digital signature
Bug#840523: debian-installer: undefined source format; .git/ may end up in source tarball
Steven Chamberlain (2016-10-12): > Suppose a debian-installer source package is produced this way: > > $ debcheckout debian-installer > $ cd debian-installer > $ debuild -S > [...] > dpkg-source: warning: no source format specified in debian/source/format, see > dpkg-source(1) > dpkg-source: warning: source directory 'debian-installer' is not > - 'debian-installer-20160704' > dpkg-source: info: using source format '1.0' > dpkg-source: info: building debian-installer in > debian-installer_20160704.tar.gz > dpkg-source: info: building debian-installer in debian-installer_20160704.dsc > > In source format 1.0, dpkg-source does *not* exclude the .git/ directory > from the generated tarball! So if you built the source package that way, > your Git working tree's refs and config are all included in the upload, > which happened with my uploads here: > http://ftp.debian.org/debian/pool/main/d/debian-installer/debian-installer_20150422+kbsd8u2.tar.gz > http://ftp.debian.org/debian/pool/main/d/debian-installer/debian-installer_20150422+kbsd8u2+deb8u4.tar.gz debcheckout's output lets you know you're getting a git repository. I'm not sure running debuild -S without -i/-I makes this an important bug in debian-installer… > Note that source format 1.0 is only used because one is not specified in > debian/source/format. dpkg-source(1) recommends to specify a version and > the lack of a debian/source/format file may be considered an error in > future. I don't like the idea of unneeded boilerplate in source packages just because dpkg developers want to force v3 onto people so badly. > dpkg-source(1) also recommends choosing a newer format. 3.0 (native) > by default already excludes VCS directories such as .git/ from the > generated tarball, already fixing the issue above. > > 3.0 (native) does however default to .tar.xz compression, rather than > .tar.gz as used at the moment. I'm not sure if that may be an issue for > other tools. Maybe they should be fixed in that case. Or _if_ it's > preferred to still use .tar.gz, that could be specified in > debian/source/options: > compression = "gzip" scripts/debian/byhand-di doesn't seem to look at something which isn't the images tarball; I'm not sure whether something else might needed being looked at. > Attached is my proposed patch, for consideration. In case someone wants to merge this, I would like to see this very carefully reviewed for possible side effects. Getting an error during the next release, or worse a regression only seen afterwards, would really be annoying. KiBi. signature.asc Description: Digital signature
Bug#841062: installation-reports
On Mon, Oct 17, 2016 at 11:49:05AM +0200, Erwan Prioul wrote: > Package: installation-reports > > Boot method: ISO image > Image version: > http://cdimage.debian.org/mirror/cdimage/daily-builds/daily/current/ppc64el/iso-cd/debian-testing-ppc64el-netinst.iso > Date: Mon Oct 17 00:44:56 2016 > > Machine: qemu VM / P8 baremetal / powerVM > Processor: ppc64el > Memory: 4Gb > Partitions: > /dev/sda1 JFS (more than 10Gb) > /dev/sda3 swap > > Initial boot: [O] > Detect network card:[O] > Configure network: [O] > Detect CD: [O] > Load installer modules: [O] > Detect hard drives: [O] > Partition hard drives: [O] > Install base system:[O] > Clock/timezone setup: [O] > User/password setup:[O] > Install tasks: [O] > Install boot loader:[E] > Overall install:[E] > > Comments/Problems: > > When partitionning the disk, I chose the guided partitionning to use the > entire disk and one partition, then I changed the file system of the main > partition to JFS instead of ext4. > Everything went right until the grub installation. > It failed with: > > Install the GRUB boot loader on a hard disk > --- > > !! ERROR: Unable to install GRUB in /dev/sda1 > > Executing 'grub-install /dev/sda1' failed. > > This is a fatal error. > > from /var/log/syslog: > Oct 17 00:51:19 grub-installer: info: Installing grub on '/dev/sda1' > Oct 17 00:51:19 grub-installer: info: grub-install does not support > --no-floppy > Oct 17 00:51:19 grub-installer: info: Running chroot /target grub-install > --force "/dev/sda1" > Oct 17 00:51:19 grub-installer: Installing for powerpc-ieee1275 platform. > Oct 17 00:51:20 grub-installer: grub-install: error: > Oct 17 00:51:20 grub-installer: unknown filesystem. > Oct 17 00:51:20 grub-installer: error: Running 'grub-install --force > "/dev/sda1"' failed. > Oct 17 01:09:20 main-menu[974]: (process:5214): File descriptor 3 > (pipe:[9531]) leaked on lvdisplay invocation. Parent PID 5736: /bin/sh > Oct 17 01:09:20 main-menu[974]: (process:5214): File descriptor 4 > (/dev/pts/4) leaked on lvdisplay invocation. Parent PID 5736: /bin/sh > Oct 17 01:09:20 main-menu[974]: (process:5214): File descriptor 5 > (/dev/pts/4) leaked on lvdisplay invocation. Parent PID 5736: /bin/sh > Oct 17 01:09:20 main-menu[974]: (process:5214): File descriptor 6 > (/dev/pts/4) leaked on lvdisplay invocation. Parent PID 5736: /bin/sh > Oct 17 01:09:20 main-menu[974]: (process:5214): Volume group "sda" not found > Oct 17 01:09:20 main-menu[974]: (process:5214): Cannot process volume group > sda > Oct 17 01:09:20 main-menu[974]: WARNING **: Configuring 'grub-installer' > failed with error code 1 > Oct 17 01:09:20 main-menu[974]: WARNING **: Menu item 'grub-installer' failed. I just tried it and it worked fine. I picked the default guided partitioning, then changed the root partition (partition 2) from ext4 to JFS. I did NOT delete and create any partitions from the default guided setup. I think, based on your error, that you deleted partition 1 (8MB the PReP boot partition) which is required for installing the boot loader in IBM power systems. Or maybe you change the use type to JFS from PReP boot. Partition 1 (PReP boot) does NOT contain a filesystem and is not mounted. Grub is written to it raw and the firmware loads the contents of the partition into ram and executes it raw. -- Len Sorensen
Bug#841072: marked as done (installation-report: failure to mount the EFI partition: IO charset ascii not found)
Your message dated Mon, 17 Oct 2016 18:43:33 +0200 with message-id <20161017164333.lbpnbt3hys4xw...@home.ouaza.com> and subject line Re: Bug#841072: installation-report: failure to mount the EFI partition: IO charset ascii not found has caused the Debian Bug report #841072, regarding installation-report: failure to mount the EFI partition: IO charset ascii not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 841072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841072 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Version: 2.62 Severity: important -- Package-specific info: Boot method: USB key Image version: http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso build of 2016-10-03 Date: 2016-10-17 Machine: Lenovo Thinkpad X260 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [X] Detect network card:[X] Configure network: [X] Detect CD: [X] Load installer modules: [X] Clock/timezone setup: [X] User/password setup:[X] Detect hard drives: [X] Partition hard drives: [E] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: I have booted the installer in UEFI mode and in the partitioning step, the installer fails to mount the EFI partition that it created: Oct 17 19:27:31 kernel: [ 325.233318] FAT-fs (sda1): IO charset ascii not found Oct 17 19:27:46 main-menu[406]: (process:6083): mount: mounting /dev/sda1 on /target/boot/efi failed: Invalid argument Oct 17 19:27:46 main-menu[406]: WARNING **: Configuring 'partman-base' failed with error code 2 Oct 17 19:27:46 main-menu[406]: WARNING **: Menu item 'partman-base' failed. In fact, I'm not even sure that it did format the partition that it created. I don't see anything like this in the syslog file. And looking in the partman log file it rather seems like that the EFI partition is created as ext2! I'm attaching the full log files of the installation attempt. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ install-x260.tar.gz Description: application/gzip --- End Message --- --- Begin Message --- On Mon, 17 Oct 2016, Cyril Brulebois wrote: > http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/ has builds > dated from today, which should work since the linux bug has been fixed, > and builds now work again (pettersson had issues past week). > > Please close this bug report if you confirm the fix. Confirmed. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/--- End Message ---
Bug#841135: iso-scan/filename ignored in Debian 8.6.0 => cannot put it on multiboot USB stick
Package: iso-scan Version: 1.53 Hi, I'm trying to set up a multiboot USB stick (containing bootable Debian, Ubuntu, Redhat, etc. distributions on one media) For this, I am following the instructions at https://wiki.archlinux.org/index.php/Multiboot_USB_drive#Debian However, despite all attempts to the contrary, iso-scan seems to steadfastly ignore the iso-scan/filename parameter: it neither takes it at face value (as the sole qualifying filename for an ISO), nor does it prompt the user if multiple ISOs are on the stick. With the result that it tries to install from an Ubuntu ISO that also happens to be on the stick, and (predictably) fails. However, modifying the /var/lib/dpkg/info/iso-scan.postinst script as follows fixes the issue: Before the "for dir in . ./*; do" loop, insert: db_get iso-scan/filename if [ -f "./$RET" ] ; then iso=`echo "$RET" | sed 's;^/;;'` log "Found ISO $iso on $dev" ISO_COUNT=$(($ISO_COUNT + 1)) add_usable_iso $iso $dev else ... and after it, insert: fi I'm also wondering why in Debian we have to download a special hd-media initrd.gz from https://mirrors.kernel.org/debian/dists/stable/main/installer-amd64/current/images/hd-media/ at all, rather than having the standard initrd.gz included in the ISO itself be able to also boot from an USB stick (as is the case in Ubuntu, and in many other distros) Thanks for your attention, Alain
