To be honest, I haven't found stopping or restarting compton makes any difference, and starting dropbox a long time after tint2 and compton have started doesn't seem to help either.
Also tried Right-click>Quit Dropbox >> Menu>Network>Dropbox>start Dropbox to no effect, likewise restarting tint2 from the menu...
...but, some combination of restarting Dropbox and restarting tint2 does get rid of that white square!
I haven't yet done it enough times to pin it down exactly, but some repetition of the two will do it. Mysterious.
Another alternative which I haven't tried might be to install the beta dropbox 3.1.27 here: https://www.dropboxforum.com/hc/communi … ld-3-1-270
S11, with the greatest respect, it looks to me that that libc6 dependency is for a version greater than or equal to 2.7
My Wheezy comes with libc6 2.13-38+deb7u6 which I think is the default, so ffmpeg 8:1.0.10-dmo1ought to be OK, no?
Right now I'm running on a laptop with a recently installed #! Waldorf, regular debian ffmpeg installed, so in the interests of science I upgraded ffmpeg from the deb-multimedia repos to see what I got. This is what I did:
*) Open http://www.deb-multimedia.org/ and read the instructions.
*) Add this line to /etc/apt/sources.list
deb http://www.deb-multimedia.org wheezy main non-free
*) Run these commands in a terminal:
sudo apt-get update sudo apt-get install deb-multimedia-keyring sudo apt-get dist-upgrade
A lot of libraries were installed and upgraded, including ffmpeg.
*) To check the situation, run:
apt-cache policy ffmpeg ffmpeg: Installed: 8:1.0.10-dmo1 Candidate: 8:1.0.10-dmo1 Version table: *** 8:1.0.10-dmo1 0 500 http://www.deb-multimedia.org/ wheezy/main i386 Packages 100 /var/lib/dpkg/status 6:0.8.16-1 0 500 http://http.debian.net/debian/ wheezy/main i386 Packages 500 http://security.debian.org/ wheezy/updates/main i386 Packages
So we now have 8:1.0.10-dmo1. (I made no changes to pinning settings - the deb-multimedia repos have the default pinning of 500.)
I think part of the problem you've been having - which I initially overlooked - is that you have your wheezy-backports pinned at the same level as the multimedia repo.
I think this might have been it. Usually multimedia get the default pinning - higher than backports - so dist-upgrade pulls in a load of newer libraries which the new ffmpeg needs.
What I seem to remember reading about the ffmpeg vs av-tools thing is that for a while ffmpeg looked as if it wasn't getting much work, so Debian regarded it as obsolete and shifted focus to av-tools. According to the deb-multimedia site, ffmpeg is moving again now.
@flaneur I was just about to post about that very thing. I tried replacing those icons with ones from Faenza-Dark-Crunchbang, and yes I got back my nice grey icon... but, with a square white background! The icons themselves are transparent, but that white background is coming in from somewhere else I guess.
I might also mention that the popup menu no longer follows the gtk theme like all the other systray apps. I suppose this is all connected with the switch to Qt.
A #!/Xfce hybrid installer that does that: http://crunchbang.org/forums/viewtopic.php?id=30132
I've just installed #! on a laptop, and running the install-dropbox script got the new version 3.0.3.
There are many improvements apparently, but the icon I got in tint2's system tray looks ugly.
In 2.10.52 it pulls in the gtk theme "Faenza Crunchbang Dark" for me, and blends in nicely with the rest of the tray:
But 3.0.3 has a non-transparent white background:
I'm guessing that the new dropbox is enforcing its own hard-coded icons from somewhere...
Does anyone have any suggenstions to fix this?
Just did a search on 'mount hfsplus permissions' and the first result was this: http://askubuntu.com/questions/100167/h … ermissions
Didn't read it too carefully though.
Absolute right/wrong vs relative...
Clearly torturing a child is wrong. I don't think anybody would disagree with that.
Abusing power to exploit others is also wrong in my book.
After that, there are areas where different cultures have different ideas. Now, I don't buy into that "Asian values" argument used by those in power in China and Singapore to deny their people freedom of speech or fair access to the rule of law, for example, but there are many other areas where there is room to disagree. Sex, property, the rights of the individual vs the rights of the group...
A mature community ought to be able to discuss differences of point of view without insulting each other.
There was no entry for hfsplus, but:
Mount options for hfs
Set the creator/type values as shown by the MacOS finder used
for creating new files. Default values: '????'.
Set the owner and group of all files. (Default: the uid and gid
of the current process.)
dir_umask=n, file_umask=n, umask=n
Set the umask used for all directories, all regular files, or
all files and directories. Defaults to the umask of the current
Would the uid option do it for you? Or set umask to 000?
Maybe it's the Waldorf GTK2 theme, which has no buttons at the ends of the scrollbar. I edited mine using pvsage's suggestion here: http://crunchbang.org/forums/viewtopic. … 92#p296992
It doesn't remove the "border" but makes it more useful perhaps?
libc6 is right at the centre of things. Many, if not most, packages depend on it, and depend on a certain version of it. The packages on Wheezy need 2.13 and those on Jessie are compiled to work with 2.19. Of course there is some backward-compatibility, but generally it is very dangerous to mess with libc6.
Try a search for 'libc6' on this forum for a start.
There are in fact ways of getting a different libc6 to be used by a certain package only but this is getting pretty advanced...
A recently installed Waldorf on a laptop with 1G of RAM booted up using about 87MB. That's before you start running any programs of course... (You'll probably need a bit more for a 64 bit system.)
On the buffer thing - if I've got this right, buffered memory is just stuff that was used in the past and the system thinks if you need it again soon it'll be quicker to get it from RAM than off the hard disk. Unlike the other memory figure it's not essential, just good to have if you've got the free memory space. The without-buffer figure is the one to watch if you're in danger of running out of RAM.
^this is true - I got thoroughly confused myself on the difference between GTK themes and window manager themes. (Was there something about lxappearance handling both in recent versions?)
Maybe the "User Interface Settings" item needs to be nearer the top of the menu, anyway, and possibly renamed?
Luc, don't want to nitpick, but:
The --update will only copy files that changed in the original location to the backup location (new files and modified files). Files that did not change will not be copied so the backup will take shorter the second time you run it.
Just for the record, it's my understanding that this is what rsync does anyway, even without that option.
My reading of man rsync is that the --update option will cause rsync to skip files at the destination that are newer than the equivalent in the source, even if the source file is different.
I have been known to be wrong on occasions though...
I use CrunchBang
[x] original source.list (with possible additions)
 with original source.list edited to use testing (with possible additions, less waldorf repos)
 with original source.list edited to use sid (with possible additions, less waldorf repos)
CrunchBang is my:
[x] only system
 primary - dual boot
 not my primary - dual boots
AH -pvsage has got it covered already, but I'll post this anyway...
Try apt-cache policy for cases like this:
~$ apt-cache policy terminator terminator: Installed: 0.93-4-bzr1026 Candidate: 0.93-4-bzr1026 Version table: 0.95-1 0 500 http://http.debian.net/debian/ wheezy/main amd64 Packages *** 0.93-4-bzr1026 0 1001 http://packages.crunchbang.org/waldorf/ waldorf/main amd64 Packages 100 /var/lib/dpkg/status
So the cause is the 1001 pinning that the #! packages get by default.
You can force the terminator version by running:
sudo apt-get install terminator=0.95-1
but before doing that you might want to check the changelog and see if 0.95-1 actually has any new features or bugfixes you need.
I don't use terminator so I upgraded to see what happened - the new terminator looks OK and seems to run without errors, except for this message:
/usr/share/terminator/terminatorlib/terminal.py:700: GtkWarning: IA__gtk_box_reorder_child: assertion `old_link != NULL' failed self.reorder_child(self.vte, 0)
which might be harmless...
Alad, thanks for that link.
The technically competent sides tend to largely fall in these two broad categories:
a) Proponents are usually part of the modern Desktop Linux bandwagon. They run contemporary mainstream distributions with the latest software, use and contribute to large desktop environment initiatives and related standards like the *kits. They’re not necessarily purely focused on the Linux desktop. They’ll often work on features ostensibly meant for enterprise server management, cloud computing, embedded systems and other needs, but the rhetoric of needing a better desktop and following the example set by Windows and OS X is largely pervasive amongst their ranks. They will decry what they perceive as “integration failures”, “fragmentation” and are generally hostile towards research projects and anything they see as “toy projects”. They are hackers, but their mindset is largely geared towards reducing interface complexity, instead of implementation complexity, and will frequently argue against the alleged pitfalls of too much configurability, while seeing computers as appliances instead of tools.
b) Opponents are a bit more varied in their backgrounds, but they typically hail from more niche distributions like Slackware, Gentoo, CRUX and others. They are largely uninterested in many of the Desktop Linux “advancements”, value configuration, minimalism and care about malleability more than user friendliness. They’re often familiar with many other Unix-like environments besides Linux, though they retain a fondness for the latter. They have their own pet projects and are likely to use, contribute to or at least follow a lot of small projects in the low-level system plumbing area. They can likely name at least a dozen alternatives to the GNU coreutils (I can name about 7, I think), generally favor traditional Unix principles and see computers as tools. These are the people more likely to be sympathetic to things like the suckless philosophy.
Ultimately, the cruel irony is that in systemd’s attempt to supposedly unify the distributions, it has created a huge rift unlike any other and is exacerbating the long-present hostilities between desktop Linux and minimalist Linux sides at rates that are absolutely atypical.
Would many CrunchBang users fall somewhere between in their affiliations? Without being on a level to contribute anything to either camp I can feel empathy with both positions. While enjoying a system that I don't have to configure in order to do every little task smoothly and efficiently, I do appreciate being able to tweak things to my taste, and not having to run a mountain of processes that I'm not actually using...