You are not logged in.
- Topics: Active | Unanswered
#76 Re: Installation » Odd mouse behaviour » 2019-02-16 18:53:56
Tatwi wrote:Kernel 4.19:
- Add backports repo
echo "deb http://ftp.debian.org/debian stretch-backports main" | sudo tee -a /etc/apt/sources.list > /dev/null
sudo apt-get updatein Devuan you need ascii-backports, not stretch-backports. you shouldn't be mixing Debian/Devuan repos, not a good practice...
Thanks. I'll change it.
Edit:
I changed the sources.list to the correct version for Devuan. Updated, fortunately nothing broke. Chalk that up to it being years since I have used a backport of anything and following a guide for Debian lol... Knowledge, use it or lose it! 
#77 Re: Installation » Installing devuan without pulseaudio. » 2019-02-15 07:18:26
Ron wrote:Does Miyo have pulseaudio already removed? It's not installed on my system and I don't remember removing it.
Hi Ron! Hope you're doing well!
Miyo was "pulse-free" until Miyo-Modern was released late last year.
With that release, I decided to include it for two reasons...
1. Miyo is meant to make it easier for those who may be interested in a window manager, but they haven't pulled the trigger yet (for whatever reason).
2. Though I personally prefer using alsa, there are many folks who have more than one soundcard. Unfortunately, alsa doesn't automatically choose the correct one; whereas, pulseaudio does. So...for those who may be unaware of how to set their correct soundcard with alsa, I decided to use pulse in my latest builds in order to help folks.
Those who are familiar with setting their sound card with alsa will have no problem removing pulse...and yes, I've removed it with no issues on actual installations. Just run these commands...
sudo apt-get remove --purge pulseaudio*
sudo apt-get remove --purge pavucontrol*
sudo apt-get autoremove
After that, set your soundcard with alsa (if needed), reboot, and bam! Sound without pulsification!
So, unless you've reinstalled with Miyo-Modern or Miyo-Basic...you didn't get pulseaudio from me!
LOLOLOLOLOLOLOLOLOL!
I can confirm that it is that easy to simply remove Pulse Audio after installation. Personally, I remove PA, because it causes regular drops in signal ("choppiness") when recording audio through the RCA inputs on my TV tuner card (which is hooked up to my sound board).
If you're not familiar with setting the priority of your sound card in ALSA, here is what I do:
1. List sound cards installed
cat /proc/asound/cards
Output:
0 [SB ]: HDA-Intel - HDA ATI SB
HDA ATI SB at 0xfeb00000 irq 16
1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xfea60000 irq 49
2 [SAA7134 ]: SAA7134 - SAA7134
saa7133[0] at 0xfe700000 irq 20
3 [U0x46d0x825 ]: USB-Audio - USB Device 0x46d:0x825
USB Device 0x46d:0x825 at usb-0000:04:00.0-1, high speed2. List playback devices
aplay -l
Output:
**** List of PLAYBACK Hardware Devices ****
card 0: SB [HDA ATI SB], device 0: ALC887-VD Analog [ALC887-VD Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: SB [HDA ATI SB], device 1: ALC887-VD Digital [ALC887-VD Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]
Subdevices: 1/1
Subdevice #0: subdevice #03. Edit Alsa config
sudo nano /etc/modprobe.d/alsa.conf
options snd-hda-intel id=Intel index=0
options snd_hda_codec_hdmi id=HDMI index=1
options saa7134_alsa id=SAA7134 index=2Where 0 is the default output option and snd-hda-intel is the audio out on my motherboard.
If you're using Xfce, you may also find that it is helpful to have a volume icon on the toolbar. Thankfully there is an option for that in the repo!
sudo apt-get install volumeicon-alsa
And then add it to the startup
(Menu > Settings > Session and Startup > Application Autostart)
Command: volumeicon
#78 Re: Installation » Odd mouse behaviour » 2019-02-15 06:56:09
This issue appears to be resolved for me now. I decided to reinstall Devuan 2.0 on a test hard drive again yesterday (otherwise same hardware as before) and I have not experienced the right click issue. Awesome, because that was really my only gripe with Devuan (I didn't want to accidentally delete items).
I haven't done much to customize this installation, beyond using the backport of kernel 4.19.0 (which works better with my AMD R9 270 video card). Here are the notes of the customization/installation, in case they are helpful...
Installation:
- Net install, Xfce desktop, no unusual choices or customizations.
Sudo:
- visudo opens in nano by default already. Woohoo!
Kernel 4.19:
- Add backports repo
echo "deb http://ftp.debian.org/debian stretch-backports main" | sudo tee -a /etc/apt/sources.list > /dev/null
sudo apt-get update
- Update all packages to backports versions
sudo apt-get -t stretch-backports upgrade
- Search for available kernels
apt-cache search linux-image
- Install kernel 4.19
apt-get install linux-image-4.19.0-0.bpo.1-amd64
Uninstall Old Kernel:
- List installed kernels
dpkg --get-selections|grep linux-image
- Remove old kernel
sudo apt-get remove linux-image-4.9.0-6-amd64
AMD GPU Drivers:
apt-get install firmware-amd-graphics
Fix Screen Tearing:
- Double check that Xfce compositing is off (Menu > Settings > Window Manager Tweeks > Compositor).
- Install Compton
apt-get install compton compton-conf compton-conf-l10n
- Add Compton to startup (Menu > Settings > Session and Startup > Application Autostart)
compton --backend glx --paint-on-overlay --vsync opengl-swc
#79 Re: Installation » Odd mouse behaviour » 2018-10-28 07:56:32
Altoid wrote:I assume that you are referring to Applications -> Settings -> Mouse and Touchpad -> Behaviour?
Double Click Time = 400-500 ms
Double Click Distance = 5 px
I'm giving these settings ago as of now. Hopefully it works out. Wasn't really sure how high was too high for those settings.
Incidentally, I tried https://www.theregister.co.uk/ in Firefox (60.2.2esr) and I could right click normally on every link I tried. Only addon I have enabled is UBlock Origin.
Update 2018.10.28:10:12PM EST:
Yup, the issue is still happening to me when using Thunar. Super annoying and somewhat dangerous (would hate to accidentally delete something/everything important!).
Sorry I don't have anything useful to add in the way of troubleshooting or explanations. I don't seem to have the issue with all software, not even other GTK+ applications.
I'm going to try using Caja instead of Thunar for now.
#80 Re: Installation » Odd mouse behaviour » 2018-10-24 16:25:10
Altoid wrote:When I 'left click' on a link, instead of getting the drop down menu so as to be able to select what to do ie: open link in new tab/window/private window, etc. it directly opens the link in a new tab.
You probably mean Right-Click, but whatever. I wonder if this is the same as your other problem, that the popup menu isnt displayed long enough for you to react. And then the top menu option (Open Link in New Tab) is being selected "quickly" before you realize it?
Both these problems happen to me, randomly also, but I notice it in Thunar. I can Right-Click on empty space to bring up the menu, and the top menu option "Create Folder" gets selected before I can react. Also, experience your other problem; the menu quickly goes away and I have to hold the right button down and navigate the menu while its pressed.
I am using an old HP usb wire mouse.
I thought that was my imagination! I've noticed this happening from time to time as well. I'm not ruling out that it's a PEBKAC issue, but if it's not, how do you narrow down to find the root cause?
I'm using a Logitec M510 wireless mouse (with the receiver plugged into the keyboard 5" away), ASCII with XFCE.
Poking at Thunar, right clicking on the open space, it seems that if I click too quickly I can initiate a double left click (and that would be a definitive PEBKAC) which then triggers the default action (create folder). The didn't happen to me when I tested in Firefox (I normally use Chromium, doesn't happen there either) and that seems to be related to how Firefox doesn't automatically select an option from the menu. So, that doesn't explain the issue Altoid is having.
By default the double click time in the XFCE Mouse and Touchpad panel is 250ms. Could try increasing it or perhaps it's already very low for Altoid for some reason. If that's not it, maybe it's an issue in the kernel module for mice where the "de-bounce" code isn't always effective.
#81 Re: News & Announcements » Debian Buster release to partially drop non-systemd support » 2018-10-24 16:00:19
As a former Slackware user from 1998-2008ish, the convenient package management system and the larger amount of directly related documentation (in large part due to Ubuntu's popularity) are why I went with Debian (and Debian-based distros). Honestly, I don't really care about the init system, I just don't want to use garbage software like pulseaudio and systemd.
I could use Slackware, but it's just so much easier to configure and update a Debian-based system. Devuan is pretty bare bones when it comes to configuration, yet the only thing I had to manually change when I installed it recently was the order of my sound devices. That's it, for the whole system! Slackware 14.2 on the other hand... I just gave up trying to get X.Org to run properly...
Sorry, my point here is that Debian used to be something special, something ... not Slackware... and now Devuan is what Debian used to be. It's annoying and it's stupid that such a thing had to occur, but it is what it is and think that's the way Devuan should be looked at going forward. If that means having to maintain packages from the software developer's source, well I guess that's what will have to be done, right? That's what Slackware and PCLinuxOS do.
I've never maintained any packages, but I am quite certain that I am capable of doing so. However, I'm sure I don't truly appreciate the scope of such a project and I'm not familiar with the associated commitments of one's time and resources. With that in mind, I'm willing to maintain some part of the system.
So I ask,
What would it take to for Devuan to be a stand-alone distro that doesn't require anything from Debian at all?
Would the end result be basically the same "Debian" we had in Wheezy and prior releases?
Is it worth the effort?
With that last question, I was imagining putting the time into making a Debian-like system using Slackware packages or just joining PCLinuxOS and perhaps making a "stable" release (using the Debian installer) based off their rolling release. I mean, time is after all the ultimate currency; Where's it best spent?
Board footer
