Since update-manager was removed from Debian Jessie, I am looking for something similar or a way to install update-manager for 8.2. I would like a GUI.
I have tried gnome-packagekit, but some of the commands don't appear to work or it seems incomplete and I don't know of a way to test to make sure that it is working.
Other sites recommended to use smartpm. However, I cannot seem to find the plugin xfce4-smartpm-plugin in [Xfce Goodies] that would work as a notifier.
Unattended-upgrades does not meet my specifications, because to my knowledge there is no GUI configuration for this.
Though Debian Jessie is a great distro, I am finding it difficult to recommend to some newer users because it does lack a GUI updater/notifier at this time.
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 installed jessie 8.1 and wmii ( Version: 3.10~20120413+hg2813-8) and I use a basic wmiirc.
Code: Select all:~/.wmii-3.10$ ls -la wmiirc -rwxr-xr-x 1 root root 8033 août 1 17:28 wmiirc
If I want to run wmii the system says:Code: Select all:~$ wmii
wmii: fatal: another window manager is already running
Some information :
Code: Select all~$ update-alternatives --config x-window-manager Il existe 3 choix pour l'alternative x-window-manager (qui fournit /usr/bin/x-window-manager).
Sélection Chemin Priorité État ------------------------------------------------------------ 0 /usr/bin/wmii 60 mode automatique 1 /usr/bin/metacity 60 mode manuel 2 /usr/bin/mutter 60 mode manuel * 3 /usr/bin/wmii 60 mode manuel
I believe this has something to do with an mdadm update which was included in the release. When I configured the array, I didn't partition the disk devices, so maybe that has something to do with it. I am thinking of rebuilding the array and partitioning prior to build, but a quick fix would be referable.
And also something appears to have happened to the raid device since the update.
Prior to update, the array was /dev/md0 - now it is /dev/md/0 which is a symbolic link back to /dev/md0.
mdadm --detail --scan now reports /dev/md/0 where previously it reported /dev/md0
I created a new RAID1 array on a fresh system and immediately after the create, these messages appear at 5 minute intervals.
I have a quite simple installation of Debian 8 Jessie XFCE and the resume from suspend is not working 9 out of 10 times. The system is single booted if that matters. I have found a few solutions to this problem but they were not suitable to my case as I don't have an Nvidia GPU but only Intel Onboard:
Code: Select all# lspci -v 00:00.0 Host bridge: Intel Corporation 82Q35 Express DRAM Controller (rev 02) Subsystem: Hewlett-Packard Company Device 2818 Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=0b <?> Kernel driver in use: agpgart-intel
When I try to resume, I can hear the system booting but I can't see anything on the screen and the keyboard is not working either (no light on Num Lock and Caps Lock). The only option is to press the power button for a few seconds to stop the machine and then push again to start booting again.
I always get this error message from my update notifier an error occurred, please run Package manger from the right-click menu or apt-get in a terminal to see what is wrong. The error message was: 'Unknown Error" '<type 'exceptions.SystemError'>' (E:Opening configuration file /etc/apt/apt.conf.d/99synaptic - ifstream::ifstream (13:Permission denied))' This usually means that your installed packages have unmet dependencies
I have used Debian on this computer for over a year now. A little while back update manager stopped working. It now prompts me to update a varying number of packages (85-97), but when I try and run it I get this message:
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. E: _cache->open() failed, please report.
I'm not sure where to report this. I'm the only user of this computer. I tried running dpkg as directed, but that results in the following:
shop-amd-rebuild:/home/steve# dpkg --configure -a Setting up linux-image-2.6.26-2-amd64 (2.6.26-26lenny1) ... Running depmod. Running mkinitramfs-kpkg.
In trying to get openbox running in new Jessie installation, I followed an instruction in openbox.org: Help: XFCE/Openbox.
" If you want to use the Openbox root menu instead of Xfce's, you could terminate Xfdesktop by running the following:"
Code: Select allxfdesktop --quit.
That eliminated everything on the desktop except the Debian8 background image and the panel clock and made it impossible to do anything other than log out via a right click on the panel. Shutting down and rebooting just brings back the same situation. No terminal available.
After I upgraded debian wheezy to debian jassie I cannot find how to switch off the computer from GNOME and XFCE. On GNOME I even cannot see a logout button. Where is it hidden?
I have just updated my Squeeze system. The update included a newer version of network-manager (and it can not be more than a few hours old). After the update all network functionality on my machine (via knetwork-manager) is broken. The GUI applet has no effect.
Hence can anyone help me: a) Downgrade network-manager by one version; b) Find out what is causing knetworkmanager to break; c) See if the problem is with knetworkmanager or network-manager.
I am currently using Debian Testing, managing my wireless connection with NetworkManager and the Gnome nm-applet. Both have just been updated: network-manager from 0.8.1-6+squeeze1 to 0.8.2-6 and network-manager-gnome from 0.8.1-2 to 0.8.2-4.On installation of the new packages, I have no problems. However, on a reboot, I can no-longer connect to any wireless connection. I am not prompted on start-up for the password to unlock the Gnome keyring and when I left-click on the nm-applet icon and then click on a network to connect to it, nothing happens.I do not think this is a driver or NetworkManager daemon problem. If I run "nmcli dev wifi" or left-click on the applet icon, NetworkManager seems to scan for wireless networks properly and returns a list including the one I wish to connect to.
I receive these messages after I enter my user_id and password in Ubuntu 9.04;
"An error occured while loading or saving configuration information for update notifier. Some of your configuration settings may not work properly." then clicking on details box this can be seen;- {Failed to connect configuration server; some possible causes are that you need to enable TCP/IP networking for ORBIT, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Could not send message to gconf daemon: Message did not receive a reply (timeout by message bus))}
then there's another error message;
"An error occured while loading or saving configuration information for evolution-alarm-notify. Some of your configuration settings may not work properly." then clicking on details box this can be seen;- {Failed to connect configuration server; some possible causes are that you need to enable TCP/IP networking for ORBIT, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Could not send message to gconf daemon: Message did not receive a reply (timeout by message bus))}
when I try to update my Debian, I have the following internal error:Error message:Fetch failed: W:Failed to fetch [URL] Unable to find expected entry free/binary-i386/Packages in Meta-index file (malformed Release file?), W:Failed to fetch [URL] Unable to find expected entry free/binary-i386/Packages in Meta-index file (malformed Release file?) , W:Failed to fetch [URL] Unable to find expected entry free/binary-i386/Packages in Meta-index file (malformed Release file?), E:Some index files failed to download, they have been ignored, or old ones used instead.
When I insert a dvd-rom I dont get the option for the file manager. I do get k3b, vlc,dragon and two other options. Im guessing this is a bug since this didnt happen with Wheezy. When I insert a dvd data disc I do get the file manager option. Strange this is, after inserting the data disc, removing it and then reinserting the dvd-rom I see the option for file manager. How can I get the file manager option to show everytime I insert a dvd-rom? I tried to,create a new option in system setting but man is that stuff confusing.
i,want to be able to browse a dvd-rom movie/video using dolphin when i insert one. I want open with file manager to be one of the choices. I think file manager is the choice.
I recently upgrade from wheezy to jessie. I had a problem with the icons and solved it. Now when i place the xfce4-power-manager-plugin on the panel, the plugin is using more RAM than it needs. Currently its using 960 MiB. Yesterday it used about 3 GiB of RAM. It doesn't happen if the plugin is removed from panel.
Command in task manager: /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libxfce4powermanager.so 20 20972767 power-manager-plugin Power Manager Plugin Display the battery levels of your device and control the brightness of your display.
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?
I installed Debian Jessie on my Hummingbaord. I use it with apache, owncloud and minidlna but after some days i rebooted the system and then i can't log in with SSH anymore.
The message I get:
Access denied Using keyboard-interactive authentication. Password:
And this again and again, although I enter the right password. If I login directly on the Hummingboard all works normally...
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 have installed debian 8.8.1 stable and run updates. When I run the cat release command it shows stretch/sid. I made no changes to the apt/sources list.
What do i have to do so it only updates with the stable release I am planning to use it as a server and only want stable fixes.
Configuring gpsd with Wheezy was a breeze. Just had to run "sudo dpkg-reconfigure gpsd", answer a few questions, and it worked like a charm. With Debian Jessie the following happens:
tsi@sxf-tsi:~$ sudo dpkg-reconfigure gpsd Warning: Stopping gpsd.service, but it can still be activated by: gpsd.socket Creating/updating gpsd user account... tsi@sxf-tsi:~$
How does one bring up the gpsd configuration dialog with Jessie?
I've after latest jessie update a problem with service samba restart. If I use "service samba restart", there is a timeout (after long time) and error.
Output of "systemctl status samba.service":
Code: Select all● samba.service - LSB: ensure Samba daemons are started (nmbd and smbd) Loaded: loaded (/etc/init.d/samba) Active: failed (Result: timeout) since Mo 2014-10-20 02:16:57 CEST; 7s ago Process: 6205 ExecStart=/etc/init.d/samba start (code=killed, signal=TERM)
Okt 20 02:16:57 server systemd[1]: samba.service start operation timed out. Terminating. Okt 20 02:16:57 server systemd[1]: Failed to start LSB: ensure Samba daemons are started (nmbd and smbd).
[Code] ....
Whats going wrong. "service samba restart" should bring no error message if the service is not running previously.
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?
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?
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):
