Re: apt-get errors
On Mon, Sep 29, 2014 at 02:20:04PM -0500, John Aten wrote: > Hi all, > > I recently installed Debian Wheezy on an old Dell Inspiron laptop. It's > working pretty well, aside from a few hiccups. One of these happens when > updating. apt-get update returns the following errors: > > Err http://http.us.debian.org wheezy/non-free i386 Packages > 404 Not Found [IP: 128.61.240.89 80] [snip] Just happened to me too few mins ago with http://ftp.it.debian.org, usually (very rarely) when it happen I assume is the mirror still not synced, so I wait a while (from few hours to a couple of days) before changing mirror in /etc/apt/sources.list. (now is just fine, work again) > > > I ran the command again, and got this: > > E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource > temporarily unavailable) > E: Unable to lock directory /var/lib/apt/lists/ > > Is there anything I can do about this? Probably apt is still executing or crashed without removing /var/lib/apt/lists/lock, you should make sure isn't running then I think /var/lib/apt/lists/lock could be safely removed. Cheers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140929220335.GA1138@hellspawn
Re: chromium >= 37.0.2062.117 on i386
On Thu, Sep 25, 2014 at 09:45:24PM +0200, Alex Andreotti wrote: > On Thu, Sep 25, 2014 at 09:33:50PM +0200, Sven Joachim wrote: > > On 2014-09-25 21:10 +0200, Alex Andreotti wrote: > > > > > Hello, > > > > > > is there a way to get a .deb of chromium >= 37.0.2062.117 on arch > > > i386? (unstable/sid) > > > (if need to be built it is ok if there's a debian/rules) > > > > Since the package FTBFS on the buildd, your only chance is to build from > > source. Which is likely not to work, but at least you can try. > > > > > The cpu is an amd64 (with sse2 support) but I've the system installed > > > as i386. > > > > You want to have at least 4 GB of RAM and 15 GB disk space free. The > > build is likely going to take a few hours, unless it fails early. > > > > Good luck, > > I'll give a try :) > Thank you You were right about the numbers dpkg-buildpackage -rfakeroot -uc -b -j4 28439,94s user 6571,60s system 280% cpu 3:28:10,43 total du -sh ~/src/chromium-deb 12G compiling take an average of 2G or less but the final link is critical 3.5G+ (my desktop take about 250M) I had to close some chromium window :) Installed and running so far, my <3 to the maintainers. Cheers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140925233646.GD30826@hellspawn
Re: chromium >= 37.0.2062.117 on i386
On Thu, Sep 25, 2014 at 04:17:54PM -0400, Bob Weber wrote: > On Thu, Sep 25, 2014 at 09:33:50PM +0200, Sven Joachim wrote: > >> On 2014-09-25 21:10 +0200, Alex Andreotti wrote: > >> > >>> Hello, > >>> > >>> is there a way to get a .deb of chromium >= 37.0.2062.117 on arch > >>> i386? (unstable/sid) > >>> (if need to be built it is ok if there's a debian/rules) > >> Since the package FTBFS on the buildd, your only chance is to build from > >> source. Which is likely not to work, but at least you can try. > >> > >>> The cpu is an amd64 (with sse2 support) but I've the system installed > >>> as i386. > >> You want to have at least 4 GB of RAM and 15 GB disk space free. The > >> build is likely going to take a few hours, unless it fails early. > >> > >> Good luck, > > I'll give a try :) > > Thank you > > Just install from google: https://www.google.com/chrome/browser/beta.html > > I am using it in testing (64 bit) and a vm with debian 7.5 (32 bit) both at > version 38.0.2125.77 beta. It even comes with pepperflash Version 15.0.0.152. > > ...bob Thank you Bob that's seem a nice one, I'll give a try later even if the build ends properly (still in progress, looks clean till now and what a surprise... clang) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140925211415.GC30826@hellspawn
Re: chromium >= 37.0.2062.117 on i386
On Thu, Sep 25, 2014 at 09:33:50PM +0200, Sven Joachim wrote: > On 2014-09-25 21:10 +0200, Alex Andreotti wrote: > > > Hello, > > > > is there a way to get a .deb of chromium >= 37.0.2062.117 on arch > > i386? (unstable/sid) > > (if need to be built it is ok if there's a debian/rules) > > Since the package FTBFS on the buildd, your only chance is to build from > source. Which is likely not to work, but at least you can try. > > > The cpu is an amd64 (with sse2 support) but I've the system installed > > as i386. > > You want to have at least 4 GB of RAM and 15 GB disk space free. The > build is likely going to take a few hours, unless it fails early. > > Good luck, I'll give a try :) Thank you -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140925194524.GB30826@hellspawn
chromium >= 37.0.2062.117 on i386
Hello, is there a way to get a .deb of chromium >= 37.0.2062.117 on arch i386? (unstable/sid) (if need to be built it is ok if there's a debian/rules) The cpu is an amd64 (with sse2 support) but I've the system installed as i386. Thanks in advance Cheers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140925191055.GA30826@hellspawn
semi-random boot problem
Hello all, I've a problem within the initrd, *sometime* it fail to mount the root directory and after a while it fall back to the shell. My guess is a timing issue, the ssd disk "attach" before some process (udev?) is listening for disk events, but it is only a guess. I recently added an ssd disk, the grub is in sda, the / is in sdb. sdb is partitioned as GPT and the grub entry is by uuid. The initrd try to mount /dev/disk/by-uuid/blablabla, when it fail /dev/disk doesn't exist at all. kernel version: 3.14-1-686-pae initramfs-tools 0.115 k command line: /boot/vmlinuz-3.14-1-686-pae root=UUID=0feeec25-eea0-487d-906e-1590990911a0 ro noresume gfxpayload=true quiet ipv6.disable=1 Somebody experienced this problem already or have suggestions where to look? Thanks in advance Cheers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140513122135.GC8969@hellspawn
Re: Confusion
On Thu, May 08, 2014 at 04:31:03PM +0930, josh wrote: > Hi, [snip] > I have downloaded 'wheezy' and created a CD from the Iso image. When I > attempt to boot from the CD the screen image comes up, I respond to a > few options, then the system reports unable to read from the CD - which > it has, of course, been doing. This recall to my mind a Windows (so sorry to name it here) bug where bios calls were used on first stage boot but then the real driver was missing (sata if I remember correctly). Long time I don't use a Debian installer to install a Debian but I'm pretty sure you can use alt+function keys (or alt+ctrl+function) while installing when you get the error to get a shell and begin investigate the problem looking for error messages, even plug some pendrive and collect some log to share with the list. [snip] Good luck Cheers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140508225515.GB14227@hellspawn
Re: boot in console mode from grub2
On Mon, May 05, 2014 at 10:21:55PM +0300, Andrei POPESCU wrote: > On Lu, 05 mai 14, 13:43:54, Steve Litt wrote: > > > > I'm confused. Wasn't what the OP wanted a boot in regular text mode, no > > GUI, no framebuffer, just ascii codes straight to the monitor? That > > happens *a long time* before the display manager runs. > > The OP said no GUI, but nothing about framebuffer. > > [snip] Ehm, sorry maybe I miss some email about this thread but.. if all the OP want is just to not start X: - sysv-init: - disable the *dm service assuming default runlevel is 2 in /etc/inittab eg: # mv /etc/rc2.d/S03lightdm /etc/rc2.d/K03lightdm - or edit another runlevel eg: do it in /etc/rc3.d then append 3 to grub's kernel command line - systemd: - change the default.target from graphical to multi-user (I'm still a newbie of systemd don't know how to change it on Debian in a persistent way, should be a symbolic link) but on kernel command line you could be able to overwrite the default with systemd.unit=multi-user.target Hope it help. Cheers [snip] -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140508222629.GA14227@hellspawn
Re: systemd-udevd: failed to execute /lib/udev/kmod
On Mon, May 05, 2014 at 06:06:58PM +0200, Michael Biebl wrote: > Am 05.05.2014 17:03, schrieb Alex Andreotti: > > > systemd-udevd[253]: failed to execute '/lib/udev/kmod' 'kmod sg': No > > such file or directory > > Fixed in systemd.git: > http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=commitdiff;h=f11a2ddeb6a43f99179f2f9d322ee08cb41db5b0 > > Will be part of the next upload. Thanks, it work. Regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140505171722.GA1607@hellspawn
systemd-udevd: failed to execute /lib/udev/kmod
Hello, I'm running a jessie/sid in [ReadonlyRoot](https://wiki.debian.org/ReadonlyRoot) over an ssd. Recently it just dist-upgraded to systemd, apart a little dependency on debian-fixup.service (var.mount) almost everything seem to work fine. But there's this following error I can't find nothing about, any hint would be apreciated. Thanks in advance. systemd[1]: Starting udev Kernel Device Manager... systemd[1]: Started udev Kernel Device Manager. systemd-udevd[253]: failed to execute '/lib/udev/kmod' 'kmod sg': No such file or directory -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140505150323.GA18774@hellspawn
