I "installed" FF52 esr this morning, in order to still be able to use java within the browser (see here).
Works fine; but FF uses an older version of Java; it tells me it is using Java 1.7.
But when I do a simply java -version command line, I am told that I have Java 1.8 there.
So how exactly do I control which Java version is "plugged in"?
This question asks how to install FF32 bit while keeping the 64 bit.
I want the much more simple thing: is there a canonical way to install firefox 52 ESR as "default" firefox in my 16.04?
I found this launchpad team ... but there are no packages; probably no wonder given the fact that the linked blog article dates back to 2012.
So, 2017, Ubuntu 16.04; how to install FF 52 ESR (as I simply need the java plugin to work for me).
( my current solution: I downloaded the TAR file from mozilla, extracted that to /opt; and then changed /usr/bin/firefox to be a link to that ESR version of firefox. works, but ugly )
Just installed the new hardware enablement stack yesterday; all fine.
Today, kernel update to 4.8.0-39-generic ... and after reboot and entering my login password ... nothing. Just my desktop; no mouse pointer; full hang; I have to press the power button to switch of the machine in the end.
Any idea anybody?
I took my old NV-GS500 Panasonic camcorder; in order to finally turn all our recordings into digital media.
So far, things worked easily:
ffmpeg -i infile -pix_fmt yuv420p -crf 23 outfile to turn that dv file into an mp4But alas, the quality of the mp4 isn't that convincing. Especially on rapid movements, lots of pixelish stuff.
Thus, I want to improve the whole thing. And as now discovered that kino is actually "dead"; I am wondering what combination of tools gives me good quality; as easily as possible.
Update: the full command for ffmpeg is already given above, here is the output I am receiving when running that:
> ffmpeg -i capture001.dv -pix_fmt yuv420p -crf 23 test.mp4
ffmpeg version 2.8.10-0ubuntu0.16.04.1 Copyright (c) 2000-2016 the FFmpeg developers
built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.4) 20160609
configuration: --prefix=/usr --extra-version=0ubuntu0.16.04.1 --build-suffix=-ffmpeg --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --cc=cc --cxx=g++ --enable-gpl --enable-shared --disable-stripping --disable-decoder=libopenjpeg --disable-decoder=libschroedinger --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-librtmp --enable-libschroedinger --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxvid --enable-libzvbi --enable-openal --enable-opengl --enable-x11grab --enable-libdc1394 --enable-libiec61883 --enable-libzmq --enable-frei0r --enable-libx264 --enable-libopencv
WARNING: library configuration mismatch
avcodec configuration: --prefix=/usr --extra-version=0ubuntu0.16.04.1 --build-suffix=-ffmpeg --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --cc=cc --cxx=g++ --enable-gpl --enable-shared --disable-stripping --disable-decoder=libopenjpeg --disable-decoder=libschroedinger --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-librtmp --enable-libschroedinger --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxvid --enable-libzvbi --enable-openal --enable-opengl --enable-x11grab --enable-libdc1394 --enable-libiec61883 --enable-libzmq --enable-frei0r --enable-libx264 --enable-libopencv --enable-version3 --disable-doc --disable-programs --disable-avdevice --disable-avfilter --disable-avformat --disable-avresample --disable-postproc --disable-swscale --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libvo_aacenc --enable-libvo_amrwbenc
libavutil 54. 31.100 / 54. 31.100
libavcodec 56. 60.100 / 56. 60.100
libavformat 56. 40.101 / 56. 40.101
libavdevice 56. 4.100 / 56. 4.100
libavfilter 5. 40.101 / 5. 40.101
libavresample 2. 1. 0 / 2. 1. 0
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 2.101 / 1. 2.101
libpostproc 53. 3.100 / 53. 3.100
[dv @ 0x2566420] Detected timecode is invalid
[dv @ 0x2566420] Estimating duration from bitrate, this may be inaccurate
Input #0, dv, from 'capture001.dv':
Duration: 00:39:45.36, start: 0.000000, bitrate: 28800 kb/s
Stream #0:0: Video: dvvideo, yuv420p, 720x576 [SAR 64:45 DAR 16:9], 28800 kb/s, 25 fps, 25 tbr, 25 tbn, 25 tbc
Stream #0:1: Audio: pcm_s16le, 32000 Hz, stereo, s16, 1024 kb/s
Stream #0:2: Audio: pcm_s16le, 32000 Hz, stereo, s16, 1024 kb/s
[libx264 @ 0x256dea0] using SAR=64/45
[libx264 @ 0x256dea0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
[libx264 @ 0x256dea0] profile High, level 3.0
[libx264 @ 0x256dea0] 264 - core 148 r2643 5c65704 - H.264/MPEG-4 AVC codec - Copyleft 2003-2015 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
Output #0, mp4, to 'test.mp4':
Metadata:
encoder : Lavf56.40.101
Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv420p, 720x576 [SAR 64:45 DAR 16:9], q=-1--1, 25 fps, 12800 tbn, 25 tbc
Metadata:
encoder : Lavc56.60.100 libx264
Stream #0:1: Audio: aac (libvo_aacenc) ([64][0][0][0] / 0x0040), 32000 Hz, stereo, s16, 128 kb/s
Metadata:
encoder : Lavc56.60.100 libvo_aacenc
Stream mapping:
Stream #0:0 -> #0:0 (dvvideo (native) -> h264 (libx264))
Stream #0:1 -> #0:1 (pcm_s16le (native) -> aac (libvo_aacenc))
Press [q] to stop, [?] for help
frame= 1449 fps=112 q=-1.0 Lsize= 10373kB time=00:00:57.93 bitrate=1466.7kbits/s
video:9424kB audio:906kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.411332%
[libx264 @ 0x256dea0] frame I:29 Avg QP:22.01 size: 23022
[libx264 @ 0x256dea0] frame P:826 Avg QP:24.37 size: 8655
[libx264 @ 0x256dea0] frame B:594 Avg QP:25.43 size: 3086
[libx264 @ 0x256dea0] consecutive B-frames: 29.4% 42.9% 14.7% 13.0%
[libx264 @ 0x256dea0] mb I I16..4: 21.0% 76.6% 2.3%
[libx264 @ 0x256dea0] mb P I16..4: 1.7% 5.9% 0.5% P16..4: 46.9% 9.4% 6.7% 0.0% 0.0% skip:28.9%
[libx264 @ 0x256dea0] mb B I16..4: 0.0% 0.1% 0.0% B16..8: 48.5% 2.5% 0.6% direct: 3.3% skip:44.8% L0:46.0% L1:50.8% BI: 3.2%
[libx264 @ 0x256dea0] 8x8 transform intra:73.6% inter:82.2%
[libx264 @ 0x256dea0] coded y,uvDC,uvAC intra: 66.2% 56.2% 6.0% inter: 19.5% 23.4% 0.1%
[libx264 @ 0x256dea0] i16 v,h,dc,p: 14% 39% 12% 35%
[libx264 @ 0x256dea0] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 18% 16% 33% 5% 5% 6% 6% 5% 7%
[libx264 @ 0x256dea0] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 9% 60% 14% 3% 3% 3% 3% 2% 2%
[libx264 @ 0x256dea0] i8c dc,h,v,p: 56% 20% 21% 3%
[libx264 @ 0x256dea0] Weighted P-Frames: Y:14.9% UV:1.5%
[libx264 @ 0x256dea0] ref P L0: 62.5% 14.1% 15.9% 6.8% 0.7%
[libx264 @ 0x256dea0] ref B L0: 81.5% 17.0% 1.5%
[libx264 @ 0x256dea0] ref B L1: 94.9% 5.1%
[libx264 @ 0x256dea0] kb/s:1331.94
Exiting normally, received signal 2.
(interrupted after a few seconds with ctrl-c)
I am using the indicator-systemtray-unity for quite some time; and initially, it worked really good for me: I clicked the indicator, and it would display a little array below the indicator; containing all the systemtray icons.
At some point, something strange happened ... I don't know what caused it, but now the system try icons were always showing up. In the middle of the Unity "top bar" there was now a section that constantly showed the icons. I have found no way to disable that, but I didn't see that as a big problem (actually: it was quite nice: the icons were always visible).
But: I am using a laptop. When the laptop is the in the docking station, I am only using two external monitors; I normally keep the lid of my laptop closed.
Now my problem: since lately ... the system tray icons are no longer shown on my external monitors. When I open up the lid of my laptop, the icons are still there, in the middle of the "top bar"; but they don't show up on my external monitors.
In order to fix this problem: a) I ran sudo apt-get --purge remove indicator-systemtray-unity ... and re-installed b) I tried clicking on the little button, but no matter what; any left/right click just pops up a "Settings" dropdown, which pops up another dropdown ("Backgrounds"); and making changes there doesn't seem to have any effect.
So, long story short, is there a way to reliable "reset" the indicator, so that it only shows the icons when I click the indicator?
Btw, I am running 16.04; but I encountered similar issues before, when running the indicator on 14.04.
running 14.04.3 with unity. Since some days, occasionally my screen will not blank and lock; although "brightness and lock" is configured to exactly do that after 3 minutes.
I checked for answers here, but couldn't find anything helpful. And no, I really like the blank unity stuff; so I don't want to install x screensaver (and I never had x screensaver installed on this system).
it sounds like a stupid question, but I hope it isnt.
I want to create a simple xterm with a fixed title. I tried:
xterm -title whatever (that is what xterm --help suggests)
xterm -T whatever (according to man pages, this is the same as --title)
but well, my xterm always comes up showing username@hostname:~ in the title. I guess that this title comes from some environment variable; but I would prefer if I do not have to make a permanent change to my .bashrc or .profile just to be able to create one xterm with a fixed title?!
This is xubuntu 14.04
our generous management considers handing out SSDs to replace the HDDs in our laptops.
I am told that SSDs will have the same size as the HDDs; so I am now wondering: should I simply use "dd" to copy my existing xubuntu 14.04 installation (and maybe then, afterwards do the tunings listed for that related question)?
Or are there any major "technical" advantages in doing a "completely fresh" installation of xubuntu on that SSD?
In other words: will doing such a "full binary" copy have any negative effects regarding SSD performance, caching ... ?
EDIT no. 2: my current installation was created using the "default" ubuntu installer; meaning it uses LUKS and LVM. Providing some low level information:
sudo pvs
PV VG Fmt Attr PSize PFree
/dev/mapper/sda5_crypt xubuntu-vg lvm2 a-- 465,52g 44,00m
sudo lvs
LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
root xubuntu-vg -wi-ao--- 449,83g
swap_1 xubuntu-vg -wi-ao--- 15,64g
sudo fdisk -lu
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00079ee9
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 499711 248832 83 Linux
/dev/sda2 501758 976771071 488134657 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda5 501760 976771071 488134656 83 Linux
Disk /dev/mapper/sda5_crypt: 499.8 GB, 499847790592 bytes
255 heads, 63 sectors/track, 60769 cylinders, total 976265216 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/sda5_crypt doesn't contain a valid partition table
Disk /dev/mapper/xubuntu--vg-root: 483.0 GB, 483003465728 bytes
255 heads, 63 sectors/track, 58721 cylinders, total 943366144 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/xubuntu--vg-root doesn't contain a valid partition table
Disk /dev/mapper/xubuntu--vg-swap_1: 16.8 GB, 16793993216 bytes
255 heads, 63 sectors/track, 2041 cylinders, total 32800768 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/xubuntu--vg-swap_1 doesn't contain a valid partition table
cat /etc/fstab
...
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/mapper/xubuntu--vg-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda1 during installation
UUID=b58b2697-1bf2-4ad3-80bd-4dee61e63fe4 /boot ext2 defaults 0 2
/dev/mapper/xubuntu--vg-swap_1 none swap sw 0 0
Running xubuntu 14.04; and today I had to increase the font size for a presentation ... and when toggling back I happened to click in the wrong place; and now I am struggling how to undo that.
So, basically I have two question:
I have a framework written in python, and for testing purposes I basically want to do a subprocess (aka shell call) ... that should simply come back with a RC != 0. I tried to invoke some non-existing executable; or to run "exit 1"; but those are for some reason translated to a FileNotFoundError.
So, what else could I do to trigger a return code != 0 (in a "reliable" way; meaning the command should not suddenly return 0 at a future point in time).
I thought to "search" for a binary called exit, but well:
> /usr/bin/env exit
/usr/bin/env: exit: No such file or directory
Basically I like to have a "clean" system; so I run the ubuntu-tweak janitor from time to time to delete the old kernels. Today I did some manual checking and found the subdirectory 3.13.0-49-generic within /lib/modules, That is fine it is my current kernel on 14.04; and yes, I want all the modules in there.
But then there are two older subdirectories 3.13.0-32-generic and 3.8.0-31-generic that contain various files like modules.alias, etc; and in the 3.8 directory, some really old vbox ko files.
Also when I run dkms status I am told:
bbswitch, 0.7, 3.13.0-29-generic, x86_64: built
bbswitch, 0.7, 3.13.0-49-generic, x86_64: installed
I have two questions:
bbswitch; and how would I delete it manually?
I recently upgraded to chrome 40; and this version of chrome disallows connections to servers using sslv3. But for my internal work, I have to connect to such an internal server (the server admins know about the problem; but basically they are very busy right now; and they will not update this server for some more weeks). So I am basically broken - I can't get to that machine.
So I thought to simply fetch the chrome v39 DEBs from somewhere, install that and keep it pinned for the next weeks.
But well; I haven't found this "somewhere" yet. When I try to browse to "http://dl.google.com/linux/chrome/deb/" there is just a 404 error.
Any idea, anybody?
I am running Xubuntu 14.04 on a Lenovo W530.
The other day we received brand new Plantronics Blackwire C420 headsets.
After a short while I realized that something was strange - and I nailed it down: the headset has 4 control buttons (volume up/down, mute, "phone"). When I press any of these buttons, the "mouse click handler" dies. This means: mouse clicks ... do not cause actions any more. If I unplug the headset; or close the application that is currently using the headset (like my SUT call window) everything goes back to normal.
I did some searching, found
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/993655?comments=all
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1006156
The last link points to http://www.helplinux.ru/wiki/en:kb:ubuntu-plantronics
That page gives an instruction for 13.10 / 14.04.
So I ran
lsusb | grep -i plantronics Bus 001 Device 006: ID 047f:aa14 Plantronics, Inc.
Then I ran
sudo evtest (I selected the headset and pressed phone / volume up / volume down / mute on / mute off and got)
Event: time 1421919129.677039, type 4 (EV_MSC), code 4 (MSC_SCAN), value b0020
Event: time 1421919129.677039, type 1 (EV_KEY), code 256 (BTN_0), value 1
Event: time 1421919129.677039, -------------- SYN_REPORT ------------
Event: time 1421919132.913033, type 4 (EV_MSC), code 4 (MSC_SCAN), value ffa000b2
Event: time 1421919132.913033, type 1 (EV_KEY), code 261 (BTN_5), value 1
Event: time 1421919132.913033, type 1 (EV_KEY), code 261 (BTN_5), value 0
Event: time 1421919132.913033, type 4 (EV_MSC), code 4 (MSC_SCAN), value ffa000f8
Event: time 1421919132.913033, type 1 (EV_KEY), code 266 (?), value 0
Event: time 1421919132.913033, type 4 (EV_MSC), code 4 (MSC_SCAN), value ffa000f9
Event: time 1421919132.913033, type 1 (EV_KEY), code 267 (?), value 0
Event: time 1421919132.913033, -------------- SYN_REPORT ------------
Event: time 1421919133.959032, type 4 (EV_MSC), code 4 (MSC_SCAN), value ffa000b1
Event: time 1421919133.959032, type 1 (EV_KEY), code 260 (BTN_4), value 1
Event: time 1421919133.959032, type 1 (EV_KEY), code 260 (BTN_4), value 0
Event: time 1421919133.959032, -------------- SYN_REPORT ------------
Event: time 1421919135.896964, type 4 (EV_MSC), code 4 (MSC_SCAN), value b002f
Event: time 1421919135.896964, type 1 (EV_KEY), code 257 (BTN_1), value 1
Event: time 1421919135.896964, -------------- SYN_REPORT ------------
Event: time 1421919139.744963, type 4 (EV_MSC), code 4 (MSC_SCAN), value b002f
Event: time 1421919139.744963, type 1 (EV_KEY), code 257 (BTN_1), value 0
Event: time 1421919139.744963, -------------- SYN_REPORT ------------
Then I followed the instruction from the Russian page and created
cat /etc/udev/rules.d/49-plantronics.rules
ACTION!="add|change", GOTO="xorg_plantronics_end"
KERNEL!="event*", GOTO="xorg_plantronics_end"
SUBSYSTEMS=="usb", ENV{ID_BUS}=="", IMPORT{builtin}="usb_id"
ENV{ID_VENDOR_ID}=="047f", ENV{ID_MODEL_ID}=="aa14", ENV{ID_INPUT_KEY}="1", ENV{ID_INPUT_KEYBOARD}="1"
Plus:
cat /etc/udev/hwdb.d/50-keyboard.hwdb
keyboard:usb:v047FpAA14*
KEYBOARD_KEY_ffa000b1=volumeup
KEYBOARD_KEY_ffa000b2=volumedown
KEYBOARD_KEY_b002f=micmute
KEYBOARD_KEY_b0020=phone
Finally I ran ... sudo udevadm hwdb --update ; sudo udevadm control --reload ... and I also rebooted.
Long story short: it doesn't help. When pressing any of the buttons, the mouse click handler still goes away. Interestingly enough, coworker is running same hardware with Gnome3 ... and he doesn't have this problem ;-(
Any thoughts, ideas, suggestions are welcome (expect "use Gnome3 instead of xubuntu"). For example I am wondering if there any log files that would tell me if these udef control files have any effect, or are malformed, ...
My companies software stack for Linux includes some "security scripts" that check if the screensaver is configured according to our security policy. I am about to extend that script to handle light locker.
Step 1 will be to retrieve the current light-locker settings. So where can I find them?
I found the "unity tweak tool" the other day, and today I played around a bit ... and today I wanted to make some adaptions for the task switcher.
There is a field for windows switcher shortcuts; and I am wondering: how on earth would I disable shortcuts?
Example: it says Start switcher for all Workspaces
I can now click on "" and it then says "New shortcut" ... but well, I dont want to set a shortcut. And I could not find a way to get it to show "Disabled" like it does for other entries.
Any idea how that would work?
unfortunately, we have some intranet sites that "insecure" content; thus I really really want to start chrome with "--allow-running-insecure-content".
I "locked" chrome to the unity launcher, later on, I edited /usr/share/applications/google-chrome.desktop and added this parameter.
But when starting chrome using the unity launcher ... it doesn't start in that mode. I had a closer look and saw that the .desktop file even says "--incognito", and no, chrome does start in normal mode.
Long story short: why is the desktop file content not relevant when starting chrome using the unity launcher panel?
I have a second hard drive that I am regularly adding to my Laptop in order to store backup data there.
Earlier on, after I logged in, the drive showed up in the unity launcher, I could click it, and it became mounted as "/media/myuserid/backup".
Today, I had to give away the drive to a coworker, he used it for some installation. After I got it back, I just wiped his stuff, created a single ext4 partition, labeled it "backup", like I did when initially preparing that disk.
But now, when I click the "drive icon" in the launcher, the drive gets mounted like /media/myuserid/partition--uuid
So instead of using my label "backup", it is mounted under the UUID of the partition. Honestly, I liked the other behavior much better.
Any idea what is going on here?
I think there are similar questions around, but not exactly the same problem:
I just bought a Plantronics Voyager Legend UC. Like all "UC" models, the headset comes with a small bluetooth dongle. When plugging the dongle, it immediately pairs with the headset, all fine.
When turning to the "audio devices" a new device shows up: Plantronics BT 300. Using the PulseAudio volume control I can setup different profiles, like "analog mono output", or "analog mono duplex".
But unfortunately NO sound is reaching the headset.
Running Ubuntu 12.10 64 bit. Any idea anybody?
He there,
the release notes for kernel 3.8 do mention improved performance for ext4 using small files. That alone sounds interesting; now I am wondering: will there be a simple PPA approach at some point that allows to use 3.8 kernels on 12.10 (and/or maybe 12.04)?
In the sense of: I just add the ppa once; and then like with "normal" kernels I dont need to worry about any updates, they just come along without any further activity on my side?
Or does using upstream kernels imply that I have to fetch out myself any time a new 3.8 versions comes around the corner?
at some point in time I discovered the "window rules" plugin within the compiz config manager. One can use that to automatically show some special application on every workspace for example (so instead of each time "click window title, select 'always on visible workspace' ... you could write down a rule to do it for you).
Now; with a fresh installation of 12.10 ... there are no more "window rules" within the compiz config manager.
Anyone aware of other ways to achieve similar behavior?