I am now for four weeks on Wheezy KDE after turning away from PCLinuxOS.But now that Jessie KDE is out, I installed it on a free 20 GB partition to have a look.What I really like is the following:
At start up on Wheezy GRUB MENU - INIT messages - KDE welcome screen -> desktop..I am missing those INIT messages. Gives me a good feeling for system status.I understand, we now have systemd, but is there a possibility to have those reassuring messages at startup and maybe also at shut down?
Is there any way to capture the "[OK]" or "[FAILED]" messages? I would like to know which daemons starts successfully and which ones fails. Any way to tell the system to save those messages in /var/log? I could do CTRL-Print Screen but I would rather not.
I am building a live USB key using Ubuntu 9.10 Karmic. No upgrades have been applied. It is as it came in the ISO that was distributed.I would like to create a smooth start-up/logout process where no messages pop up (even briefly) that might confuse someone who is not very tech savvy. I'm referring to the messages that show up right before the login screen during start-up (between usplash and xsplash I think) that say:
"Starting early crypto disks ..."
and also the messages that show up on a black screen right after you initiate logout. It seems to sometimes show system messages including some error messages that can confuse users.Does anyone know of a way to hide, redirect, or disable these messages? I just don't want cryptic messages popping up even briefly that are going to confuse casual users. I'm stuck with version 9.10 since I've made some custom mods and would rather not redo them for a new release.
I'm running Debian Testing and since some time ago I'm getting the following messages:Any ideas how to solve this warnings?
(gtk-update-icon-cache:9204): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory Processing triggers for gconf2 ...
I have a syslog-ng running and kernel build of 2.6.34.8 I use a syslog API in my program with facility LOG_LOCAL5 and and levels debug err and crit and info. when I ran on the older syslog facility I had everything logged fine as I intended. now I have written these rules into the syslog-ng.conf:
I have an older version of ggv on RHEL for viewing PostScript (.ps) files, but the binary I have refuses to open files from AFS. ggv-2.12.0 is able to open these files from AFS just fine on my Mac. I was not able to find packaged binaries for RHEL 5 or 6 for ggv-2.12.0, so I downloaded the source and compiled it. Unfortunately, it fails to start, printing these error messages:
[code]...
Does anyone know the fix? Or alternatively, is there another good and well-maintained PostScript viewer for Linux?
Code: <snip> Hit http://volatile.debian.org lenny/volatile/main Sources Hit http://http.us.debian.org stable/contrib Packages Ign http://packages.enlightenment.org lenny/main Packages/DiffIndex Hit http://http.us.debian.org stable/non-free Packages
[Code]...
W: Some index files failed to download, they have been ignored, or old ones used instead.W: You may want to run apt-get update to correct these problems
I have a small LAN. I am in the process of installing a Debian Lenny/Squeeze system into the LAN. I want to send and receive system messages using rwalld and wall.I can send a system message from my Debian system to another box using rwall. I can send a local message within the Debian box using wall in a console.I cannot send a local message using wall Konsole in KDE 3.5.x. The KDE Write daemon fails to provide any pop-up window./usr/bin/wall is installed from the bsdutils package and is set to -rwxr-sr-x.
The ktalkd package is installed. The KDE control center shows a configuration option in Internet & Network settings called Local Network Chat.When not in X, mesg is set to y at the console. After starting KDE and I open Konsole, mesg is always set to n. I don't know how this setting toggles. Further, setting mesg to y in Konsole has no effect on getting wall to work.mesg is set to y when I run xterm in KDE. Then wall works within that terminal window. However, the KDE Write daemon does not see the message in xterm.When I send a message from another system to the Debian system using rwall, xterm receives the message but not Konsole or the KDE Write daemon.
When I send a wall message from Konsole, xterm receives the message but not Konsole or the KDE Write daemon.I changed TTYPERM in login.defs to 0620 to no avail.I do not have this problem on the non-Debian systems.
I've enabled BOOTLOGD_ENABLE=Yes in /etc/default/bootlogd on my Squeeze (Upgrade from Lenny) installed on the notebook, but after Retsrat NO bootlog messages in /var/log/boot. Is it a BUG?
/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
During the boot-sequence of jessie there is more text flying by on the screen (including some errors or warnings) than I can read thorugh fast enough. I don't think this is very serious stuff, and if it were I could always look at dmesg and or syslog i /var/log but I would find it really convenient to log these messages in a file instead of sifting through or grep-ing dmesg.
When duckduckgoing this matter I found [URL] ....
I installed tried bootlogd but when configuring it to "yes" and rebooting nothing comes up in /var/log/boot.
Then I saw this line in above link
If you use systemd as your init system, you may need to use systemctl to debug boot problems.
I have a small LAN. I am in the process of installing a Debian Lenny/Squeeze system into the LAN. I want to send and receive system messages using rwalld and wall.I can send a system message from my Debian system to another box using rwall. I can send a local message within the Debian box using wall in a console.I cannot send a local message using wall Konsole in KDE 3.5.x. The KDE Write daemon fails to provide any pop-up window./usr/bin/wall is installed from the bsdutils package and is set to -rwxr-sr-x.
The ktalkd package is installed. The KDE control center shows a configuration option in Internet & Network settings called Local Network Chat.When not in X, mesg is set to y at the console. After starting KDE and I open Konsole, mesg is always set to n. I don't know how this setting toggles. Further, setting mesg to y in Konsole has no effect on getting wall to work.mesg is set to y when I run xterm in KDE. Then wall works within that terminal window. However, the KDE Write daemon does not see the message in xterm.When I send a message from another system to the Debian system using rwall, xterm receives the message but not Konsole or the KDE Write daemon.
An issue that has been hassling me for years since I started using Linux (Debian!) is related to the boot messages that quickly scroll on the video during the boot process. The main hassle is related to the fact that I cannot get a log of those messages. The second hassle is due to the fact that with my brand new netbook (Toshiba NB200) I cannot even stop the scroll and go back along the message stream with SHIFT+PageUpDown to understand what's going on. Of course I know that I can get a log of the boot process with 'dmesg' but I get the feeling that the very first lines show some problem I cannot grab at all.
I'm running GNU/linux systems on all my PCs: Debian unstable, Ubuntu 9.10, and use Clonezilla (alternative based on Ubuntu Karmic), SystemRescueCD (beta and stable) to diagnose problems if needed.
My issue is that I've got a few hard drives that I can no longer mount either under linux or Windows, but Windows at least sees all the drives whereas linux sometimes tells me absolutely nothing:
1) one drive (Seagate 250GiB AS drive) has an ext3 file system, and /var/log/messages shows me lots of lines of information for the USB connection when I attach it, including the size of the drive, but can not mount anymore. Windows too sees the drive. I haven't tried to recover data from it.
2) two drives (not mine, both 500GiB drives) have NTFS file systems. With these, when I attach them, there is not even one line of information in /var/log/messages, or in the kernel or authentication logs. However, on the same computer booted up with Windows XP SP2 the device is seen by windows, including the size. Windows cannot mount the drive, but recovery software can after about 2 weeks' running, recover virtually all the data (I let it run using each of the various options for the guessed drive geometry/file system settings).
So my question is: why would linux not even give me a single line in /var/log/messages, not even to say that something has been attached to a USB port? I'd like to believe that linux does see something but that the USB/SCSI emulation is somewhat faulty and could be improved.
I'm not sure what kernel modules I should be looking at for the physical connection control.
Does anyone experience burning problem with Brasero? At first, everything was great, but lately I receive all kind of messages (mounting problem, ejecting problem etc.) and burning is unsuccessful.
Looking through syslog, I see some peculiar messages that occur when booting my Debian machine up. Can anyone explain to me, why it seams to think my filesystem is read only, and what do the other messages mean? Is there anything I need to start worrying about?
Feb 26 08:48:21 chris-desktop kernel: [ 4.082355] EXT3-fs (sdb3): recovery required on readonly filesystem Feb 26 08:48:21 chris-desktop kernel: [ 4.082361] EXT3-fs (sdb3): write access will be enabled during recovery
I would like to have Icedove display the number of unread messages in the task/window bar when both active or minimized; note I am not interested in a system tray solution just yet. There must be a hack to do this right? Would it involve recompiling Icedove?
I'm trying to stop all boot time messages from appearing -- basically I'd like to have a simple blank screen from grub to xdm.
I tried everything -- used the "quiet" option in grub's config, added dmesg -n 1 to rc.local, changed console=ttySx, set kernel.printk in sysctl.conf to 4 1 1 7, and even eradicated rsyslogd altogether... to no avail. I still see all sorts of messages on my screen.
Howto hide boot text messages on the screen during Lenny startup? I've tried to change in /boot/grub/menu.lst:
Code: ## additional options to use with the default boot option, but not with the ## alternatives ## e.g. defoptions=vga=791 resume=/dev/hda5 # defoptions=quiet splash
The system crontab (/etc/crontab) uses the same format, except that the username for the command is specified after the time and date fields and before the command.
[code]...
Every hour, I get an e-mail complaining about the first line of the crontab:
[code]...
I get the same complaint from the other entries: It looks to me as if cron, or anacron, is trying to execute the user (root) as a command. Predictably, the shell doesn't like it, so barfs and triggers an e-mail about it. Why is this not doing what the man page says it should do? The 2nd problem I believe is related to exim, not cron. The e-mails I'm getting above are being bounced from my ISP because they are directed to root@myisp.com, rather than my regular e-mail address. When the message bounces, it bounces to my regular e-mail address. In /etc/aliases, I have root: [URL]... and in etc/email-addresses I have root: [URL]... Adding the entry to /etc/email-addresses allowed the bounce to find me because the sender's address is [URL]... but how can I get cron to send these messages to me in the first place, instead of root?
Installed 6.01a from DVD 1 on a system with 4GB ram. Installer installed amd64 version by default. When I try to install amd64.deb files I get "wrong architecture" error messages from the package manager. root@Laptop-RalphDeb:/home/ralphq# uname -r 2.6.32-5-amd64 root@Laptop-RalphDeb:/home/ralphq# uname -p unknown Why I can install amd64 programs and why I get unknown for the uname -p command?
More than 7 G bytes were logged to the messages file last three weeks I got this message in /var/log/messages I want to stop this messaging cause it takes to much space
I've got a Shorewall (Shoreline?) firewall up and running, but it's logging to /var/log/messages. I'd much rather have it logging to another location e.g. /var/log/firewall but can't find (a clear enough) explanation on how to do this. Apparently, it varies greatly depending on the distro, the kernel, and the version of Shorewall that is running. You'd think it would be something as simple as setting a path in a config file, but apparently not. I'm running a stock Lenny kernel on the firewall machine. It comes with version 4.0.15 of Shorewall.
So everytime I resume Ubuntu from hibernation, it remains black for a time then 2 messages on the screen appear for about 10 seconds before I can log-in:
Code: [ 0.556247] [drm:init_ring_common] *ERROR* render ring head not reset to zero ctl 00000000 head 02001000 tail 00000000 start 02001000 [ 0.556320] [drm:init_ring_common] *ERROR* render ring head forced to zero ctl 00000000 head 00000000 tail 00000000 start 02001000
I need help in setting up the native e-mail client included in Debian Squeeze. My ultimate goal is to have the Debian e-mail client download e-mail messages and process attachments automatically.
I am running Sid. After a dist-upgrade, when I boot into a DE, trying to run applications doesn't work.
If I click on an icon, I see a "Starting <Application>" icon on the task bar and then it dies. If I try running Alt-F2 and then typing the name of the application, nothing happens.
I just upgraded one of my non-mission-critical servers to squeeze just to see how it would go. Since the upgrade NFS is broken. When I try to start it I get:
Starting NFS kernel daemon: nfsdrpc.nfsd: unable to resolve ANYADDR:nfs to inet address: Servname not supported for ai_socktype rpc.nfsd: unable to set any sockets for nfsd failed!
I've tried searching on those errors, but all I've found is that this has happened to others when no network interfaces are started; this is clearly not the case with this server, since other services are running and working on both interfaces.
