Choose style:

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - christianvl

Pages: 1 ... 11 12 [13]
GNU/Linux Discussion / Re: Ravenports
« on: November 22, 2017, 03:32:38 pm »
Ravenports (and NIX) don't solve the issue snaps/flatpacks/etc. are trying to address.

They require the source code to be submitted to the repository .. something closed source devs are never going to do.
(can you see Adobe saying "sure we trust you with our closely guarded Photoshop source code, please be careful with it" ?)

They're a good solution for open source software, but not one I'm convinced is necessary .. generally if open source software is good enough it'll get packaged by the community anyway without the dev needing to supply anything more than just the source code.

snaps/flatpacks/etc. are an attempt to get the CLOSED source world interested in packaging for Linux, where they never have to release (and hence loose control over) their precious source code .. they themselves can just create a single pre-compiled package that installs in any distro.

Personally I'm not convinced by that reasoning (or the implementation), but I guess we'll see.
To install Skype, Chrome, etc., we have to add their repositories to our sources. Sorry if this is a dumb question, but is it considered safer/better than snaps?

As I understood,  with NIX or ravenports it's easier to install (and mantain?) one package that will work in many different distros, even more exotic ones, without the need to compile from source.

I always tend toward Debian or Ubuntu because I need some packages for my work that are only avaliable as DEB files and I lack the knowledge, skills and time to try to make it work with something else. Just out of curiosity, those are packages to manage digital certificates and sign documents in Brazil and to do online banking.

Thank God Peppermint is based on Ubuntu!

Enviado de meu Lenovo TB-8504F usando Tapatalk

GNU/Linux Discussion / Ravenports
« on: November 22, 2017, 07:50:12 am »
This topic was originally lost due to the forum outage (,6209.0.html).

I've decided to open it again as I find the subject very interesting.

I'd like to know the general opinion on Ravenports ( Is it a better solution than Snaps/Flatpacks and the like? More secure? Have anyone used it and could care to give an opinion? Is there something else similar?

For example, If Pepppermint OS developers would share the ICE tool to another distros, what would be the preferable way?

[EDIT] I had to edit the original post because I've accidentally clicked on save while writing.

Hardware / Re: How to disable the touchscreen
« on: November 20, 2017, 02:45:40 pm »
Yes! That did the trick! Thank you very much (again!) PCNetSpec!

Just FYI, now I have
Code: [Select]
xinput list
⎡ Virtual core pointer                    id=2 [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              id=4 [slave  pointer  (2)]
⎜   ↳ ELAN Touchscreen Pen                    id=11 [slave  pointer  (2)]
⎜   ↳ DLL0674:00 06CB:75DB Touchpad            id=13 [slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad              id=15 [slave  pointer  (2)]
⎣ Virtual core keyboard                    id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard              id=5 [slave  keyboard (3)]
    ↳ Power Button                            id=6 [slave  keyboard (3)]
    ↳ Video Bus                                id=7 [slave  keyboard (3)]
    ↳ Power Button                            id=8 [slave  keyboard (3)]
    ↳ Sleep Button                            id=9 [slave  keyboard (3)]
    ↳ Integrated_Webcam_HD                    id=10 [slave  keyboard (3)]
    ↳ Intel Virtual Button driver              id=12 [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            id=14 [slave  keyboard (3)]
    ↳ Dell WMI hotkeys                        id=16 [slave  keyboard (3)]
    ↳ DELL Wireless hotkeys                    id=17 [slave  keyboard (3)]

Hardware / Re: How to disable the touchscreen
« on: November 20, 2017, 06:48:43 am »
Before that though have you checked if you can disable the touchscreen in the BIOS ?
Yes I did and I haven't found any option to do that.

If xidput id 12 is the touchscreen, does it stop working if you unload the elan_i2c driver:

No it doesn't...  :-\

Hardware / Re: How to disable the touchscreen
« on: November 19, 2017, 03:18:46 pm »
Here it goes:
Code: [Select]
Module                  Size  Used by
rfcomm                 77824  2
ccm                    20480  2
bnep                   20480  2
dm_crypt               28672  1
dell_wmi               16384  0
dell_laptop            20480  0
dell_smm_hwmon         16384  0
ath3k                  20480  0
btusb                  45056  0
btrtl                  16384  1 btusb
btbcm                  16384  1 btusb
btintel                16384  1 btusb
bluetooth             557056  32 btrtl,btintel,bnep,btbcm,rfcomm,ath3k,btusb
hid_multitouch         20480  0
hid_sensor_rotation    16384  0
hid_sensor_incl_3d     16384  0
hid_sensor_magn_3d     16384  1
hid_sensor_gyro_3d     16384  0
uvcvideo               90112  0
hid_sensor_accel_3d    16384  0
hid_sensor_als         16384  1
videobuf2_vmalloc      16384  1 uvcvideo
hid_sensor_trigger     16384  11 hid_sensor_incl_3d,hid_sensor_als,hid_sensor_accel_3d,hid_sensor_magn_3d,hid_sensor_gyro_3d,hid_sensor_rotation
videobuf2_memops       16384  1 videobuf2_vmalloc
industrialio_triggered_buffer    16384  6 hid_sensor_incl_3d,hid_sensor_als,hid_sensor_accel_3d,hid_sensor_magn_3d,hid_sensor_gyro_3d,hid_sensor_rotation
videobuf2_v4l2         24576  1 uvcvideo
kfifo_buf              16384  1 industrialio_triggered_buffer
videobuf2_core         40960  2 uvcvideo,videobuf2_v4l2
hid_sensor_iio_common    16384  7 hid_sensor_incl_3d,hid_sensor_als,hid_sensor_accel_3d,hid_sensor_trigger,hid_sensor_magn_3d,hid_sensor_gyro_3d,hid_sensor_rotation
industrialio           69632  11 hid_sensor_incl_3d,hid_sensor_als,hid_sensor_accel_3d,hid_sensor_trigger,hid_sensor_magn_3d,hid_sensor_gyro_3d,hid_sensor_rotation,industrialio_triggered_buffer,kfifo_buf
videodev              172032  3 uvcvideo,videobuf2_core,videobuf2_v4l2
media                  40960  2 uvcvideo,videodev
snd_hda_codec_hdmi     49152  1
intel_rapl             20480  0
x86_pkg_temp_thermal    16384  0
intel_powerclamp       16384  0
coretemp               16384  0
kvm_intel             200704  0
kvm                   593920  1 kvm_intel
irqbypass              16384  1 kvm
crct10dif_pclmul       16384  0
crc32_pclmul           16384  0
ghash_clmulni_intel    16384  0
pcbc                   16384  0
dell_led               16384  0
dell_smbios            16384  3 dell_wmi,dell_led,dell_laptop
dcdbas                 16384  1 dell_smbios
aesni_intel           167936  703
aes_x86_64             20480  1 aesni_intel
arc4                   16384  2
crypto_simd            16384  1 aesni_intel
glue_helper            16384  1 aesni_intel
cryptd                 24576  352 crypto_simd,ghash_clmulni_intel,aesni_intel
intel_cstate           20480  0
ath9k                 147456  0
intel_rapl_perf        16384  0
ath9k_common           36864  1 ath9k
ath9k_hw              466944  2 ath9k,ath9k_common
snd_hda_codec_realtek    90112  1
ath                    28672  3 ath9k_hw,ath9k,ath9k_common
snd_hda_codec_generic    73728  1 snd_hda_codec_realtek
snd_seq_midi           16384  0
snd_seq_midi_event     16384  1 snd_seq_midi
mac80211              782336  1 ath9k
snd_rawmidi            32768  1 snd_seq_midi
input_leds             16384  0
joydev                 20480  0
snd_seq                65536  2 snd_seq_midi_event,snd_seq_midi
serio_raw              16384  0
snd_hda_intel          36864  5
snd_soc_rt5640        118784  0
intel_pch_thermal      16384  0
snd_soc_rl6231         16384  1 snd_soc_rt5640
cfg80211              602112  4 mac80211,ath9k,ath,ath9k_common
snd_hda_codec         126976  4 snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
snd_soc_core          233472  1 snd_soc_rt5640
lpc_ich                24576  0
snd_compress           20480  1 snd_soc_core
snd_hda_core           81920  5 snd_hda_intel,snd_hda_codec,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
ac97_bus               16384  1 snd_soc_core
snd_pcm_dmaengine      16384  1 snd_soc_core
snd_hwdep              16384  1 snd_hda_codec
shpchp                 36864  0
elan_i2c               36864  0
snd_pcm               102400  7 snd_hda_intel,snd_hda_codec,snd_pcm_dmaengine,snd_hda_core,snd_soc_rt5640,snd_hda_codec_hdmi,snd_soc_core
snd_seq_device         16384  3 snd_seq,snd_rawmidi,snd_seq_midi
snd_timer              32768  2 snd_seq,snd_pcm
mei_me                 40960  0
mei                   102400  1 mei_me
snd                    77824  23 snd_compress,snd_hda_intel,snd_hwdep,snd_seq,snd_hda_codec,snd_timer,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_seq_device,snd_hda_codec_realtek,snd_soc_core,snd_pcm
processor_thermal_device    16384  0
soundcore              16384  1 snd
intel_soc_dts_iosf     16384  1 processor_thermal_device
int3406_thermal        16384  0
intel_vbtn             16384  0
int3403_thermal        16384  0
sparse_keymap          16384  2 dell_wmi,intel_vbtn
dw_dmac                16384  0
dw_dmac_core           24576  1 dw_dmac
dell_smo8800           16384  0
i2c_designware_platform    16384  0
i2c_designware_core    20480  1 i2c_designware_platform
int3402_thermal        16384  0
int340x_thermal_zone    16384  3 int3402_thermal,int3403_thermal,processor_thermal_device
spi_pxa2xx_platform    24576  0
int3400_thermal        16384  0
8250_dw                16384  0
acpi_thermal_rel       16384  1 int3400_thermal
soc_button_array       16384  0
dell_rbtn              16384  0
mac_hid                16384  0
sunrpc                335872  1
parport_pc             32768  0
ppdev                  20480  0
lp                     20480  0
parport                49152  3 lp,parport_pc,ppdev
autofs4                40960  2
btrfs                1089536  0
xor                    24576  1 btrfs
raid6_pq              114688  1 btrfs
hid_sensor_custom      20480  0
hid_sensor_hub         20480  9 hid_sensor_incl_3d,hid_sensor_als,hid_sensor_accel_3d,hid_sensor_iio_common,hid_sensor_trigger,hid_sensor_magn_3d,hid_sensor_gyro_3d,hid_sensor_rotation,hid_sensor_custom
usbhid                 53248  0
i915                 1449984  7
i2c_algo_bit           16384  1 i915
drm_kms_helper        151552  1 i915
psmouse               139264  0
syscopyarea            16384  1 drm_kms_helper
sysfillrect            16384  1 drm_kms_helper
sysimgblt              16384  1 drm_kms_helper
fb_sys_fops            16384  1 drm_kms_helper
ahci                   36864  2
drm                   352256  6 i915,drm_kms_helper
libahci                32768  1 ahci
wmi                    16384  2 dell_wmi,dell_led
video                  40960  4 dell_wmi,dell_laptop,int3406_thermal,i915
i2c_hid                20480  0
sdhci_acpi             16384  0
hid                   118784  4 hid_sensor_hub,i2c_hid,usbhid,hid_multitouch
sdhci                  45056  1 sdhci_acpi
fjes                   77824  0

VinDSL I'd keep my distance from any touchscreen laptop. This "ghost touch" problem is quite common (as far as Google can tell...). My sister has a Lenovo 2x1 (just like my Dell) and she didn't had any problem so far.

As for my Dell, I also had to replace my HDD. This computer is 2 years old.

Hardware / How to disable the touchscreen [SOLVED]
« on: November 19, 2017, 05:59:29 am »
My laptop has a touchscreen. I don't use this feature and it is more annoying than a real feature. My panel suffers with ghost touches (sometimes the screen goes crazy, clicking randomly at the screen and then it is impossible to use the system.

There is a simple workaround, using this command:

Code: [Select]
xinput list
⎡ Virtual core pointer                    id=2 [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              id=4 [slave  pointer  (2)]
⎜   ↳ ELAN Touchscreen Pen                    id=11 [slave  pointer  (2)]
⎜   ↳ DLL0674:00 06CB:75DB Touchpad            id=14 [slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad              id=16 [slave  pointer  (2)]
⎜   ↳ ELAN Touchscreen                        id=12 [slave  pointer  (2)]
⎣ Virtual core keyboard                    id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard              id=5 [slave  keyboard (3)]
    ↳ Power Button                            id=6 [slave  keyboard (3)]
    ↳ Video Bus                                id=7 [slave  keyboard (3)]
    ↳ Power Button                            id=8 [slave  keyboard (3)]
    ↳ Sleep Button                            id=9 [slave  keyboard (3)]
    ↳ Integrated_Webcam_HD                    id=10 [slave  keyboard (3)]
    ↳ Intel Virtual Button driver              id=13 [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            id=15 [slave  keyboard (3)]
    ↳ Dell WMI hotkeys                        id=17 [slave  keyboard (3)]
    ↳ DELL Wireless hotkeys                    id=18 [slave  keyboard (3)]

and then

Code: [Select]
xinput disable 12

Adding this last command to my "Autostart" means I can forget about it.

However, I wonder if disabling the driver would be a better solution, specially considering battery life and ghost clicks in the login screen (although, honestly, that never had been a real problem). Anyway, how could I disable the driver for the touchscreen?

Code: [Select]
inxi -Fxz
System:    Host: christian-pepper-dell Kernel: 4.10.0-38-generic x86_64 (64 bit gcc: 5.4.0)
           Desktop: N/A Distro: Peppermint Eight
Machine:   System: Dell (portable) product: Inspiron 7347 v: 00h
           Mobo: Dell model: 0THD6P v: A00 Bios: Dell v: A09 date: 10/17/2016
CPU:       Dual core Intel Core i5-4210U (-HT-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9577
           clock speeds: max: 2700 MHz 1: 1124 MHz 2: 1105 MHz 3: 1000 MHz
           4: 999 MHz
Graphics:  Card: Intel Haswell-ULT Integrated Graphics Controller
           bus-ID: 00:02.0
           Display Server: X.Org 1.19.3 drivers: (unloaded: fbdev,vesa)
           Resolution: 1920x1080@60.00hz
           GLX Renderer: Mesa DRI Intel Haswell Mobile
           GLX Version: 3.0 Mesa 17.0.2 Direct Rendering: Yes
Audio:     Card-1 Intel 8 Series HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 Intel Haswell-ULT HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:03.0
           Sound: Advanced Linux Sound Architecture v: k4.10.0-38-generic
Network:   Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter
           driver: ath9k bus-ID: 01:00.0
           IF: wlp1s0 state: up mac: <filter>
           Card-2: Atheros usb-ID: 001-004
           IF: null-if-id state: N/A speed: N/A duplex: N/A mac: N/A
Drives:    HDD Total Size: 250.1GB (7.4% used)
           ID-1: /dev/sda model: Hitachi_HTS54252 size: 250.1GB
Partition: ID-1: / size: 87G used: 9.7G (12%) fs: ext4 dev: /dev/sda6
           ID-2: swap-1 size: 8.51GB used: 0.00GB (0%) fs: swap dev: /dev/dm-0
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 53.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 212 Uptime: 28 min Memory: 971.7/7909.9MB
           Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (fish) inxi: 2.2.35

Software & Applications / Re: Sakura and Fish Shell
« on: November 19, 2017, 05:37:36 am »
Thanks again and sorry for the delay.

So.... I've undone everything, and it was all back to normal (as is was supposed to be the default install). Then I've decided to edit the menu entry for the terminal with "sakura -e fish". This time around, the Plank icon responded accordingly and the terminal window opened with the fish command  :)

I've rebooted and everything still the same, just like I wanted!

So I guess I can mark this topic as solved. PCNetSpec thank you very much for your time and effort.

Software & Applications / Re: Sakura and Fish Shell
« on: November 17, 2017, 04:30:50 pm »
Okay undo all the changes you've made, so change the launcher lines back to just "sakura" and the keyboard shortcut back to "x-terminal-emulator"

Now here's the best way to set fish as your default shell

In the main menu open
System Tools > Users and Groups

in the left hand pane click on your user account to highlight it

Click the "Advanced Settings" button .. and enter your password when prompted.

In the next dialog box, choose the "Advanced" tab.

on the "Shell:" line click the little arrow button to display the drop menu

select "/usr/bin/fish"

Click the "OK" button.

Now you need to log off and on again before the change will take effect.

Now whenever you open sakura it should use fish as the shell.
I'll try it as soon as I get home.

Thanks again.

Just to be sure, I was afraid to set fish as my default shell because I was under the impression that it could cause instability issues. 

Enviado de meu Quantum Fly usando Tapatalk

Software & Applications / Re: Sakura and Fish Shell
« on: November 17, 2017, 02:35:42 pm »
Thank you very much for your help!

The keyboard shortcut worked flawlessly.

The menu entry didn't... it just opened the terminal normally (without the fish command).
Looking into the /usr/share/applications directory, there is two files for the terminal, one called Terminal and another called Terminal Emulator
Terminal runs
Code: [Select]
sakura -e fish
but it returns an error:
There was an error launching the application.

Terminal Emulator runs
Code: [Select]
exo-open --launch TerminalEmulator
And it launches sakura normally (wihtout the fish command).

The menu entry still works, but it only launches sakura with fish if i set "-e fish" on the command settings.

The plank icon for the terminal doesn't work anymore. I can add the icon but it won't launch it.

Software & Applications / Sakura and Fish Shell [SOLVED]
« on: November 17, 2017, 08:06:58 am »
I'm using Peppermint 8 and I like to use the fish shell

I don't want it to replace the default shell, however I do use it frequently, so I just edit the menu launcher to:

Code: [Select]
sakura -e fish

However, I can't figure out how to achieve the same result when using the keyboard shortcut "crtl + alt + t" or when I pin Sakura to my Plank dock. I have tried to edit the LXSession configuration to: "Terminal-manager x-terminal-emulator -e fish" but no success... Maybe I should just change this line to read "sakura -e fish"? This may sound stupid, but could I mess up my system doing this?


I'm using Peppermint 8 and I have the Plank dock installed. When using Chrome apps created with ICE, the Plank dock displays the Chrome icon (ignoring the SSB icon). Everywhere else, the system displays the proper icon. It doesn't make any difference if I use the site favicon or set one myself.
However, if I create the Chrome app using Chrome's built-in feature ("more tools > add to desktop"), the web app is positioned under "chrome apps" in the menu, but plank displays the icon that I have chosen.
I 'don't mind using Chrome, but i really would rather use ICE for web apps, as it allows for a better organization of web apps and I can freely choose a different browser (something that's very useful when dealing with different accounts for the same provider (I'm looking at you Google).   

Pages: 1 ... 11 12 [13]