Re: The same environment variables everywhere
Am 26.02.2017 um 13:26 schrieb Teemu Likonen: > I would like to hear some ideas on how to set various environment > variables (PATH, MANPATH, EDITOR etc.) in one place that would make them > effective everywhere. My "everywhere" means: > > - X session started through lightdm and ~/.xsession script > - Linux console login (bash) > - user's systemd services Put them into /etc/environment. Matthias
Re: kernel performance: 3.16 vs. 4.9
Am 06.02.2017 um 00:12 schrieb Ben Caradoc-Davies: > On 06/02/17 09:59, Matthias Bodenbinder wrote: >> Am 05.02.2017 um 09:03 schrieb Matthias Bodenbinder: >>> Hi, >>> I have upgraded my PC to newest chipset and CPU: Kaby Lake, Z270 with >>> i7-7700K. >>> Out of curiosity I did a kernel benchmark. Comparing darktable performance >>> with kernel 3.16.0-4-amd64 and 4.9.0-1-amd64. I use the following command >>> to run darktable: >>> darktable-cli test.CR2 test.jpg --core -d perf -d opencl >>> The results are surprising for me. Kernel 4.9 very much outperformance >>> kernel 3.16. Here are the results with and without opencl (using a Geforce >>> GTX750TI): >>> kernel 3.16kernel 4.9 >>> with opencl16 s9 s >>> without opencl120 s23 s >>> Without opencl, that is with pure CPU performance, the difference is a >>> factor of 5! >>> Why is that? What am I missing? I can hardly believe that kernel 4.9 is so >>> much faster. >>> Matthias >> Hi, >> the issue is solved. It is related to the CPU frequency driver acpi-cpufreq >> vs. intel_pstate and the governor powersave vs. >> performance. >> With kernel 4.9 the default CPU frequency driver for my hardware is >> intel_pstate. And I had the governor set to "powersave" in >> /etc/default/cpufrequtils. I do not see big performance differences between >> "powersave" and "performance" settings with intel_pstate. >> But with kernel 3.16 the default CPU frequency driver is acpi-cpufreq. With >> my settings in /etc/default/cpufrequtils it running in "powersave" mode >> which is giving this dramatic performance collapse. With governor "ondemand" >> or "performance" kernel 3.16 is as fast as kernel 4.9. >> Sorry for the confusion. >> Matthias > > Matthias that is very interesting. Your findings seem different to those > reported on Phoronix; no doubt the p-state driver is undergoing some changes > to improve Kaby Lake support: > http://www.phoronix.com/scan.php?page=article&item=pstate-cpufreq-kbl&num=1 > http://www.phoronix.com/scan.php?page=article&item=pstate-cpufreq-kbl&num=2 > https://www.phoronix.com/scan.php?page=news_item&px=P-State-Kabylake-Patching > > Kind regards, > The phoronix article only compares the performance governors. It does not investigate the performance decrease with acpi-cpufreq+powersave. Based on the articles I made another test with kernel 4.9 + acpi-cpufreq + performance and compared it to kernel 4.9 + intel_pstate + performance. The difference after several runs is minimal 23-24 s for intel_pstate vs. 22 s for acpi-cpufreq. Not sure if that is meaningful but it seems to support what phoronix is reporting. Matthias
Re: kernel performance: 3.16 vs. 4.9
Am 05.02.2017 um 09:03 schrieb Matthias Bodenbinder: > Hi, > > I have upgraded my PC to newest chipset and CPU: Kaby Lake, Z270 with > i7-7700K. > > Out of curiosity I did a kernel benchmark. Comparing darktable performance > with kernel 3.16.0-4-amd64 and 4.9.0-1-amd64. I use the following command to > run darktable: > darktable-cli test.CR2 test.jpg --core -d perf -d opencl > > The results are surprising for me. Kernel 4.9 very much outperformance kernel > 3.16. Here are the results with and without opencl (using a Geforce GTX750TI): > > kernel 3.16 kernel 4.9 > with opencl 16 s9 s > without opencl120 s 23 s > > Without opencl, that is with pure CPU performance, the difference is a factor > of 5! > > Why is that? What am I missing? I can hardly believe that kernel 4.9 is so > much faster. > > Matthias > > > > Hi, the issue is solved. It is related to the CPU frequency driver acpi-cpufreq vs. intel_pstate and the governor powersave vs. performance. With kernel 4.9 the default CPU frequency driver for my hardware is intel_pstate. And I had the governor set to "powersave" in /etc/default/cpufrequtils. I do not see big performance differences between "powersave" and "performance" settings with intel_pstate. But with kernel 3.16 the default CPU frequency driver is acpi-cpufreq. With my settings in /etc/default/cpufrequtils it running in "powersave" mode which is giving this dramatic performance collapse. With governor "ondemand" or "performance" kernel 3.16 is as fast as kernel 4.9. Sorry for the confusion. Matthias
Re: kernel performance: 3.16 vs. 4.9
Am 05.02.2017 um 09:49 schrieb deloptes: > have a look at the code changes. Looking at the code changes from 3.16 to 4.9 ? Good idea. I will start right now ;-) Matthias
kernel performance: 3.16 vs. 4.9
Hi, I have upgraded my PC to newest chipset and CPU: Kaby Lake, Z270 with i7-7700K. Out of curiosity I did a kernel benchmark. Comparing darktable performance with kernel 3.16.0-4-amd64 and 4.9.0-1-amd64. I use the following command to run darktable: darktable-cli test.CR2 test.jpg --core -d perf -d opencl The results are surprising for me. Kernel 4.9 very much outperformance kernel 3.16. Here are the results with and without opencl (using a Geforce GTX750TI): kernel 3.16 kernel 4.9 with opencl 16 s9 s without opencl 120 s 23 s Without opencl, that is with pure CPU performance, the difference is a factor of 5! Why is that? What am I missing? I can hardly believe that kernel 4.9 is so much faster. Matthias
Re: can not set time
Am 04.02.2017 um 17:43 schrieb Jude DaShiell: On Sat, 4 Feb 2017, Matthias Bodenbinder wrote: Date: Sat, 4 Feb 2017 09:07:00 From: Matthias Bodenbinder To: debian-user@lists.debian.org Subject: Re: can not set time Resent-Date: Sat, 4 Feb 2017 14:07:22 + (UTC) Resent-From: debian-user@lists.debian.org Am 04.02.2017 um 14:36 schrieb Jude DaShiell: please check that other box and see if it has systemd-timesyncd.service on it. You can probably start that service up and solve that problem. Then try timedatectl set-ntp true. That should make timesync happen on boot. On Sat, 4 Feb 2017, Matthias Bodenbinder wrote: timedatectl set-ntp true did not help. It is not changing the time. My reference PC has debian testing running with systemd-timesyncd. But the broken PC is MINT LMDE which is still on init.d. Matthias Okay, since you have ntp, ntpd -qg and then hwclock --systohc --utc may get this working for you. We probably don't need to do anything with your timezone setting link to /etc/localtime by now. Hello Jude, I tried it all. I googled almost every command related to time setting and tried it out. But it did not work. I am still not sure why. But now, after switching to systemd and systemd-timesyncd it works. See my other post. Thank you for help anyways. Matthias
Re: can not set time
Am 04.02.2017 um 15:49 schrieb Matthias Bodenbinder: More info: I switched to systemd and systemd-timesyncd. During boot the time is synced back and forth multiple times and in the end it stays wrong. Look at this. See the timestamps for each line. Going back and forth. Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: Using NTP server 78.46.253.198:123 (2.debian.pool.ntp.org). Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.925s/0.016s/0.000s/+0ppm Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.914s/0.017s/323.505s/+0pp Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.904s/0.015s/792.414s/+0pp Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.894s/0.015s/723.371s/+0pp Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.885s/0.015s/647.003s/+0pp Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. The switch to systemd and systemd-timesyncd did the trick. But it takes very long. Its obvious from the journal messages but I did not get it at first: timesyncd changes the time in small increments of only 0.01 seconds. I just had to wait and now the time is correct. Matthias
Re: can not set time
More info: I switched to systemd and systemd-timesyncd. During boot the time is synced back and forth multiple times and in the end it stays wrong. Look at this. See the timestamps for each line. Going back and forth. Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: Using NTP server 78.46.253.198:123 (2.debian.pool.ntp.org). Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.925s/0.016s/0.000s/+0ppm Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.914s/0.017s/323.505s/+0pp Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.904s/0.015s/792.414s/+0pp Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.894s/0.015s/723.371s/+0pp Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.885s/0.015s/647.003s/+0pp Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.874s/0.016s/560.321s/+0pp Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.864s/0.015s/457.500s/+0pp Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.854s/0.015s/323.501s/+0pp Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.844s/0.015s/0.036s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.834s/0.015s/0.045s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.824s/0.016s/0.029s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.814s/0.015s/0.025s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.804s/0.015s/0.025s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.794s/0.015s/0.029s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.784s/0.015s/0.036s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.774s/0.016s/0.045s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.764s/0.016s/0.030s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.754s/0.015s/0.045s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.744s/0.015s/0.037s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.733s/0.016s/0.030s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.723s/0.015s/0.025s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.713s/0.015s/0.025s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.702s/0.017s/0.030s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44
Re: can not set time
Am 04.02.2017 um 14:36 schrieb Jude DaShiell: > please check that other box and see if it has systemd-timesyncd.service on it. > You can probably start that service up and solve that problem. > Then try timedatectl set-ntp true. > That should make timesync happen on boot. > On Sat, 4 Feb 2017, Matthias Bodenbinder wrote: timedatectl set-ntp true did not help. It is not changing the time. My reference PC has debian testing running with systemd-timesyncd. But the broken PC is MINT LMDE which is still on init.d. Matthias
can not set time
Hi, I have a weird issue with one of my debian boxes (LMDE): I can not set the time. The time is off by ca. 14 min and whatever I try to fix it is failing. I tried ntp, ntpdate, date and rdate. Nothing helps. ntpdate shows the offset but is not fixing it. 91# ntpdate 0.debian.pool.ntp.org 4 Feb 14:03:55 ntpdate[8159]: step time server 85.114.132.52 offset -855.296824 sec rdate is showing some interesting behaviour. If I run a command like "date && rdate -v ptbtime1.ptb.de && date" to see the time before and after rdate, the output suggests that rdate was successful: 81# date && rdate -v ptbtime1.ptb.de && date Sat Feb 4 14:16:04 CET 2017 Sat Feb 4 14:01:49 CET 2017 rdate: adjust local clock by -855 seconds Sat Feb 4 14:01:49 CET 2017 But in fact 1 second later the time is back to old values again: 82# date Sat Feb 4 14:16:06 CET 2017 timedatectl is showing wrong time as well: 93# timedatectl Local time: Sat 2017-02-04 14:20:39 CET Universal time: Sat 2017-02-04 13:20:39 UTC RTC time: Sat 2017-02-04 13:20:39 Time zone: Europe/Berlin (CET, +0100) But is should be: Local time: Sa 2017-02-04 14:06:25 CET Universal time: Sa 2017-02-04 13:06:25 UTC RTC time: Sa 2017-02-04 13:06:25 Time zone: Europe/Berlin (CET, +0100) I am lost. Matthias
Re: apt-get is not following preferences.d
Am 25.01.2017 um 20:04 schrieb Michael Lange: Hi, On Wed, 25 Jan 2017 07:18:07 +0100 Matthias Bodenbinder wrote: (...) I do not have that file /etc/apt/apt.conf.d/02periodic. I put /etc/cron.daily/apt back where it belongs and this morning the pinning was screwed up again. This is really weird. Then you could try to create the file and add the line APT::Periodic::Update-Package-Lists "0"; and see if that helps. Maybe your system somehow has a different default. Regards Michael I created that file with this line but it does not help. Still the same odd pinning after boot. So my problem might not be related to /etc/cron.daily/apt. I guess I have to start searching again :-( Matthias
Re: apt-get is not following preferences.d
Am 23.01.2017 um 11:47 schrieb Michael Lange: Hi, On Mon, 23 Jan 2017 08:40:32 +0100 Matthias Bodenbinder wrote: (...)Yes, this is exactly what happens on my PC. But it has no solution. In the meantime I found a workaround. I moved /etc/cron.daily/apt out of the way. It looks like this script is being executed during boot before the network is ready. How can I make sure that the script /etc/cron.daily/apt is only executed when network is up? What is this script good for anyways? From what the comment at the top of the script says: # This file understands the following apt configuration variables: # Values here are the default. # Create /etc/apt/apt.conf.d/02periodic file to set your preference. (...) # # APT::Periodic::Update-Package-Lists "0"; # - Do "apt-get update" automatically every n-days (0=disable) # it looks like you have a file /etc/apt/apt.conf.d/02periodic where APT::Periodic::Update-Package-Lists is set to "1" (or so). Here (on Jessie) such a file does not exist, and as promised the updates don't happen. Regards Michael Hello Michael, I do not have that file /etc/apt/apt.conf.d/02periodic. I put /etc/cron.daily/apt back where it belongs and this morning the pinning was screwed up again. This is really weird. Matthias
Re: apt-get is not following preferences.d
Am 12.01.2017 um 20:31 schrieb Sven Hartge: Matthias Bodenbinder wrote: What is going wrong here? Any idea? Possibly https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849382 Grüße, Sven. Yes, this is exactly what happens on my PC. But it has no solution. In the meantime I found a workaround. I moved /etc/cron.daily/apt out of the way. It looks like this script is being executed during boot before the network is ready. How can I make sure that the script /etc/cron.daily/apt is only executed when network is up? What is this script good for anyways? Matthias
Re: apt-get is not following preferences.d
Am 12.01.2017 um 19:43 schrieb Michael Lange: Just a shot in the dark: maybe the apt-get update at boot time is done before a network connection has been established? I noticed that this can lead to the exact behavior you describe when pinning is in use. Apparently a bug in apt. Regards Michael Hello Michael, I gave it a try. I unplugged the network and did an apt-get update. This is throwing all the errors that the repos are not available. But in the end the next "apt-get dist-upgrade" indeed wants to update all packages to testing. So it seems that this is an issue with network not ready while apt-get update is being performed. How do I fix this? Where to look? And thank you for the hint, Michael. Matthias
apt-get is not following preferences.d
Hi, I have a weird behaviour on one of my debian boxes. It is running Mint LMDE and the issue is the following: I have several additional sources defined: debian testing, debian backports, etc. I have defined priorities for the repos so that testing has prio 300 and does not replace the stable packages automatically. That works fine if I do an "apt-get update" followed by an "apt-get dist-upgrade". No issue. The issue only occurs directly after boot. Somehow there is an "apt-get update" excecuted during boot time and this is ignoring the repo priorities. If I do a "apt-get dist-upgrade" directly after boot it wants to upgrade all packages to the testing version ("1547 upgraded, 358 newly installed, 97 to remove and 36 not upgraded."). This is a mistake. After boot the priorities are all set to 500. Example: 12# apt-cache policy zip vim-common zip: Installed: 3.0-8 Candidate: 3.0-11 Version table: 3.0-11 0 500 http://ftp.de.debian.org/debian/ testing/main amd64 Packages *** 3.0-8 0 500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages 100 /var/lib/dpkg/status vim-common: Installed: 2:7.4.488-7+deb8u1 Candidate: 2:8.0.0134-1 Version table: 2:8.0.0134-1 0 500 http://ftp.de.debian.org/debian/ testing/main amd64 Packages *** 2:7.4.488-7+deb8u1 0 500 http://security.debian.org/ jessie/updates/main amd64 Packages 100 /var/lib/dpkg/status 2:7.4.488-7 0 500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages If I do an "apt-get update" everything is back to normal. 15# apt-cache policy zip vim-common zip: Installed: 3.0-8 Candidate: 3.0-8 Version table: 3.0-11 0 300 http://ftp.de.debian.org/debian/ testing/main amd64 Packages *** 3.0-8 0 500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages 100 /var/lib/dpkg/status vim-common: Installed: 2:7.4.488-7+deb8u1 Candidate: 2:7.4.488-7+deb8u1 Version table: 2:8.0.0134-1 0 300 http://ftp.de.debian.org/debian/ testing/main amd64 Packages *** 2:7.4.488-7+deb8u1 0 500 http://security.debian.org/ jessie/updates/main amd64 Packages 100 /var/lib/dpkg/status 2:7.4.488-7 0 500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages What is going wrong here? Any idea? Matthias
repository uses weak digest algorithm (SHA1)
Hi, I have a weird signature issue with an LMDE Mint repository. I know that this is not pure debian but nevertheless I think my question is best posted here. The issue is: I have 4 PC and 1 laptop at home. All running LMDE2. When I do "apt-get update" the PCs have no issue. But the laptop says: # last 2 lines of "apt-get update" output W: http://linux-mint.froonix.org/dists/betsy/Release.gpg: Signature by key E1A38B8F144675D060EA666F3EE67F3D0FF405B2 uses weak digest algorithm (SHA1) W: http://extra.linuxmint.com/dists/betsy/Release.gpg: Signature by key E1A38B8F144675D060EA666F3EE67F3D0FF405B2 uses weak digest algorithm (SHA1) ## I reinstalled all keyring debs on the laptop. I am using the exact same sources on the laptop and the PCs (rsync of /etc/apt/sources.list*). During the last test I even rsync'ed all /etc/apt/trusted* to the laptop. I tried to fetch it via apt-key: ## # apt-key adv --keyserver keyserver.ubuntu.com --recv-keys E1A38B8F144675D060EA666F3EE67F3D0FF405B2 Executing: /tmp/tmp.9xZlldxhO9/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys E1A38B8F144675D060EA666F3EE67F3D0FF405B2 gpg: requesting key 0FF405B2 from hkp server keyserver.ubuntu.com gpg: key 0FF405B2: "Clement Lefebvre (Linux Mint Package Repository v1) " not changed gpg: Total number processed: 1 gpg: unchanged: 1 ## But the laptop keeps throwing these signature warnings - and only the laptop. Why is that? Thank you for your help. Matthias
Re: btrfs: mixing raid0 and raid1 - How?
Hello Andy, I am trying to stay with newest versions as long as it does not jeopardize stability. I am using Mint LMDE2 with debian backports. So I do have kernel 4.4+71~bpo8+1 running. btrfs tools are from debian stable, which has version 3.17. I am wondering if it would make sense to also get the tools from the backports repo which has version 4.4-1~bpo8+1. I understand from your message that I should do that. Right? Matthias 4.4+71~bpo8+1 Am 16.04.2016 um 19:57 schrieb Andy Smith: > Hello, > > On Sat, Apr 16, 2016 at 01:35:20PM +0200, Luis Felipe Tabera Alonso wrote: >> Still btrfs is quite young, I am not sure if there are serious issues in >> 3.17, >> I would make some experiments before actual use. > > If you are going to use btrfs I would consider it essential to be > subscribed to the linux-btrfs mailing list. You will also need to > use a much newer kernel than 3.17, and you will need to commit to > continuing to use newer kernels for some time yet. > > I mention this because you need to be aware that you may still hit > issues where you need the help of linux-btrfs and that there is a > need to use newer kernels than you will find packaged in Debian > stable. > > I do myself run btrfs at home and I thought I had a stable > combination of kernel version and userland tools (btrfs-tools), but > when I came to need to replace a dead device I found that subsequent > developments in btrfs meant I needed a newer btrfs-tools, and that > in turn meant I needed a newer kernel. > > If the idea of having to upgrade kernel and some userland tools in > order to recover from a simple situation of a dead device does not > appeal to you then btrfs may not yet be for you. Things like this > are why I do not yet run it in production. > > Cheers, > Andy >
Re: btrfs: mixing raid0 and raid1 - How?
You are right. I did the same test with dd. It took a while ;-) 23# dd if=/dev/zero of=file.zero dd: Schreiben in „file.zero“: Auf dem Gerät ist kein Speicherplatz mehr verfügbar 1462670786+0 Datensätze ein 1462670785+0 Datensätze aus 748887441920 Bytes (749 GB) kopiert, 14831,9 s, 50,5 MB/s 24# ll -h insgesamt 698G -rw-r--r-- 1 root root 698G Apr 16 20:03 file.zero Thank you for helping me! Matthias Am 16.04.2016 um 13:35 schrieb Luis Felipe Tabera Alonso: > On sábado, 16 de abril de 2016 12:05:05 (CEST) Matthias Bodenbinder wrote: > >> 38# df -h /mnt/test/ >> Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf >> /dev/sdg 699G 17M 466G 1% /mnt/test > > df is not reliable for btrfs raids, it is better to use btrfs fi df to check > actual used space. > > Using btrfs-tools and kernel from sid (4.4): > > root@mychabol:/mnt/temporal# dd if=/dev/zero of=disk1 bs=1 count=0 seek=750M > root@mychabol:/mnt/temporal# dd if=/dev/zero of=disk2 bs=1 count=0 seek=500M > root@mychabol:/mnt/temporal# dd if=/dev/zero of=disk3 bs=1 count=0 seek=250M > > root@mychabol:/mnt/temporal# mkfs.btrfs -f -draid1 -mraid1 disk1 disk2 disk3 > btrfs-progs v4.4 > See http://btrfs.wiki.kernel.org for more information. > > Label: (null) > UUID: 4fbfda48-3a10-4e1b-92d8-96be759c2a8c > Node size: 16384 > Sector size:4096 > Filesystem size:1.46GiB > Block group profiles: > Data: RAID183.00MiB > Metadata: RAID183.00MiB > System: RAID112.00MiB > SSD detected: no > Incompat features: extref, skinny-metadata > Number of devices: 3 > Devices: >IDSIZE PATH > 1 750.00MiB disk1 > 2 500.00MiB disk2 > 3 250.00MiB disk3 > > root@mychabol:/mnt/temporal# losetup /dev/loop0 disk1 > root@mychabol:/mnt/temporal# losetup /dev/loop1 disk2 > root@mychabol:/mnt/temporal# losetup /dev/loop2 disk3 > > root@mychabol:/mnt/temporal# mkdir test > root@mychabol:/mnt/temporal# mount /dev/loop0 test > > root@mychabol:/mnt/temporal# btrfs fi df test/ > Data, RAID1: total=75.00MiB, used=0.00B > System, RAID1: total=8.00MiB, used=16.00KiB > Metadata, RAID1: total=75.00MiB, used=112.00KiB > GlobalReserve, single: total=16.00MiB, used=0.00B > > root@mychabol:/mnt/temporal# df -h test/ > S.ficheros Tamaño Usados Disp Uso% Montado en > /dev/loop0 750M17M 491M 4% /mnt/temporal/test > > Like in your case, df thinks that there are only 491M usable. However, if I > try to fill the volume > > root@mychabol:/mnt/temporal# cd test/ > root@mychabol:/mnt/temporal/test# dd if=/dev/zero of=file.zero > dd: escribiendo en 'file.zero': No queda espacio en el dispositivo > 1345402+0 registros leídos > 1345401+0 registros escritos > 688845312 bytes (689 MB, 657 MiB) copied, 3,10508 s, 222 MB/s > > root@mychabol:/mnt/temporal/test# ls -lh > total 657M > -rw-r--r-- 1 root root 657M abr 16 13:24 file.zero > root@mychabol:/mnt/temporal/test# df -h . > S.ficheros Tamaño Usados Disp Uso% Montado en > /dev/loop0 750M 674M 64K 100% /mnt/temporal/test > > With the 75M of metadata, you can check that this fills the three devices. > Moreover > > root@mychabol:/mnt/temporal/test# rm file.zero > root@mychabol:/mnt/temporal/test# df -h . > S.ficheros Tamaño Usados Disp Uso% Montado en > /dev/loop0 750M17M 657M 3% /mnt/temporal/test > > Try to do the same to see if df gets more accurate. > > Still btrfs is quite young, I am not sure if there are serious issues in > 3.17, > I would make some experiments before actual use. > > Bests > > Luis > >
Re: btrfs: mixing raid0 and raid1 - How?
And: 39# btrfs filesystem show Label: none uuid: 35db7af4-a116-45fa-8611-97aeb5d4a8d3 Total devices 3 FS bytes used 640.00KiB devid1 size 698.64GiB used 2.02GiB path /dev/sdg devid2 size 465.76GiB used 1.01GiB path /dev/sdh devid3 size 232.88GiB used 1.01GiB path /dev/sdi Am 16.04.2016 um 12:05 schrieb Matthias Bodenbinder: > Hello Luis, > > I followed that link which confirms that a btrfs raid1 out of these three > devices should give 750 GB of data capacity. But his is not what I get. > > This is what I have: > > Disk /dev/sdg: 698,7 GiB, 750156374016 bytes, 1465149168 sectors > Disk /dev/sdh: 465,8 GiB, 500107862016 bytes, 976773168 sectors > Disk /dev/sdi: 232,9 GiB, 250058268160 bytes, 488395055 sectors > > So it is actually not 750 GB but 700. Anyways... > > This is what I did: > > ### > 35# mkfs.btrfs -f -d raid1 -m raid1 /dev/sdg /dev/sdh /dev/sdi > Btrfs v3.17 > See http://btrfs.wiki.kernel.org for more information. > > Turning ON incompat feature 'extref': increased hardlink limit per file to > 65536 > adding device /dev/sdh id 2 > adding device /dev/sdi id 3 > fs created label (null) on /dev/sdg > nodesize 16384 leafsize 16384 sectorsize 4096 size 1.36TiB > > 36# mount /dev/sdg /mnt/test/ > > 37# btrfs fi df /mnt/test/ > Data, RAID1: total=1.00GiB, used=512.00KiB > Data, single: total=8.00MiB, used=0.00B > System, RAID1: total=8.00MiB, used=16.00KiB > System, single: total=4.00MiB, used=0.00B > Metadata, RAID1: total=1.00GiB, used=112.00KiB > Metadata, single: total=8.00MiB, used=0.00B > GlobalReserve, single: total=16.00MiB, used=0.00B > > 38# df -h /mnt/test/ > Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf > /dev/sdg 699G 17M 466G 1% /mnt/test > > ### > > This leaves me with just 466 GB of free disc space. > Something is wrong. Either what I am doing is wrong or the web page is wrong. > > Matthias > > > Am 16.04.2016 um 10:20 schrieb Luis Felipe Tabera Alonso: >> On sábado, 16 de abril de 2016 9:00:00 (CEST) Matthias Bodenbinder wrote: >>> Hello, >>> >>> I have 3 hard drive with 750 GB, 500 GB and 250 GB. I want to use btrfs as >>> filesystem. This will be my first test installation of btrfs. >>> >>> My target is to get redundancy as well as a 750 GB data capacity. So I was >>> thinking to create a raid0 with the 500 and 250 GB drive. This would result >>> in a raid0 with 750 GB capacity. I want to add this raid0 as a mirror in a >>> raid1 with the other 750 GB drive. >>> >>> But how do I do that? >>> >>> Thanks >>> Matthias >> >> Disclaimer: I have necer made anything further than a btrfs raid1 with two >> equally sized devices. >> >> >> If you create a raid1 with the three devices you will get 750GB with >> redundancy. Current Btrfs raid1 means "data and metadata is copied twice in >> different devices". And btrfs is smart enough to not copy the data in the >> two >> smaller disks. I am not sure if this web page is accurate http:// >> carfax.org.uk/btrfs-usage/ but you can take a look. >> >> You can also create a single virtual device from the 250 and 500 devices >> using >> mdadm or lvm and then create a btrfs raid1 out of the 750GB device and the >> virtual device. >> >> With the "pure" btrfs setup, if you lose a single device you will be able to >> mount the device as "degraded". >> >> With the mixed setting, you can lose a single device and read the data. >> Moreover, you can lose the two small devices and still be able to mount the >> volume. >> >> luis >> >> >> > > >
Re: btrfs: mixing raid0 and raid1 - How?
Hello Luis, I followed that link which confirms that a btrfs raid1 out of these three devices should give 750 GB of data capacity. But his is not what I get. This is what I have: Disk /dev/sdg: 698,7 GiB, 750156374016 bytes, 1465149168 sectors Disk /dev/sdh: 465,8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdi: 232,9 GiB, 250058268160 bytes, 488395055 sectors So it is actually not 750 GB but 700. Anyways... This is what I did: ### 35# mkfs.btrfs -f -d raid1 -m raid1 /dev/sdg /dev/sdh /dev/sdi Btrfs v3.17 See http://btrfs.wiki.kernel.org for more information. Turning ON incompat feature 'extref': increased hardlink limit per file to 65536 adding device /dev/sdh id 2 adding device /dev/sdi id 3 fs created label (null) on /dev/sdg nodesize 16384 leafsize 16384 sectorsize 4096 size 1.36TiB 36# mount /dev/sdg /mnt/test/ 37# btrfs fi df /mnt/test/ Data, RAID1: total=1.00GiB, used=512.00KiB Data, single: total=8.00MiB, used=0.00B System, RAID1: total=8.00MiB, used=16.00KiB System, single: total=4.00MiB, used=0.00B Metadata, RAID1: total=1.00GiB, used=112.00KiB Metadata, single: total=8.00MiB, used=0.00B GlobalReserve, single: total=16.00MiB, used=0.00B 38# df -h /mnt/test/ Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf /dev/sdg 699G 17M 466G 1% /mnt/test ### This leaves me with just 466 GB of free disc space. Something is wrong. Either what I am doing is wrong or the web page is wrong. Matthias Am 16.04.2016 um 10:20 schrieb Luis Felipe Tabera Alonso: > On sábado, 16 de abril de 2016 9:00:00 (CEST) Matthias Bodenbinder wrote: >> Hello, >> >> I have 3 hard drive with 750 GB, 500 GB and 250 GB. I want to use btrfs as >> filesystem. This will be my first test installation of btrfs. >> >> My target is to get redundancy as well as a 750 GB data capacity. So I was >> thinking to create a raid0 with the 500 and 250 GB drive. This would result >> in a raid0 with 750 GB capacity. I want to add this raid0 as a mirror in a >> raid1 with the other 750 GB drive. >> >> But how do I do that? >> >> Thanks >> Matthias > > Disclaimer: I have necer made anything further than a btrfs raid1 with two > equally sized devices. > > > If you create a raid1 with the three devices you will get 750GB with > redundancy. Current Btrfs raid1 means "data and metadata is copied twice in > different devices". And btrfs is smart enough to not copy the data in the two > smaller disks. I am not sure if this web page is accurate http:// > carfax.org.uk/btrfs-usage/ but you can take a look. > > You can also create a single virtual device from the 250 and 500 devices > using > mdadm or lvm and then create a btrfs raid1 out of the 750GB device and the > virtual device. > > With the "pure" btrfs setup, if you lose a single device you will be able to > mount the device as "degraded". > > With the mixed setting, you can lose a single device and read the data. > Moreover, you can lose the two small devices and still be able to mount the > volume. > > luis > > >
btrfs: mixing raid0 and raid1 - How?
Hello, I have 3 hard drive with 750 GB, 500 GB and 250 GB. I want to use btrfs as filesystem. This will be my first test installation of btrfs. My target is to get redundancy as well as a 750 GB data capacity. So I was thinking to create a raid0 with the 500 and 250 GB drive. This would result in a raid0 with 750 GB capacity. I want to add this raid0 as a mirror in a raid1 with the other 750 GB drive. But how do I do that? Thanks Matthias
Re: apt-get error messages
Am 06.12.2015 um 22:47 schrieb Klaus Jantzen: > On 12/05/2015 08:56 PM, Myscelus wrote: >> On 12/05/2015 08:55 PM, Klaus Jantzen wrote: >>> Hi, >>> >>> due to a typing error - I wanted to say 'dpkg --add-architecture i386' >>> but wrote 'i368' - >>> I get the following error messages when running apt-get update: >>> >>> >>> ... >>> >>> W: Failed to fetch >>> http://download.virtualbox.org/virtualbox/debian/dists/vivid/Release >>> Unable to find expected entry 'contrib/binary-i368/Packages' in Release >>> file (Wrong sources.list entry or malformed file) >>> >>> W: Failed to fetch >>> http://ftp-stud.hs-esslingen.de/debian/dists/wheezy-updates/Release >>> Unable to find expected entry 'main/binary-i368/Packages' in Release >>> file (Wrong sources.list entry or malformed file) >>> >>> W: Failed to fetch >>> http://security.debian.org/dists/wheezy/updates/Release Unable to find >>> expected entry 'main/binary-i368/Packages' in Release file (Wrong >>> sources.list entry or malformed file) >>> >>> ... >>> >>> >>> Where is the information for these erroneous requests stored? >>> How can I remove it? >> >> dpkg --remove-architecture i368 >> >> > > That seems to have done something. > At least the messages shown above disappeared when I said > > dpkg --remove-architecture i368 > apt-get update > > But I cannot add the correct architecture: > > dpkg --add-architecture i386 > apt-get update > dpkg --print-architecture > > just shows me 'amd64'. > 'apt-get update' seems to have found some i386 packages > but the second architecture is not printed out. > > That output is correct. "dpkg --print-architecture" shows the default architecture for which packages are installed. Try dpkg --print-foreign-architectures That should output "i386" Matthias
Re: Upgrade Jessie to kernel 4.2
Am 06.12.2015 um 15:55 schrieb David Parfitt: > (Setup info at end) > I am considering upgrading the kernel my stable install to kernel > version 4.2 from jessie-backports. The main purpose of this is to see > whether it helps with the problem I have been having with sound. > > *My question is* : how much / what do I risk breaking in doing this? I would say you are not risking anything. As long as you do not deinstall your current kernel. You can always switch back to your old kernel during boot. And if you are not satisfied with the 4.2 kernel you can simply deinstall it. Matthias
weird BIOS / USB Problem with Technotrend S2-4600
Hi, I have a strange problem with my PC booting while my newly aqcuired Technotrend S2-4600 DVB-S2 USB box is connected. When I start for the first time (cold boot with the usb box), everything is fine. firmware is installed and I can watch TV with vdr and xine or vlc. No issue. But as soon as I power off and on again the issue occurs. The next time when I power on, the PC does ot boot. It does not even get to the boot loader. Not even the BIos messages are displayed, not even the first initial beep is played. The screen is just black. But when I unplug the Technotrend box the beep sounds immediately and the boot process starts. Attaching the box immediately again during boot works fine and I can watch TV. Why is that? I can not find any BIOS setting that could help. Motherboard is a Asus P8H67-V; Bios version 3707. What is going wrong here? Any idea? Matthias
pinning issue or what?
Hi, I wanted to have cinnamon 2.8 on debian testing. So I played around with the lmde2 repos (betsy) in testing and managed to install cinnamon 2.8. In the course of this activity I had to donwgrade a handful of packages. It is working now. All is fine, except When I do "apt-get dist-upgrade" it wants to remove cinnamon: 35# d-u Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: cinnamon cinnamon-screensaver gir1.2-webkit2-3.0 The following NEW packages will be installed: libgtop2-7 The following packages have been kept back: libjavascriptcoregtk-3.0-0 libwebkitgtk-3.0-0 The following packages will be upgraded: gir1.2-javascriptcoregtk-3.0 gir1.2-webkit-3.0 libmarco-private0 libnemo-extension1 marco marco-common 6 upgraded, 1 newly installed, 3 to remove and 2 not upgraded. Need to get 287 kB/1241 kB of archives. After this operation, 1207 kB disk space will be freed. Do you want to continue? [Y/n] ^C Why is that? The policy says: 36# apt-cache policy cinnamon cinnamon: Installed: 2.8.4+betsy Candidate: 2.8.4+betsy Version table: *** 2.8.4+betsy 0 900 http://packages.linuxmint.com/ betsy/main amd64 Packages 100 /var/lib/dpkg/status 2.6.13-1 0 500 http://ftp.de.debian.org/debian/ testing/main amd64 Packages 100 http://ftp.de.debian.org/debian/ unstable/main amd64 Packages 2.2.16-5 0 500 http://ftp.de.debian.org/debian/ stable/main amd64 Packages >From that point of view it should keep cinnamon. Here are my pinning values: 37# cat 99_debian Package: * Pin: release a=stable,l=debian Pin-Priority: 500 Package: * Pin: release o=Debian,l=Debian-Security Pin-Priority: 500 Package: * Pin: release a=testing,l=debian Pin-Priority: 500 Package: * Pin: release a=unstable,l=debian Pin-Priority: 100 Package: * Pin: release a=experimental Pin-Priority: 100,l=debian rakete - root - /etc/apt/preferences.d 38# cat 98_mint Package: * Pin: origin packages.linuxmint.com Pin-Priority: 900 Package: * Pin: origin www.deb-multimedia.org Pin-Priority: 500 --- Any idea? Thanks Matthias
Re: Where is digikam?
Am 09.11.2015 um 18:42 schrieb Francesco Ariis: > On Mon, Nov 09, 2015 at 06:38:11PM +0100, Matthias Bodenbinder wrote: >> Hi, >> >> I see digikam in unstable for a very long time now. But it is not coming >> to testing. Why is that? Wasnt the push to testing supposed to be an >> automatic process? Or does digikam in unstable still have critical bugs? >> What is the reason for the delay? >> >> Matthias >> > > Hey Matthias, > from [1] leading to (`Check why`) [2], apparently depends on stuff > which is not into testing yet. > > [1] https://packages.qa.debian.org/d/digikam.html > [2] https://release.debian.org/migration/testing.pl?package=digikam > > Many thanks. This is helpful ... but confusing either. The page https://release.debian.org/migration/testing.pl?package=digikam says: * digikam is waiting for opencv * opencv has the same version in unstable and testing (2.4.9.1+dfsg-1.2) but a few lines done it says: * digikam depends on libopencv-core2.4 which is not available in testing This sounds contradictory to me. Matthias
Where is digikam?
Hi, I see digikam in unstable for a very long time now. But it is not coming to testing. Why is that? Wasnt the push to testing supposed to be an automatic process? Or does digikam in unstable still have critical bugs? What is the reason for the delay? Matthias
Either KLauncher is not running anymore, or it failed to start the application.
Hi, I am running a debian 8 stable system and have some trouble with KDE or KLauncher. Every once in a while, directly after loging into KDE I can not launch a program, e.g. iceweasel. The system seems to hang, not reacting to mouse clicks. After waiting for a minute or so an error message pops up that says: "Error launching /usr/share/applications/iceweasel.desktop. Either KLauncher is not running anymore, or it failed to start the application. After this message, KDE works fine. It is just this first minute after login which causes the issue. And it only happens may be 1 in 10 times. I have no clue what is going on and how to debug this thing. Any ideas what is going on here? Matthias
Re: Temporarily hold a package............
Am 09.05.2015 um 05:20 schrieb Charlie: > > From my keyboard: > > I have been looking through the man pages for: apt-get, apt-get upgrade, > but I'm certain I don't understand how I might hold a package for a > while? > > Anyone who can and is inclined to help, might assist me for the whole > testing cycle in this case with their advice. > > I get this when I attempt an upgrade of stretch: > > Retrieving bug reports... > > Done Parsing Found/Fixed information... > > Done serious bugs of openssl (1.0.1k-3 → 1.0.2a-1) > b1 - #770605 - openssl: Removes symbol without SONAME bump > > Merged with: 768476 768522 769023 770278 771169 771993 781094 781929 > > Summary: > openssl(1 bug) > > Are you sure you want to install/upgrade the above packages? > [Y/n/?/...] n > ** > ** Exiting with an error in order to stop the installation. ** > ** : Hi Charlie, you could either pin a package in /etc/apt/preferences.d/ Package: hello Pin: release n=lenny Pin-Priority: 995 .. see http://blog.opperschaap.net/2009/12/12/using-the-preferences-file-on-debian-and-debian-based-distributions/ or hold a package sudo apt-mark hold package_name .. see http://askubuntu.com/questions/18654/how-to-prevent-updating-of-a-specific-package Matthias -- 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/mikbv1$rc$1...@ger.gmane.org
Re: issue with systemd-udev-settle
Am 01.05.2015 um 08:36 schrieb Michael Biebl: It's a workaround. So it might still be worth a bug report against the linux kernel. I did that: Bug#783934: Acknowledgement (linux-image-3.16.0-4-amd64: systemd-udev-settle waiting 50 s during boot for snd-usb-audio) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783934 Matthias -- 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/mhvsu2$7oi$1...@ger.gmane.org
Re: System wide proxy in Debian Jessie
Am 01.05.2015 um 08:49 schrieb Avinash Sonawane: Which is the standard/recommended way to set system wide proxy in Debian instead of editing utility specific rc files (wgetrc, apt.conf etc)? I am aware of /etc/environment, setting http_proxy environ variable and then export it, editing bashrc. What you need is a "transparent proxy". This is setup in the background with iptables and squid. It will ensure that all IP traffic is routed through the proxy. Regardless of invidual app settings or environment variables. I had this running a few years ago and it worked perfectly. But I can not recall the detailed setup anymore. Just google "transparent proxy" and you will find your way. e.g. http://www.tldp.org/HOWTO/TransparentProxy-5.html http://www.tldp.org/HOWTO/TransparentProxy-6.html Matthias -- 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/mhvted$i3h$1...@ger.gmane.org
Re: issue with systemd-udev-settle
Am 01.05.2015 um 00:00 schrieb Michael Biebl: You could try blacklisting "snd-usb-audio" via $ echo "blacklist snd-usb-audio" > /etc/modprobe.d/no-usb-audio.conf Maybe that helps (you might need to rebuild your initramfs as well) This did the trick. The sound is disabled, the boot is fast and the usb hub in the keyboard is still working. Perfect!. Thank you all so much for your support. Matthias -- 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/mhv1r0$afe$1...@ger.gmane.org
Re: issue with systemd-udev-settle
Am 30.04.2015 um 16:57 schrieb Matthias Bodenbinder: > Am 30.04.2015 um 15:09 schrieb Michael Biebl: >> As you can see above, systemd-udevd timeouts processing the events from >> that device and is eventually killed. The internal timeout for udev is >> 90s. If you add the the remaining time to boot the system, that would >> explain the 2min boot times. >> >> This looks like either buggy hardware or a bug in the kernel. >> >> Can you try with a different keyboard and mouse directly attached to >> your computer, not via a hub? > > Yes, that is it. > > It is the keyboard! I tried a different one and the computer boots fast. > > The keyboard is not new. I had it running on the same computer for several > years. All with debian wheezy. No problems. Why is that now? I doubt that > this is a hw issue although I have never tested the sound module in that > keyboard. > > What can I do about it? I like this keyboard. I do not want to replace it. > Can I deactivate probing for usb sound? > > Matthias I tested the keyboard on a different PC with a current debian testing instalation and the issue is more or less the same. Except for the waiting time. On the debian testing machine I have to wait less than 50% of the time than on the other PC. Strange? Is that CPU performance dependent or was the timing changed between Jessie and debian testing? Anyways, I would like to deactivate the sound device in that keyboard so that udev is not waiting anymore. But how? Matthias -- 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/mhtolt$m4o$1...@ger.gmane.org
Re: issue with systemd-udev-settle
Am 30.04.2015 um 15:09 schrieb Michael Biebl: As you can see above, systemd-udevd timeouts processing the events from that device and is eventually killed. The internal timeout for udev is 90s. If you add the the remaining time to boot the system, that would explain the 2min boot times. This looks like either buggy hardware or a bug in the kernel. Can you try with a different keyboard and mouse directly attached to your computer, not via a hub? Yes, that is it. It is the keyboard! I tried a different one and the computer boots fast. The keyboard is not new. I had it running on the same computer for several years. All with debian wheezy. No problems. Why is that now? I doubt that this is a hw issue although I have never tested the sound module in that keyboard. What can I do about it? I like this keyboard. I do not want to replace it. Can I deactivate probing for usb sound? Matthias -- 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/mhtfs7$r27$1...@ger.gmane.org
Re: issue with systemd-udev-settle
Am 29.04.2015 um 19:23 schrieb Christian Seiler: Just for the purpose of debugging, could you increase RateLimitBurst to 1 or so (i.e. 10x the default value) in /etc/systemd/journald.conf and reboot? (Set it back again after you're done deubgging, else your logs might get flooded.) The 1 value did not help. I deactivated any limits: RateLimitInterval=0 RateLimitBurst=0 Here is what I found: Start of log is at Apr 30 07:27:55 Apr 30 07:27:55 xxx systemd-udevd[60]: starting version 215 # then it is working on all partitions. # sdc is an SSD # sdc2 is swap # sdb1 is lvm Apr 30 07:27:55 xxx systemd-udevd[175]: device 0x7f6bbb28f7b0 has devpath '/devices/pci:00/:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb1' Apr 30 07:27:55 xxx systemd-udevd[175]: restoring old watch on '/dev/sdb1' Apr 30 07:27:55 xxx systemd-udevd[175]: adding watch on '/dev/sdb1' Apr 30 07:27:55 xxx systemd-udevd[175]: device 0x7f6bbb28f7b0 has devpath '/devices/pci:00/:00:11.0/ata3/host2/target2:0:0/2:0:0:0/block/sdc/sdc3' Apr 30 07:27:55 xxx systemd-udevd[175]: restoring old watch on '/dev/sdc3' Apr 30 07:27:55 xxx systemd-udevd[175]: adding watch on '/dev/sdc3' # there are hundreds of udev message for the next 5 sec until 07:28:00 # then there are only a few udev messages for the next 50 sec until 07:28:50 # before hundreds of udev messages start again Apr 30 07:28:01 xxx systemd-udevd[175]: seq 1598 queued, 'add' 'input' Apr 30 07:28:01 xxx systemd-udevd[175]: seq 1599 queued, 'add' 'input' Apr 30 07:28:01 xxx systemd-udevd[175]: seq 1600 queued, 'add' 'input' Apr 30 07:28:01 xxx systemd-udevd[175]: seq 1601 queued, 'add' 'input' Apr 30 07:28:01 xxx systemd-udevd[175]: seq 1602 queued, 'add' 'input' Apr 30 07:28:04 xxx systemd-udevd[175]: validate module index Apr 30 07:28:04 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:07 xxx systemd-udevd[175]: validate module index Apr 30 07:28:07 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:10 xxx systemd-udevd[175]: validate module index Apr 30 07:28:10 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:13 xxx systemd-udevd[175]: validate module index Apr 30 07:28:13 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:16 xxx systemd-udevd[175]: validate module index Apr 30 07:28:16 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:19 xxx systemd-udevd[175]: validate module index Apr 30 07:28:19 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:19 xxx systemd-journal[170]: Forwarding to syslog missed 3809 messages. Apr 30 07:28:22 xxx systemd-udevd[175]: validate module index Apr 30 07:28:22 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:25 xxx systemd-udevd[175]: validate module index Apr 30 07:28:25 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:28 xxx systemd-udevd[175]: validate module index Apr 30 07:28:28 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:31 xxx systemd-udevd[175]: worker [196] /devices/pci:00/:00:12.2/usb1/1-4/1-4.4/1-4.4:1.0 timeout; kill it Apr 30 07:28:31 xxx systemd-udevd[175]: seq 1229 '/devices/pci:00/:00:12.2/usb1/1-4/1-4.4/1-4.4:1.0' killed Apr 30 07:28:31 xxx systemd-udevd[175]: validate module index Apr 30 07:28:31 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:34 xxx systemd-udevd[175]: validate module index Apr 30 07:28:34 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:37 xxx systemd-udevd[175]: validate module index Apr 30 07:28:37 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:40 xxx systemd-udevd[175]: validate module index Apr 30 07:28:40 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:43 xxx systemd-udevd[175]: validate module index Apr 30 07:28:43 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:46 xxx systemd-udevd[175]: validate module index Apr 30 07:28:46 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:49 xxx systemd-udevd[175]: validate module index Apr 30 07:28:49 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:49 xxx systemd-journal[170]: Forwarding to syslog missed 22 messages. Apr 30 07:28:50 xxx kernel: usbcore: registered new interface driver snd-usb-audio Apr 30 07:28:50 xxx systemd-udevd[175]: seq 1603 queued, 'add' 'sound' Apr 30 07:28:50 xxx systemd-udevd[175]: seq 1604 queued, 'add' 'sound' Apr 30 07:28:50 xxx systemd-udevd[175]: worker [196] exit Apr 30 07:28:50 xxx systemd-udevd[175]: worker [196] terminated by signal 9 (Killed) Apr 30 07:28:50 xxx systemd-udevd[175]: worker [196] cleaned up
Re: issue with systemd-udev-settle
Am 29.04.2015 um 10:32 schrieb Christian Seiler: Just use journalctl (without -b) to see all messages (they are still in RAM in the journal - as per the log you posted, journald will use up to 80 MiB [2] which is more than enough to keep all 3000 or so messages). Just look through them (there are going to be a lot of debug messages from udev) and look at the timestamps. There you'll be able to see where the delay happens - and maybe you'll have a chance of figuring out, what the problem is. If it's nothing obvious, just post the last 20 or so udev messages before the large gap in the timestamps and every udev message afterwards. If there is no gap and udev is constantly doing something, take a look at what it's actually doing. No way. Just using journalctl makes no difference: Apr 29 18:45:08 xxx systemd-journal[170]: Forwarding to syslog missed 3819 messages. Apr 29 18:45:14 xxx systemd-journal[170]: Suppressed 2818 messages from /system.slice/systemd-udevd.service And this is exactly the time period where I would expect the issue to pop up. Any other idea? Matthias -- 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/mhr2a3$vu4$1...@ger.gmane.org
Re: issue with systemd-udev-settle
Am 29.04.2015 um 15:28 schrieb Michael Biebl: Am 29.04.2015 um 10:32 schrieb Christian Seiler: Am 2015-04-29 07:15, schrieb Matthias Bodenbinder: systemd-analyze blame: 56.397s systemd-udev-settle.service Yeah, that shouldn't happen. Matthias, do you have any custom udev rules in /etc/udev/rules.d/? Is this an upgraded or freshly installed system? This is a clean install. I tried to upgrade from wheezy but could not boot afterwards. boot eror "init not found" and I was left with and initramd shell. I could not fix that so I made a clean install. /etc/udev/rules.d/ has only one file: xxx - root - /etc/udev/rules.d 17# cat 70-persistent-net.rules # This file was automatically generated by the /lib/udev/write_net_rules # program, run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single # line, and change only the value of the NAME= key. # PCI device 0x10ec:0x8168 (r8169) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:24:1d:d6:df:5f", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" Matthias -- 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/mhr1i8$f41$1...@ger.gmane.org
Re: issue with systemd-udev-settle
Hello Christian, first of all many thanks for your very detailed reply. This was excellent! I activated systemd-udev-settle again and want to debug the situtation according to your instructions (with udev.log-priority etc.). Here is the time consumption: systemd-analyze blame: ## 56.397s systemd-udev-settle.service 2.735s postfix.service 482ms NetworkManager.service 470ms lvm2-activation-early.service 456ms ModemManager.service 363ms systemd-logind.service 336ms alsa-restore.service 333ms rc-local.service 333ms speech-dispatcher.service 332ms pppd-dns.service 332ms exim4.service 330ms minidlna.service 328ms openvpn.service 326ms dovecot.service 251ms avahi-daemon.service 213ms networking.service 146ms keyboard-setup.service 136ms console-setup.service 126ms kdm.service 125ms systemd-modules-load.service 117ms systemd-fsck@dev-vol\x2dgrp1-lv_1.service 111ms systemd-fsck@dev-disk-by\x2duuid-68a8248c\x2d38fd\x2d4d5c\x2d83fa\x2da2aff3ff9ce5.service 110ms kbd.service 97ms systemd-fsck@dev-disk-by\x2duuid-22c1ca3a\x2dc781\x2d46b2\x2d98d3\x2de2a5733d68d2.service 90ms lvm2-monitor.service 84ms packagekit.service 73ms nfs-common.service 71ms saned.service 68ms rpcbind.service 58ms raid5.mount 52ms udisks2.service 44ms polkitd.service 43ms rsyslog.service 40ms systemd-user-sessions.service 38ms user@1000.service 38ms colord.service 37ms systemd-udev-trigger.service 36ms systemd-fsck@dev-disk-by\x2duuid-5085c7fb\x2d926d\x2d4f44\x2db8d0\x2d78b571f805d7.service 35ms lvm2-activation.service 28ms systemd-tmpfiles-setup-dev.service 26ms systemd-update-utmp.service 26ms systemd-journal-flush.service 25ms rtkit-daemon.service 24ms upower.service 22ms lvm2-pvscan@8:17.service 22ms media-data.mount 16ms media-data2.mount 15ms systemd-remount-fs.service 15ms dev-mqueue.mount 14ms sys-kernel-debug.mount 13ms systemd-setup-dgram-qlen.service 13ms dev-hugepages.mount 12ms systemd-tmpfiles-setup.service 11ms systemd-random-seed.service 8ms kmod-static-nodes.service 8ms sys-fs-fuse-connections.mount 8ms var-tmp.mount 8ms systemd-update-utmp-runlevel.service 8ms systemd-sysctl.service 7ms dev-disk-by\x2duuid-13030826\x2d8987\x2d46c9\x2dbc1f\x2d8a9e9a4549c9.swap 7ms tmp.mount 6ms home.mount 5ms systemd-udevd.service 1ms udev-finish.service But I am not really happy with the log since I find the following statement when doing a journalctl -b: start of log Apr 29 06:51:55 xxx systemd-journal[164]: Runtime journal is using 8.0M (max allowed 79.2M, trying to leave 118.8M free of 784.2M available → current limit 79.2M). Apr 29 06:52:19 xxx systemd-journal[164]: Forwarding to syslog missed 3819 messages. Apr 29 06:52:25 xxx systemd-journal[164]: Suppressed 2818 messages from /system.slice/systemd-udevd.service Looks like I am missing plenty of udev log messages during the critical phase of the boot process. Any idea what to do about it? Thanks for your help. Matthias -- 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/554068f4.8090...@bodenbinder.de
Re: no ntp installed
Am 28.04.2015 um 16:38 schrieb Michael Biebl: An alternative is, to use systemd-timesyncd.service, which is already shipped in the systemd package, but disabled by default. It's more lightweight then ntp and doesn't do all the fancy tricks ntp does. It also doesn't provide an NTP server. For most users timesyncd should be sufficient, so you can just run $ systemctl enable systemd-timesyncd.service $ systemctl start systemd-timesyncd.service Thank you for this hint. I will try this in favor of ntp. Lets see how that works. How can I montior this service to check if it works correctly? By the way, is there a comprehensive documentation for all the systemd services which are available. Matthias -- 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/mhppn3$r42$1...@ger.gmane.org
issue with systemd-udev-settle
Hi, I installed debian 8 on one of my PCs and got into trouble with extra long boot times of > 2 min. I found out that it due to systemd-udev-settle.service. My PC is using lvm and that somehow interferes with systemd-udev-settle.service. The web tells that systemd-udev-settle.service is needed for lvm. Nevertheless I deactivated it with systemctl mask systemd-udev-settle The PC is booting fast now and the logical volumne is mounted just fine. Q1) So what is the thing about systemd-udev-settle being needed for lvm? Do I miss something? Q2) Is there a way to set a shorter timeout value for systemd-udev-settle.service? Thanks Matthias -- 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/mhn6vs$hlm$1...@ger.gmane.org
no ntp installed
Hi, I installed debian 8 on one of my PCs and found out that no ntp or ntpdate or rdate is installed. How is debian 8 synchronizing the system time? Greetings Matthias -- 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/mhn6d8$6l6$1...@ger.gmane.org
Re: temporarily disable shutdown
Am 29.03.2015 um 17:35 schrieb Michael Biebl: > Am 29.03.2015 um 11:42 schrieb Matthias Bodenbinder: >> Am 28.03.2015 um 18:51 schrieb Michael Biebl: >>> You can run something like >>> >>> systemd-inhibit --what=shutdown --mode=block /bin/sleep 3600 >>> >>> to block shutdown for 1h. >> >> This does NOT work. I tested it with debian testing. > > Are you sure you are using systemd as PID 1? PID 1 is /sbin/init with lrwxrwxrwx 1 root root 20 Feb 13 12:22 /sbin/init -> /lib/systemd/systemd All my tests where with local root: KDE+konsole, as regular user. Either executing "poweroff" via "su -" in the konsole or clicking shutdown button in KDE. Example: In konsole #1: su - systemd-inhibit --what="idle:sleep:shutdown" --mode=block sleep 3600 In konsole #2: su - poweroff The computer is just powered off. Matthias -- 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/mfenu3$qqf$1...@ger.gmane.org
Re: temporarily disable shutdown
Am 28.03.2015 um 18:51 schrieb Michael Biebl: > You can run something like > > systemd-inhibit --what=shutdown --mode=block /bin/sleep 3600 > > to block shutdown for 1h. This does NOT work. I tested it with debian testing. It does not prevent shutdown through hte KDE GUI. And even on the commandline a "poweroff" is still successfully executed. Matthias -- 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/mf8hdu$f5f$1...@ger.gmane.org
Re: temporarily disable shutdown
Hello Michael, that is a very good suggestion. Thank you. But I also have debian stable. Do you have any idea for debain stable as well? Matthias -- 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/mf8apt$j92$1...@ger.gmane.org
temporarily disable shutdown
Hi, how can I temporarily disable shutdown or reboot? My use case is the following: I create a file /tmp/NO_SHUTDOWN. If that file exists, a shutdown or reboot should not be possible. I have molly-guard installed and a script in /etc/molly-guard/run.d/ tests the existence of that file and prevents shutdown/reboot on the commandline. But a user in KDE can still do reboot/shutdown from either KDE or even KDM. How can I prevent that with a file /tmp/NO_SHUTDOWN. Thank you for your help Matthias -- 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/mf6odd$lje$1...@ger.gmane.org
Re: shutdown icon changed
Am 18.03.2015 um 07:07 schrieb Matthias Bodenbinder: > Hi, > > I am running debian testing and kde4. The icon theme is oxygen. But the > shutdown icon which is shown in the taskbar and in the menu is the shutdown > icon from the high-contrast theme. Basically this is black-and-white instead > of the red shutdowen icon from the oxygen theme. I opened the systemsettings > and switch back and forth through the different icon themes. All icons are > changed according to my selection except for the shutdown icon. It always > stays the same. > > What is happening here? > > Thanks > Matthias > > I found the root cause: KDE is taking the icons from /usr/share/icons/hicolor/ regardless which theme is actually being used. I neeed to rename the corresponding icons to get it working again: cd /usr/share/icons/hicolor/ find . | grep weg ./scalable/apps/system-shutdown.svg.weg ./48x48/apps/system-reboot.png.weg ./48x48/apps/system-log-out.png.weg ./48x48/apps/system-hibernate.png.weg ./48x48/apps/system-shutdown.png.weg ./48x48/apps/system-suspend.png.weg Those icons got installed by xfce4-session from debian experimental. From my pijnt of view this is a bug in KDE. It should stick to the icons from the selected theme and not go into hicolor. Matthias -- 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/megi78$hh4$1...@ger.gmane.org
Re: shutdown icon changed
Am 18.03.2015 um 07:07 schrieb Matthias Bodenbinder: > Hi, > > I am running debian testing and kde4. The icon theme is oxygen. But the > shutdown icon which is shown in the taskbar and in the menu is the shutdown > icon from the high-contrast theme. Basically this is black-and-white instead > of the red shutdowen icon from the oxygen theme. I opened the systemsettings > and switch back and forth through the different icon themes. All icons are > changed according to my selection except for the shutdown icon. It always > stays the same. > > What is happening here? > > Thanks > Matthias > > Actually, it is 3 icons that always stay the same: shutdown, logoff and restart. Matthias -- 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/meb5ok$pgp$1...@ger.gmane.org
shutdown icon changed
Hi, I am running debian testing and kde4. The icon theme is oxygen. But the shutdown icon which is shown in the taskbar and in the menu is the shutdown icon from the high-contrast theme. Basically this is black-and-white instead of the red shutdowen icon from the oxygen theme. I opened the systemsettings and switch back and forth through the different icon themes. All icons are changed according to my selection except for the shutdown icon. It always stays the same. What is happening here? Thanks Matthias -- 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/meb4nm$e2o$1...@ger.gmane.org
icedove+iceowl+junk +"This message contains an invitation to an event"
Hi, since a few days I am getting the following message when applying the junk filter to my inbox: "This message contains an invitation to an event" I can not do anything about it and it does not tell me which message it means. Any idea how to solve that? 7# dpkg -l | egrep "icedove|iceowl" ii calendar-exchange-provider 3.2.0~beta47-1 all MS Exchange support for iceowl-extension ii calendar-google-provider31.2.0-1 all Google Calendar support for lightning- and iceowl-extension ii icedove 31.2.0-1 amd64mail/news client with RSS and integrated spam filter support ii icedove-l10n-de 1:31.0-1 all German language package for Icedove ii iceowl-extension31.2.0-1 amd64Calendar Extension for Thunderbird/Icedove Greetings Matthias -- 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/m53puo$k0o$1...@ger.gmane.org
Re: iceweasel and dolphin
Scott, you made my day! Your email helped me to solve the issue. Thanks a lot. dolphin was set as my default file browser: 2# xdg-mime query default inode/directory dolphin.desktop I followed your next advice to disable nautilus in /usr/share/dbus-1/services mv org.freedesktop.FileManager1.service org.freedesktop.FileManager1.service.bak After doing that iceweasel used nemo ;-) But not dolphin. Therefore I edited /usr/share/applications/defaults.list. It listed a whole bunch of apps in inode/directory incl. nemo I removed them all except for inode/directory=kde4-dolphin.desktop And that was it! iceweasel now uses dolphin to open folders. Thanks a lot Matthias PS As soon as I enable "org.freedesktop.FileManager1.service" again, iceweasel switches back to nautilus. Looks like this is leading the mime type assignments. I would prefer default.list to lead that. Is that just an iceweasel/firefox thing or intentional for the whole system? Am 25.11.2014 um 09:28 schrieb Scott Ferguson: > On 25/11/14 17:17, Matthias Bodenbinder wrote: >> Hi, >> >> I am getting crazy with iceweasel not opening dolphin for "containing >> folders". > > Hi, I run Debian Wheezy, with some backports, Iceweasel 33.1, KDE4[*1] > and *no* GNOME on this workstation. > > [*1] kdebase-bin 4:4.8.4-2 (heavily customised KDE installation) > > > To see the current file browser system association (as your usual user):- > xdg-mime query default inode/directory > > *1.* to make dolphin the default file browser (as your usual user):- > xdg-mime default dolphin.desktop inode/directory > > *** > Note: that relies on you having a "dolphin.desktop" config file - your > installation of GNOME, and my not, makes that problematic. If you have > "locate" installed *and* 'you' are a member of "mlocate" you can check > for it's existence with "mlocate":- > mlocate dolphin.desktop > /usr/share/app-install/desktop/dolphin.desktop > /usr/share/applications/kde4/dolphin.desktop > > *If* you don't get those results you can create them, by downloading > them from the attachments to this email, and saving them to the correct > locations (you'll need to change the filenames I've used to indicate > their future locations, to dolphin.desktop, and mv them from where you > download them as "root"). > *** > > *2.* You 'may' need to disable Nautilus as the default file browser - in > which case (check for it's existence first with "ls"), as "root":- > mv /usr/share/dbus-1/services/org.freedesktop.FileManager1.service{,.bak} > > Note that's one line of code. > > *Further considerations for GNOME possible problems* > Please note, again, I don't have/use GNOME so I'm forced to guess and > try and cover all possibilities I can think of (no guarantee that's > actually *all* - the standard Debian promise applies - "if it breaks you > get to keep both pieces") > > *1.* Check that Nautilus isn't set in default apps:- > as the usual user:- > grep -i nautilus /usr/share/applications/defaults.list > if you get a result, as "root":- > cp cat /usr/share/applications/defaults.list{,.bak} > then edit it as "root" and remove the Nautilus line:- > nano /usr/share/applications/defaults.list > > *2.* Repeat step *1.* above with:- > ~/.local/share/applications/mimeapps.list > ~/.local/share/applications/defaults.list > > > > *Further integration of KDE4 and Iceweasel* > > *To add KDE's KPart capabilities* > As root:- > apt-get -s install kpartsplugin | less > if you're happy with what will be installed, proceed with the installation:- > apt-get install kpartsplugin > Go to System Settings on the KMenu -> Network and Connectivity -> > KPartsPlugin > Configure to suit your needs > > *To add QT-style-like ability to Iceweasel* (it's a GTK app) > As root:- > *1.* apt-get -s install gtk2-engines-oxygen | less > if you're happy with what will be installed, proceed with the installation:- > apt-get install gtk2-engines-oxygen > > *2.* apt-get -s install kde-config-gtk-style | less > if you're happy with what will be installed, proceed with the installation:- > apt-get install kde-config-gtk-style > org.freedesktop.FileManager1.service.bak > *3.* Go to System Settings on the KMenu -> Common Appearance and > Behaviour -> Gtk Configuration > Configure to suit your needs > > *4.* Install a KDE-like theme in Iceweasel (fro
iceweasel and dolphin
Hi, I am getting crazy with iceweasel not opening dolphin for "containing folders". I searched the web for hours and tried everything I found. Working with mimeTypes.rdf in personal iceweasel folder ~/.local/share/applications/mimeapps.list /etc/gnome/defaults.list (I am running KDE but have gnome installed as well) /usr/share/applications/defaults.list /usr/share/applications/mimeinfo.cache adding dolphn.desktop to indode/directory like this inode/directory=dolphin.desktop or this inode/directory=nemo.desktop;caja.desktop;nautilus.desktop;Thunar.desktop;kde4-dolphin.desktop where kde4-dolphin.desktop is the default entry in /usr/share/applications/defaults.list but it does not exist. Changing it to dolphin.desktop does not help. So how to I tell iceweasel to open "containing folders" for downloads with dolphin and not with nautilus? This drives me crazy. Matthias -- 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/m516tp$h8i$1...@ger.gmane.org
Re: exail missing plugin
I got it. exaile needs "gstreamer0.10-fluendo-mp3" Matthias -- 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/luh2o1$6r9$1...@ger.gmane.org
Re: exail missing plugin
Am 06.09.2014 um 13:48 schrieb Chris Bannister: > On Sat, Sep 06, 2014 at 12:33:37PM +0200, Matthias Bodenbinder wrote: >> Hi, >> >> I just installed exaile 3.3.2-1 for debian testing. But when I try to >> play my mp3 files it says: "no suitable plugins found". What is >> missing? > > root@tal:~# apt-cache show exail > N: Unable to locate package exail > E: No packages found > root@tal:~# > > It seems quite a lot. A lot more information for a starter. BTW, I *am* > running testing. > > > I see the error now: You should look for exaile and not exail Matthias -- 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/luf66l$o8d$3...@ger.gmane.org
Re: exail missing plugin
Am 06.09.2014 um 13:48 schrieb Chris Bannister: > On Sat, Sep 06, 2014 at 12:33:37PM +0200, Matthias Bodenbinder wrote: >> Hi, >> >> I just installed exaile 3.3.2-1 for debian testing. But when I try to >> play my mp3 files it says: "no suitable plugins found". What is >> missing? > > root@tal:~# apt-cache show exail > N: Unable to locate package exail > E: No packages found > root@tal:~# > > It seems quite a lot. A lot more information for a starter. BTW, I *am* > running testing. > Something wrong with your repos or your package list? 19# apt-cache policy exaile exaile: Installiert: 3.3.2-1 Installationskandidat: 3.3.2-1 Versionstabelle: 3.4.0.2-1 0 600 http://ftp.de.debian.org/debian/ unstable/main amd64 Packages *** 3.3.2-1 0 900 http://ftp.de.debian.org/debian/ testing/main amd64 Packages 100 /var/lib/dpkg/status 0.3.2.2-3 0 800 http://ftp.de.debian.org/debian/ wheezy/main amd64 Packages Matthias -- 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/luf659$o8d$2...@ger.gmane.org
Re: exail missing plugin
Am 06.09.2014 um 15:29 schrieb Curt: > On 2014-09-06, Matthias Bodenbinder wrote: >> Hi, >> >> I just installed exaile 3.3.2-1 for debian testing. But when I try to >> play my mp3 files it says: "no suitable plugins found". What is >> missing? >> > > Maybe 'gstreamer ffmpeg' (shot in the dark)? > > I did that. But it did not solve the problem. Interesting though that gstreamer0.10-ffmpeg is only in stable and in unstable, but not in testing. That should not be, right? 16# apt-cache policy gstreamer0.10-ffmpeg gstreamer0.10-ffmpeg: Installiert: 0.10.13-5 Installationskandidat: 0.10.13-5 Versionstabelle: *** 0.10.13-5 0 800 http://ftp.de.debian.org/debian/ wheezy/main amd64 Packages 600 http://ftp.de.debian.org/debian/ unstable/main amd64 Packages 100 /var/lib/dpkg/status Matthias -- 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/luf61e$o8d$1...@ger.gmane.org
exail missing plugin
Hi, I just installed exaile 3.3.2-1 for debian testing. But when I try to play my mp3 files it says: "no suitable plugins found". What is missing? 10# exaile INFO: Loading Exaile 3.3.2 on Python 2.7.8... INFO: Loading settings... INFO: Using de_DE UTF-8 locale INFO: Loading plugins... INFO: Loading collection... INFO: Loading devices... INFO: Loading interface... WARNING : Failed to connect to HAL, autodetection of devices will be disabled. INFO: Using GTK+ 2.24.24 INFO: Loading main window... INFO: Connecting main window events... INFO: Loading panels... INFO: Connecting panel events... INFO: Done loading main window... INFO: Playing file:///opt/music/neu/30_seconds_to_mars/a_beautiful_lie/01_attack.mp3 ERROR : ['__class__', '__cmp__', '__delattr__', '__dict__', '__doc__', '__format__', '__getattribute__', '__grefcount__', '__gstminiobject_init__', '__gtype__', '__hash__', '__init__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', 'copy', 'flags', 'parse_async_start', 'parse_buffering', 'parse_buffering_stats', 'parse_clock_lost', 'parse_clock_provide', 'parse_duration', 'parse_error', 'parse_info', 'parse_new_clock', 'parse_qos', 'parse_qos_stats', 'parse_qos_values', 'parse_request_state', 'parse_segment_done', 'parse_segment_start', 'parse_state_changed', 'parse_step_done', 'parse_step_start', 'parse_stream_status', 'parse_structure_change', 'parse _ tag', 'parse_tag_full', 'parse_warning', 'set_buffering_stats', 'set_qos_stats', 'set_qos_values', 'set_seqnum', 'src', 'structure', 'timestamp', 'type'] gstreamer is installed: ii gstreamer-tools 0.10.36-1.4amd64Tools for use with GStreamer ii gstreamer0.10-alsa:amd64 0.10.36-1.3amd64GStreamer plugin for ALSA ii gstreamer0.10-gconf:amd640.10.31-3+nmu3 amd64GStreamer plugin for getting the sink/source information from GConf ii gstreamer0.10-nice:amd64 0.1.7-1amd64ICE library (GStreamer 0.10 plugin) ii gstreamer0.10-plugins-bad:amd64 0.10.23-7.2+b2 amd64GStreamer plugins from the "bad" set ii gstreamer0.10-plugins-base:amd64 0.10.36-1.3amd64GStreamer plugins from the "base" set ii gstreamer0.10-plugins-good:amd64 0.10.31-3+nmu3 amd64GStreamer plugins from the "good" set ii gstreamer0.10-pulseaudio:amd64 0.10.31-3+nmu3 amd64GStreamer plugin for PulseAudio ii gstreamer0.10-tools 0.10.36-1.4amd64Tools for use with GStreamer ii gstreamer0.10-x:amd640.10.36-1.3amd64GStreamer plugins for X11 and Pango ii gstreamer1.0-clutter 2.0.12-1 amd64Clutter PLugin for GStreamer 1.0 ii gstreamer1.0-libav:amd64 1.4.1-1.1 amd64libav plugin for GStreamer ii gstreamer1.0-plugins-bad:amd64 1.4.1-1amd64GStreamer plugins from the "bad" set ii gstreamer1.0-plugins-base:amd64 1.4.1-1amd64GStreamer plugins from the "base" set ii gstreamer1.0-plugins-good:amd64 1.4.1-1amd64GStreamer plugins from the "good" set ii gstreamer1.0-plugins-ugly:amd64 1.4.1-1amd64GStreamer plugins from the "ugly" set ii gstreamer1.0-pulseaudio:amd641.4.1-1amd64GStreamer plugin for PulseAudio ii gstreamer1.0-x:amd64 1.4.1-1amd64GStreamer plugins for X11 and Pango Kind Regards Matthias -- 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/luenu1$qqa$1...@ger.gmane.org
apt-get update during boot
Hi, somehow my system is running an apt-get update or something similar during boot. Whenever I login after boot I can do a "apt-get dist-upgrade" directly because the package list is already up to date. If I am too fast with the "apt-get dist-upgrade" it even complains that the database is locked by another process. waiting a few more seconds solves that. And this is true regardless which desktop I use: kde, xfce or cinnamon. I could not find any hint ffpr apt in /etc/init.d or /etc/xdg/autostart. So where is that apt-get update happening? is it webmin? Greetings Matthias PS I am using debian testing -- 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/lubh85$l5u$1...@ger.gmane.org
SOLVED: CD drive not showing up anymore
Am 03.12.2013 08:59, schrieb Matthias Bodenbinder: > Hello, > > somehow my computer does not automatically pop up with a message when I enter > a CD or DVD. Not in KDE, GNOME or XFCE. There is no automatic action at all. > I can not even see any log entries when closing the CD tray with a new CD. > But it used to work in the past. This is a new issue to me. > > I am using Debian Testing. It works fine with USB sticks. And it doesnt work > on second PC either which I just installed from scratch with debian testing. > > Any idea what is broken and how to get this working again? > > Thanks > Matthias > > Hi All, the issue is solved: I needed to enable kernel polling via echo 2000 > /sys/module/block/parameters/events_dfl_poll_msecs This is a known bug (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725978) and the issue lies probably in udev. The polling is supposed to be set in /lib/udev/rules.d/60-persistent-storage.rules but somehow it does not work. Also reported here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713877 Matthias -- 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/l7te4j$n0a$1...@ger.gmane.org
Re: CD drive not showing up anymore
And what I also find strange is, that I do not see ANY log entry when I close the tray with a new CD. Not in syslog, daemon.log, messages or user.log. Can this be a dbus issue? Matthias -- 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/l7k7tl$d9p$1...@ger.gmane.org
Re: CD drive not showing up anymore
Am 03.12.2013 09:15, schrieb Ralf Mardorf: >>> I have to add that I can mount the CD manually (mount /dev/sr0 >>> /media/cdrom) without problem. >> >> What was upgraded? Take a look at /var/log/apt/history.log, synaptics >> history or what ever you are using to upgrade. > > http://askubuntu.com/questions/21657/show-apt-get-installed-packages-history-via-commandline > > Anything in ~/.xsession-errors? ~/.xsession-errors does not show anything. /var/log/apt/history.log only contains entries from today, but the problem is already a few days old. Dont know when it occured the first time because I am not handling CDs that often. Matthias -- 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/l7k4j1$98t$1...@ger.gmane.org
Re: CD drive not showing up anymore
Am 03.12.2013 08:59, schrieb Matthias Bodenbinder: > Hello, > > somehow my computer does not automatically pop up with a message when I enter > a CD or DVD. Not in KDE, GNOME or XFCE. There is no automatic action at all. > I can not even see any log entries when closing the CD tray with a new CD. > But it used to work in the past. This is a new issue to me. > > I am using Debian Testing. It works fine with USB sticks. And it doesnt work > on second PC either which I just installed from scratch with debian testing. > > Any idea what is broken and how to get this working again? > > Thanks > Matthias > > I have to add that I can mount the CD manually (mount /dev/sr0 /media/cdrom) without problem. Matthias -- 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/l7k37e$omr$1...@ger.gmane.org
CD drive not showing up anymore
Hello, somehow my computer does not automatically pop up with a message when I enter a CD or DVD. Not in KDE, GNOME or XFCE. There is no automatic action at all. I can not even see any log entries when closing the CD tray with a new CD. But it used to work in the past. This is a new issue to me. I am using Debian Testing. It works fine with USB sticks. And it doesnt work on second PC either which I just installed from scratch with debian testing. Any idea what is broken and how to get this working again? Thanks Matthias -- 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/l7k311$n6k$1...@ger.gmane.org
configure gnome help page
Hi All, I had MINT LMDE installed on my PC but moved back to Debian Testing. I did not do a clean reinstall but simply changed the repositories and the pinning. If I start the Help function now in a gnome terminal or nautilus - either via F1 or "Help" menu - the system still opens the MINT URL: http://www.linuxmint.com/documentation.php How can I change that? And what would be the correct URL in Debian Testing? Thanks in advance Matthias -- 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/l5fcj6$8vf$1...@ger.gmane.org
KDE suspend / hibernate just executes the screensaver
Hi, I have posted the same question today in german language. Sorry for that. Here it is in english. I am running Mint LMDE with incoming repos = basically debian testing. On the commandline I can suspend and hibernate the computer with pm-suspend and pm-hibernate. But when I click on the Suspend or Hibernate button in the KDE exit dialog only the screensaver gets started. What is missing? Ciao Matthias -- 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/k2p76b$87o$1...@ger.gmane.org
KDE Ruhezustand/Tiefschlaf => Bildschirmschoner
Hallo zusammen, wie kann ich in KDE (Mint LMDE incoming distro) einstellen das bei Ruhezustand/Tiefschlaf pm_suspend oder pm_hibernate aufgerufen werden? Sowohl pm_suspend als auch pm_hibernate funktionieren wenn ich sie auf der Komamndozeile aufrufe, aber wenn ich aus dem KDE Menu heraus "Verlassen" -> "Ruhezustand / Tiefschlaf" aufrufe, startet nur der Bildschirmschoner. Gruß Matthias PS Das ist mein zweiter Versuch. das erste Posting ist nicht mehr aufgetaucht. -- 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/k2p6pq$56u$1...@ger.gmane.org
Re: Install Debian on a UEFI-motherboard ?
Am 10.09.2012 20:28, schrieb Tom Rausner: > Hi Folks. > I have a tower PC with a serious motherboard problem. > It is unable to pass data from one place (say the harddisk) > to another (say a CDROM), without drowning it in errors. > I think some pathways in the motherboard is broken, so I want to > replace it. BUT most of the motherboards on the market doesn't > have an old-style BIOS, they've got the UEFI-thing. So the question > is; can I replace my motherboard with one infested with the UEFI-thing > and get a Debian install to work on it ? > No problem at all. I can recommend Asus P8H67-V. This is what I have and it works perfectly incl. on-board graphic with a core i7-2600K @ 3.4 GHz Matthias -- 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/k2nphe$ap6$1...@ger.gmane.org