Google Chrome breaks cups
Google Chrome breaks cups
Maybe it's the wrong section...and I suppose this has already been discovered by other users...anyway, installing google chrome (the .deb one from google site) breaks cups, you can't print anymore, nor enter in any section of the cups page to configure the printer...maybe someone has solved this issue?
Google Chrome breaks cups
I noticed the same problem.
It's easy enough to start over again (re-install puppy or use a new save file). That will bring CUPS back.
I also found a nice thread about re-installing CUPS. Hope this helps.
http://www.murga-linux.com/puppy/viewtopic.php?t=40665
It's easy enough to start over again (re-install puppy or use a new save file). That will bring CUPS back.
I also found a nice thread about re-installing CUPS. Hope this helps.
http://www.murga-linux.com/puppy/viewtopic.php?t=40665
[color=darkblue][size=150]1st rule of intelligent tinkering - save all the parts.
-- Source Unknown[/size][/color]
-- Source Unknown[/size][/color]
Re: Google Chrome breaks cups
Yuck!! Generally, it turns out that a permission got changed somewhere. I converted the pet (or deb) to an sfs, and am not having problems. SFS would be less likely to overwrite anything, so might be worth a try.johndgeek wrote:
It's easy enough to start over again (re-install puppy or use a new save file). That will bring CUPS back.
Because Puppy can install a DEB file just by clicking on it, people assume that this a legitimate way to install software. Unfortunately, some DEBs contain ownership and permission information that is incompatible with Puppy.
Normally, you won't see a problem because the default root user in Puppy will override any conflicts. But CUPS works as a non-privileged user and will fail when it sees the conflict. People then tend to blame CUPS for the failure.
Normally, you won't see a problem because the default root user in Puppy will override any conflicts. But CUPS works as a non-privileged user and will fail when it sees the conflict. People then tend to blame CUPS for the failure.
- KusaNoKaito
- Posts: 99
- Joined: Fri 19 Feb 2010, 22:52
- Location: Florida
- Contact:
I was just experimenting with the idea of locking down cup files so ownership/permissions can't get changed. The printer seems to still work. The files could be unlocked for adding/managing.rcrsn51 wrote:Because Puppy can install a DEB file just by clicking on it, people assume that this a legitimate way to install software. Unfortunately, some DEBs contain ownership and permission information that is incompatible with Puppy.
Normally, you won't see a problem because the default root user in Puppy will override any conflicts. But CUPS works as a non-privileged user and will fail when it sees the conflict. People then tend to blame CUPS for the failure.
Code: Select all
#!/bin/bash
## Locks in printer permissions: root:nobody
## To reverse, change to "chattr -i"
[ -f /tmp/list ] && rm /tmp/list
cd /etc/cups
ls -l | grep "nobody" | cut -d " " -f8 >>/tmp/list
cd /initrd/pup_rw/etc/cups
while read line; do
chattr +i "$line"
done < /tmp/list
chattr -R +i /initrd/pup_rw/var/cache/cups
chattr -R +i /initrd/pup_rw/var/log/cups
rm /tmp/list
### Note: leave /var/spool alone
#chattr -R -i /initrd/pup_rw/var/spool/cups