M12 11.9.92

[BurtHulland]

I hate it when that happens.

I love it when a bootable USB is working properly, but for me anyway it's easier most of the time to burn a disk.

Uncle mark, this is the first time a key has gone bad on me. It is much easier and quicker as I see it to use a USB key (assuming I have one available) than to burn a disk. I only do that when I can't use a USB key for some reason.

[richb]

What was in mine below. I only added the last line.

Which is a typical Mepis 12 way of doing it, (I know yours is from Kubuntu)
what you are doing is letting the original script setup a color, and then resetting it again, Why? set it up from within the original script then it works as it should, without an extra action,
It is doing things like this that make booting from a Mepis 12 DVD as slow as it is, plus it takes more resources because the system is going round in circles before it finds out just what it should be doing.

Why? Because I was too dumb to do any different.

[Paul..]

I hate it when that happens.

I love it when a bootable USB is working properly, but for me anyway it's easier most of the time to burn a disk.

Uncle mark, this is the first time a key has gone bad on me. It is much easier and quicker as I see it to use a USB key (assuming I have one available) than to burn a disk. I only do that when I can't use a USB key for some reason.

Burt, my wife teaches photography and burns through USB keys like nobody's business...the kid's all use them to take their photos home and they get heavy use.

[smilliken]

Just a finding with my 64 bi install. I noticed that when I try to go from Windows 8 to Mepis on a reboot, Mepis get to the login screen and lets me place my password in, I press enter and I get the splash screen, but then the computer hangs, doesn't get to the desktop. If do a hard shutdown from there and then restart the laptop, it comes right to the desktop. I've tried this a half a dozen times with the same results each time.

It may be something simple or nothing at all.

[BurtHulland]

Burt, my wife teaches photography and burns through USB keys like nobody's business...the kid's all use them to take their photos home and they get heavy use.

That's the difference - I only use them (with one exception) for ISO files to install vaious distributions. So they don't get erased very often; that is what kills flash ROM's.

The exceptioin is a 64-gig chip I use to reinstall the data files in the directories I use in place of a saved 'home'; with that the data files can be used with ANY linux distro. This allows me to make installations for test or production use without losing any data. I rewrite the changed files on it every month or so. (Normally these files are kept up to data via the clouds.)

[zeeone]

What was in mine below. I only added the last line.

Code:
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything
case $- in
*i*) ;;
*) return;;
esac

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar

# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi

if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
;;
*)
;;
esac

# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'

alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'
fi

# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'

# Add an "alert" alias for long running commands. Use like so:
# sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.

if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
if [ -f /usr/share/bash-completion/bash_completion ]; then
. /usr/share/bash-completion/bash_completion
elif [ -f /etc/bash_completion ]; then
. /etc/bash_completion
fi
fi
export PS1="\e[1;32m\u[\w]\\$ \e[m "
____________________________________________________________________________________________________________________

In every distro that uses the BASH terminal that so far that I have checked, the .bashrc user file is the same, line for line. So all one has
to do is remove the # and save the file. Then there will be green for user and red for root.

[JBoman]

having occasional system freeze up while watching newscasts on the net... audio continues but video freezes and system becomes unresponsive to all input from keyboard or mouse...requires a hard kill and reboot when it happens. Any ideas appreciated. Using desktop machine in sig is a Dell Optiplex 740 slimline.

[beckwith]

Joany has said I should post this problem under M12 - originally it was
thread 322381 under 64bit Regulars.
I have M11.9.70_64 installed - for a quite a while - since it was first
released. My problem is is that apps running under Wine will not print.
Originally the app would "hang" and had to be terminated. After changing
the printer settings to "share published printers" and "allow printing
from the Internet" the app no longer "hangs" but still does print.
Nothing every appears in the queue. The Printer is an HP2050 using
hpsups3.12.6, the kernel is 3.5-1-mepis64. Ia32libs and Lib32bss-mdns
are installed. Wine is 1.4.1
I only use two apps unders Wine: neither will print, both are old...
Word97 and PDG7. I only use Word to confirm that saving a doc in
Word format is acceptable to my publisher. PDG7 is label printing app.
It's not a mjor problem, but M12 is long time coming, and maybe no
one else has noticed this problem.

[DBeckett]

 
Sorry if this has been brought up already, but has anyone mentioned this?

http://packages.debian.org/wheezy/libwine-print

[KBD]

Had my first issue, though it was probably KDE and not Mepis. Using Mepis to stream video through my 42" TV. I had all the power management turned off, and it worked fine, but after I recently ran updates it started shutting off the screen after 10 minutes. I looked this up an its a very old KDE issue, which makes me wonder if someone didn't add it back in where it had been fixed. I fixed it by turning on Dim and Power Saver under power managment and setting for 360 min.
I think I'm going to do as suggested by someone on the list and set all my Wheezy installs only to update security. I can't stand updates breaking or otherwise creating issues in systems that worked perfectly. Anyway, everything else has been flawless for me in Wheezy across 4 installations, 3 KDE and 1 Gnome Wheezy.