[SOLVED (mostly)] Re: SAMBA problems on Debian 8.8
2:4.2.14+dfsg-0+deb8u7+b1
amd64Samba Virtual FileSystem plugins
On Sat, Jul 15, 2017 at 11:09 AM, Jason Wittlin-Cohen
<jwittlinco...@gmail.com <mailto:jwittlinco...@gmail.com>> wrote:
You are running an out-of-date version of samba
(2:4.2.14+dfsg-0+deb8u6 vs. 4.2.14+dfsg-0+deb8u7+b1). In addition,
you seem to be missing samba-common-bin, samba-dsdb-modules, and
python-samba, all of which are dependencies of samba.
Try 'sudo apt-get install --reinstall samba'
If that doesn't include install the removed packages, run, 'sudo
apt-get install samba-common-bin samba-dsdb-modules python-samba'
On Sat, Jul 15, 2017 at 11:01 AM, Hans Kraus <h...@hanswkraus.com
<mailto:h...@hanswkraus.com>> wrote:
Am 15.07.2017 um 16:05 schrieb Jason Wittlin-Cohen:
What does 'dpkg -l | grep samba' show?
On Sat, Jul 15, 2017 at 10:01 AM, Hans Kraus
<h...@hanswkraus.com <mailto:h...@hanswkraus.com>
<mailto:h...@hanswkraus.com <mailto:h...@hanswkraus.com>>>
wrote:
Am 15.07.2017 um 14:48 schrieb Jason Wittlin-Cohen:
Did you run an apt-get dist-upgrade yesterday?
Debian released
updated Samba packages as part of a security
update. However,
the updated packages had dependency issues and were
quickly
replaced by new packages. If you attempted to run a
dist-upgrade with the broken packages, it would
have installed
samba and samba-core. Check to see whether your
samba packages
are still installed.
On Sat, Jul 15, 2017 at 7:56 AM, Hans Kraus
<h...@hanswkraus.com <mailto:h...@hanswkraus.com>
<mailto:h...@hanswkraus.com
<mailto:h...@hanswkraus.com>> <mailto:h...@hanswkraus.com
<mailto:h...@hanswkraus.com>
<mailto:h...@hanswkraus.com
<mailto:h...@hanswkraus.com>>>> wrote:
Hi,
yesterday, 14. July, about 9:30 pm my SAMBA
shares on
Debian simply
stopped working. I did not do anything on the
system.
When I now try to connect to them from Windows
8.1 I do not
see them
in the "Connect Network Drive" window.
When I enter the address manually I get the
error "The
connection isn't
accepted from the remote device ...".
All texts are my translations from German, so
the will be only
approximately correct.
Any advice for me and what debug info shall I
supply?
Kind regards,
Hans
No, definitely not. I do updates/upgrades rather
infrequently and I
issued (packed in a small script):
/usr/sbin/update-smart-drivedb
apt-get update
apt-get -y upgrade
apt-get -y autoremove
only after the error occurred.
Kind regards,
Hans
root@robbe:/var/log/samba# dpkg -l | grep samba
rc samba 2:4.2.14+dfsg-0+deb8u6 amd64
SMB/CIFS file, print, and login server for Unix
ii samba-common 2:4.2.14+dfsg-0+deb8u7 all
common files used by both the Samba server and client
ii samba-dsdb-modules 2:4.2.14+dfsg-0+deb8u7+b1
amd64Samba Directory Services Database
ii samba-libs:amd64 2:4.2.14+dfsg-0+deb8u7+b1amd64
Samba core libraries
ii samba-vfs-modules 2:4.2.14+dfsg-0+deb8u7+b1
amd64Samba Virtual FileSystem plugins
ii vlc-plugin-samba 2.2.6-1~deb8u1 amd64
Samba plugin for VLC
root@robbe:/var/log/samba#
Kind regards,
Hans
Re: SAMBA problems on Debian 8.8
Am 15.07.2017 um 14:58 schrieb Ulf Volmer: On 15.07.2017 13:56, Hans Kraus wrote: yesterday, 14. July, about 9:30 pm my SAMBA shares on Debian simply stopped working. I did not do anything on the system. There were samba updates for jessie yesterday. First one was broken on some systems so maybe it will help to do an upgrade again. Any advice for me and what debug info shall I supply? is samba running? If yes, any messages in the log? best regards Ulf Hi, thanks for the help to all. apt-get upgrade/update installed nothing. Therefore I presume that I have the latest updates. I tried to restart the Samba server: root@robbe:/var/log/samba# systemctl restart smbd.service Querying the status gives: root@robbe:/var/log/samba# systemctl status smbd.service ● smbd.service - LSB: start Samba SMB/CIFS daemon (smbd) Loaded: loaded (/etc/init.d/smbd) Active: active (exited) since Sat 2017-07-15 15:35:43 CEST; 6s ago Process: 17381 ExecStop=/etc/init.d/smbd stop (code=exited, status=0/SUCCESS) Process: 17384 ExecStart=/etc/init.d/smbd start (code=exited, status=0/SUCCESS) Jul 15 15:35:43 robbe systemd[1]: Starting LSB: start Samba SMB/CIFS daemon (smbd)... Jul 15 15:35:43 robbe systemd[1]: Started LSB: start Samba SMB/CIFS daemon (smbd). root@robbe:/var/log/samba# I don't find in the output of 'ps -elf' anything with samba or smb. In '/var/log/samba' the latest files are from yesterday, around the time the error occurred. The log files are (the bigger ones are truncated): log.nmbd ... [2017/07/14 20:49:01.939924, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) find_domain_master_name_query_fail: Unable to find the Domain Master Browser name KRAUS_ZUHAUSE<1b> for the workgroup KRAUS_ZUHAUSE. Unable to sync browse lists in this workgroup. [2017/07/14 20:49:01.940054, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) find_domain_master_name_query_fail: Unable to find the Domain Master Browser name KRAUS_ZUHAUSE<1b> for the workgroup KRAUS_ZUHAUSE. Unable to sync browse lists in this workgroup. [2017/07/14 21:04:01.949910, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) find_domain_master_name_query_fail: Unable to find the Domain Master Browser name KRAUS_ZUHAUSE<1b> for the workgroup KRAUS_ZUHAUSE. Unable to sync browse lists in this workgroup. [2017/07/14 21:04:01.950037, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) find_domain_master_name_query_fail: Unable to find the Domain Master Browser name KRAUS_ZUHAUSE<1b> for the workgroup KRAUS_ZUHAUSE. Unable to sync browse lists in this workgroup. [2017/07/14 21:19:01.963122, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) find_domain_master_name_query_fail: Unable to find the Domain Master Browser name KRAUS_ZUHAUSE<1b> for the workgroup KRAUS_ZUHAUSE. Unable to sync browse lists in this workgroup. [2017/07/14 21:19:01.963239, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) find_domain_master_name_query_fail: Unable to find the Domain Master Browser name KRAUS_ZUHAUSE<1b> for the workgroup KRAUS_ZUHAUSE. Unable to sync browse lists in this workgroup. [2017/07/14 21:34:01.964702, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) find_domain_master_name_query_fail: Unable to find the Domain Master Browser name KRAUS_ZUHAUSE<1b> for the workgroup KRAUS_ZUHAUSE. Unable to sync browse lists in this workgroup. [2017/07/14 21:34:01.964832, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) find_domain_master_name_query_fail: Unable to find the Domain Master Browser name KRAUS_ZUHAUSE<1b> for the workgroup KRAUS_ZUHAUSE. Unable to sync browse lists in this workgroup. [2017/07/14 21:40:44.998819, 0] ../source3/nmbd/nmbd.c:58(terminate) Got SIGTERM: going down... log.smbd [2017/07/14 21:40:46.136827, 0] ../lib/util/pidfile.c:153(pidfile_unlink) Failed to delete pidfile /var/run/samba/smbd.pid. Error was No such file or directory log.wb-BUILTIN [2017/06/23 11:38:12.736446, 0] ../source3/winbindd/winbindd.c:266(winbindd_sig_term_handl
Re: SAMBA problems on Debian 8.8
Am 15.07.2017 um 16:05 schrieb Jason Wittlin-Cohen: What does 'dpkg -l | grep samba' show? On Sat, Jul 15, 2017 at 10:01 AM, Hans Kraus <h...@hanswkraus.com <mailto:h...@hanswkraus.com>> wrote: Am 15.07.2017 um 14:48 schrieb Jason Wittlin-Cohen: Did you run an apt-get dist-upgrade yesterday? Debian released updated Samba packages as part of a security update. However, the updated packages had dependency issues and were quickly replaced by new packages. If you attempted to run a dist-upgrade with the broken packages, it would have installed samba and samba-core. Check to see whether your samba packages are still installed. On Sat, Jul 15, 2017 at 7:56 AM, Hans Kraus <h...@hanswkraus.com <mailto:h...@hanswkraus.com> <mailto:h...@hanswkraus.com <mailto:h...@hanswkraus.com>>> wrote: Hi, yesterday, 14. July, about 9:30 pm my SAMBA shares on Debian simply stopped working. I did not do anything on the system. When I now try to connect to them from Windows 8.1 I do not see them in the "Connect Network Drive" window. When I enter the address manually I get the error "The connection isn't accepted from the remote device ...". All texts are my translations from German, so the will be only approximately correct. Any advice for me and what debug info shall I supply? Kind regards, Hans No, definitely not. I do updates/upgrades rather infrequently and I issued (packed in a small script): /usr/sbin/update-smart-drivedb apt-get update apt-get -y upgrade apt-get -y autoremove only after the error occurred. Kind regards, Hans root@robbe:/var/log/samba# dpkg -l | grep samba rc samba 2:4.2.14+dfsg-0+deb8u6 amd64SMB/CIFS file, print, and login server for Unix ii samba-common 2:4.2.14+dfsg-0+deb8u7 all common files used by both the Samba server and client ii samba-dsdb-modules 2:4.2.14+dfsg-0+deb8u7+b1amd64 Samba Directory Services Database ii samba-libs:amd64 2:4.2.14+dfsg-0+deb8u7+b1amd64 Samba core libraries ii samba-vfs-modules 2:4.2.14+dfsg-0+deb8u7+b1amd64 Samba Virtual FileSystem plugins ii vlc-plugin-samba 2.2.6-1~deb8u1 amd64 Samba plugin for VLC root@robbe:/var/log/samba# Kind regards, Hans PS: Sorry for the personal mails.
SAMBA problems on Debian 8.8
Hi, yesterday, 14. July, about 9:30 pm my SAMBA shares on Debian simply stopped working. I did not do anything on the system. When I now try to connect to them from Windows 8.1 I do not see them in the "Connect Network Drive" window. When I enter the address manually I get the error "The connection isn't accepted from the remote device ...". All texts are my translations from German, so the will be only approximately correct. Any advice for me and what debug info shall I supply? Kind regards, Hans
mdadm: no more mails during monthly scrubbing under Jessie
Hi, I recently upgrades my Debian sever from Wheezy to Jessie. I have the standard configuration, especially the monthly ckeck via the cron entry: "57 0 * * 0 root if [ -x /usr/share/mdadm/checkarray ] && [ $(date +\%d) -le 7 ]; then /usr/share/mdadm/checkarray --cron --all --idle --quiet; fi". Under Wheezy I got progress mails like: - MD Device: /dev/md/robbe:storage Event: Rebuild60 /proc/mdstat: Personalities : [raid6] [raid5] [raid4] md127 : active raid6 sdk1[0] sde1[9] sdi1[8] sdf[7] sdj1[5] sdg1[4] sdh1[6] 19534426880 blocks super 1.2 level 6, 128k chunk, algorithm 2 [7/7] [UUU] [>] check = 60.9% (2381950248/3906885376) finish=259.5min speed=97924K/sec Action ready: 2016-04-03 12:13:13.949761 unused devices: - from mdadm system, at the start of the scrub, every 20% and at the end. I do not get these mails any more, the change was around my upgrade from Wheezy to Jessie, sorry, I don't know the date exactly (theese mails came every month ...). Extensive googling brought up nothing except some users complaining about theese mails ... How do I enable theese mails again? I like them as security info that all is well with my Raid. I asked this very question on the list 'linux-r...@vger.kernel.org' but got from Neil Brown the advice: > You would probably be better off asking on a Debian help list, or > open a Debian bug. This is a configuration specific to Debian. Kind regards, Hans
mdadm - Progress mails of checkarray now missing
Hi, I used to get progress mails from mdadm checkarray in the form of -- MD Device: /dev/md/robbe:storage Event: RebuildStarted /proc/mdstat: Personalities : [raid6] [raid5] [raid4] md127 : active raid6 sdk1[0] sde1[9] sdi1[8] sdf[7] sdj1[5] sdg1[4] sdh1[6] 19534426880 blocks super 1.2 level 6, 128k chunk, algorithm 2 [7/7] [UUU] [>] check = 0.0% (24/3906885376) finish=2034836.1min speed=24K/sec Action ready: 2020-01-18 02:53:07.554049 unused devices: -- for every 20% of checking finished. I don't get them any more. "mdadm --monitor --scan --test -1" still mails to me; therefore I suppose that the mailing system still works. The crontab entry in "/etc/cron.d/mdadm" is "57 0 * * 0 root if [ -x /usr/share/mdadm/checkarray ] && [ $(date +\%d) -le 7 ]; then /usr/share/mdadm/checkarray --cron --all --idle --quiet; fi". I haven't changed it. Is it possible to re-enable these progress mails? Kind regards, Hans
Re: Partial Success [was: Re: Problems with upgrade from Wheezy to Jessie]
Hi, Am 09.10.2016 um 23:46 schrieb Brian: On Sat 08 Oct 2016 at 13:50:19 +0200, Hans Kraus wrote: after following the propositions of Brian: dpkg -l | grep fglrx Lines with "ii" indicate installed packages. Purge and see what a reboot does. and Jörg-Volker Peetz: Hi, I also saw the other e-mail exchange with Brian where you concluded to purge all "fglrx"-related packages. Similarily, there seem to be "nvidia" packages on your system. Try dpkg -l | grep -i nvidia Purge them also. Then have a look which xorg-video drivers are left: dpkg -l | grep xorg-video Leave only xserver-xorg-video-radeon on the system. And have a look if there's still an "glx-alternative" package left, like glx-alternative-mesa. This could also be purged. I issued: [Account of package purging snipped] Which partially solved my problems. The system is now booting into Gnome again. This is a fantastic step forwards. Before you had nothing, now you have something. Why the original issue occured is a mystery. Why it was cured is also a mystery. A problem remains: the contents of the screen (I controlled only text based ones like Thunderbird) are sometimes overwritten. This happens for lines where the text is partially overwritten with other text (normally or skewed) and line backgrounds. The contents are restored if I move the mouse pointer to the distorted parts. This looks like a driver issue to me. Is there a better mailing list to cope with these problems as 'debian-user'? But now the proposition is very different. We know you cannot have that much of a driver problem because you can boot into GNOME. But you think you have. Maybe its so. Let's eliminate GNOME. Boot and do 'ps ax | grep xinit'. Kill xinit with 'kill process_number'. Install fvwm and xterm (you can purge them later). Issue the command 'startx'. Check that nothing gnomish is running with 'ps ax | grep gnome. Start an xterm (right or left click, I forget which). Any problems? Start iceweasel (firefox) from an xterm. Any problems? Read a few man pages. Any problems? Play with opening any program on your system. Any problems? Which program? What are the symptoms? Sorry, 'ps ax | grep xinit' didn't give any processes. The most similar to X thing I found was: = 1350 tty7 Ssl+ 4:14 /usr/bin/Xorg :0 -novtswitch -background none -noreset -verbose 3 -auth /var/run/gdm3/auth-for-Debian-gdm-ceY7sk/database -seat seat0 -nolisten tcp vt7 = The whole output pf 'ps ax' is enclosed as ps.txt. Two parts of screenshots with error regions in them are enclosed as err?.png. I hope that's OK to include small graphics files, but to describe display problems in text form is a bit awkward (at least to me). I thought that my problems may be driver related because when I saw such behaviour on Windows machines the culprit was always the graphics driver. Thanks & regards, Hans PID TTY STAT TIME COMMAND 1 ?Ss 0:39 /sbin/init 2 ?S 0:00 [kthreadd] 3 ?S 0:24 [ksoftirqd/0] 5 ?S< 0:00 [kworker/0:0H] 7 ?S 4:38 [rcu_sched] 8 ?S 0:00 [rcu_bh] 9 ?S 0:00 [migration/0] 10 ?S 0:01 [watchdog/0] 11 ?S 0:01 [watchdog/1] 12 ?S 0:00 [migration/1] 13 ?S 0:21 [ksoftirqd/1] 15 ?S< 0:00 [kworker/1:0H] 16 ?S 0:01 [watchdog/2] 17 ?S 0:00 [migration/2] 18 ?S 0:20 [ksoftirqd/2] 20 ?S< 0:00 [kworker/2:0H] 21 ?S 0:01 [watchdog/3] 22 ?S 0:00 [migration/3] 23 ?S 0:20 [ksoftirqd/3] 25 ?S< 0:00 [kworker/3:0H] 26 ?S 0:01 [watchdog/4] 27 ?S 0:00 [migration/4] 28 ?S 0:24 [ksoftirqd/4] 30 ?S< 0:00 [kworker/4:0H] 31 ?S 0:01 [watchdog/5] 32 ?S 0:00 [migration/5] 33 ?S 0:21 [ksoftirqd/5] 35 ?S< 0:00 [kworker/5:0H] 36 ?S< 0:00 [khelper] 37 ?S 0:00 [kdevtmpfs] 38 ?S< 0:00 [netns] 39 ?S 0:00 [khungtaskd] 40 ?S< 0:00 [writeback] 41 ?SN 0:00 [ksmd] 42 ?SN 0:00 [khugepaged] 43 ?S< 0:00 [crypto] 44 ?S< 0:00 [kintegrityd] 45 ?S< 0:00 [bioset] 46 ?S< 0:00 [kblockd] 50 ?S 0:00 [kswapd0] 51 ?S< 0:00 [vmstat] 52 ?S 0:03 [fsnotify_mark] 58 ?S< 0:00 [kthrotld] 60 ?S< 0:00 [ipv6_addrconf] 62 ?S< 0:00 [deferwq] 107 ?S 0:00 [scsi_eh_0] 108 ?
Partial Success [was: Re: Problems with upgrade from Wheezy to Jessie]
Hi, after following the propositions of Brian: dpkg -l | grep fglrx Lines with "ii" indicate installed packages. Purge and see what a reboot does. and Jörg-Volker Peetz: > Hi, > > I also saw the other e-mail exchange with Brian where you concluded to purge all > "fglrx"-related packages. Similarily, there seem to be "nvidia" packages on your > system. Try > > dpkg -l | grep -i nvidia > > Purge them also. Then have a look which xorg-video drivers are left: > > dpkg -l | grep xorg-video > > Leave only xserver-xorg-video-radeon on the system. > > And have a look if there's still an "glx-alternative" package left, like > glx-alternative-mesa. This could also be purged. I issued: === root@robbe:/etc/X11# apt-get purge fglrx-atieventsd fglrx-driver fglrx-modules-dkms glx-alternative-fglrx libfglrx:amd64 libfglrx-amdxvba1:amd64 libgl1-fglrx-glx:amd64 root@robbe:/etc/X11# apt-get purge glx-alternative-nvidia libegl1-nvidia:amd64 libgl1-nvidia-glx:amd64 libgl1-nvidia-glx:i386 libgl1-nvidia-glx-i386 libgles1-nvidia:amd64 libgles2-nvidia:amd64 libnvidia-eglcore:amd64 libnvidia-ml1:amd64 libnvidia-ml1:amd64 libxvmcnvidia1:amd64 nvidia-alternative nvidia-driver nvidia-driver-bin nvidia-glx nvidia-installer-cleanup nvidia-kernel-common nvidia-kernel-dkms nvidia-modprobe nvidia-settings nvidia-support nvidia-vdpau-driver:amd64 xserver-xorg-video-nvidia root@robbe:/etc/X11# apt-get install xserver-xorg-video-radeon Reading package lists... Done Building dependency tree Reading state information... Done xserver-xorg-video-radeon is already the newest version. xserver-xorg-video-radeon set to manually installed. The following package was automatically installed and is no longer required: libxnvctrl0 Use 'apt-get autoremove' to remove it. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@robbe:/etc/X11# === Which partially solved my problems. The system is now booting into Gnome again. A problem remains: the contents of the screen (I controlled only text based ones like Thunderbird) are sometimes overwritten. This happens for lines where the text is partially overwritten with other text (normally or skewed) and line backgrounds. The contents are restored if I move the mouse pointer to the distorted parts. This looks like a driver issue to me. Is there a better mailing list to cope with these problems as 'debian-user'? Many thanks to all which helped me, Kind regards, Hans
Re: Problems with upgrade from Wheezy to Jessie
Hi, Am 06.10.2016 um 20:43 schrieb Brian: On Thu 06 Oct 2016 at 19:39:21 +0200, Hans Kraus wrote: [...] (What does the glxinfo command give?) root@robbe:~# glxinfo Error: unable to open display That is when you used a terminal. Boot into X with xinit -- vt$XDG_VTNR It is not pretty but there is an xterm to type commands into. What is the output? I'm not able to start the xterm. Nothing happens hen I type Ctrl-D in the sad computer window. When I start another shell and login into it I get for 'xinit -- vt$XDG_VTNR': = (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" after 7 requests (7 known processed) with 0 events remaining. = After deleting /tmp/.X0-lock I get: = _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running (EE) Fatal server error: (EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. X connection to :0 broken (explicit kill or server shutdown). = Thanks & regards, Hans
Re:: Problems with upgrade from Wheezy to Jessie
Hi, the requested outputs: Am 06.10.2016 um 19:56 schrieb Jörg-Volker Peetz: Hans Kraus wrote on 10/06/16 19:40: Am 05.10.2016 um 22:16 schrieb Jörg-Volker Peetz: [already sent to the list; sent it again to you since you asked for CC] Hans Kraus wrote on 10/04/16 20:01: Hi, The VGA output: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 03e0 Flags: bus master, fast devsel, latency 0, IRQ 53 Memory at d000 (64-bit, prefetchable) [size=256M] Memory at fe2e (64-bit, non-prefetchable) [size=128K] I/O ports at 8000 [size=256] Expansion ROM at fe2c [disabled] [size=128K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [150] Advanced Error Reporting Kernel driver in use: radeon I appended the '/var/log/Xorg.0.log' as text file. I hope that's OK. As far as I know I didn't install a special video driver. At least not for Jessie, and, to the best of my knowledge, not for Wheezy too. What is the output of dpkg -S /usr/lib/xorg/modules/linux/libglx.so which is loaded according to Xorg.0.log? Regards, jvp. root@robbe:~# dpkg -S /usr/lib/xorg/modules/linux/libglx.so dpkg-query: no path found matching pattern /usr/lib/xorg/modules/linux/libglx.so Regards, Hans Is this file really present on your system? What does ls -lF /usr/lib/xorg/modules/linux/libglx.so show? Is there a link somewhere in this path? root@robbe:~# ls -lF /usr/lib/xorg/modules/linux/libglx.so lrwxrwxrwx 1 root root 38 Sep 25 12:44 /usr/lib/xorg/modules/linux/libglx.so -> /etc/alternatives/glx--linux-libglx.so ls -lF /usr/lib/xorg/modules/linux ls -lF /usr/lib/xorg/modules root@robbe:~# ls -lF /usr/lib/xorg/modules/linux total 64 -rw-r--r-- 1 root root 64432 Mar 25 2016 libfglrxdrm.so lrwxrwxrwx 1 root root38 Sep 25 12:44 libglx.so -> /etc/alternatives/glx--linux-libglx.so root@robbe:~# root@robbe:~# ls -lF /usr/lib/xorg/modules total 15852 -rw-r--r-- 1 root root 205784 Mar 25 2016 amdxmm.so drwxr-xr-x 2 root root 4096 Sep 25 13:04 drivers/ drwxr-xr-x 2 root root 4096 Sep 25 12:44 extensions/ -rw-r--r-- 1 root root 14984744 Mar 25 2016 glesx.so drwxr-xr-x 2 root root 4096 Sep 25 12:45 input/ -rw-r--r-- 1 root root96976 Feb 11 2015 libexa.so -rw-r--r-- 1 root root18760 Feb 11 2015 libfbdevhw.so -rw-r--r-- 1 root root 154768 Feb 11 2015 libfb.so -rw-r--r-- 1 root root 286992 Feb 11 2015 libglamoregl.so -rw-r--r-- 1 root root 146248 Feb 11 2015 libint10.so -rw-r--r-- 1 root root10440 Feb 11 2015 libshadowfb.so -rw-r--r-- 1 root root35080 Feb 11 2015 libshadow.so -rw-r--r-- 1 root root22992 Feb 11 2015 libvbe.so -rw-r--r-- 1 root root31872 Feb 11 2015 libvgahw.so -rw-r--r-- 1 root root 195728 Feb 11 2015 libwfb.so drwxr-xr-x 2 root root 4096 Sep 25 12:44 linux/ drwxr-xr-x 2 root root 4096 Sep 25 12:45 multimedia/ According to Xorg.0.log it should belong to some NVIDIA package. What does dpkg -S /usr/lib/xorg/modules/linux print out? root@robbe:~# dpkg -S /usr/lib/xorg/modules/linux glx-alternative-nvidia, glx-alternative-fglrx, fglrx-driver: /usr/lib/xorg/modules/linux Regards, jvp. Thanks & regards, Hans
Re: Problems with upgrade from Wheezy to Jessie
Am 05.10.2016 um 22:16 schrieb Jörg-Volker Peetz: [already sent to the list; sent it again to you since you asked for CC] Hans Kraus wrote on 10/04/16 20:01: Hi, The VGA output: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 03e0 Flags: bus master, fast devsel, latency 0, IRQ 53 Memory at d000 (64-bit, prefetchable) [size=256M] Memory at fe2e (64-bit, non-prefetchable) [size=128K] I/O ports at 8000 [size=256] Expansion ROM at fe2c [disabled] [size=128K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [150] Advanced Error Reporting Kernel driver in use: radeon I appended the '/var/log/Xorg.0.log' as text file. I hope that's OK. As far as I know I didn't install a special video driver. At least not for Jessie, and, to the best of my knowledge, not for Wheezy too. What is the output of dpkg -S /usr/lib/xorg/modules/linux/libglx.so which is loaded according to Xorg.0.log? Regards, jvp. root@robbe:~# dpkg -S /usr/lib/xorg/modules/linux/libglx.so dpkg-query: no path found matching pattern /usr/lib/xorg/modules/linux/libglx.so Regards, Hans
Re: Problems with upgrade from Wheezy to Jessie
Hi, Am 05.10.2016 um 20:58 schrieb Brian: On Wed 05 Oct 2016 at 19:50:50 +0200, Hans Kraus wrote: thanks to all. Brian is right with his opinion that I'm not subscribed to the list. I sent a 'subscribe' to but didn't get an answer (or at least I didn't find it). The reply comes back to the address you subscribed from. Maybe that wasn't h...@hanswkraus.com. But we will not dwell on that; you can sort it out at another time. How do I switch drivers under Debian, especiallay from the "AMD FGLRX driver for Radeon adapters" to the "free radeon driver, which is the default in jessie"? I did not mean to imply you are using the FGLRX driver. Your "lspci -v" output shows > Kernel driver in use: radeon which implies otherwise. But the journalctl output doesn't look happy. To answer your question: dpkg -l | grep fglrx Lines with "ii" indicate installed packages. Purge and see what a reboot does. root@robbe:~# dpkg -l | grep fglrx ii fglrx-atieventsd 1:15.9-4~deb8u2 amd64events daemon for the non-free ATI/AMD RadeonHD display driver ii fglrx-driver 1:15.9-4~deb8u2 amd64non-free ATI/AMD RadeonHD display driver ii fglrx-modules-dkms 1:15.9-4~deb8u2 amd64dkms module source for the non-free ATI/AMD RadeonHD display driver ii glx-alternative-fglrx 0.5.1 amd64allows the selection of FGLRX as GLX provider ii libfglrx:amd64 1:15.9-4~deb8u2 amd64non-free ATI/AMD RadeonHD display driver (runtime libraries) ii libfglrx-amdxvba1:amd64 1:15.9-4~deb8u2 amd64AMD XvBA (X-Video Bitstream Acceleration) backend for VA API ii libgl1-fglrx-glx:amd64 1:15.9-4~deb8u2 amd64proprietary libGL for the non-free ATI/AMD RadeonHD display driver Is it OK to purge all these? (What does the glxinfo command give?) root@robbe:~# glxinfo Error: unable to open display Thanks, Hans
Re: Problems with upgrade from Wheezy to Jessie
Hi, thanks to all. Brian is right with his opinion that I'm not subscribed to the list. I sent a 'subscribe' to but didn't get an answer (or at least I didn't find it). How do I switch drivers under Debian, especiallay from the "AMD FGLRX driver for Radeon adapters" to the "free radeon driver, which is the default in jessie"? Kind regards, Hans PS: Please send any mails regarding this with a 'CC' to me.
Re: Problems with upgrade from Wheezy to Jessie
Hi, The VGA output: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 03e0 Flags: bus master, fast devsel, latency 0, IRQ 53 Memory at d000 (64-bit, prefetchable) [size=256M] Memory at fe2e (64-bit, non-prefetchable) [size=128K] I/O ports at 8000 [size=256] Expansion ROM at fe2c [disabled] [size=128K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [150] Advanced Error Reporting Kernel driver in use: radeon I appended the '/var/log/Xorg.0.log' as text file. I hope that's OK. As far as I know I didn't install a special video driver. At least not for Jessie, and, to the best of my knowledge, not for Wheezy too. Many thanks & regards, Hans Am 03.10.2016 um 21:42 schrieb Christian Seiler: [ kernel, dist-upgrade ] All looks fine, you seem to have an up to date Jessie system and the only thing that was installed was the security update DSA-3684-1 of this morning. On 10/03/2016 08:42 PM, Hans Kraus wrote: Oct 02 17:24:37 robbe /etc/gdm3/Xsession[2351]: Xlib: extension "GLX" missing on display ":0". Oct 02 17:24:37 robbe /etc/gdm3/Xsession[2351]: gnome-session-is-accelerated: No hardware 3D support. There's your problem: as far as I know, GNOME under Jessie only works if you have 3D OpenGL hardware acceleration support. And apparently your GPU is either not supported (maybe not anymore) or you don't have the right driver loaded. Could you post the contents of /var/log/Xorg.0.log? (It may repeat itself, every time the X server is started, only the last one of these repeats is sufficient.) Also, what graphics card do you have? (You can find out via "lspci -v" as root and looking for a device with "VGA" in the device type.) Do you have any special drivers installed? (For example, if you have an NVIDIA card, do you have the proprietary nvidia drivers installed?) Regards, Christian [18.722] X.Org X Server 1.16.4 Release Date: 2014-12-20 [18.722] X Protocol Version 11, Revision 0 [18.722] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [18.722] Current Operating System: Linux robbe 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u1 (2016-09-03) x86_64 [18.722] Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/vg_root-lv_root ro quiet [18.722] Build Date: 11 February 2015 12:32:02AM [18.722] xorg-server 2:1.16.4-1 (http://www.debian.org/support) [18.722] Current version of pixman: 0.32.6 [18.722]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [18.722] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [18.722] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Oct 2 17:24:35 2016 [18.724] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [18.726] (==) No Layout section. Using the first Screen section. [18.726] (==) No screen section available. Using defaults. [18.726] (**) |-->Screen "Default Screen Section" (0) [18.726] (**) | |-->Monitor "" [18.726] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [18.726] (==) Automatically adding devices [18.726] (==) Automatically enabling devices [18.726] (==) Automatically adding GPU devices [18.730] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [18.730]Entry deleted from font path. [18.733] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [18.733] (==) ModulePath set to "/usr/lib/xorg/modules" [18.733] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [18.733] (II) Loader magic: 0x7f58902fbd80 [18.733] (II) Module ABI versions: [18.733]X.Org ANSI C Emulation: 0.4 [18.733]X.Org Video Driver: 18.0 [18.733]X.Org XInput driver : 21.0 [18.733]X.Org Server Extension : 8.0 [
Re: Problems with upgrade from Wheezy to Jessie
: extension "GLX" missing on display ":0". Oct 02 17:24:43 robbe /etc/gdm3/Xsession[2351]: gnome-session-check-accelerated: Helper exited with code 256 Oct 02 17:24:43 robbe /etc/gdm3/Xsession[2351]: ** (process:2351): WARNING **: software acceleration check failed: Child process exited with code 1 Oct 03 18:29:00 robbe gnome-session[2351]: ** (gnome-session-quit:2908): WARNING **: Failed to call logout: The name org.gnome.SessionManager was not provided by any .service files === Thanks & kind regards, Hans Am 03.10.2016 um 19:21 schrieb Christian Seiler: On 10/03/2016 06:50 PM, Hans Kraus wrote: With "gui stopped" I mean the following: After the boot process, instead of the graphical login screen where one can select the user, enter the password and do some selections, the following screen appears: A pic of a sad computer with the text (the first line is in bold): === Oh no! Something has gone wrong. A problem occurred and the system can't recover. Please log out and try again. --- | Log Out | --- === I get the same screen when I choose another shell (via Ctrl-Alt-F2), log in as root and enter: startx. Ok, this appears to be a GNOME-specific error message. Could you restart the computer, try to log in, wait until that message pops up, don't close the message, switch to another console (Ctrl+Alt+F2) and run the following command as root? journalctl -b1 -n40 _UID=1000 (Replace 1000 with your user id, you can look it via running id in the console as your normal user; 1000 is the default for the first user created by the Debian installer.) See if there's anything in that output that might be relevant here. The /etc/apt/sources.list: === root@robbe:~# cat /etc/apt/sources.list # deb http://ftp.at.debian.org/debian/ wheezy main # deb http://backports.debian.org/debian-backports wheezy-backports non-free deb http://ftp.at.debian.org/debian/ jessie-backports main contrib non-free deb http://ftp.at.debian.org/debian/ jessie main contrib non-free deb-src http://ftp.at.debian.org/debian/ jessie 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 # wheezy-updates, previously known as 'volatile' deb http://ftp.at.debian.org/debian/ jessie-updates main contrib non-free deb-src http://ftp.at.debian.org/debian/ jessie-updates main contrib non-free deb http://ftp.de.debian.org/debian/ jessie-backports main contrib non-free === Side note: you have jessie-backports in there twice (first and last uncommented line), but that's completely harmless. Otherwise, looks fine. Could you run apt-get update apt-get dist-upgrade and see if it still wants to upgrade additional software? Also, what kernel version are you running? (Find that out via the command "uname -a".) Regards, Christian
Re: Problems with upgrade from Wheezy to Jessie
Hi, thank's for your sppedy reaction. With "gui stopped" I mean the following: After the boot process, instead of the graphical login screen where one can select the user, enter the password and do some selections, the following screen appears: A pic of a sad computer with the text (the first line is in bold): === Oh no! Something has gone wrong. A problem occurred and the system can't recover. Please log out and try again. --- | Log Out | --- === I get the same screen when I choose another shell (via Ctrl-Alt-F2), log in as root and enter: startx. The /etc/apt/sources.list: === root@robbe:~# cat /etc/apt/sources.list # deb http://ftp.at.debian.org/debian/ wheezy main # deb http://backports.debian.org/debian-backports wheezy-backports non-free deb http://ftp.at.debian.org/debian/ jessie-backports main contrib non-free deb http://ftp.at.debian.org/debian/ jessie main contrib non-free deb-src http://ftp.at.debian.org/debian/ jessie 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 # wheezy-updates, previously known as 'volatile' deb http://ftp.at.debian.org/debian/ jessie-updates main contrib non-free deb-src http://ftp.at.debian.org/debian/ jessie-updates main contrib non-free deb http://ftp.de.debian.org/debian/ jessie-backports main contrib non-free === The parts "main contrib non-free" are on the same line; Thundebird insists on line breaks ... Kind regards, Hans Am 02.10.2016 um 20:31 schrieb Christian Seiler: On 10/02/2016 05:59 PM, Hans Kraus wrote: I upgraded my Debian server about a week ago from Wheezy to Jessie. After that the GUI stopped, This is a bit vague, so a better explanation would be good. What exactly do you mean "gui stopped"? Did that happen during the update? Or at boot? Does the login screen show up? Does this message show up after login? I see only the grey screen with the sad computer telling me " Oh no, Something is Wrong" and the only option is to log out. Could you transcribe the precise error message? I installed the package again with: apt-get install task-gnome-desktop I did not get any error message, but that didn't cure my problem. Afterwards I tried: "dpkg --configure -a". Again, I didn't get any error message but that didn't cure my problem. That means your packages are in a state that dpkg assumes to be consistent. However, since you upgraded recently, and apparently still have access to your shell, could you tell us what the contents of /etc/apt/sources.list is? Regards, Christian
Problems with upgrade from Wheezy to Jessie
Hi, I upgraded my Debian server about a week ago from Wheezy to Jessie. After that the GUI stopped, I see only the grey screen with the sad computer telling me " Oh no, Something is Wrong" and the only option is to log out. I'm using Gnome as my desktop. I installed the package again with: apt-get install task-gnome-desktop I did not get any error message, but that didn't cure my problem. Afterwards I tried: "dpkg --configure -a". Again, I didn't get any error message but that didn't cure my problem. I rebooted the system several times but with no avail. Which info should I provide and/or where should I check my system for errors? The text based login via ssh (I use Putty from Win 8.1) functions without problems. Kind regards, Hans
