/var/log/syslog is full of messages
/etc/gdm3/Xsession[3408]: ![1433316153,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] #011ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1
What this means and how to fix it?
I installed a Debian server a few time ago, with the Squeeze version.
Now I want to upgrade it to Jessie, but all related documentation only talk about the procedures to upgrade from Wheezy to Jessie.
What should I do? Upgrade first Squeeze to Wheezy and after that to Jessie, or I can upgrade from Squeeze to Jessie?
I upgraded my Wheezy 7.8 to make sure all packages were installed Before taking the next step to upgrade to Jessie.I upgraded to Jessie and it seemed to run OK....but after reboot I had no network Connection..I checked ifconfig and the wrong network card mac address is being assigned to the wrong card....?I have a clonezilla server on my server, so this was my network interfaces before and after upgrade
Code: Select all# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
[code]...
I even checked nano /etc/resolv.conf and sure enough my gateway was the same for my Internet eth0.When I ran ifconfig I could see that the eth0 mac address was set as eth1..I tried to reset my drbl for clonezilla but that only sees the vmware Connection and not my actural cards.. have taken alook at /etc/udev/rules.d/70-persistent-net.rules and the assignment is right but not ifconfig?
With "quiet" removed from the grub linux line, I'm getting the following error messages when the boot hangs up early in the boot process (19.768231 seconds into boot).:
input: HDA NVidia HDMI/DP,pcm=3 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input6
input: HDA NVidia HDMI/DP,pcm=7 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input7
input: HDA NVidia HDMI/DP,pcm=8 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input8
So, is this a NVidia issue or a sound card issue?
I installed a package (kicad) on my wheezy system using apt-get and it pulled down a shedload more files than I expected.When I restarted the system it turns out I've also been upgraded to
Release 8.0 Jessie
Kernel Linux 3.2.0-4-amd64
GNOME 3.4.2
However I don't have gnome any more. Only XFCE.I tried
Code: Select allroot@client:~# apt-get install gnome
Reading package lists... Done.Building dependency tree.Reading state information... Done.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 packages have unmet dependencies:
gnome : Depends: gnome-core (= 1:3.14+3) but it is not going to be installed
Depends: evolution (>= 3.12) but it is not going to be installed
Depends: evolution-plugins (>= 3.12) but it is not going to be installed
Depends: gnome-shell-extension-weather but it is not going to be installed
Recommends: gnome-software but it is not installable
E: Unable to correct problems, you have held broken packages.
My /etc/apt/sources.list is
Code: Select all#
# deb cdrom:[Debian GNU/Linux 7.7.0 _Wheezy_ - Official amd64 NETINST Binary-1 20141018-13:04]/ wheezy main
#deb cdrom:[Debian GNU/Linux 7.7.0 _Wheezy_ - Official amd64 NETINST Binary-1 20141018-13:04]/ wheezy main
deb http://mirror.waia.asn.au/debian/ wheezy main
deb-src http://mirror.waia.asn.au/debian/ wheezy main
[code]....
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] ....
X won't start (awesome WM) after upgrading to jessie. It seems to startup up, then just stops. I'm running startx from the command line after logging in. The xorg log (bottom) looks good and I see an exit code of zero.
I do see this in sysout:
Code: Select alldebian xf86TokenToOptinfo: table is NULL
Googled around but I can't find anything specific on this one.
I'm not using any xorg.conf, as booting into a linux rescue cd everything works ok
Code: Select all[ 2275.960]
X.Org X Server 1.16.4
Release Date: 2014-12-20
[ 2275.960] X Protocol Version 11, Revision 0
[ 2275.960] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[ 2275.960] Current Operating System: Linux jj 3.14.25 #1 SMP Fri Dec 5 10:17:33 EST 2014 x86_64
[Code] .....
After upgrade no sound. I tried "alsactl init" fix and that worked for awhile. Now even that isn't working.
Also tried the following:
# /etc/init.d/alsa-utils reset
[ ok ] Resetting ALSA...done.
# /etc/init.d/alsa-utils restart
# alsactl init
Found hardware: "HDA-Intel" "Realtek ALC898" "HDA:10ec0899,38421034,00100003" "0x1034" "0x3842"
Hardware is initialized using a generic method
Dell Vostro 230 with integrated Broadcom NIC.
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
A bit of research found the suggestion:
$ lspci -tv | grep -i ether
+-1c.2-[02]----00.0 Broadcom Corporation NetLink BCM57788 Gigabit Ethernet PCIe
$ cat /proc/acpi/wakeup
Device S-state Status Sysfs node
P0P2 S4 *disabled
P0P3 S4 *disabled
[Code] ....
How to get wakeonlan working under Jessie with a Broadcom BCM57788?
I installed Jessie with the RC1. URL...A2) The network install images for testing (jessie) can be found at URL...However, unless you want to test the installer for testing the better choice is to use the stable installer to install a minimal stable system and then upgrade to testing by changing your /etc/apt/sources.list file.
View 8 Replies View Relatedis it possible to simulate upgrading a Squeeze installation to a Wheezy or Jessie installation, on a OVH server ?I would like simulate upgrading server, and if not problems, upgrading in real time.I don't do that manipulation, and I don't do mistakes on a production server.
View 2 Replies View RelatedI upgraded my laptop from Debian Wheezy to Jessie the other day, and just as before my wifi auto-connects to my router, and I can "ping http://www.google.com" just fine, but only for like a minute. Then the Internet access dies, but I'm still connected fine to my router, and I can ping its IP address. If I connect to the router through cable / eth0 everything works just fine, and I have full Internet access.
I assume there is something wonky with how ip address is assigned after the upgrade, how can I fix this, or trouble shoot further?
(I run Gnome desktop, with network manager).
I have an asus eee 1015px, which was running dualboot windows and wheezy with no problems (except the browsers seeming to take up a lot of CPU). Today having backed up everything, I wanted to upgrade to jessie. URL...
Everything seemed to be progressing fine, no strange messages, it took 1 hour for
Code: Select allapt-get upgrade
but maybe that's normal. However, then when I did
Code: Select allapt-get dist-upgrade
It froze at 17.30 with a weird screen. The sort of thing you never want to see on an install, a sad face and blocks instead of text.
pic: URL...
Then it moved on and gave a readout, which seemed pretty ominous
pic: URl...
It then moved and gave a readout, hanging again:
pic3: URl...
Now it seems to be in loop, moving on every 15 minutes or so but always ending up with the same screenful of text shown in the foto below, which ends with the last line reading like this:
Code: Select all[17798.587776] ieee80211 phy0: brcms_ops_bss_info_changed: arp filtering: enabled true, count 1 (implement)
or later
Code: Select all[20209.229273] ieee80211 phy0: brcms_ops_bss_info_changed: arp filtering: enabled true, count 1 (implement)
This pic shows the full screen: URL....
This is baffling for me I'm not very experienced with debian.
I just upgraded my Debian Wheezy XFCE 32-Bite to Jessie.
Now some strange freezes occur. After 10sec - 3min after login the GUi freezes and the screen gets blurry and some "lines" appear.
I never suffered from this bug under Wheezy. What could be wrong? Some conflict with the X-server?
I upgraded from Wheezy to Jessie yesterday and no longer have sound. I don't think anything is muted. I checked alsamixer and everything is on. MOC, VLC, speaker-test and aplay are all giving me errors. MOC refuses to load.
Code: Select allccc@de:~$ speaker-test
speaker-test 1.0.28
Playback device is default
Stream parameters are 48000Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
Playback open error: -2,No such file or directory
Code: Select allaplay /usr/share/sounds/alsa/Front_Center.wav
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
aplay: main:722: audio open error: No such file or directory
Code: Select allccc@de:~$ mocp
Running the server...
Trying JACK...
Trying ALSA...
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
Trying OSS...
[CODE]....
Should I have a normal alsa-base.conf file?
I'm running a Debian derivative (Voyage linux).With the latest version based on Debian 8.0 Jessie and kernel 3.14.12 I have frequent pops, clicks and stutters in sound played through a USB dac, especially with higher resolution files. A previous version of this distribution worked fine, which was based on Debian 6.0.2 "Squeeze" and kernel 2.6.38. The files played are stored on a pata (to sata) device.I suspect I have an IRQ problem, I've made the following observations:
- The following processes are producing a combined 15-20% cpu load depending on the resolution currently being played. In the Squeeze based distribution these processes are not visible, so I'm not sure what that means.
irq/15-ehci_hcd
irq/15-ohci_
irq/15-pata_amd_hcd
- ksoftirq is also slightly elevated at 1.6 when running 'Jessie' compared to 0 on the 'Squeeze'
- The si line in 'top' seems also to be quite high (between 2 and 7) compared to when running 'Squeeze' (between 0 and and occasional 0.3).
- system load is also quite high
Below I have the contents of /proc/interrupts. It seems the problem lies in irq 15 being shared between usb and pata device(s). I already tried adding a few kernel options but without results: a.o. pci=routeirq, acpi=off. The latter did change the order of irq15, moving the pata device one position up.
'Squeeze' distribution: cat /proc/interrupts
CPU0
0: 2610959 XT-PIC-XT-PIC timer
1: 0 XT-PIC-XT-PIC i8042
2: 0 XT-PIC-XT-PIC cascade
3: 1 XT-PIC-XT-PIC
[code]...
I have upgraded my debian server on april when Jessie came up, but I *forgot* to reboot at this time. As a new kernel* was released this week as a security update, and since my server installed it (via unattended-upgrade on security packages), I rebooted it last night. It never came back online.
I have access to a rescue boot (Ubuntu 12.04 LTS), and tried to analyse the failure (by mounting /sys /dev /proc and /boot and chrooting), but without luck so far.
As it's a dedicated server, I don't have access to the console. What I know :
No log in var/log since the failed reboot. I don't know how to have/find others logs.Previous kernel was 3.2.0-4-amd64, new is 3.16.0-4-amd64, What I tried without luck) :
Change the booting kernel, via update-grub. Tried 3.2, 3.2 with sysvinit and 3.16 rescue mode I think. I should have done it right, but without console it's hard to tell.apt-get update/apt-get upgrade/apt-get dist-upgradeadding nomodeset to kernel load in grubWhat I haven't tried :
update-initramfs, I don't really know why it would block the boot
*linux-image-3.16.0-4-amd64:amd64 3.16.7-ckt11-1+deb8u2
I recently upgraded my debian system from jessie to stretch. Before then, I was mostly using hibernation instead of shutting off the laptop, to allow myself to get back faster to work the next day. Since my upgrade, though, it is impossible for me to resume from hibernation: after the normal boot sequence and the passphrase to decrypt my lvm partition, when it has loaded the information from RAM the screen just stays with a blinking "_" (underscore) in the top left corner.
I have hibernate and uswsusp packages installed. I also installed tuxonice-userui package to do some tests with the hibernate-ram and hibernate-disk commands. While using hibernate-disk (hibernate-ram didn't work, because "s2ram: unknown machine"), my system hibernates correctly, and I saw that during resume it was correctly loading everything from swap and then going back to the "underscore screen", confirming that the resume problem was happening after loading data from swap.
I tried booting using the recovery kernel in grub. For a time it worked, but today I didn't get the chance to make it work. The only solution was for me to boot my kernel by adding the "noresume" option to it, thus forcing it to restart.
I upgraded from deb7 to deb8, but am no longer able to boot. After passing the grub boot menu, the following messages are displayed:
Code:
Select allLoading, please wait...
[ 6.065713] systemd-fsck[148]: /dev/sda1: clean, 428644/1310720 files, 410616
9/52442880 blocks
[ 7.480551] Error: Driver 'pcspkr' is already registered, aborting...
[ 8.692700] systemd-fsck[341]: /dev/sda5: clean, 145485/6176768 files, 17407409/24695552 blocks
[ 18.066215] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated). Use CAP_NET_ADMIN and alias netdev- instead
_
The screen then clears and an underscore is displayed as the sole character at the top left position of the screen. The system hangs at this point. During installation, I rejected two changed files: /etc/init.d/bootlogd and /etc/libreoffice/sofficerc. For both, I opted to keep the installed version (the default choice of the installer) rather than replacing with the new version. The first might be related to the problem, although it seems to be responsible only for logging the boot process, and I would not expect this to compromise booting.
In case this information is useful, sda1 is mounted at /, sda2 is swap space, sda3 is extended, and sda5 is a logical partition mounted at /home.
I am able to boot into rescue mode, but other than that the system is not usable. Unfortunately, no useful error messages are given to aid in diagnosing the problem.
I've changed my /etc/apt/sources.lst file to use "jessie" repositories instead of "wheezy". I then ran synaptic and updated everything (there were loads of packages, something like 2000 to update).
After this I rebooted. The grub menu shows as usual with the background image I'd set and the operating systems as usual (including Windows 7) however there is no longer a 5 second countdown and when I select *any* menu option, it asks for a username and password.
I don't know what username and password it's asking for as I never used to have one set!!! I did have a username and password set up so that if you wanted to edit a grub menu option so I tried that but to no avail.
I'm using MBR/BIOS not EFI.
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.
View 4 Replies View RelatedI 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 just upgraded to jessie and now Samba won't let me log in anymore. I merged smb.conf manually. It now looks like this (removed comments):
Code: Select all[global]
workgroup = WORKGROUP
dns proxy = no
bind interfaces only = no
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 0
[Code] .....
With smbclient logs as follows:
Code: Select allsmbclient -L 192...
Enter user's password:
session setup failed: NT_STATUS_UNSUCCESSFUL
If I provide a wrong password, it raises NT_STATUS_LOGON_FAILURE, also if retry with the correct password.
Not sure about what resolved the issue. But after I purged samba, reconfigured it, added the users AND set www-data's shell to bash again (which was changed during the update), it now seems to work
Under wheezy, I could set gnome-terminal profile to partial transparency, i.e., to display the desktop wallpaper behind the text. (E.g., a picture of my girlfriend.) But after upgrade to Jessie, this option completely disappeared, and now I can only pick a solid color. Do I need to flip a setting or something to get this back? Am running default Gnome desktop (not fallback mode) though I think I only have 2D acceleration.
View 3 Replies View RelatedI 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.
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:
Code: Select allcharlie@asimov:~$ ps ax | grep gdm3
1058 ? Sl 0:00 /usr/sbin/gdm3
3993 tty2 S+ 0:00 grep gdm3
charlie@asimov:~$ sudo service gdm3 status
[Code] .....
I'm not sure why it prints that it's starting gdm3, but it does that every time I run `sudo service gdm3 status'.
Here's a copy of my /var/log/Xorg.0.log.
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.
Just wanted to check, would the kernel in Jessie blacklist queued trim for the Samsung 840 EVO for compatibility with firmware EXT0DB6Q as per similar situations that have occurred with other drives?
View 2 Replies View RelatedI have done on previous releases, but this time it hangs on me. It's "only" a Virtualbox, so I can reproduce it.
The wheezy already runs systemd, and is fully updated to to latest packages. Does not run any graphical.
Edits the source.list and does
$ apt-get update
$ apt-get upgrade # Did on one upgrade
$ apt-get dist-upgrade
It starts to upgrade (complains about missing version in libpgp-error), libc is installed, but at some point the systemd is running at high CPU and a dpkg seems to be stalled.
Should I disable systemd on wheezy before? This might not have been tested so much.
