Bug#794453: systemd: System freezee when systemd starts
Agree that the language was bad :( You filed this bug against version 215-17, yet you talk about 220-7. > Please clarify. > I have been unable to boot the machine with any version of systemd since 220-7 and which have been released to testing. The machine freezes as soon as systemd is started. I am able to reinstall systemd 215-17, which works just fine, which is the only version, where I can file a bug. Second, your subject says "system freeze when systemd starts", yet the > bug report talks about an install problem regarding udev. > Please clarify. > I am able to install newer version of systemd (and the five packages systemd depend on incl udev). For systemd 222-2 udev can not be installed as already reported.
Bug#757207: systemd: Installation of systemd makes system unbootable
As requested content of /etc/fstab === # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # /dev/mapper/ares-root / ext4errors=remount-ro 0 1 # /boot was on /dev/sda1 during installation UUID=CS0IM3-x23c-6Iyg-vtLc-NPWI-FuS2-cSFvr8 /boot ext2 defaults0 2 /dev/mapper/ares-swap_1 noneswapsw 0 0 /dev/sr0/media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/sdb1 /media/usb0 autorw,user,noauto 0 0 content of /etc/crypttab = sda5_crypt UUID=08cb6482-b013-44a8-8158-3bb41812a7f4 none luks Output ofls -la /dev/disk/by-uuid/ == lrwxrwxrwx 1 root root 10 Aug 7 07:30 08cb6482-b013-44a8-8158-3bb41812a7f4 -> ../../sda5 lrwxrwxrwx 1 root root 10 Aug 7 07:30 39eb5a09-2859-4891-a22f-ff844891f5cf -> ../../dm-1 lrwxrwxrwx 1 root root 10 Aug 7 07:30 da9bc68a-a904-40aa-b8cc-26df3faf5c6d -> ../../dm-2 Regards Jens
Bug#757207: systemd: Installation of systemd makes system unbootable
Package: systemd Severity: critical Justification: breaks the whole system The bug is properly related to #754059, but unlike Filippo, I was stupid enough to update to systemd, which resulted in the removal of sysvinit-core and resulted in an unbotable system. Using emergency mode (which is also a problem due to #755581), I was able to re-add sysvinit-core, which subsequently removed network-manager:i386 (0.9.10.0-1), kde-plasma-desktop:i386 (84), hplip:i386 (3.14.6-1), plasma-nm:i386 (0.9.3.3-4), printer-driver-postscript-hp:i386 (3.14.6-1), systemd-sysv:i386 (208-6), kde-standard:i386 (84), polkit-kde-1:i386 (0.99.1-1), packagekit:i386 (0.8.17-4), appstream-index:i386 (0.7.0-2), task-kde-desktop:i386 (3.20), policykit-1-gnome:i386 (0.105-2), listaller:i386 (0.5.8-2), plasma-widget-networkmanagement:i386 (0.9.3.3-4), gvfs:i386 (1.20.2-1), colord:i386 (1.2.1-1), libpam-systemd:i386 (208-6), udisks2:i386 (2.1.3-2), packagekit-tools:i386 (0.8.17-4), gvfs-daemons:i386 (1.20.2-1), policykit-1:i386 (0.105-6.1), apper:i386 (0.8.2-3) Have looked at the different bug reports, but have not found anyway to restablish my system. What systemd packages should be added, it order for my system to work properly again? And do I need to modify anything else? Looked at the systemd wiki entry, but that seems a bit outdated with respect to the discussion taking place on the debian-devel mailing-list. Adding systemd, systemd-shim and cgmanager did not help. Trying to add several of the packages in the above list .e.f. network-manager requires systemd and will remove sysvinit-core and make my system unbootable again. Since I am using a LVM2 encripted disk, this report may also be related to #678438 and/or #692120. Relevant version numbers for the systemd packages are systemd 208-6 systemd-shim 6-4 cgmanager 0.28.3 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.14-1-686-pae (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-1 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53.2 ii libacl1 2.2.52-1 ii libaudit11:2.3.7-1 ii libblkid12.20.1-5.8 ii libc62.19-7 ii libcap2 1:2.24-3 ii libcap2-bin 1:2.24-3 ii libcryptsetup4 2:1.6.4-4 ii libdbus-1-3 1.8.6-1 ii libgcrypt11 1.5.3-5 ii libkmod2 18-1 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.8-3 ii libselinux1 2.3-1 ii libsystemd-daemon0 208-6 ii libsystemd-journal0 208-6 ii libsystemd-login0208-6 ii libudev1 208-6 ii libwrap0 7.6.q-25 ii sysv-rc 2.88dsf-53.2 ii udev 208-6 ii util-linux 2.20.1-5.8 Versions of packages systemd recommends: pn libpam-systemd Versions of packages systemd suggests: pn systemd-ui -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#311776: Please, close this bug
Please close this bug. Although apache failed to upgrade my configuration from 1.3.26.1+1.48-0woody3 to 1.3.26-6 (stable Woody to Sarge), with my very simple configuration, a port of my configuration to the new config file removed the unknown problem. Regards, Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#291203: Debian configuration of postfix fails
An error slipped into my previous mail, what I meant to say was that: I do NOT see the comment regard an extra blank line in a parameter, but DebConf stops at the same place. Regards, Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#291203: Debian configuration of postfix fails
Package: postfix Version: 2.1.5-9 Followup-For: Bug #291203 Debian just plain refuse to install on my testing distribution. Maybee due to unknown dependicy on a package. A few days ago, I upgraded another host with a minimal stable woody to current testing (almost Sarge) and afterwards installed Postfix without any problem. Is there anyway I can debug the reason that Debconf stops as mentioned in the original #291203 report. I do see the comment regard an extra blank line in a parameter, but DebConf stops at the same place. Regards, Jens -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (600, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.11.6 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages postfix depends on: ii adduser 3.63 Add and remove users and groups ii debconf [debconf-2.0] 1.4.30.13Debian configuration management sy ii dpkg1.10.28 Package maintenance system for Deb ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libdb4.24.2.52-18Berkeley v4.2 Database Libraries [ ii libgdbm31.8.3-2 GNU dbm database routines (runtime ii netbase 4.21 Basic TCP/IP networking system -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#311776: apache-ssl: Basic Authentication does not work
On Fri, 3 Jun 2005, Thom May wrote: > Severity 311776 normal > kthxbye > > Hi, > it's likely that you have an erroneous config, rather than this being a bug > in apache. If basic auth was broken, I assure you that we'd have noticed by > now. Well from my experience with Debian. I tend to agree, > The problem you're reporting is often a symptom of having multiple auth > providers loaded; have a look at /etc/apache-ssl/modules.conf or attach it > here and check you don't have mod_auth_sys or mod_auth_system installed. > Cheers, > -Thom > I have upgraded a stable Woody to Sarge keeping my original config file (that might be my problem). In that config file only mod_auth_ssl is enabled - modules.conf is never loaded. I will port my 1.3.26 configuration to the new 1.3.36-6 config file and see what happens. Regard Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#311776: apache-ssl: Basic Authentication does not work
Package: apache-ssl Version: 1.3.33-6 Severity: grave Justification: renders package unusable Basic authentication does not work. Users are not recognized, and in the logfile it states "user not found" <-- notice the extra space between "user" and "not", indicating that apache-ssl seem to think the user is identified by an empty string. This bug seem not related related to to bug #266218 or #288424, but is considered critical considering this version is going to be the default package in Sarge -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.18-bf2.4 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages apache-ssl depends on: ii apache-common 1.3.33-6 support files for all Apache webse ii debconf 1.4.30.13Debian configuration management sy ii dpkg1.10.27 Package maintenance system for Deb ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libdb4.24.2.52-18Berkeley v4.2 Database Libraries [ ii libexpat1 1.95.8-3 XML parsing C library - runtime li ii libmagic1 4.12-1 File type determination library us ii libssl0.9.7 0.9.7e-3 SSL shared libraries ii logrotate 3.7-5Log rotation utility ii mime-support3.28-1 MIME files 'mime.types' & 'mailcap ii openssl 0.9.7e-3 Secure Socket Layer (SSL) binary a ii perl5.8.4-8 Larry Wall's Practical Extraction ii ssl-cert1.0-11 Simple debconf wrapper for openssl -- debconf information: apache-ssl/server-admin: [EMAIL PROTECTED] * apache-ssl/enable-suexec: false apache-ssl/init: true apache-ssl/server-name: novo.ddre.dk apache-ssl/document-root: /home/webs/novo/htdocs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
