Debian :: Getting A Warning That Some Updates Are Unauthenticated
Feb 3, 2011
When installing updates, I am getting a warning that some updates are unauthenticated and may be malicious. These are all "lib" files. I am not willing to corrupt this laptop. That's why I moved to Linux in the first place..
I had (and still do) a working dual-boot XP/Karmic (GRUB version 1.97 beta4). I shrank the Ubuntu partition and set up partitions and installed Debian 5.04. When I got to the point of installing GRUB, I told Debian to install grub to MBR. On rebooting, Ubuntu was not an option on the NEW (looked different) grub menu.Maybe it was GRUB2? Could boot to either XP or Debian though.
Thought easiest thing was to reinstall Ubuntu since it seems to "see" other OS's more reliably. So I did, and installed GRUB again during its install to MBR. Then, all three were in the GRUB menu (version 1.97 beta4 again), but when tried booting to Debian, got an error (forget the wording), but think it was because the partitions got renumbered when installing Ubuntu.
SO, reinstalled Debian, reformatting the partitions but not deleting them first so the numbering stayed the same. When got to the part for installing GRUB, I told it to skip (I got some kind of error that said "Install failed. This is a fatal error. You will have to boot with an external device..."), hoping now the current GRUB would work.
Now, all three were on the GRUB menu, but when I tried to boot Debian, I got "no such device" and a list of numbers/letters after it. And "press any key to continue", which takes you back to the GRUB menu (version 1.97 beta4, by the way).
O.K., did sudo update-grub in ubuntu and rebooted. Now, Debian 5.04 shows as last entry in GRUB, and choosing it starts a boot, which hangs at "Begin: Waiting for root file system....".
Waiting long enough at the "Waiting for root file system..." hang results in a series of notifications:
WARNING bootdevice may be renamed. Try root=dev/hda3 Gave up waiting for root device. Common problems: -Boot args (cat /proc/cmdline) -Check rootdelay= (did the system wait long enough?) -Check root= (did the sytem wait for the right device?) -Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/sda3 does not exist. Dropping to a shell!
In Gparted, the partition with Debian root is hdc3, although on the GRUB menu it's listed as /dev/sda3. However, in Gparted the Windows partition is hdc1 and on GRUB it's /dev/sda1, and it boots fine.....
Is my Debian install just borked? Did telling it to skip installing a bootloader (I got some kind of error that said "Install failed. This is a fatal error. You will have to boot with an external device..." ruin it?
If skipping the bootloader install did ruin it, how do you install Debian without borking your current GRUB? That's what happened the first time.
I'm running Debian Testing and since some time ago I'm getting the following messages:Any ideas how to solve this warnings?
(gtk-update-icon-cache:9204): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory Processing triggers for gconf2 ...
i just tried to install Ubuntu Netbook 10.04 on my old Amilo Lifebook P Series. But after the boot screen and the choice to install Ubuntu i get stuck at the Ubuntu screen with the little dots on the bottom If I hit esc i can see the warning (process 257): GLib-WARNING **: getpwuid_(r) failed due to unknown user id (0)
I have made two partitions / and /home . / is where all the packages and other stuff lives and /home is where user i.e. my data lives. I am sure everybody knows the 'disk space is less' warning dialog box when either we install too many packages or when we download many things. Now the last time it happened by mistake I clicked on do not show more warnings. Now I want to have that warning dialog box back. looked at System > Preferences submenu as well as System > Administration but have not been able to find any info. on the same.
I noticed today I downloaded the amd64 netinst ISO for 'testing' and during the installation, it warned me of a the fact that I was installing using the 2.6.30.x kernel and I am now attempting to install a 2.6.32.x kernel. Is this is a common warning because I have never seen it before. I got it with both the netist & the businesscard image. Has anyone seen this before and is this a problem? Just trying to understand whats going on under the hood. I don't have the error in front of me since I am on my phone away from the office.
I just downloaded the Debian (Squeeze) businesscard 'netinst' ISO and every time I attempted to run an install, I keep getting the following error:http://yfrog.com/ngdeberrorp
I am an old Debian user, ho just reinstalled it again to see how it evolved since my las version (3.2). I am sharing it with Arch Linux, And decided to let bot of them. I am using GDM compiled and configured in Arch, and removed GDM2 from Debian (i just like the easy menu.list from the old GDM). The problem is that when i update the kernel, it didn't fing GDM and drops an error message. I tried removing the distro-preconfigured Kernels, as i compiled my own 3.0.0-rc2 Kerenel, but i cant delete the previous ones. Now everytime i do an install or uptgrade, apt-get drops wastes some time, and drops an error message:
[code]...
What can i do? i googled some similar errors, but where just messed up mirror.lists, or similar, i know it isnt the cause of fail.
PHP Warning: mysqli_connect(): (28000/1045): Access denied for user 'root'@'localhost' (using password: YES) in /var/www/..../libraries/database/mysqli_connection.php on line 23
i am new to linux . i have the basic knowledge of networking. a week ago i installed debian Lenny version on an old pentium 3.in addition i installed a ddclient configured it according to many tutorials....i searched google a few days but didnt find my case.i ran the folowing command :
Debian 5.0. Lately after login following warning popup;Your system had a kernel failure
There is diagnostic information availiable for this failure. Do you want to submit this infomation to the www.kerneloops.org
-> Yes
$ uname -aLinux vm0.debian50 2.6.26-2-686 #1 SMP Wed May 12 21:56:10 UTC 2010 i686 GNU/Linux
Reboot to old kernel 2.6.26-1 the said warning doesn't popup. Reboot again to kernel 2.6.26-2 and after login no kernel failure warning popup. I did it twice. IIRC I encountered this problem before.
i have the basic knowledge of networking. a week ago i installed debian Lenny version on an old pentium 3. in addition i installed a ddclient configured it according to many tutorials.i searched google a few days but didnt find my case. i ran the folowing command :
I am using Debian testing i386. Just upgraded to 2.6.39-2-686-pae. After reboot, and ever since, I am getting warning: WARNING: Could not find hdaps input device (No such file or directory). You may be using an incompatible version of the hdaps module. Falling back to reading the position from sysfs (uses more power). Use '-y' to silence this warning.
Every time I open my terminal a warning message shows up. The warning is the following:
Code: Select allwarning: output DFP2 not found; ignoring
There is no output DFP2 in my system. I ran xrarndr and the outputs are the following:
Code: Select allScreen 0: minimum 320 x 200, current 3840 x 1080, maximum 8192 x 8192 VGA1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 477mm x 268mm   1920x1080   60.00*+   1680x1050   59.95   1600x900   59.98   1280x1024   75.02  60.02Â
[Code] ...... Â
HDMI1 disconnected (normal left inverted right x axis y axis) DP1 disconnected (normal left inverted right x axis y axis) HDMI2 connected primary 1920x1080+1920+0 (normal left inverted right x axis y axis) 477mm x 268mm
  1920x1080   60.00*+ 50.00  59.94   1680x1050   59.88   1600x900   59.98   1280x1024   75.02  60.02Â
[Code] ....
HDMI3 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) DP3 disconnected (normal left inverted right x axis y axis)
I experienced this problem on Friday but didn't have time to write a warning.A couple of days ago, xserver-xorg-core 2:1.10.2-1+b1 reached Testing before a corresponding dependency (recommendation), thus breaking the hardware acceleration. The issue is (better) described here (1) by a developer.A possible solution is to keep (2) the previous version (2:1.10.2-1) or, if you already installed the faulty one, to grab the former version from Debian Snapshots (3) and downgrade the package.Because the error was a simple path change, one could also keep the new version of xserver-xorg-core and link the DRI Mesa modules to the directories that are inspected now (as described here [4]).The issue has already been addressed (5) and a new version should appear in Testing shortly.[URL]
I'm doing a fully automated install of Etch, installing the standard system task. I'm using PXE boot with a preseed file.
I do this a lot, and I've not had problems before. This morning, it's stuck at 5% on "Select and install software" saying "Please wait...". The log on console #4 says:
WARNING: untrusted versions of the following packages will be installed!
[snip]
Do you want to ignore this warning and proceed anyway?
I installed a system yesterday without any problems, so I wonder if there's a recent problem with the mirrors I'm using. My /target/etc/apt/sources.list contains:
deb [url] deb [url]
So it looks like either the UK mirror or security.debian.org.
Code: Select alldone. Setting parameters of disc: (none). Setting preliminary keymap...done. Activating swap...done. Checking root file system...fsck from util-linux-ng 2.17.2
[Code] ....
An automatic file system check (fsck) of the root filesystem failed. A manual fsck must be performed, then the system restarted. The fsck should be performed in maintenance mode with the root filesystem mounted in read-only mode. ... failed!
The root filesystem is currently mounted in read-only mode. A maintenance shell will now be started. After performing system maintenance, press CONTROL-D to terminate the maintenance shell and restart the system. ... (warning).
Give root password for maintenance (or type Control-D to continue): _
For now, I just don't know what I should to do next to my system has started to work again...