Bug#865015: debian-installer: Live installers are unable to start, "There was a problem reading data from the CD-ROM"
It turns out that my write to USB had an error as dd didn't do a good job on my thumb drive. But again I used dd to write the image and it worked great and I am able to complete install. Thank you so much steve. I know this is wrong place to ask, but anyone know why I am not able to do root login in a bash shell via gnome-terminal? On Jun 22, 2017 7:09 AM, "Steve McIntyre" wrote: > On Wed, Jun 21, 2017 at 11:55:03PM -0400, piruthiviraj natarajan wrote: > > > >I tried this image and it breaks down after running for a while, bringing > up > >the same error message. > >https://cdimage.debian.org/cdimage/unofficial/non-free/ > cd-including-firmware/ > >9.0.1-live+nonfree/amd64/iso-hybrid/debian-live-9.0.1- > amd64-mate+nonfree.iso > > I've just done a test installation using that exact image with no > problems. Are you *sure* you're using 9.0.1? This is one of the things > that was fixed in the 9.0.1 rebuild... > > -- > Steve McIntyre, Cambridge, UK. > st...@einval.com > Welcome my son, welcome to the machine. > >
Bug#865015: debian-installer: Live installers are unable to start, "There was a problem reading data from the CD-ROM"
I tried this image and it breaks down after running for a while, bringing up the same error message. https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/9.0.1-live+nonfree/amd64/iso-hybrid/debian-live-9.0.1-amd64-mate+nonfree.iso
Bug#734976: a workaround
On Thu, 30 Jan 2014 13:23:51 +0530 piruthiviraj natarajan < piruthivi...@gmail.com> wrote: > echo "options iwlwifi 11n_disable=1" > >> /etc/modprobe.d/iwlwifi-disable11n.conf > > This seems to help prevent the error messages from dmesg. currently this workaround doesn't help either. we are dying out here with this wireless card for months. Please somebody help!
Bug#734976: a workaround
echo "options iwlwifi 11n_disable=1" >> /etc/modprobe.d/iwlwifi-disable11n.conf This seems to help prevent the error messages from dmesg.
Bug#727708: linux is not about choice
This thing about 'Linux/Debian is all about choice' reminds me of the famous post I read in the past about choice. http://www.redhat.com/archives/fedora-devel-list/2008-January/msg00861.html
Bug#727708:
I think people should read this from Lennart about some basic insights of what to look for in a Init system which has not been discussed in this thread. https://plus.google.com/u/0/+LennartPoetteringTheOneAndOnly/posts/ip8e1DqJdxT
Bug#734976: probably related bug
http://www.spinics.net/lists/linux-wireless/msg113874.html
Bug#734832: it segfaults in sysV init too.
cat /var/log/messages | grep thermald Jan 10 13:48:15 debian kernel: [8.170564] traps: thermald[2163] general protection ip:41d5a2 sp:7fff1f94f010 error:0 in thermald[40+6] Jan 10 13:51:26 debian kernel: [ 198.826276] thermald[3344]: segfault at 1cdc000 ip 0041dd14 sp 7fff15a0b830 error 4 in thermald[40+6] root@debian:~#
Bug#734832: journalctl info
root@debian:~# journalctl | grep thermald Jan 10 11:26:08 debian thermald[854]: thermald ver 1.1: Ready to serve requests: Daemonizing.. Jan 10 11:26:08 debian thermald[961]: 13 CPUID levels; family:model:stepping 0x6:3a:9 (6:58:9) Jan 10 11:26:08 debian thermald[961]: Polling mode is enabled: 4 Jan 10 11:26:08 debian thermald[961]: sensor_update: type acpitz Jan 10 11:26:08 debian thermald[961]: sensor_update: type pkg-temp-0 Jan 10 11:26:08 debian thermald[961]: thd_read_default_thermal_sensors loaded 2 sensors Jan 10 11:26:08 debian thermald[802]: Starting thermald Jan 10 11:26:08 debian thermald[961]: Dumping parsed XML Data Jan 10 11:26:08 debian thermald[961]: *** Index 0 *** Jan 10 11:26:08 debian thermald[961]: Name: Generic X86 Laptop Device Jan 10 11:26:08 debian thermald[961]: UUID: Jan 10 11:26:08 debian thermald[961]: type: 0 Jan 10 11:26:08 debian thermald[961]: Sensor 0 Jan 10 11:26:08 debian thermald[961]: Name: TSKN Jan 10 11:26:08 debian thermald[961]: Path: Jan 10 11:26:08 debian thermald[961]: Async Capable: 1 Jan 10 11:26:08 debian thermald[961]: Zone 0 Jan 10 11:26:08 debian thermald[961]: Name: SKIN Jan 10 11:26:08 debian thermald[961]: Trip Point 0 Jan 10 11:26:08 debian thermald[961]: temp id 44000 Jan 10 11:26:08 debian thermald[961]: trip type 2 Jan 10 11:26:08 debian thermald[961]: hyst id 0 Jan 10 11:26:08 debian thermald[961]: Trip id 0 Jan 10 11:26:08 debian thermald[961]: type rapl_controller Jan 10 11:26:08 debian thermald[961]: influence 100 Jan 10 11:26:08 debian thermald[961]: SamplingPeriod 16 Jan 10 11:26:08 debian thermald[961]: Trip id 1 Jan 10 11:26:08 debian thermald[961]: type intel_powerclamp Jan 10 11:26:08 debian thermald[961]: influence 100 Jan 10 11:26:08 debian thermald[961]: SamplingPeriod 12 Jan 10 11:26:08 debian thermald[961]: *** Index 1 *** Jan 10 11:26:08 debian thermald[961]: Name: Example Platform Name Jan 10 11:26:08 debian thermald[961]: UUID: Example UUID Jan 10 11:26:08 debian thermald[961]: type: 0 Jan 10 11:26:08 debian thermald[961]: Sensor 0 Jan 10 11:26:08 debian thermald[961]: Name: TSKN Jan 10 11:26:08 debian thermald[961]: Path: Jan 10 11:26:08 debian thermald[961]: Async Capable: 1 Jan 10 11:26:08 debian thermald[961]: Sensor 1 Jan 10 11:26:08 debian thermald[961]: Name: example_sensor_1 Jan 10 11:26:08 debian thermald[961]: Path: /some_path Jan 10 11:26:08 debian thermald[961]: Async Capable: 0 Jan 10 11:26:08 debian thermald[961]: Sensor 2 Jan 10 11:26:08 debian thermald[961]: Name: example_thermal_sysfs_sensor Jan 10 11:26:08 debian thermald[961]: Path: Jan 10 11:26:08 debian thermald[961]: Async Capable: 1 Jan 10 11:26:08 debian thermald[961]: Zone 0 Jan 10 11:26:08 debian thermald[961]: Name: Example Zone type Jan 10 11:26:08 debian thermald[961]: Trip Point 0 Jan 10 11:26:08 debian thermald[961]: temp id 75000 Jan 10 11:26:08 debian thermald[961]: trip type 1 Jan 10 11:26:08 debian thermald[961]: hyst id 0 Jan 10 11:26:08 debian thermald[961]: Trip id 0 Jan 10 11:26:08 debian thermald[961]: type example_cooling_device Jan 10 11:26:08 debian thermald[961]: influence 100 Jan 10 11:26:08 debian thermald[961]: SamplingPeriod 12 Jan 10 11:26:08 debian thermald[961]: Cooling Dev 0 Jan 10 11:26:08 debian thermald[961]: Type: example_cooling_device Jan 10 11:26:08 debian thermald[961]: Path: Jan 10 11:26:08 debian thermald[961]: Min: 0 Jan 10 11:26:08 debian thermald[961]: Max: 50 Jan 10 11:26:08 debian thermald[961]: Step: 10 Jan 10 11:26:08 debian thermald[961]: AutoDownControl: 0 Jan 10 11:26:08 debian thermald[961]: PID: Kp 0.001000 Jan 10 11:26:08 debian thermald[961]: PID: Ki 0.000100 Jan 10 11:26:08 debian thermald[961]: PID: Kd 0.000100 Jan 10 11:26:08 debian thermald[961]: UUID is [9FB5441A-14F8-11E2-83C6-B888E38F0DE9] Jan 10 11:26:08 debian thermald[961]: product name is[20132] Jan 10 11:26:08 debian thermald[961]: Product Name matched [wildcard] Jan 10 11:26:08 debian thermald[961]: sensor id 5: No temp sysfs for reading raw temp Jan 10 11:26:08 debian thermald[961]: sensor index:0 acpitz Async:0 Jan 10 11:26:08 debian thermald[961]: sensor index:1 pkg-temp-0 Async:1 Jan 10 11:26:08 debian thermald[961]: sensor index:2 temp1_input Async:0 Jan 10 11:26:08 debian thermald[961]: sensor index:3 temp2_input Async:0 Jan 10 11:26:08 debian thermald[961]: sensor index:4 temp3_input Async:0 Jan 10 11:26:08 debian thermald[961]: thd_read_default_cooling devices loaded 10 cdevs Jan 10 11:26:08 debian thermald[961]: powercap RAPL no long term time window Jan 10 11:26:08 debian thermald[961]: MSR READ Failed Jan 10 11:26:08 debian thermald[961]: MSR READ Failed Jan 10 11:26:08 debian thermald[961]: MSR READ Failed Jan 10 11:26:08 debian thermald[961]: MSR READ Failed Jan 10 11:26:08 debian thermald[961]: MSR READ Failed Jan 10 11:26:08 debian thermald[961]: MSR READ Failed Jan 10 11:26:08 debian thermald[961]: Use Default pstate drv settings Jan 10 11:26:08 debian thermald[961]: UUID is [9FB5441A-14F8-11E2-83C6-B888E38F0DE9] Jan 10 11:2
Bug#734832: thermald exits while trying to use with systemd init
Package: thermald Version: 1.1~rc2-2 When I try to see the status of the thermald in systemctl status thermald it has already exited and doesn't stay up. I am using the latest kernel from experimental. uname -a Linux debian 3.13-rc6-amd64 #1 SMP Debian 3.13~rc6-1~exp1 (2013-12-30) x86_64 GNU/Linux I have IVB core i7 3630M mobile intel CPU systemctl status thermald thermald.service - LSB: Start the Intel power daemon Loaded: loaded (/etc/init.d/thermald) Active: active (exited) since Fri 2014-01-10 11:26:08 IST; 4min 7s ago Process: 802 ExecStart=/etc/init.d/thermald start (code=exited, status=0/SUCCESS) Jan 10 11:26:08 debian thermald[961]: Use Default pstate drv settings Jan 10 11:26:08 debian thermald[961]: UUID is [9FB5441A-14F8-11E2-83C6-B888E38F0DE9] Jan 10 11:26:08 debian thermald[961]: product name is[20132] Jan 10 11:26:08 debian thermald[961]: Product Name matched [wildcard] Jan 10 11:26:08 debian thermald[961]: 0: Processor, C:0 MN: 0 MX:10 ST:1 pt:/sys/class/thermal/ rd_bk 1 Jan 10 11:26:08 debian thermald[961]: 1: Processor, C:0 MN: 0 MX:10 ST:1 pt:/sys/class/thermal/ rd_bk 1 Jan 10 11:26:08 debian thermald[961]: 2: Processor, C:0 MN: 0 MX:10 ST:1 pt:/sys/class/thermal/ rd_bk 1 Jan 10 11:26:08 debian thermald[961]: 3: Processor, C:0 MN: 0 MX:10 ST:1 pt:/sys/class/thermal/ rd_bk 1 Jan 10 11:26:08 debian thermald[961]: 4: Processor, C:0 MN: 0 MX:10 ST:1 pt:/sys/class/thermal/ rd_bk 1 Jan 10 11:26:08 debian thermald[961]: 5: Processor, C:0 MN: 0 MX:10 ST:1 pt:/sys/class/thermal/ rd_bk 1 If there is any other info required I would be glad to provide.
Bug#708738: smplayer exits when width of floating control is changed
Package: smplayer version: 0.8.0-1 The current smplayer in sid exits when setting are changed in the options>preferences>Interface>floating control > width. When the width is adjusted and we apply the changes the smplayer exits abruptly. This bug is fixed in smplayer version 0.8.5 Please update to the latest upstream version. http://smplayer.sourceforge.net/forum/viewtopic.php?f=3&t=6203 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#708618: selection is reported incorrectly in file chooser button
Package: gtk+2.0 version: 2.24.17-2 When you add a torrent you should be able to download it to a user specified location on your hard disk. But in Deluge 1.3.3 when you select file->add a torrent->options->downloadlocation-> other(scroll down to the lowest in the menu). What ever location you set in "other" is not recognized by the application and it sets itself to default /home/user/Downloads. This issue is fixed in 2.24.18 upstream. Please update. The links: https://bugzilla.redhat.com/show_bug.cgi?id=845040 https://bugzilla.gnome.org/show_bug.cgi?id=691040 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#703715:
I have the same issue in Debian Wheezy 7.0 release. The random freezes can only reverted by restarting X in tty. I have an ivybridge Lenovo Y580 system. lspci 00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) 00:1c.3 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 4 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04) 01:00.0 VGA compatible controller: NVIDIA Corporation Device 0fd4 (rev ff) 02:00.0 Ethernet controller: Atheros Communications Inc. AR8161 Gigabit Ethernet (rev 08) 03:00.0 Network controller: Intel Corporation Centrino Wireless-N 2200 (rev c4) 04:00.0 System peripheral: JMicron Technology Corp. SD/MMC Host Controller (rev 30) 04:00.2 SD Host controller: JMicron Technology Corp. Standard SD Host Controller (rev 30) 04:00.3 System peripheral: JMicron Technology Corp. MS Host Controller (rev 30) 04:00.4 System peripheral: JMicron Technology Corp. xD Host Controller (rev 30) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#703673: Request to backport acpi changes to Debian sid for proper acpi child device handling
Package: linux-image-3.2.0-4-amd64 Version: 3.2.39-2 Severity: important There is a upstream linux kernel bug https://bugzilla.kernel.org/show_bug.cgi?id=42696 which prevents the Lenovo Y580/Y470/Y570 and Toshiba Satellite P870 devices unable to find the Nvidia card through proper acpi device handling. It has been discussed in detail in this thread as well at bumblebee git page too. https://github.com/Bumblebee-Project/bbswitch/issues/2 It has been fixed since Linux kernel 3.9 rc2 through this patch https://bugzilla.kernel.org/attachment.cgi?id=89731. The bug applies to wheezy as well and backporting the new kernel changes would fix the proper acpi handling. I hereby request the kernel maintainers to backport these changes to Debian wheezy. Thank you, Dr. Piruthiviraj Natarajan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#696848: general: USB flash drive unmount problems (both squeeze/wheezy)
Fedora had the same bug and it has been fixed with the recent commits. see if this lengthy report helps. https://bugzilla.redhat.com/show_bug.cgi?id=885133
Bug#696807: [APT::Clean-Installed "0";] doesn't remove packages from experimental and testing repos when invoking autoclean
Package: apt Version: 0.9.7.7 I 'm running debian wheezy testing installed from Debian beta 4 cd.iso. root@localhost:~# cat /etc/apt/apt.conf APT::Clean-Installed "0"; // auto-remove breaks on meta packages APT::Get::AutomaticRemove "0"; APT::Get::HideAutoRemove "1"; // Recommends are as of now still abused in many packages APT::Install-Recommends "0"; APT::Install-Suggests "0"; Debug::pkgAutoRemove "0"; Acquire::PDiffs "0"; // Remove apt unauthenticated warnings APT::Get::AllowUnauthenticated "0"; root@localhost:~# root@localhost:~# cat /etc/apt/sources.list deb http://ftp.debian.org/debian/ testing main contrib non-free #deb-src http://ftp.debian.org/debian/ testing main contrib non-free deb http://security.debian.org/ wheezy/updates main deb-src http://security.debian.org/ wheezy/updates main deb http://ftp.debian.org/debian/ experimental main contrib non-free deb http://www.deb-multimedia.org/ testing main non-free root@localhost:~# root@localhost:~#uname -a Linux localhost 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux But after doing an apt-get autoclean, it left some packages in the cache(after removing some vlc related .deb files), and I found that the action was incomplete and it didn't remove the packages that I downloaded from the experimental repos and testing. I still have iceweasel_10.0.11esr-1_amd64. deb from testing repo. linux-image-3.7-trunk-amd64_3.7.1-1~experimental.1_amd64.deb from experimental repo. These .deb files are still located in my /var/cache/apt/archives/ These files should have been deleted by the autoclean command. I reported this in debian-user mailing list and was directed to file a bugreport here. I can give you more info if you want.
Bug#683756: selinux in permissive mode breaks gdm and X
You want us to change the type "bin_t" into what? I assumed that you want to relabel the type and I tried relabelling #chcon -t xdm_exec_t /usr/sbin/gdm3 but it didn't work. Still stuck with a black screen. I had to disable the selinux at boot to login to X. Now I am at #ls -Z /usr/sbin/gdm3 system_u:object_r:xdm_exec_t:s0 /usr/sbin/gdm3
Bug#683756: selinux in permissive mode breaks gdm and X
I have the selinux-policy-default package installed. root@debian:~# semanage login -l Login NameSELinux User MLS/MCS Range __default__ unconfined_u systemLow-systemHigh root unconfined_u systemLow-systemHigh system_u system_u systemLow-systemHigh root@debian:~#
Bug#683756: selinux in permissive mode breaks gdm and X
The enforcing mode of selinux breaks the gdm3 too.
