Debian Configuration :: Jessie After Dist-upgrade / Password Not Working
Jul 13, 2015
updated my jessie by apt-get dist-upgrade and there was an error said there was something wrong with some database, and I needed to run some command, but after the upgrade I forgot to run the command. After I rebooted my system I found there was not any password needed for a normal user or the root. But if I change to the emergency mode, a root password is needed.
This is on my AMD64 Testing box...A couple days ago during an apt-get dist-upgrade, near the end I saw the errors below.
I haven't noticed anything broken, yet. I usually only see dkms errors when VBox squawks after an update and I run /etc/init.d vboxdrv setup.
The section of the results containing the errors to the end of the output:
Code: Select allSetting up linux-image-4.3.0-1-amd64 (4.3.5-1) ... /etc/kernel/postinst.d/dkms: error: db5 error(-30969) from dbenv->open: BDB0091 DB_VERSION_MISMATCH: Database environment version mismatch error: cannot open Packages index using db5 - (-30969) error: cannot open Packages database in /root/.rpmdb error: db5 error(-30969) from dbenv->open: BDB0091 DB_VERSION_MISMATCH: Database environment version mismatch
After running a dist-upgrade (from stable to testing) KDE stopped working, all I get (after login in with lightdm) are the modals you can see in the attachments . I do not think it is an X issue, because I can login using lightdm (and MATE is working fine).
I suspect this is because I had KDE installed before running the upgrade. The things I tried so far are:
- Runing "apt-get remove kdelibs-bin kdelibs5-data" . Then "apt-get autoremove". I did it to remove every KDE related package, after that, I ran "aptitude purge '~c' " to clean all config files. And finally "apt-get install kde-standard" to get KDE again. - Removed .cache, .config and .kde folders. Also removed .lock files in .config folder, as I saw somewhere. - Looked for some log files, but I could not find anything (I don't even know where to look really )
This is almost a fresh debian install so I don't mind breaking things, but I would like to get KDE working.
I have used a quite obscure device called Cideko AK0b [URL] .... for quite some time now and it has worked perfectly for almost 2 years now, both in Wheezy and in Jessie. However since I made an dist-upgrade a while back the mouse has totally stopped working. The system works through wifi - strangely enough - but everything else works. Keyboard and gamepad buttons. The manufacture says the things doesn't work on linux and so far I have proved them wrong.
But now the mouse is just out right dead no matter what I do. Have looked into mouse autosuspend but no avail so far. My suspicion is systemd but that is as good as any guess.
This is my dmesg.
Code: Select allroot@cryptserv:/home/dencrypt# dmesg | grep Cideko [ 3.158099] usb 6-3: Manufacturer: Cideko Inc. [ 3.469194] input: Cideko Inc. AK08b Device as /devices/pci0000:00/0000:00:12.1/usb6/6-3/6-3:1.0/0003:20E8:5860.0001/input/input2 [ 3.469329] hid-generic 0003:20E8:5860.0001: input,hidraw0: USB HID v1.10 Keyboard [Cideko Inc. AK08b Device] on usb-0000:00:12.1-3/input0
I had a Linux server with Wheezy, I have 2 internal drive, one for linux OS, the other our Video On Demand drive that must be accessible to Windows and online. (That's why I chose NTFS, with our large video files, FAT will not work, and EXT isn't compatible with windows sharing, and I haven't gotten FTP to work right .
So I upgraded to Jessie today, and everything went smoothly until I tried to access my NTFS drive. (Named WowzaStorage)
I used FSTAB to auto-mount the drive (/dev/sdb1) to /media/ntfs/ on boot. All of this worked swimmingly on Wheezy, but since the update, something got mucked up and I cannot figure it out.
When accessing the mounted NTFS folder in /media/ (if it even shows up) gives me a 'Cannot be found' 'Input/Output error'
When in gParted to examine the drive, I can select it and view all the correct info, but I keep getting "error informing the kernel about modifications to partition /dev/sdb1/ --invalid argument"
Now first I thought maybe the NTFS driver was faulty and I removed 'ntfs-3g' and reinstalled it.
Now when I am in Terminal, after i umount and mount sdb1, I can CD to the drive but not the folders on it... Also using the File Browser, I get errors, and missing folders.
I get "Unhandled error message: Error when getting information for file '/media/ntfs': Input/output error"
I've upgraded a server on our LAN from fully functioning Wheezy to Jessie. All seems fine except remote administering using Putty from my windows workstation when issuing reboot from command line, it goes down and reboots but stops at login prompt asking for username and password and does not come back on the LAN network. This server does not normally have a monitor or keyboard so my ability to remote admin this server in effect is disabled.
If I log on, it will come back on the LAN network. I've checked the logs but can't see any errors. Is it in the configuration of Jessie somewhere or perhaps a Grub issue. I have 5 other production Wheezy servers that I intend to update to Jessie once I understand how to deal with this problem.
I eventually gave up and migrated to mdadm. Works just fine. Having upgraded to jessie and solved one problem
I find the next one. When I boot into jessie my RAID device (just a data partition not /) is not found causing the boot to fail as per problems reported here
After booting I can mount my RAID device but if it's in the fstab when booting it fails. Also, I notice that some of my lvm device names have changed. After a bit of hunting around I found a couple of solutions pointing to running dmraid as a service during boot and changing the entry for the RAID device in fstab to use the UUID.
This seems to work. However this seems to be a workaround and as the lvm device paths for my / and /usr partitions have also changed, I'm wondering if there is a bug here as mentioned in the second link?
The / and /usr paths changed to /dev/dm-2 and /dev/dm-3 from the /dev/mapper/ form.
I had a pretty much standard installation according to some tutorial (I don't remember, which one) for courier, including ssl. After upgrading from Wheezy (7) to Jessie (8) everything continued working fine, excep ssl connections to pop or imap.
In the log I get this error message while connecting to imapd-ssl:
--- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 7 bytes and written 341 bytes --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE ---
TLS over STARTTLS is also not working and does not invoke a log-entry. So I want to solve the ssl-problem first. I guess the STARTTLS-problem is automatically solved then.
My update procedure was:
Editing /etc/apt/sources.listapt-get updateapt-get upgradeapt-get dist-upgradeKeep all configuration files regarding courier.
I have just upgraded to Jessie and everything seems to be OK apart from printing from a windows machine to my print share. This was working previously under wheezy. I can print a test page from Cups without any problems, but when I try and print from windows, Samba seems to crash completely and is constantly writing these messages to the logs. Then I lose access to the other shares, presumably while it repeatedly crashes.
STATUS=daemon 'smbd' finished starting up and ready to serve connectionsPANIC: assert failed at ../source3/printing/printing.c(486): pjob->jobid == jobid [2015/09/22 12:02:03.989596, 0] ../source3/lib/util.c:785(smb_panic_s3) PANIC (pid 3704): assert failed: pjob->jobid == jobid [2015/09/22 12:02:03.991930, 0] ../source3/lib/util.c:896(log_stack_trace) BACKTRACE: 27 stack frames:
Wakeonlan was working just fine with Wheezy on this machine. After upgrade, wakeonlan will resume from suspend but not from shutdown.
I have no problem with other machines (same software setup) after upgrade. None of my other machines have a broadcom NIC.
No BIOS settings were changed during the upgrade. If I enter the BIOS on boot and make sure settings are correct then 'save' and shutdown, without booting to debian, I can then successfully wakeonlan. Then, if I do not boot debian, but shutdown before debian starts, I can wakeonlan successfully again.
If I boot debian and then shutdown, game over: wakeonlan nolonger works.
$ ethtool eth0 | grep -i wake Supports Wake-on: g Wake-on: g
I installed elog 2.9.2+2014.05.11git44800a72 on my Jessie system. When entering a new post just a simple plain text editing box is shown instead of the WYSIWYG editor, and no drag and drop area for attachments is shown. When I start the elog service with "systemctl start elog" I get this suspect message in the journal: "FCKedit NOT detected".
Indeed, I see that the elog installation creates a symlink which I guess is supposed to point to the fckeditor installation, which nevertheless is missing:
Code: Select allroot@static-3-080:/usr/share/elog/scripts# ll fckeditor lrwxrwxrwx 1 root root 15 Oct 25 2014 fckeditor -> ../../fckeditor root@static-3-080:/usr/share/elog/scripts# ll ../../fckeditor ls: cannot access ../../fckeditor: No such file or directory
I installed ckeditor 4.4.4+dfsg1-3 but his did not fix the problem. I'd say that either the elog package is broken or that it misses a dependency on a package providing FCKedit. Or maybe my system is misconfigured?
I upgraded from wheezy to jessie, but now I just boot to a console. I've gone through and made sure all packages are up to their latest versions, and I've made sure gnome, xorg, and xserver-xorg are reinstalled (during the upgrade they got uninstalled..).
Here's what happens when I run startx manually:
Code: Select allcharlie@asimov:~$ startx X.Org X Server 1.16.4 Release Date: 2014-12-20 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
Note also that this whole time, gdm3 has been running:
A couple of days ago I followed a guide online in order to install Adobe Reader and this guide recommended a specific package that needed the jessie repository, I added it (unaware the jessie was the name of the new distribution on testing) and so I found myself upgrading to Jessie, which is fine since is working quite alright, but since then I can't sent any document to my wi-fi printer.
I had no problem with Wheezy, I installed two printers: one connected to the usb interface and the other one to the wifi (but is actually the same). With Jessie when I try to print something and select the wi-fi one nothing happens. If i try to add a new one I can't since debian doesn't find it and I can't even delete the old "malfunctioning" one.
I just did a dist upgrade on two computers. One of them was fine with the network manager, but the other, netbook, now refuses to start the service. If I do service start network-manager I'll get a message saying a process started, but it must be immediately dying since I can't find the pid or any network manager processes at all. I looked at daemon.log and noticed it was complaining about nm-system-settings.cfg not being there. One question I have is how is this not getting generated? It's not in the deb so somehow it must be generated. I put a fake file in there and even put some data from a pastebin I found online that looked promising, and the message in daemon.log went away but the pids were still dropping off.
I have many problems with nm-applet, but I don't want to go into it so much now that the service can't start. The problem I do see popping up is something like: ** (nm-applet:2622): WARNING **: <WARN> applet_dbus_manager_start_service(): Could not acquire the NetworkManagerUserSettings service. Message: 'Connection ":1.24" is not allowed to own the service "org.freedesktop.NetworkManagerUserSettings" due to security policies in the configuration file' (had to pull message from online, don't remember the exact message) I've tried installing and reinstalling, doing a purge uninstall. Next thing I was going to try is an aptitude uninstall of all of the dependencies in case something got weird in the upgrade.
I have been using Debian for around two years now. I have a small home server running Debian stable i386 and keep it regularly updated (once or twice a week I perform apt-get update and afterwards apt-get dist-upgrade). The system was originally installed with Debian Wheezy and afterwards upgraded.
However, after entering dist-upgrade tonight, around 42 packages had to be updated. I agreed and afterwards got some errors. After apt-get install -f, the result is as follows:
Code: Select allnickolay@tegulicium:$ sudo apt-get install -f Reading package lists ... Done Building dependency tree Reading state information ... Done
After rebooting the system, I am presented with the Debian Maintenance mode (root password for maintenance or Control-D to continue).
I tried dpkg --configure -a, apt-get install -f and aptitude install -f.
Unfortunately, still no resolution of the conflicts.
I assume this has to do something with the new Jessie 8.2 release ...
After yesterday's apt-get dist-upgrade, I lost my higher screen resolutions. Only had 800x600 and 640x480. After trying to re-install the Nvidia drivers several different ways without success, I ended up purging xorg and xserver and then starting from scratch, re-installing the drivers. In doing so, I either found the problem, or created another, ha.I think part of the problem was that I mixed Nvidia proprietary and debian installations and the update broke the drivers.I am now unable to install xorg or xserver because I can not remove/purge libgl1-nvidia-alternatives.
Reinstalled Debian Squeeze (64bit/gnome) on my Notebook using Netinstall. Everything worked like always but in the setup instead of typing in a root password as asked to i just pressed enter (in the hope of not having to type in a pw in the console later, just having to press enter then)
When i needed rootpw to install some software (using SoftwareDownloader) the normal loginpw seemed to work, but not in the console. ari@HP625:~$ su - Password: su: Authentication failure
I use Debian testing for six months and I started used it six months ago. I use apt-get distupgrade for long times , but today after apt-get update and apt-get dist-upgrade , my system reboot and can not boot and I see URL...and system can not , I see this errors after grub
My friend has an ubuntu 810 machine and he wants to remove it and install debian on that.Instead of cleaning and installing, I thought why not change the sources.list and do a dist-upgrade to debian. In case it is required, I dont mind purging packages like x or desktop etc. from ubuntu to make it thin before upgrading to debian.Has anyone tried this approach instead of a clean install?
I'm running debian testing on my laptop. This morning when I ran apt-get update && apt-get dist-upgrade, I was greeted by the following errors:
Code: Select all
Calculating upgrade... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information to resolve the situation:
The following packages have unmet dependencies:
libcurl3-gnutls : Depends: librtmp1 (>= 2.4+20131018.git79459a2-3~) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
A quick search found out that package librtmp1(2:2.4~20150315.gita107cef9b-dmo1) is already installed.
I do have some packages set on hold, however I don't think that's the problem:
Code: Select all$ dpkg --get-selections | grep hold hostapd hold libgcrypt11:amd64 hold linux-image-amd64 hold
My sources.list on which I haven't touched for a very long time:
Code: Select alldeb http://mirrors.163.com/debian/ testing main non-free contrib deb-src http://mirrors.163.com/debian/ testing main non-free contrib
deb http://mirrors.163.com/debian-security/ testing/updates main contrib non-free deb-src http://mirrors.163.com/debian-security/ testing/updates main contrib non-free
deb http://mirrors.163.com/debian/ testing-updates main contrib non-free deb-src http://mirrors.163.com/debian/ testing-updates main contrib non-free
Last night I tried updating from Testing to Sid. Big mistake. Not sure what I did wrong... I changed my repos to sid, and did the usual update / dist-upgrade / autoclean / autoremove. I did not see any significant error messages during the update process. Now, I had fluxbox, gnome and openbox installed. The weird thing is after rebooting I could no longer boot into gnome or openbox as they had merged into something GNOME/Openbox, which was essentially the openbox panel, the nautilus menu on right click, and nothing else. So I purged them both but now when I try to reinstall gnome I get unresolvable dependencies (at least in the sense that both apt-get and aptitude fail to resolve them). fluxbox is still working fine, although it's missing a few things as I was using many gnome apps inside fluxbox.
I made the terrible mistake of upgrading my live Debian Lenny web server with the the dist-upgrade option in apt-get. I didn't realize this was actually an unstable upgrade and now I have had to make all sorts of choices of what configuration files to keep or upgrade ect. The apache conf files were actually bad after the upgrade and I had to replace them with the backups (phew) and the system is currently still up and running. However my virtualmin installation is no longer working due to a issue with perl ( but thats another question I guess to ask somewhere else maybe ). Anyways... I'm very scared to restart because my server is co-located somewhere else and Im the only one who has ever worked on this server so I would need to go there and fix it myself if it doesn't restart. Basically I have two questions.. is there an easy way to move back to stable packages..If so is this recommended?
And also I'm currently trying to fix some broken dependencies in the package manager but when I run "sudo aptitude -f install" It keeps telling me it is going to remove all of these packages (listed below), some of which I know are very important to the system and I cannot figure out why it would keep trying to do this. I get an error on "phonon-backend-xine" whenever it tries to upgrade just saying this
"(gtk-update-icon-cache:12343): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory"
I installed some desktop related packages a while back like gnome-desktop and I know the package is related to this, but all I really care about is making sure the server stays online and not about the desktop packages. I tried just removing kdebase-runtime and anything else that is dependent on it, but it wont let me do anything at all without fixing this broken package.
I really would just like to go back to lenny stable again but I know its probably too late since I already had it install a new kernel and grub 2 (auto configuring my new grub.list)..