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
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'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 the author of an internet radio for the Raspberry PI originally running on Debian Wheezy. The radio (radiod) service is started and stopped using the usual service commands:
service radiod start|stop|status
Since upgrading to Debian Jessie the service status and stop routines in my radio daemon are no longer called.
For example:
# service radiod status
● radiod.service - LSB: Raspberry PI Radio Daemon
Loaded: loaded (/etc/init.d/radiod)
Active: active (running) since Thu 2016-03-31 20:17:07 CEST; 15h ago
Process: 380 ExecStart=/etc/init.d/radiod start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/radiod.service
└─603 python /usr/share/radio/ada_radio.py start
If I call my program (which runs as a daemon) I see the status message from my program
# ./radiod.py status
radiod running pid 603
I have established that service stop never calls my program routines to shutdown the radiod daemon when the system is rebooted (I see that from my log files).
The reboot hangs for about 5 minutes whilst stopping the radiod service (because stop never calls my stop routines).
Below is my radiod script, which is fairly conventional, and which has been working all the time until I ported to Debian Jessie.
/etc/init.d/radiod
#!/bin/sh
#
### BEGIN INIT INFO
# Provides: radiod
# Should-Start:
# Should-Stop:
[Code] ....
I'm just completing an upgrade from wheezy to jessie and get the following error
Code: Select allProcessing triggers for initramfs-tools (0.120) ...
update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
E: intel-microcode: unsupported kernel version!
With a message like this I'm wondering if it's safe to reboot as well as how to resolve.
Is this somehow related to the change to only update the microcode on boot as reported earlier in the upgrade?
Code: Select allintel-microcode: microcode will be updated at next boot
I eventually gave up and migrated to mdadm. Works just fine. Having upgraded to jessie and solved one problem
[URL] ....
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
[URL] ....
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.
[URL] .....
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 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
00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device 2818
[CODE]..
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.
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?
View 3 Replies View RelatedI keep most of my files on my server, but fiddle with them using NFS from one or another of my laptops - so they all have static IPs assigned by my router. If I want extra speed I plug in an Ethernet cable. My old DI524 wireless G router seems quite happy to have two MAC addresses (Ethernet and wireless) assigned to the same static IP, so long as I don't try using both simultaneously. However three Wireless N routers I've tried won't allow this, nor will dd-wrt.
I really don't want to have to set up every laptop as two separate hosts on my network. 'orrible complications.
Best solution I can think of is to get the Ethernet card to spoof the wireless MAC address with e.g. macchanger, as per this excellent page here: [URL] ....
I don't mind running a script manually to do that on each occasion.
This works perfectly on my old R50 Thinkpad running Debian Squeeze, but on my R60 (running Wheezy) and T400 (running Jessie), macchanger works initially, BUT as soon as I hit 'enable networking' in the Network Manager applet, the ethernet card reverts to its original setting. So of course then my router allocates a random IP and so NFS won't work.
Exactly the same goes for the iproute method 'ip link set dev eth0 address [fakemac]' - ifconfig shows it's worked, but it reverts as soon as NetworkManager goes back up.
I don't know where Network Manager (if it is that) is getting the Ethernet card's original MAC from, it seems to be listed in /etc/udev/rules.d/70-persistent-net.rules, so on the T400 (Jessie) I've even tried creating a file in /etc/udev/rules.d/75-mac-spoof.rules along the lines suggested in that archlinux page I mentioned -
ACTION=="add", SUBSYSTEM=="net", ATTR{address}=="[original MAC]", RUN+="usr/bin/ip link set dev %k address [fake MAC]"
but it seems to have no effect.
Short of reverting to Debian Squeeze on all my laptops, I don't know what else to do. Or getting into my router and reassigning the IP / MAC address by hand every time (!).
(If there's a better way to swapping easily from wireless to Ethernet when required, I'd like to know.)
Using x11vnc server on Debian host, and TightVNC viewer client on Windows 7. All was working fine until a server host upgrade, from Wheezy to Jessie. Now, when I try to connect, TightVNC retrieves the certificate as normal, compares and accepts it, and starts stunnel. The next step would normally be to prompt for the VNC password.
Instead it gives an error:
ReadExact: Socket error while reading.
I'm guessing that some thing is missing or misconfigured after the Jessie upgrade, which broke many other things too, as Debian upgrades always seem to do. I have removed and reinstalled the x11vnc package, no effect.
The errors in the log file don't mean a lot to me.
The server is started with this command:
Code: Select allx11vnc -ssl -display :0 -usepw >>vnc-log 2>&1 &
If I start it up without the -ssl flag, and connect from the Windows system with a different client (Mobaxterm) it all goes well.
Relevant part (tail) of the server log file:
Code: Select allThe SSL VNC desktop is: myhost:0
PORT=5900
SSLPORT=5900
19/01/2016 12:31:10 SSL: accept_openssl(OPENSSL_VNC)
19/01/2016 12:31:10 SSL: spawning helper process to handle: 192.168.2.3:51942
19/01/2016 12:31:10 SSL: helper for peerport 51942 is pid 11193:
19/01/2016 12:31:10 connect_tcp: trying: 127.0.0.1 20000
[Code] ....
I have dist-upgrade from Wheezy to Jessie, however it randomly freezes. Everything was okay with kernel 3.2, but when I run several applications kernel 3.16 fails.
At below you can see the dmesg output of Jessie:
Code: Select all[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1+deb8u6 (2015-11-09)
[Code] ....
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..
I am trying to clean install Jessie 8.3.0 onto an old PC, where I already have wheezy 7.7 working. I am using the 3 DVD- i386, which passed the integrity check.
Installation goes on smoothly till completing the "Select and Install SW" stage from 1st and 2nd DVD. At this point I get the warning that "Installation step failed, ..", giving the choice to repeat.
When repeated, the process gets completed (without asking for 2nd DVD), the new installation boots normally, but the KDE desktop opens irregularly, with some basic applications missing, and some flaws during certain operations.
The APT does not show any missing/broken link. I tried and repeat the installation with different choices as for kernels and/or desktops, but got the same result. I cannot guess where the problem originates, nor whether it is a known bug of the installer.
My server has 4 1Gb eth interfaces, and an additional Broadcom dual 10Gb card. It runs Debian Jessie.Problem is, that the card fails to load, although it is identified, and its drivers is installed.I tried to update the driver with apt-get install firmware-bnx2x, but it was already up to date.
Code: Select allroot@pxe-server:~# lspci |grep -i broadcom
03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
03:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
03:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
03:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
07:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 10 Gigabit Ethernet (rev 10)
07:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 10 Gigabit Ethernet (rev 10)
[code]....
I have been happily running Wheezy on the Chromebook Pixel with little or not issues. Recently I needed to re-install and decided to try Jessie. Again I was following the excellent instructions at [URL] .... except with the Jessie image.
However everytime I went to install it (after adding in the mem=4G line) it just rebooted and brought me back to the same install screen again. I just downloaded the Wheezy image again and it is installing now perfectly.
As the subject states i have a desktop with a radeon 9200 card, when i install the firmware-linux-nonfree the system hangs when x starts(sometimes you can see the login manager, sometimes not, but you cant login at all) and i cant access any of the terminals ctrl+alt+f(1-6), after removing the firmware-linux-nonfree package the system boots, but the graphics are under software render...
View 3 Replies View RelatedI have tried to download the latest XFCE Live CD 8.3.0 i386 both by HTTP & torrent & have tried the same at various mirrors but the download consistently fails.
View 1 Replies View RelatedI am running Jessie 8.2, upgraded from Wheezy about a week ago.
KDE Desktop, static IP
NetworkManager.conf shows:
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=true
dns=none
The dns=none is to keep NetworkManager from overwriting /etc/resolv.conf (which shows):
nameserver aaa.bbb.ccc.ddd
nameserver aaa.eee.fff.ggg
nameserver aaa.hhh.iii.jjj
search mydomain.com
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...
I use debian jessie 8.1 and when i boot it, pc start fsck block clean etc.. but the fsck control is activated every on boot?
View 14 Replies View RelatedWhen 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.
View 4 Replies View RelatedConfiguring 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 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?
linux-image-3.14-0.bpo.1-amd64
linux-image-3.14-0.bpo.2-amd64
linux-image-3.16-0.bpo.2-amd64
linux-image-3.16-0.bpo.3-amd64
linux-image-3.2.0-4-amd64
How about results shown by deborphan?
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
[code]....
DE: lxde
version: Jessie
using xorg file: no
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):
Code: Select allxrandr --setprovideroutputsource 1 0
xrandr --output VGA-0 --primary --mode 1680x1050 --pos 0x0 --rotate normal
--output DVI-0 --mode 1680x1050 --pos 0x1050 --rotate left
--output HDMI-0 --off
--output VGA-1-1 --off
lxpanelctl restart
Additional info:
Code: Select all$ inxi -G
Graphics: Card-1: Advanced Micro Devices [AMD/ATI] Oland PRO [Radeon R7 240]
Card-2: Advanced Micro Devices [AMD/ATI] Oland PRO [Radeon R7 240]
Display Server: X.Org 1.16.4 drivers: ati,radeon (unloaded: fbdev,vesa)
Resolution: 1680x1050@59.88hz, 1680x1050@59.95hz
GLX Renderer: Gallium 0.4 on AMD OLAND GLX Version: 3.0 Mesa 10.3.2
[Code] .....
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?
