Bug#757861: I can reproduce this issue
Hi, i can reproduce this issue with the latest Jessie release. Wifi hardware is an ipw2200 in this case. During installation I can not connect to a WPA secured network. I just get into an endless loop asking for the SSID and key. A connection to an open network works well. In the installer log i can see the following entries which might be interesting for this issue: netcfg: INFO: Network chosen: FOO. Proceeding to connect. apt-install: Queueing package wpasupplicant for later installation netcfg: INFO: Couldn't connect to wpasupplicant dnesg says that the firmware ipw2200-bss.fw has been loaded. Will there be an update to the installer for Jessie? Kind regards Kay
Bug#782070: [live-config] preseed file for installation is not copied in binary/install
Am 07.04.2015 um 13:13 schrieb Louis-Maurice De Sousa: ... Even if I put a file preseed.cfg in each of these directories, the file is not copied in binary/install where the debian installer searchs it when booting with the live key. I had the same issue when I did migrate from Wheezy to Jessie. I figured out that the preseed.cfg file is now put to the root folder of the installer image. I have my own isolinux configuration file where I had to change the installer boot parameter for the preseed file to file=/preseed.cfg. I don't know what the default isolinux configuration looks like in Jessie, but with this setting it works for me. Kind regards Kay -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648629: segfault in libgnome-shell.so at startup
Hello, this bug report can be closed. I had a hard disk crash and did a clean installation. Now gnome-shell works very well. And sorry for the garbage at the beginning of my bug report. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#485484: dhcpcd should NOT conflict with dhcp3-client
Hello, I think that dhcpcd should not conflict with dhcp3-client. Why should I not be allowed to have two DHCP clients installed at the same time? In my scenario I want to use Network Manager, which depends on dhcp3-client. But for one VPN connection I need dhcpcd. So I don't really need dhcp3-client, but Network Manager needs it. I would suggest to remove the conflict, because you can run both clients at the same time without trouble. Let the user decide whether he/she needs two DHCP clients or not. Same like for web browsers, file managers etc. Thanks! Kind regards Kay -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521325: At least 0.6.12-5 of the package works
Hi, I have the same problem here on three different machines. All machines are running Debian testing with the latest updates. DBUS is sending the events on the system message bus, but ivman does not care. This behaviour changed a few weeks ago. In the beginning I thought that I changed something that brakes the functionality, but now it seems that ivman is responsible. On all of my machines, ivman is running in user mode with a specific user configuration. The system-wide ivman is disabled. I installed version 0.6.12-5 of the package and it works fine. I don't know whether there are more recent versions available. The problem at least occurs on 0.6.14-3.1. Best regards -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
