Debian Multimedia :: Mondo Rescue Not Working On Jessie
May 9, 2015
i can't use imondo restore anymore, due to upgtading to jessie, did aynone get to make it work with jessie. I love to use mondo restore because i can get hots backpus, and i can do partial restore so i can restore my full system preserving home foldest, other way i have to move my home folder, very much waste of time. I cant get installed it but it doesnt open up, it says mondo, mindi bad installed or something like that.
I install CentOS 5.5 from DVD, set root password and log in as root. Then I install Mondo Rescue backup solution, make a backup and restore from it. After that, the system boots just like before, but I cannot log in. When I enter the right password, a couple of lines of text flicks briefly on a screen, too fast to read and the it returns to the initial password prompt. When I enter wrong password, it says "Login incorrect".What am I doing wrong?
I am sending a message to mondo-devel mailing list, but I suspect the root of the problem lies in CentOS, or something that I do wrong with it?I have installed both i386 and x86_64 versions of CentOS 5.5 from DVD's, the problem is the same.I'm running this on a separate machine that I have just for experiments with CentOS and virtualization. I install CentOS with defaults except I uncheck "Desktop - Gnome" and check "Virtualization". I can reinstall if needed.
Yesterday I used the Live DVD's Rescue Mode to re-install Grub(2) in the MBR of my hard drive. Today, I am surprised to see a very different /etc/apt/sources.list file that only has one line, as follows:
Code: Select alldeb cdrom:[Debian GNU/Linux 8.2.0 _Jessie_ - Official amd64 DVD Binary-1 20150906-11:13]/ jessie contrib main
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
[Code] ...
Note also that this whole time, gdm3 has been running:
Now i want to create a resue disk for my Centos5.5i think mondoArchive tool is best for this job.i installed mondo by usingyum install mondoand it is intalled successfullybut i cant see it inApplication>sytem toolshow can i run it in a GUI mode.
I have a problem with compiling bibliography in Latex running on Debain Jessie. I have even tried to compile the stock example provided by ShareLatex web site, and it still doesn't work.I keep getting same error messages, when I run my own files AND the stock example:
I found no citation commands---while reading file document.aux I found no ibdata command---while reading file document.aux I found no ibstyle command---while reading file document.aux
How to get Toshiba Satellite's bluetooth to work. Here is output that I think may be useful.... but I could be wrong. Pretty much everything I have found is outdated, has dead links, or didn't work.
So far, I've learned (at least from what I've understood) it has to do with kernel drivers/modules not working. I'm on Jessie right now since my graphics driver didn't work on the stable kernel.
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
Installed Jessie and added the Nvidia Proprietary drivers. All looks good.
When I open the Gnome Tweak Tool it appears to be working fine but won't change anything. If I click on a check box the check appears for a split second and then disappears. Tried re-starting a few times, same. Haven't found anything relevant on the net yet.
I have a 'little' problem with my vps, which was working before. Here is what I made:
- order an new IP and I was trying to modify /etc/network/interfaces in order to configure the ip - even if I was logged as root, I wasn't able to modify 'interfaces' so I tried sudo and alsoto mount (different commands I found.) - rebooted the VPS
Current situation: I can access ssh, but ispconfig3 and the websites are not working anymore.
I installed Jessie (8.1.0) and encountered a problem which is non-existent in Wheezy (7.8.0).
My shell is zsh and I use tmux both installed from packages, I use this zsh feature that when you type "ls /" and then hit "Tab" twice, it will present you a menu where you can select the directory you want navigating the menu with the arrow keys. It works fine out of tmux (in bare shell) but stopped working inside a tmux session. In bare shell you hit Tab twice and get into the menu, in tmux you hit Tab twice and it displays the table of suggestions but just keeps cycling suggestions (cycling directory names) and not sending me to the menu.
Here's some screenshots:
1) Working (no tmux): I hit tab twice and got in the menu.
2) Not working (in tmux): I hit tab twice and it just cycled directory names after "/"
t isn't in my config file, I tried without my .tmux.conf (with tmux set to default settings) and it still had no effect.
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.
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 have a couple of Logitech wireless mice (M325) with USB Unifying receivers, one for a couple of netbooks (Asus & HP) and one for my old desktop. These have been working very nicely
under 32 bit OSs :-
Windows XP
Debian testing (Wheezy & Jessie)
I now have a new 64 bit desktop (Intel i5) and the Logitech mouse
DOES work with :-
The Bios Windows 7
But it does NOT work with :-
Debian Jessie
I have found an old mechanical Sun 3 button mouse (USB), which has got me working to some extent, but does remind me why I got an optical wireless mouse!
My old 32 bit desktop reports :-
Code: Select all$ uname -a Linux copper 3.10-2-686-pae #1 SMP Debian 3.10.7-1 (2013-08-17) i686 GNU/Linux
I need to get the comparative info off the new desktop, but I am currently hampered by the old mouse and the bug, whereby when I asked for the LXDE desktop I also got Gnome installed, and Lightdm ignores my request to start LXDE and dumps me in Gnome!!
The main differences that I have found was in the modules where the 32 bit one uses uhci_hcd, while the 64 bit one uses xhci_hcd. The dmesg section is like the above, finding the Unifying device, but is missing the last line where djdevice finds the mouse..
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 am having sound issues with iBook G4 running Debain Jessie. I am dual booting Ubuntu_MATE 15.04 and Jessie on the same HD. For PowerpC iBooks and PowerBooks you need to manully load the snd-aoa-i2sbus module in order to open alsamisxer so you can set you PCM Channel. I have done this when I ran Jessie on my PowerBook and sound worked with no issues. Now on this iBook I have ran both Lubuntu and Ubuntu-MATE with sound working by using this method. However when I installed Jessie I loaded the module, got aslmixer to load and set my PCM Channel but no sound.
I've been having problems with audio not working through the speakers since I upgraded to Jessie. I did a fresh install, the same hardware worked out of the box on Wheezy. Audio does work through the headphones - searching Google results in a LOT of similar issues on various distros, but none of the suggestions I've found have worked. Pulseaudio is not installed.
Alsamixer shows that the speakers are un-muted, and toggling the headphone auto-mute in case that was causing problems doesn't work. lsmod shows that snd_hda_codec_hdmi is loaded and in use - could it be trying to send sound via HDMI? Odd, because this laptop does not have an HDMI port. Blacklisting that module doesn't seem to make a difference however.
On install my wifi was working, but when I rebooted it stopped working.Since then I've tried numerous things to attempt recovery of wifi. No luck so far.
I have a problem with my laptop Dell Inspiron 1525 wireless on Jessie Cinnamon.
I have installed the b43 firmware and after that everything seemed working but just for a few seconds.
I have tried to reboot and after that I can't browse the internet just for a few seconds and after that Iceweasel loading and loading and nothing's happening.
I can't surf on the net just with cable but the wifi setup shows everything is okay 95% signal strength and connected. Also tried reinstall the firmware and reboot and it's all the same after.
I recently updated my Debian jessie system (for the first time in a few months). It broke my video driver (fortunately a dpkg-reconfigure fixed that) and my wireless driver (forget how I fixed that...), and my sound. ALSA still thinks I have an output device, I've set volumes all the way up in alsamixer.
In vlc and firefox, I can't hear anything using the default audio out (which I think is pulseaudio), nor can I hear anything if I ask them to use ALSA output directly. I've tried rebooting, killing/manually starting pulseaudio, etc to no avail.
I think it was either the kernel upgrade (went from 3.10 to 3.13) or a configuration option in some sound subsystem that broke. To be clear, sound was working perfectly before the upgrade. My machine is an Ivy Bridge-era Zenbook.
I am running a small Debian Jessie installation on my Zotac Nano AD10 (based on AMD's E-350, Radeon 6310). I use it as an MPD server, it outputs to my receiver over HDMI.
Up until kernel 3.11 that works fine. My GRUB command line looks like this (default grub.cfg file):
Playback device is plughw:0,3 Stream parameters are 48000Hz, S16_LE, 1 channels Using 16 octaves of pink noise Rate set to 48000Hz (requested 48000Hz) Buffer size range from 64 to 16384 Period size range from 32 to 8192 Using max buffer size 16384
[Code] ...
I've tried fixing this repeatedly (3.12, 3.13, 3.14) but everytime i find myself returning to 3.11 because that keeps working.... Some posts suggest running xrandr could get it working, but this is a headless installation, so I cannot use xrandr.
For reference, OpenELEC works on this same system (separate install), and they're up to 3.14 as well. Never had a problem with OpenELEC and the audio not working.
I recently upgraded from wheezy to jessie and everything went as planned with dist-upgrade. However I just noticed that I can't play any video file. I thought about upgrading vlc, as it was already installed but it had dependency problems. So I tried to remove it
Code: Select allsudo apt-get remove --purge vlc
Then If I try to install vlc I receive this message:
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 may resolve the situation:
The following packages have unmet dependencies:
vlc : Depends: vlc-nox (= 2.2.0~rc2-2) but 2.0.3-5+deb7u2+b1 is to be installed Depends: libvlccore8 (>= 2.2.0~pre1) but it is not going to be installed Recommends: vlc-plugin-notify (= 2.2.0~rc2-2) but it is not going to be installed Recommends: vlc-plugin-samba (= 2.2.0~rc2-2) but it is not going to be installed Breaks: vlc-nox (< 2.2.0~pre2-2~) but 2.0.3-5+deb7u2+b1 is to be installed E: Unable to correct problems, you have held broken packages.
Now, I thought about removing vlc-data but I received this message saying that 253 packages will be removed (624Mb worth of applications). Am I uninstalling my entire system with this?
This is my sources.list
deb http://ftp.us.debian.org/debian stable main contrib non-free deb-src http://ftp.us.debian.org/debian stable main contrib non-free deb http://ftp.debian.org/debian/ jessie-updates main contrib non-free deb-src http://ftp.debian.org/debian/ jessie-updates main contrib non-free deb http://security.debian.org/ jessie/updates main contrib non-free deb-src http://security.debian.org/ jessie/updates main contrib non-free
- Debian boots normally - I get the login screen - Once my credentials entered, I see only the grey foreground of the login screen for a couple of seconds, then a black screen with a prompt for like half a second and then I'm back to the login screen. No error message, nothing.
When booting in recovery mode and use startx, it works fine (it's my setup at the moment). From there, if I start gdm3 (systemctl start gdm.service), I get the black screen with a prompt and I can do nothing, I have to shut down directly by pressing the button.I tried to add Debian-gdm user to the video group (even if I don't use nVidia drivers), to replace gdm by lightdm and even to remove any display manager but the issue is not solved.Here are some outputs:
Code: Select all# dpkg-reconfigure gdm3 Job for gdm.service failed. See 'systemctl status gdm.service' and 'journalctl -xn' for details. invoke-rc.d: initscript gdm3, action "reload" failed Code: Select all# journalctl -xn -- Logs begin at Tue 2015-12-29 19:16:26 CET, end at Tue 2015-12-29 20:20:55 CET
[code]....
Since removing gdm didn't change anything, I assume it doesn't have anything to do with it but still.
It's for a Lenovo x140e laptop with Jessie. Specs online commonly describe the laptop as having BCM43142 but I ran "lspci -knn | grep -iA2 net" and the output says I have BCM43228. Not sure why there is that discrepancy but I am assuming the latter, BCM43228, is what is actually in my computer.
Anyway, I originally installed "broadcom-sta-common", "module-assistant", and "broadcom-sta-source", but that resulted in nothing happening so I think I am going to "apt-get purge" those and start over.
I know about the Debian wiki "wl" page but it only provides instructions up to Wheezy, not Jessie. And I read many previous threads but they often contain different instructions and mixed results, plus there are many moving parts here (kernel, OS, driver, packages) and the instructions seem to be changing over time.
Does the order of install for those above packages matter at all? Do I need the kernel header or not and, if so, how do I use it? Are there any other packages I need? What is the process?
I'm trying out a Jessie install and have noticed VNC doesn't work as well as it used to. I often install a desktop environment on a headless machine, disable *dm, and use vnc4server to create a desktop session if I want to use a GUI. When I try to do the same on Jessie, I run into problems.
Using Gnome, all I get is the generic "Oops something went wrong" error. Looking at .xsession-errors, there are some errors that hint at the problem.
Code: Select allXsession: X session started for ryan at Mon Dec 29 06:07:30 CST 2014 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8
[Code] ....
Some possibly related bugs: [URL] ...
The same thing seems to happen with Cinnamon. Since I doubt a fix for the above issue will make it into Jessie, I tried XFCE. However, that doesn't work correctly either. When running XFCE via VNC something is misreporting the version of xrandr as 1.1 instead of 1.4. Since xfsettingsd appears to want version 1.2+, many things are broken.
This post on the Ubuntu forums suggests the issue might be fixed in xfsettingsd version 4.11: [URL] .....
Is there a better way of getting a remote desktop in Jessie that I'm overlooking?
I am using Jessie. 64 bits. I have been using Sound Converter in other distros (LMDE, Ubuntu, etc) in the past.Jessie has Sound Converter 2.1.3. I think I have installed the needed codecs. When I try to convert from mp4 to mp3, the program gets stuck, and nothing happens. Other formats can be converted.
When I use SoundKonverter (also in Jessie, version 2.1.1) it works with no problem, converting from mp4 to mp3. Nevertheless I would prefer to use Sound Converter.
A few weeks ago I have installed Debian Jessie on KDE Desktop Version. I have a problem with the Display Manager Kdm, if i log out session the monitor turns off (DVI No Signal), the only option that I have it's forced shutdown or reboot via power button. I try another DM lightdm and this works fine. But i liked to know why log out session crash on Kdm.
Adding : TerminateServer=true at the end of /etc/kde4/kdm/kdmrc (Section :[X-:*-Core], solve the issue.
