Bug#1053089: Source of issue identified
A user on the VSIDO forum identified the problem as that lxdm 5.3-5 only supports the Industrial theme. Changing to Industrial them brings back the login but using any other theme causes failure to show a gretter login menu -- Thank you, VastOne V-Ger VSIDO Developer
Bug#1053089: Login procedure
After the blank screen at the lxdm login, doing a ctrl alt f1 to tty1 I login and immediately startx initiates and takes me to my desktop. This is just information being passed along -- Thank you, VastOne V-Ger VSIDO Developer
Bug#1053089: Had to switch
The VSIDO distro had to switch to lightdm because lxdm is no longer usable, a decision that was not well received. I have done everything I can to identify the error, attached is the latest lxdm.log. I am not sure whatever else there is I can provide to help someone reproduce this error. -- Thank you, VastOne V-Ger VSIDO Developer ** Message: 17:28:45.792: find greeter (nil) ** Message: 17:28:45.792: find idle (nil) ** Message: 17:28:45.794: 1696458525: add xserver watch X.Org X Server 1.21.1.8 X Protocol Version 11, Revision 0 Current Operating System: Linux vsido 6.5.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.5.3-1 (2023-09-13) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1-amd64 root=UUID=cc813a83-98c7-41d6-ace2-81be9a32aec4 ro net.ifnames=0 quiet nvme_core.default_ps_max_latency_us=1000 xorg-server 2:21.1.8-1 (https://www.debian.org/support) Current version of pixman: 0.42.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 4 17:28:45 2023 (==) Using config file: "/etc/X11/xorg.conf" (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" ** Message: 17:28:46.909: 1696458526: start xserver in 1 retry ** Message: 17:28:46.909: add 0x55b3c1493610 ** Message: 17:28:46.909: prepare greeter on /var/run/lxdm/lxdm-:0.auth ** Message: 17:28:46.910: start greeter on /var/run/lxdm/lxdm-:0.auth (lxdm-greeter-gtk:1352): dbind-WARNING **: 17:28:46.975: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files (lxdm-greeter-gtk:1352): Gtk-WARNING **: 17:28:46.983: Theme parsing error: gtk.css:138:54: Using one color stop with linear-gradient() is deprecated. (lxdm-greeter-gtk:1352): Gtk-WARNING **: 17:28:46.983: Theme parsing error: gtk.css:169:56: Using one color stop with linear-gradient() is deprecated. (lxdm-greeter-gtk:1352): Gtk-WARNING **: 17:28:46.983: Theme parsing error: gtk.css:179:56: Using one color stop with linear-gradient() is deprecated. (lxdm-greeter-gtk:1352): Gtk-WARNING **: 17:28:46.984: Theme parsing error: gtk.css:188:56: Using one color stop with linear-gradient() is deprecated. (lxdm-greeter-gtk:1352): Gtk-WARNING **: 17:28:46.984: Theme parsing error: gtk.css:195:56: Using one color stop with linear-gradient() is deprecated. (lxdm-greeter-gtk:1352): Gtk-WARNING **: 17:28:46.984: Theme parsing error: gtk.css:202:56: Using one color stop with linear-gradient() is deprecated. (lxdm-greeter-gtk:1352): Gtk-WARNING **: 17:28:46.984: Theme parsing error: gtk.css:210:71: Using one color stop with linear-gradient() is deprecated. (lxdm-greeter-gtk:1352): Gtk-WARNING **: 17:28:46.984: Theme parsing error: gtk.css:219:73: Using one color stop with linear-gradient() is deprecated. (lxdm-greeter-gtk:1352): Gtk-WARNING **: 17:28:46.984: Theme parsing error: gtk.css:228:72: Using one color stop with linear-gradient() is deprecated. (lxdm-greeter-gtk:1352): Gtk-WARNING **: 17:28:46.985: Theme parsing error: gtk.css:440:56: Using one color stop with linear-gradient() is deprecated. (lxdm-greeter-gtk:1352): Gtk-WARNING **: 17:28:46.985: Theme parsing error: gtk.css:510:72: Using one color stop with linear-gradient() is deprecated. (lxdm-greeter-gtk:1352): Gtk-WARNING **: 17:28:46.985: Theme parsing error: gtk.css:548:72: Using one color stop with linear-gradient() is deprecated. (lxdm-greeter-gtk:1352): Gtk-WARNING **: 17:28:46.985: Theme parsing error: gtk.css:619:74: Using one color stop with linear-gradient() is deprecated. (lxdm-greeter-gtk:1352): Gtk-WARNING **: 17:28:46.985: Theme parsing error: gtk.css:625:76: Using one color stop with linear-gradient() is deprecated. (lxdm-greeter-gtk:1352): Gtk-WARNING **: 17:28:46.985: Theme parsing error: gtk.css:651:73: Using one color stop with linear-gradient() is deprecated. (lxdm-greeter-gtk:1352): Gtk-WARNING **: 17:28:46.985: Theme parsing error: gtk.css:657:75: Using one color stop with linear-gradient() is deprecated. (lxdm-greeter-gtk:1352): Gtk-WARNING **: 17:28:46.985: Theme parsing error: gtk.css:724:56: Using one color stop with linear-gradient() is deprecated. (lxdm-greeter-gtk:1352): Gtk-WARNING **: 17:28:46.987: Theme parsing error: gtk.css:1295:60: Using one color stop with linear-gradient() is deprecated. (lxdm-greeter-gtk:1352): Gtk-WARNING **: 17:28:46.987: Theme parsing error: gtk.css:1307:62: Using one color stop with linear-gradient() is deprecated. (lxdm-greeter-gtk:1352): Gtk-WARNING **: 17:28:46.987: Theme parsing error: gtk.css:1359:62: Using one color stop with linear-gradient() is deprecated. (lxdm-greeter
Bug#1053089: lxdm.conf information
lxdm.conf information [base] ## uncomment and set autologin username to enable autologin # autologin=dgod ## uncomment and set timeout to enable timeout autologin, ## the value should >=5 # timeout=10 ## default session or desktop used when no systemwide config session=/usr/bin/fluxbox ## uncomment and set to set numlock on your keyboard # numlock=0 ## set this if you don't want to put xauth file at ~/.Xauthority # xauth_path=/tmp # not ask password for users who have empty password # skip_password=1 ## greeter used to welcome the user greeter=/usr/lib/lxdm/lxdm-greeter-gtk [server] ## arg used to start xserver, not fully function # arg=/usr/bin/X -background vt1 # uncomment this if you really want xserver listen to tcp # tcp_listen=1 [display] ## gtk theme used by greeter gtk_theme=Vertex-Dark ## background of the greeter #bg=/usr/share/backgrounds/default.png bg=/usr/share/images/desktop-base/vsido_login.png ## if show bottom pane bottom_pane=1 ## if show language select control lang=0 ## if show keyboard layout select control keyboard=0 ## the theme of greeter theme=VSIDO [input] [userlist] ## if disable the user list control at greeter disable=0 ## whitelist user white= ## blacklist user black= -- Thank you, VastOne V-Ger VSIDO Developer
Bug#1053089: lxdm: LXDM boots to a blank black screen with no options
Package: lxdm Version: 0.5.3-5 Severity: critical Justification: breaks the whole system -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages lxdm depends on: ii debconf [debconf-2.0] 1.5.82 ii gtk2-engines 1:2.20.2-5+b1 ii gtk2-engines-pixbuf2.24.33-2 ii iso-codes 4.15.0-1 ii libc6 2.37-10 ii libcairo2 1.18.0-1 ii libgdk-pixbuf-2.0-02.42.10+dfsg-1+b1 ii libglib2.0-0 2.78.0-2 ii libgtk-3-0 3.24.38-5 ii libpam-modules 1.5.2-7 ii libpam-runtime 1.5.2-7 ii libpam0g 1.5.2-7 ii libpango-1.0-0 1.51.0+ds-2 ii libpangocairo-1.0-01.51.0+ds-2 ii librsvg2-common2.54.7+dfsg-2 ii libx11-6 2:1.8.6-1 ii libxcb11.15-1 ii x11-utils 7.7+5 Versions of packages lxdm recommends: pn desktop-base Versions of packages lxdm suggests: pn lxde-common -- Configuration Files: /etc/lxdm/lxdm.conf [Errno 13] Permission denied: '/etc/lxdm/lxdm.conf' -- debconf information: * shared/default-x-display-manager: lxdm
Bug#897181: Duplicate report
897181 is the same issue as the re-opened #893237 <893...@bugs.debian.org> -- Thank you, VastOne V-Ger VSIDO Developer
Bug#897181: spacefm_1.0.6-2_amd64.deb postrm called with unknown argument `abort-upgrade'
Package: spacefm_1.0.6-2_amd64.deb Version: 1.0.6-2 Preparing to unpack .../spacefm_1.0.6-2_amd64.deb ... Unpacking spacefm (1.0.6-2) over (1.0.6-1) ... postrm called with unknown argument `upgrade' dpkg: warning: old spacefm package post-removal script subprocess returned error exit status 1 dpkg: trying script from the new package instead ... postrm called with unknown argument `failed-upgrade' dpkg: error processing archive /var/cache/apt/archives/spacefm_1.0.6-2_amd64.deb (--unpack): new spacefm package post-removal script subprocess returned error exit status 1 postrm called with unknown argument `abort-upgrade' dpkg: error while cleaning up: new spacefm package post-removal script subprocess returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/spacefm_1.0.6-2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) VastOne V-Ger VSIDO Developer
Bug#893629: libgstreamer-gl1.0-0 fails to install in SID
Package: libgstreamer-gl1.0-0 Version: 1.14.0-1 When running: sudo apt-get update & sudo apt-get dist-upgade dpkg: error processing archive /var/cache/apt/archives/ libgstreamer-gl1.0-0_1.14.0-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libgstgl-1.0.so.0', which is also in package libgstreamer-plugins-bad1.0-0:amd64 1:1.12.4-dmo4 Errors were encountered while processing: /var/cache/apt/archives/libgstreamer-gl1.0-0_1.14.0-1_amd64.deb Debian Sid Kernel Linux 4.15.0-1-amd64 #1 SMP Debian 4.15.4-1 -- Thank you, VastOne V-Ger VSIDO Developer
Bug#848615: hexchat not displaying icon
Bug resolved with update today to version 2.12.3-4 Thank you On Sun, Dec 18, 2016 at 6:27 PM, VastOne <vast...@gmail.com> wrote: > The only message from terminal is this: > > (hexchat:10662): WARNING **: (pixmaps.c:104):load_pixmap: runtime check > failed: (pixbuf != NULL) > > On Sun, Dec 18, 2016 at 6:24 PM, VastOne <vast...@gmail.com> wrote: > >> DE/WM is Fluxbox ... Tint2 is the system tray and panel and VSIDO is >> based on Debian SID which is what we run it all on and system is up to date >> as of now (dist-upgrade) >> >> I am the Dev for VSIDO and I appreciate you looking into this >> >> On Sun, Dec 18, 2016 at 6:21 PM, Mattia Rizzolo <mat...@debian.org> >> wrote: >> >>> On Sun, Dec 18, 2016 at 06:13:43PM -0600, VastOne wrote: >>> > Since latest updates the icon is no longer available or visible on any >>> > panels or launch bars including systemtrays. >>> >>> Interesting. >>> >>> Which DE/WM are you using (which system tray and/or panel if >>> meaningful)? >>> In my i3bar, which is the only graphicthing I have around) it's visible. >>> Do I assume correctly you're running a regular unstable? >>> >>> -- >>> regards, >>> Mattia Rizzolo >>> >>> GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. >>> more about me: https://mapreri.org : :' : >>> Launchpad user: https://launchpad.net/~mapreri `. `'` >>> Debian QA page: https://qa.debian.org/developer.php?login=mattia `- >>> >> >> >> >> -- >> Thank you, >> >> VastOne >> V-Ger VSIDO Developer >> >> > > > -- > Thank you, > > VastOne > V-Ger VSIDO Developer > > -- Thank you, VastOne V-Ger VSIDO Developer
Bug#848615: hexchat not displaying icon
The only message from terminal is this: (hexchat:10662): WARNING **: (pixmaps.c:104):load_pixmap: runtime check failed: (pixbuf != NULL) On Sun, Dec 18, 2016 at 6:24 PM, VastOne <vast...@gmail.com> wrote: > DE/WM is Fluxbox ... Tint2 is the system tray and panel and VSIDO is based > on Debian SID which is what we run it all on and system is up to date as of > now (dist-upgrade) > > I am the Dev for VSIDO and I appreciate you looking into this > > On Sun, Dec 18, 2016 at 6:21 PM, Mattia Rizzolo <mat...@debian.org> wrote: > >> On Sun, Dec 18, 2016 at 06:13:43PM -0600, VastOne wrote: >> > Since latest updates the icon is no longer available or visible on any >> > panels or launch bars including systemtrays. >> >> Interesting. >> >> Which DE/WM are you using (which system tray and/or panel if >> meaningful)? >> In my i3bar, which is the only graphicthing I have around) it's visible. >> Do I assume correctly you're running a regular unstable? >> >> -- >> regards, >> Mattia Rizzolo >> >> GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. >> more about me: https://mapreri.org : :' : >> Launchpad user: https://launchpad.net/~mapreri `. `'` >> Debian QA page: https://qa.debian.org/developer.php?login=mattia `- >> > > > > -- > Thank you, > > VastOne > V-Ger VSIDO Developer > > -- Thank you, VastOne V-Ger VSIDO Developer
Bug#848615: hexchat not displaying icon
DE/WM is Fluxbox ... Tint2 is the system tray and panel and VSIDO is based on Debian SID which is what we run it all on and system is up to date as of now (dist-upgrade) I am the Dev for VSIDO and I appreciate you looking into this On Sun, Dec 18, 2016 at 6:21 PM, Mattia Rizzolo <mat...@debian.org> wrote: > On Sun, Dec 18, 2016 at 06:13:43PM -0600, VastOne wrote: > > Since latest updates the icon is no longer available or visible on any > > panels or launch bars including systemtrays. > > Interesting. > > Which DE/WM are you using (which system tray and/or panel if > meaningful)? > In my i3bar, which is the only graphicthing I have around) it's visible. > Do I assume correctly you're running a regular unstable? > > -- > regards, > Mattia Rizzolo > > GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. > more about me: https://mapreri.org : :' : > Launchpad user: https://launchpad.net/~mapreri `. `'` > Debian QA page: https://qa.debian.org/developer.php?login=mattia `- > -- Thank you, VastOne V-Ger VSIDO Developer
Bug#848615: hexchat not displaying icon
Package: Hexchat Version: 2.12.3-3 Since latest updates the icon is no longer available or visible on any panels or launch bars including systemtrays. The icon is a white box on a tint2 launcher panel. On the systemtray the icon is there and accessible via right click context menu but it is invisible All icons are in their proper places on the system -- Thank you, VastOne V-Ger VSIDO Developer
Bug#785273: SpaceFM symbol lookup error - undefined symbol: fdLogSock
Package: spacefm Version: 1.0.1-1 After the latest (today) rounds of SID level dist-upgrades spacefm refuses to load or start with this error from terminal spacefm: symbol lookup error: /usr/lib/x86_64-linux-gnu/libutvideo.so.15: undefined symbol: fdLogSock I suggest the undefined symbol be addressed and corrected I am using VSIDO (based on Debian SID) kernel Debian 4.0.2-1 -- Thank you, VastOne V-Ger VSIDO Developer
Bug#785273: Resolved
An update to libutvideo15 just came through SID that resolved this issue -- Thank you, VastOne V-Ger VSIDO Developer
Bug#765635: live-tools diverts and keeps update owned by procps
Package: live-tools Version: 4.0.1-1 VSIDO systems (Debian SID based distro) live-tools diverts and keeps update owned by procps even when live-tools is uninstalled This issue is causing applications like inxi to fail with an error like this: The following applications are missing from your system: Application: uptime To add to your system, install the proper distribution package for your system: Debian/Ubuntu: procps :: Arch Linux: procps :: Redhat/Fedora/Suse: procps When running: dpkg-divert --list '*uptime*' shows the package uptime which is owned by procps as diverted by live-tools diversion of /usr/share/man/man1/uptime.1.gz to /usr/share/man/man1/uptime.orig.procps.1.gz by live-tools diversion of /usr/bin/uptime to /usr/bin/uptime.orig.procps by live-tools Uninstalling live-tools and reinstalling procps does not resolve the problem Manually removing the diversion from /var/lib/dpkg/diversions and then apt-get install --reinstall procps does solve the problem Even with live-tools gone from a system there should not be in any way it can or should keep a diversion to uptime I suggest clearing it in dpkg in some way A complete look at this issue and resolution can be seen here http://vsido.org/index.php?topic=849.msg9805#msg9805 -- Thank you, VastOne - Developer of VSIDO a debian sid based distro
Bug#765635: clarification
In the subject and at one point in the content I called the package update It is in fact the procps tool uptime Please forgive my gaff and correct it if you can -- Thank you, VastOne
Bug#764978: procps 2:3.3.9-8 is missing /usr/bin/update
Package: procps Version: 2:3.3.9-8 VSIDO systems based on debian are current with the procps packages from the sid repos however /usr/bin/uptime is missing Applications such as inxi are no longer operable and fail with a message that says uptime is missing. inxi --recommends is procps /sur/bin/update is no longer available or installed I recommend update back to the procps package or identify where it has been moved to Thank you, VastOne - V-Ger - Developer
Bug#764978: errors in my bug report
/usr/bin/uptime is missing is the correct missing component /usr/bin/update and /sur/bin/update are both incorrect. My sincerest apologies -- Thank you, VastOne
Bug#763575: spacefm - Attempt to unlock mutex that was not locked
Package: spacefm Version: 0.4.9-1 Since GLib ≥ 2.41 update spacefm 0.4.9-1 has failed with the error Attempt to unlock mutex that was not locked. Reported here: https://github.com/IgnorantGuru/spacefm/issues/468 Verified here: https://mail.gnome.org/archives/commits-list/2014-August/msg08240.html Solution from BwackNinja here: https://raw.githubusercontent.com/BwackNinja/spacefm/master/src/main.c SpaceFM is the default file manager in VSIDO a distro I develop and am responsible for. We all run on the latest SID packages and kernel. I suggest building the next package with BwackNinjas source -- Thank you, VastOne
Bug#750963: syslinux: isohybrid is no longer included in syslinux on sid version
Package: syslinux Version: 3:6.03~pre1+dfsg-4 Severity: normal Tags: d-i -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages syslinux depends on: ii libc6 2.19-1 ii mtools 4.0.18-1 Versions of packages syslinux recommends: ii syslinux-common 3:6.03~pre1+dfsg-4 Versions of packages syslinux suggests: ii dosfstools 3.0.26-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#729945: preseed.cfg does not work as outlined from the manual
Package: live-build Version: 4.0~alpha30-1 Severity: normal In section 12.2 Customizing Debian Installer by preseeding of the http://live.debian.net/manual/4.x/html/live-manual.en.html#495 states This kind of customization is best accomplished with *live-build* by placing the configuration in a preseed.cfg file included in config/debian-installer/. I have included the following in the preseed.cfg file in config/debian-installer but I am seeing none of it showing in the build ## Account setup # Skip creation of a root account (normal user account will be able to# use sudo). d-i passwd/root-login boolean false ## Finishing up the installation d-i finish-install/keep-consoles boolean true d-i finish-install/reboot_in_progress note d-i debian-installer/locale string en_US Has this functionality changed? -- Thank you, VastOne
Bug#729544: closed by Daniel Baumann daniel.baum...@progress-technologies.net (reply to daniel.baum...@progress-technologies.net) (Re: Bug#729544: live-build 4.0~alpha30-1 does not see any kernel mo
I did include --debian-installer-distribution daily in the config but found it still behind a build curve stuck at 3.11-1-amd64 while the sid kernel has moved to 3.11-2-amd64. For informational purposes, the debian-installer did continue but once it got to the partition creations, there was no ext support at all I did resolve this by adding the following udebs to /config/packages.binary and start the build again core-modules-3.11-2-amd64-di_3.11.8-1_amd64.udeb crc-modules-3.11-2-amd64-di_3.11.8-1_amd64.udeb ext4-modules-3.11-2-amd64-di_3.11.8-1_amd64.udeb kernel-image-3.11-2-amd64-di_3.11.8-1_amd64.udeb The build completed, the live-cd and installation worked perfectly On Wed, Nov 13, 2013 at 11:45 PM, Debian Bug Tracking System ow...@bugs.debian.org wrote: This is an automatic notification regarding your Bug report which was filed against the live-build package: #729544: live-build 4.0~alpha30-1 does not see any kernel modules found It has been closed by Daniel Baumann daniel.baum...@progress-technologies.net (reply to daniel.baum...@progress-technologies.net). Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Daniel Baumann daniel.baum...@progress-technologies.net (reply to daniel.baum...@progress-technologies.net) by replying to this email. -- 729544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729544 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- Forwarded message -- From: Daniel Baumann daniel.baum...@progress-technologies.net To: VastOne vast...@gmail.com, sub...@bugs.debian.org Cc: 729544-d...@bugs.debian.org Date: Thu, 14 Nov 2013 06:42:34 +0100 Subject: Re: Bug#729544: live-build 4.0~alpha30-1 does not see any kernel modules found On 11/14/2013 03:58 AM, VastOne wrote: No kernel modules were found. This probably is due to a mismatch between the kernel used by this version of the installer and the kernel version available in the archive. this is because debian-installer releases happen too infrequent to match the kernel version in the archive. there's nothing live-build can do about. you can however switch to debian-installer daily builds with lb config --debian-installer-distribution daily. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- Forwarded message -- From: VastOne vast...@gmail.com To: sub...@bugs.debian.org Cc: Date: Wed, 13 Nov 2013 20:58:58 -0600 Subject: live-build 4.0~alpha30-1 does not see any kernel modules found Package: live-build Version: 4.0~alpha30-1 Severity: normal Using live-build with debian-installer on a sid based system with version 4.0~alpha30-1 from Experimental successfully building and booting a livecd session. The correct kernel packages were included in /config/packages.chroot. The installer proceeds to Load Installer Components from CD and errors oout with: No kernel modules were found. This probably is due to a mismatch between the kernel used by this version of the installer and the kernel version available in the archive. As stated, the correct kernels have been included and are what is shown with uname -a 3.10-3-amd64 #1 SMP Debian 3.10.11-1 I can be in the live system for any amount of time where needed to report any additional information -- Thank you, VastOne -- Thank you, VastOne
Bug#729544: live-build 4.0~alpha30-1 does not see any kernel modules found
Package: live-build Version: 4.0~alpha30-1 Severity: normal Using live-build with debian-installer on a sid based system with version 4.0~alpha30-1 from Experimental successfully building and booting a livecd session. The correct kernel packages were included in /config/packages.chroot. The installer proceeds to Load Installer Components from CD and errors oout with: No kernel modules were found. This probably is due to a mismatch between the kernel used by this version of the installer and the kernel version available in the archive. As stated, the correct kernels have been included and are what is shown with uname -a 3.10-3-amd64 #1 SMP Debian 3.10.11-1 I can be in the live system for any amount of time where needed to report any additional information -- Thank you, VastOne
Bug#681347: pkgsel: bussiness card and netinstall, Can't exec aptitude after Select Install Software
Package: pkgsel Severity: serious Tags: d-i Justification: fails to build from source (but built successfully in the past) Can't exec aptitude: No such file or directory at /usr/bin/debconf-apt- progress line 130. STDIN line 2. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.4.0-4.dmz.2-liquorix-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
