Re: DPKG install fails with read only filesystem on non read-only filesystem
Hello again, this is a wonderful case where rubberduck-debugging might have made sense. Right after submitting this mail I found the error. The webserver that runs the install script has a systemd unit with ProtectSystem=full set. This prevents writes to /usr even though its not specifically read only. Since with sudo its a subprocess of the parent this restriction also applies to the install script. Sorry for the spam, I hope this entry might help future people with a similar problem, Felix On 26/03/2017 17:46, Felix Winterhalter wrote: > Hello, > > for various reasons I am currently writing a script to install packages > by calling dpkg -i package.deb. > > This mechanism has worked fine for a while. Now I need to call said > script using sudo noninteractively from a webserver. > > This leads me to my error: > > Mar 26 11:36:42 debbuilder package-updater[32246]: (Reading database ... > 124404 files and directories currently installed.) > Mar 26 11:36:42 debbuilder package-updater[32246]: Preparing to unpack > .../package_0.2_all.deb ... > Mar 26 11:36:42 debbuilder package-updater[32246]: Unpacking package > (0.2) over (0.2) ... > Mar 26 11:36:42 debbuilder package-updater[32246]: dpkg: error > processing archive /tmp/package-update-unpack/unpack/package_0.2_all.deb > (--install): > Mar 26 11:36:42 debbuilder package-updater[32246]: unable to clean up > mess surrounding `./usr/share/doc/package' before installing another > version: Read-only file system > Mar 26 11:36:42 debbuilder package-updater[32246]: Errors were > encountered while processing: > Mar 26 11:36:42 debbuilder package-updater[32246]: > /tmp/package-update-unpack/unpack/package_0.2_all.deb > > Neither /tmp nor /usr is non writeable. > > Calling the package install script manually via sudo from a normal user > runs everything as normal without any error. So the package itself is > not a problem ( apparently ). > > I've been trying to find the source of this error since a couple of > hours now. I haven't been able to make any real progress and was > wondering whether anyone here would have an idea whats going wrong. > > This error is happening on two independent debian systems. > > / is mounted > > /dev/sda1 on / type ext4 (rw,relatime,data=ordered) > > tmp is a normal folder not another mountpoint > > The packages are uploaded via a python webserver. However the package > integrity is checked before applying the install. The packages > themselves are intact. > > Best regards, > Felix >
DPKG install fails with read only filesystem on non read-only filesystem
Hello, for various reasons I am currently writing a script to install packages by calling dpkg -i package.deb. This mechanism has worked fine for a while. Now I need to call said script using sudo noninteractively from a webserver. This leads me to my error: Mar 26 11:36:42 debbuilder package-updater[32246]: (Reading database ... 124404 files and directories currently installed.) Mar 26 11:36:42 debbuilder package-updater[32246]: Preparing to unpack .../package_0.2_all.deb ... Mar 26 11:36:42 debbuilder package-updater[32246]: Unpacking package (0.2) over (0.2) ... Mar 26 11:36:42 debbuilder package-updater[32246]: dpkg: error processing archive /tmp/package-update-unpack/unpack/package_0.2_all.deb (--install): Mar 26 11:36:42 debbuilder package-updater[32246]: unable to clean up mess surrounding `./usr/share/doc/package' before installing another version: Read-only file system Mar 26 11:36:42 debbuilder package-updater[32246]: Errors were encountered while processing: Mar 26 11:36:42 debbuilder package-updater[32246]: /tmp/package-update-unpack/unpack/package_0.2_all.deb Neither /tmp nor /usr is non writeable. Calling the package install script manually via sudo from a normal user runs everything as normal without any error. So the package itself is not a problem ( apparently ). I've been trying to find the source of this error since a couple of hours now. I haven't been able to make any real progress and was wondering whether anyone here would have an idea whats going wrong. This error is happening on two independent debian systems. / is mounted /dev/sda1 on / type ext4 (rw,relatime,data=ordered) tmp is a normal folder not another mountpoint The packages are uploaded via a python webserver. However the package integrity is checked before applying the install. The packages themselves are intact. Best regards, Felix
Re: GDM3 Duplicates Menus Clocks Workspace Switcher etc.
Hi Jörg, the error was caused because the old Gnome 3 Versions didn't have a check implemented for multiple monitors and just produced a menu for each monitor it found. It shouldn't happen anymore with the latest versions of Gnome 3 and gdm. So to fix the problem I would recommend: Update your gnome to the latest version (for debian the latest stable would be on wheezy right now), then proceed to delete all configuration related to gnome to reset your menus to default. Best regards, Felix On 20.11.2013 22:36, Jörg Wynands wrote: Hi Felix, found your post because i have the identical problem. Maybe you found a solution meanwhile? Best regards Jörg -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/528d201e.6010...@audiofair.de
GDM3 Duplicates Menus Clocks Workspace Switcher etc.
Hey there everyone, I just installed debian wheezy and I get the following problem with gdm3: Every time I login the menu items are added again (to the already existing items) and the clock is added and the logout menu is also added as is the workspace switcher and the taskbar ... So after 3 logins I now have three of every sort ... reinstalling gdm didn't even remove the menu entries neither did completely rm -R * ing the home directory I have no idea what to do anymore I am using a Dual Screen Setup which I had lots of trouble setting up using the free driver for ATI cards so I switched to the proprietary one and used the initalize function of aticonfig for two monitors. However Gnome shows still only one monitor in its system settings, maybe that could be related... I am very grateful for any idea! Thanks in Advance, Felix Screenshot: http://i.imgur.com/PfWgl0f.png -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50fae704.1010...@audiofair.de
