Running Ubuntu 14.04 LTS on a Dell XPS-13-9350
in the last day or two the touchpad cursor started hanging, moving slowly, and then freezing. It will only move with a click-drag holding down on the touchpad, but then when I release it opens the right click menu, and left click is ignored...
Resta...
Using the bash shell I am trying to compute 78390^91025(mod 180577)
So using the base 78290 the power of 910025 and applying the modulus of 180577,
I wish to obtain the following logic:
y=base
for i = 1 to the exponent-1
y := (y*base) mod 'modulus'
next i
print y
In doing this I hope to sa...
I am running Ubuntu 14.04 LTS on a Dell 13-XPS-9350 laptop. I've had the laptop about 2 years.
Should I upgrade to a newer version of Ubuntu?
If so which version? and How?
The Ubuntu Software Updater, and the Ubuntu Software apps, don't seem to have any information about how to install a new...
@pomsky maybe we need an PSA for the people who are reviewing that 18.04 is now fine, but i agree with you that it looks more like a bug even i cant reproduce it here
@Fabby There are no dumb questions, people which are dumb ask no questions, they just mess it up an then let others solve the mess. So asking is an intelligent way of gaining knowledge, therefore no questioni is dumb! There are only dumb answers :)
@Videonauth I think it makes sense to close the questions until it's officially released. If there is a problem with the release, whereas, for some reason it can't be released on this day, they would get better support from the development site to get an understanding of the delay.
Since you and I "agree" that we don't see any scheuling problems, it would appear to make sense for the questions to wait for the actual scheduled release before trying to get support for something that hasn't been released.
I'm sure they are very busy getting everything organized to avoid confusion and problelms. I'm sure they want the release notes and everything to match when people start downloading the official released version.
Giving support to the beta version may flood the system with things that may not be a problem in the official release.
... or may have a simple solution that could be avoided by giving support for the official release and using the official notes and provided workarounds for issues tht remain.
I only watch the clock on the LTS versions. I'll have more insight the next time as a resulf of this script:
#!/bin/bash
echo "Checking the release status of 18 04 LTS" | espeak elinkout="$(elinks "https://www.ubuntu.com/download/desktop")" status="$(echo "$elinkout" | egrep 18.04)" echo $status > status-18.04.out
while [ ! "$status" ]; do date sleep 300 done date > ubuntu-18.04LTS-releasetime.sh while :; do echo "18 04 LTS has been released." | espeak sleep 300 done
It'll be two years before I watch the clock for a release again.
I used to when I was younger... might start back again after I catchup a little bit with the current LTS versions. It takes me a little longer to soak in everything.
It would probably take a minute to get in the club.
I have been heard on some of my suggestions. I hit a lot of nerves, but some of the of the senior mods at ubuntuforums.com, apologized and told me that agreed with some of my suggestions, and mad efforts to make changes.
I believe they have ears, it just takes patiences to get through somethings.
curl -s https://whatismycountry.com/ | grep "hank you for joining us from"has as output:var typedText = {"strings":"[\"Thank you for joining us from Germany\", \"enjoy your stay\"]"};
@Zanna I suppose if you want to process text using PCRE you just use Perl. ;P grep serves a different purpose, so it's useful to implement PCRE. Note however that man grep calls the -P option “highly experimental” in v2.24 (16.04) and still “experimental” in v3.1 (18.04).
I'm not sure that means it's still experimental at all. It may have been weakened instead of removed in order to avoid controversy. I'm not saying it's not experimental, only that I haven't observed any problems with it and people seem to use it in production with some regularity. I should look for the relevant parts of the commit history...
@dessert Was the issue originally that it did not support some PCRE features, or that it did not support some features of grep (rather than of regular expressions) when using -P? It links to the shared library for PCRE.
> Perl-compatible regular expressions give additional functionality, and are documented in pcresyntax(3) and pcrepattern(3), but work only if PCRE is available in the system.
PCRE is widely used, and I've never heard anybody say it's not regarded as stable. It's not, however, used by Perl for its natively supported regular expressions. (Hence "Perl Compatible Regular Expressions.") So for some weird cases that might be another reason someone would use grep -P instead of writing perl one-liner or short Perl script.
It will stay that way until somebody changes it. It's said stuff like that for so long, and yet grep -P seems to work fine for everybody whose uses it... I don't know what to believe.
Btw, I am not saying we should ignore it. Not based on my speculation that it might be removable, anyway.
But I don't recommend people overhaul all their scripts to remove grep -P out of fear that something might go kablooey, either. :)
@Zanna I remember in the Unix group about 10 years ago, whenever a Windows admin walked in and asked "How do I..." the answer before he could even finish his question was:
at zumba class, when the singer on the track swears, my zumba instructor pulls a face and apologises to the kids. If she didn't do that, they probably wouldn't even notice. So I'm not going to go into detail about why I think it's nsfw because I don't think that would help...
@Zanna GNU sed supports octal, hexacdecimal, and decimal escape sequences, with \o, \x and \d, respectively, and the work inside character classes. I think[\d0-\d127] should match any ASCII character if sed is using the C/POSIX locale.
This does filter the ASCII-only lines from their example input, but that doesn't prove there's no gap in my reasoning about setting LC_ALL=C being sufficient to ensure it:
LC_ALL=C sed -nr '/^[\d0-\d127]+$/p'
That command doesn't do the particular line-joining task they're asking for, of course.
I don't know why the alt code for it in Windows is 0153 (you're right that it is, though), so I don't know how to enter it using that number in Ubuntu.
@Videonauth Are you saying you can't enter any characters with their unicode code point values, on your Ubuntu system, by holding down Ctrl and Shift and typing a u followed -- while still holding down Ctrl and Shift -- by the number?
Anyway, the question of how to enter characters using the number that would be use with Alt in Windows is interesting. I don't know the answer. If we don't have something for that on the site, we probably should. At worst, there should be a way to convert them automatically, so an answer could explain how. At best, there should be a way to enter them using those values.
@Zanna Thanks for posting it! I was going to say that if you were unwilling to post it then I would do so... but that I'd have to actually fully learn how it works first, which I had been hoping to learn from your post about it. :)