Debian Configuration :: Apt-get Auto-remove After Installing Jessie
Jun 20, 2015
After installing Jessie, apt-get gives me a huge list of packages with the suggestion to autoremove them. Now, I've tried auto-remove once and was left with a naked Gnome, so I was wondering if there's another way to find out which packages I should keep and which I can safely remove. Is it safe to delete packages that cannot be found using the search function for the stable release? I checked them one by one here URL....How about linux images that won't appear in the above search?
The apt-get autoremove command, I use Debian 8 for some time now and I often install a package, test it for some minutes and remove it then. I noticed that in most cases (if not all, I'm not completely sure) all the dependencies that were installed with the package (mostly libraries, of course) stay installed on the system when I remove the package.
And there is no output of apt-get that there are unnecessary pacakges which I can remove with apt-get autoremove. The autoremove command does nothing.Before I changed to Debian, I used Ubuntu and there all the dependencies are removed with apt-get autoremove when I uninstalled a package.My question is now, is this normal? if there are fundamental differences in which packages "autoremove" removes between Debian and Ubuntu?
I press On-button, Debian boots, logs in and automatically connects to the Wireless network AND! to my local pc via LAN. It runs an ssh server, so I can ssh into debian over internet and communicate with the local pc (send a magic packet).Here are my problems:
1) I don't how to log in automatically. This and this doesn't work. 2) I need a network tool that can manage multiple connections and has a reconnect feature. With the default network manager I cannot even connect to more than one network simultaneously although I have two network devices of course.
And I guess I can run all that in console mode, right?
It seems like ifconfig used to show which DNS servers were being addressed, but something has changed, I need to know whether I am referencing what I think I am... I have search this forum, googled, and come up empty... did the metrics go away with 8.2? Was I dreaming at 7.5?
So, I did the upgrade to Jessie today and everything went fine and I do like the gray look of the Gnome Classic Desktop. Not much change here.
But it is impossible for me to install the 3.16 kernel.
When I try, I get the following error (sry, it's german, but you should get the point):
Code: Select allE: /var/cache/apt/archives/linux-image-3.16.0-4-amd64_3.16.7-ckt9-3~deb8u1_amd64.deb: Extrahierte Daten für »./lib/modules/3.16.0-4-amd64/kernel/drivers/media/rc/winbond-cir.ko« können nicht nach »/lib/modules/3.16.0-4-amd64/kernel/drivers/media/rc/winbond-cir.ko.dpkg-new« kopiert werden: Es konnte nicht geschrieben werden (Auf dem Gerät ist kein Speicherplatz mehr verfügbar)
It basically says, there is not enough space on /lib to copy the modules for the new kernel. (I have about 100M free there.)
So, as you can see, there isn't that much space on / at all - don't blame me, blame the Lenny Installer. Personally I can live with the 3.2 kernel but I wonder if there is any possibility to install the never one without a total re-partitioning.
I have a relative fresh install of jessie in which I face a high cpu usage of java (top shows about 165% CPU and 12% MEM). The problem occurs right after booting the computer. These values stay constantly high for days if I leave the box running. This happens even if the computer is just sitting there without doing anything.
I have to kill java to go back to normal. So, when I do a Code: Select allkillall -KILL java the problem goes away. After that it doesn't reappear and I can use all apps installed without a problem.
Currently I am based on openjdk Code: Select allupdate-alternatives --display java java - auto mode link currently points to /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java - priority 1071 slave java.1.gz: /usr/lib/jvm/java-7-openjdk-amd64/jre/man/man1/java.1.gz Current 'best' version is '/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java'.
But I have also tried the SUN version with the same result.
Where to look to find more information on what exactly java app is using so much resources and how I can solve it? I guess I could just put somewhere in rc.d a kill java command and forget about it but I would really like to find out whats going on...
When i'm tried google there is lots of bootlogd related document there. [URL] .... Yes there is documentation. But I'm only need "enable boot logging","reading boot log". Bootlogd not worked on jessie/stretch.
I want to learn Apache Spark and I wanted to install it on a Debian Jessie pc, but it seems the packages are not in the repository. Should I download it and install it manually?
What is the best choice for the underlying distributed file system. Obviously I need to setup a stack of tools as simple as possible. Any link to tutorials for Spark on Debian, I keep finding stuff for Ubuntu.
Fresh Jessie installation with KDE desktop. Installed from Disk 1 of the dvd images. Can't figure why apt wants to remove this stuff. The only packages I removed from the base installation was iceweasel, and juk. I'd like to autoremove to clean out the amarok stuff but I'm afraid it will take all the rest with it. What do I do about this, and or how do I fix it? Does apt have a setting where if an app isn't used for x amount of time it deems it useless for removal?
Code: Select allCalculating upgrade...
The following packages were automatically installed and are no longer required: amarok-common amarok-utils apper apper-data ark cdparanoia cdrdao clamz dvd+rw-tools easy-rsa genisoimage growisofs gwenview htdig hyphen-en-us iputils-arping k3b k3b-data k3b-i18n kamera kate kcalc kdeplasma-addons kdesudo khelpcenter4 kio-audiocd kmix kopete kscreensaver ksnapshot libappstream1
I'm new to Debian, and there's something I don't understand about the packages marked as automatically installed. They are supposed to be removed by "apt-get autoremove" if no other packages depend on them, right? Well, I've installed xserver-xorg-video-ati which pulled *video-radeon, *video-r128 and *video-mach64. I later realised that I only needed *video-radeon, and got rid of xserver-xorg-video-ati and the other two. The thing is... xserver-xorg-video-radeon is still there, even if only xserver-xorg-video-ati and xserver-xorg-video-radeon-dbg depend on it, and neither are installed in my system.
I am having trouble using touch pad in jessie. My touch pad was ok when it's in wheezy but after i updated to jessie, i can't really get used to it.
I don't know whether i setting it up wrongly, sometimes, my touchpad will keep dragging, without releasing. And if I click the bottom right of the touch pad, it's not right click; instead i have to use two fingers.
etc. So how can i change to back to a more traditional usage? Also, do jessie have a setting like ubuntu saying disable touch pad while typing?
Upgraded webserver to Jessie as an upgrade to Wheezy produced errors, and before reboot everything was up and running, but as all upgrade docs and info I read, I rebooted the server. However it never came back. I have the original backup files before I did the Wheezy upgrade. I also have access by Rescue to the server.Made a back up of critical files and have a 24GB tar file and I can connect by SFTP.
how to check the Debian files... Grub etc.. I would prefer to find the issue than start again.I am not able to sudo from Putty. I cannot run apt-get update. I did go to chroot, but then I get unable to resolve host errors and Could not open lock file because Permission denied errors and asking if I am root.There is information by googling for start up issues, but as I am working remotely with a Rescue set up, a lot of the commands I see and have tied do not work.
A few days ago I upgraded from debian 7 to 8. First I update, upgrade and dist upgrade - change source list and again update, upgrade and dist upgrade.When inserting a USB disk on key, it works okay. When plugging my WD "My passport" backup USB disk it does not work. The automatic mount works, but the disk can be accessed.I tried to do it manually in a format that worked on debian 7..Manual mount fails too.
umount My passport fdisk -l (to see device name) mount -t vfat -o rw /dev/sdb1 /media/kuku/usb_mp4 dmesg | tail [ 2381.080822] sd 9:0:0:0: [sdb] No Caching mode page found [ 2381.080828] sd 9:0:0:0: [sdb] Assuming drive cache: write through
After changing my video cards from gigabyte HD5450 and saphire X550 to two saphire r7 240s one of my debian installs no longer supports rotating the monitors either with 'Monitor Settings' or xrandr. The only difference between these 2 Jessie installs is that one was upgraded and the other one was fresh. The problem is with the upgraded one. On the fresh installed debian I just put the ati proprietary driver so I won't do further testing on it but xrandr was working fine on it before that.
I tried going over the ATIHowTo [URL] .... and everything looks good. Tried purging the non free firmware and reinstalling. I verified the version numbers of libxrandr2 and kernel of both installs. It is either some scrap left over from wheezy or a configuration file I am not aware of.
So what actually happens is xrandr does not say anything, blanks out all windows on the screen with only their background color and title bar showing, changes the lxpanel to its background pattern except for 2 blanked out boxes almost to the right of the screen( I have 10 tray icons there before it blanks), activates the screen I wanted to rotate with the proper rotation. On my main screen I can't click on anything. On the rotated screen I can right click and I get my openbox right click menu like I do on my main monitor before the command but when I try to run something nothing happens. The only way I can get out of this situation is to go to ctrl-alt-f1, log in as root and type 'service lightdm restart'.
Both of these monitors are connected to the primary video card, an ati r7 240 saphire. The main one is on vga and the other one is on DVI. I also have another monitor connected to HDMI but it's not being used. I have yet another monitor connected to the VGA of the secondary GPU I don't think it's a problem is it? I tried not using 'xrandr --setprovideroutputsource 1 0' and it still did the same thing.
I tried just launching openbox with no LXDE and it did the same thing.
Also another strange thing is when I stop the lightdm service and try to 'startx' or 'xinit' my screens go blank; numlock, control-alt-delete and control-alt-f1 do nothing and the only thing I can do is an emergency REISUB. I didn't configure this install to use startx or xinit yet but should it really lock up my system?
On the affected system my script looks like this (I already did this step by step and the 'rotate left' line is causing the problem):
I am using Jessie with XFCE and I tried to write a service which executes a script to change my wallpaper. When I try to start the service with systemctl start wallpaper.service it fails and I get the outout below from systemctl status wallpaper.service
I don't think it to be a permissions issue, they are -rw- r-- r--
This service is called by a timer that goes off daily. Below is wallpaper.service
I've recently noted that the boot process in my Jessie installation is occasionally taking longer than usual, not dramatically as in "really hanging", but still noticeably slower, during which some messages are printed along the lines of
Code: Select alla starting job is running (2 of 5) and also after that, once lightdm (I'm using the MATE desktop) comes up the screen gets painted slower as well.
Unfortunately, once the system is up and running there's no longer trace in the logs (either traditional syslogs or journalctl) of such messages, however what comes to mind is that I've just recently enabled persistent logging in systemd: could this be the reason of such (occasional) slower boot process?
Other than that, what else could cause such behaviour? What should I eventually check to ensure things are OK?
I built a kernel-module for a new usb wifi-card. This worked well and resulted in a 8821au.ko-file. But now I'm trying to load this kernel module since half an hour and it doesn't work. I copied the ko-file into /lib/modules/3.16.0-4-amd64/kernel/drivers/edimax. If I just type
Code: Select allsudo modprobe 8821au
I get a
Code: Select allmodprobe: FATAL: Module 8821au not found..
But if I enter the full path inside the /lib/modules/3.16.0-4-amd64-folder:
to /etc/modules but this also doesn't seem to work. When booting I get an error-message, but it's too fast to read it and I can't find the right log-file, where the booting-part with the "[ OK ]"-messages is reported.
So my driver is ready, the onliest thing which I can't get working is loading it as a kernel-module.
I'm just trying to install a Jessie i386 image in Oracle Virtualbox.
My host specs are: Windows 7 Home Premium x64
Wheezy is installing correctly, but Jessie is not. It fails during the partitioning of the disk, and gives an error message like: unable to write to disk, start = 236342 length = 0. This is not the exact message but I'm unable to try again at the moment.
When I install Wheezy and apt-get update / upgrade to Jessie, I get a black screen after reboot..