Updates I installed in the last week or so have caused this error message to
appear instead of the disk being mounted:
Error mounting /dev/sr1 at /run/media/mick/VMDVEC_ESSH_ENG1: Command-line
`mount -t "iso9660" -o
"uhelper=udisks2,nodev,nosuid,uid=1000,gid=100,iocharset=utf8,mode=0400,dmode=0
> I had to modify the default signature verification in
> `/etc/pacman.conf` to
>
> SigLevel = Required DatabaseOptional TrustAll
>
> and now it's looking good.
FYI, turns out this wasn't enough for all cases. No combination of
signature levels, updating mirrors/databases, clearing
/etc/pacm
>
> if you run pacman -S gutenprint you will see this in the output:
>
> >>please run /usr/bin/cups-genppdupdate
> >>and restart cups deamon
>
> Run the command as root.
>
This fixed the problem, thank you for your quick reply.
In Archlinux it pays off to update in a terminal and to read the spa
On Tue, 10 Jun 2014 12:40:18 -0600
Squall Lionheart wrote:
> Since about three weeks ago after an update, I have no longer been
> able to print using CUPS. When I send a job to the print queue, it
> generates this message:
>
> stopped
> *"The PPD version (5.2.9) is not compatible with Gutenpri
I had a different problem but it might help. After upgrading to the new
CUPS I had to delete and re-add my printer before I was able to resume
printing.
On Tue, Jun 10, 2014 at 11:40 AM, Squall Lionheart <
headmastersqu...@gmail.com> wrote:
> Hello,
>
> Since about three weeks ago after an updat
This is an odd issue. I'm not sure why GDM or Lightdm are misbehaving
like this; this is a brand new issue and I am not sure as to the
culprate. There are, in fact, lines below the cleaning status. Looks
to me like part of the init process: I see a two lines from netctl
saying that it is restoring
Hello,
Since about three weeks ago after an update, I have no longer been able to
print using CUPS. When I send a job to the print queue, it generates this
message:
stopped
*"The PPD version (5.2.9) is not compatible with Gutenprint 5.2.10."*
I was unable to find anything helpful through the se
Hunter Jozwiak writes:
> installation of Gnome. I can't change TTY's, either. How do I get rid
> of this issue?
"can't change TTYs" usually means it's either disabled in xorg.conf, or
the keyboard isn't set up correctly.
--
Knowledge is volatile and fluid. Software is power.
On Tue, Jun 10, 2014 at 03:06:12PM +0200, Bjørnar Hansen wrote:
> On Sun, Jun 8, 2014 at 10:21 PM, Magnus Therning wrote:
>> I did the following
>>
>> - start the systemd service envoy@ssh-agent.socket
>> - add pam_envoy.so to /etc/pam.d/system-login
>>
>> That got it working for ssh, but not for
Hi all. After installing Arch and getting everything all nice and
setup, I've hit a bit of an issue. When I boot in to the system, I get
this: Arch: clean, 210545/15269888 files, 2401901/61048873 blocks.
This number is permanent, and won't move. It may be an issue after
installation of Gnome. I can
(Fri, Jun 06, 2014 at 07:14:45PM +0200) Magnus Therning :
> The instructions at [^1] are for the shell and for using ~/.xinitrc to
> start X. So neither is very well suited for me as I'm letting GDM log
> me in to Gnome without use of ~/.xinitrc and the agent has to be
> available also to apps sta
(Tue, Jun 10, 2014 at 03:06:12PM +0200) Bjørnar Hansen :
> On Sun, Jun 8, 2014 at 10:21 PM, Magnus Therning wrote:
> > I did the following
> >
> > - start the systemd service envoy@ssh-agent.socket
> > - add pam_envoy.so to /etc/pam.d/system-login
> >
> > That got it working for ssh, but not for g
On Sun, Jun 8, 2014 at 10:21 PM, Magnus Therning wrote:
> I did the following
>
> - start the systemd service envoy@ssh-agent.socket
> - add pam_envoy.so to /etc/pam.d/system-login
>
> That got it working for ssh, but not for gpg. Is there something else
> I should do to also get gpg-agent suppor
13 matches
Mail list logo
