Even though I'm not using anydesk, I experience the same problem. And I
think its caused by "dropbox"
> gnome-extensions disable ubuntu-appindicat...@ubuntu.com
This workaround seems to work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
> GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash
initcall_blacklist=simpledrm_platform_driver_init”
This workaround worket for me too.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268
Title:
I just did a fresh install of the official release of 22.04 LTS image
today, and hit this problem. I see no gear icon, and it defaults to X11,
with no option to select Wayland, whether I have just the NVIDIA GPU
enabled, or both the Intel integrated GPU and the NVIDIA discrete GPU
enabled in
*** This bug is a duplicate of bug 1969243 ***
https://bugs.launchpad.net/bugs/1969243
I just did a fresh install of the official release 22.04 LTS image
today, and hit this problem. No gear, and it defaults to X11, whether I
have just the NVIDIA GPU enabled, or both the Intel integrated GPU
In ubuntu 21.04, using chromium Version 98.0.4727.0 (Developer Build) (64-bit)
with kwin x window manager, i am unable to move tabs around (before or after
others). Instead new window is opening.
Short keys is working nut not mouse movement drag and drop.
--
You received this bug notification
Thanks for the suggestion. However, this does not make any difference. I
ran also "watch -n1 cat /proc/interrupts", "acpi_listen" and "sudo
showkey -s" and no reaction to brightness hotkeys whereas volume hotkeys
work and that also shows up when running these commands.
--
You received this bug
Hi, unfortunately not. Maybe it will get fixed sometime.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872311
Title:
Brightness hotkeys not working on Lenovo S740
To manage notifications about
** Changed in: snapd (Ubuntu)
Status: Incomplete => In Progress
** Changed in: snapd (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: snapd (Ubuntu)
Status: Fix Committed => New
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
** Changed in: snapd
Public bug reported:
I'm a Vaio user and my touchpad do not work at all OS boots. Sometimes
the touchpad initialize with system but stop to work after a variate
time lapse (5 minutes or 5 hours).
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-44-generic
After some more digging and having reproduced the issue a few more
times, here is what seems to happen.
Seahorse is running, using the avahi library. Seahorse has called
avahi_glib_poll_new() and some AvahiTimeout timeouts have been created.
Then things are stopped because the computer is about
I added some extra debug output in avahi and waited for the error to
happen again, in this way found out that the assertion failure happens
when the time_event_queue_root(q) call gives NULL so that the "else"
part is used in update_timeout() in avahi-core/timeeventq.c:
static void
Update II:
This used to occur again and again, plus the playback freeze was permanent.
^ also applies to v5.4.0-56
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907869
Title:
Weird audio problems
Update:
This time the playback freeze happened after an uptime of ~40min.
Did play audio almost right after logging in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907869
Title:
Weird audio
I have followed this guide
https://davidwpearson.wordpress.com/2020/01/10/lenovo-laptop-subwoofers-and-linux/#fix
i don't think it did a thing for the subwoofer, but it manages to sound a bit
nicer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Occurs only with my audio interface Steinberg UR22C, which is connected
via USB-C.
This is a regression.
Latest kernel known to work properly was: linux-image-5.4.0-48-generic.
(If I boot my current system with this one, everything's working fine.)
As far as I can tell this
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872333
Title:
MSFT0001:01 touchpad randomly does not work after boot (Lenovo Yoga
Sorry, I mixed secure boot to UEFI etc. After disabling secure boot, I
have been using mainline kernel 5.9.6-050906-generic for a while now in
Ubuntu 20.04 and the touchpad has always worked. Seems fixed there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Ubuntu 20.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1622499
Title:
[master] package kaccounts-providers (not installed) failed to
install/upgrade: trying to overwrite
https://forums.lenovo.com/t5/Other-Linux-Discussions/Lenovo-Yoga-S740
-Linux-Trackpad-very-temperamental-and-FN-Keys-barely-work/m-p/5037384
Just found out that this issue might be fixed in kernel 5.9. How could I
install 5.9 kernel and test this? I have secure boot enabled so the
mainline
Hi, just wanted to update that the problem persists in 20.10 and 4.8
kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872333
Title:
MSFT0001:01 touchpad randomly does not work after boot
Public bug reported:
When I updated from 18.04 to 20.04 with do-release-upgrade,
I noticed that the cups package prerm script would hang forever.
After I hit ctrl-C, it was fairly messy to fix the system back together.
When I traced this, I found that `which` in the prerm script
(and not just
*** This bug is a duplicate of bug 1820584 ***
https://bugs.launchpad.net/bugs/1820584
Looking at the code it seems the assertion that was triggered is in the
source code of the avahi package, so it probably makes sense to mark
this as a duplicate of bug #1820584 for avahi.
** This bug has
Related: bug #1888585 (
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1888585 )
The error "seahorse (seahorse) glib-watch.c → 195 → timeout_update →
Assertion `!t->dead'' failed." is listed with hundreds of occurrences
each day at https://errors.ubuntu.com/ but there is no bug report
> * Is this reproducible?
I don't have an exact way to reproduce it but it happens hundreds of
times each day, presumably for many different users, as seen at
https://errors.ubuntu.com/
However, although the "seahorse (seahorse) glib-watch.c → 195 →
timeout_update → Assertion `!t->dead''
Public bug reported:
This bug is seen in the list at https://errors.ubuntu.com/ where it
says: seahorse -- Ubuntu 20.04 -- seahorse (seahorse) glib-watch.c → 195
→ timeout_update → Assertion `!t->dead'' failed.
According to the list at https://errors.ubuntu.com/ it occurred 3201
times the past
Hi, with some updates during spring and summer this flickering has
stopped, so problem solved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873587
Title:
[Ice Lake] Display flickers a lot during
This is a false alarm, at least partly. If username is defined like
sftp://u...@some.server.org, everything works OK. It is likely that in
the live USB test case the server I use checks username from LDAP. As I
did not specify user name and the default "ubuntu" was used, connection
got denied. On
Public bug reported:
When trying to connect a server using ssh:// or sftp:// no user/password
information is asked and I get error saying "Access Denied".
Expected behaviour: user/password would be asked.
I tested also with 20.04 live USB - same behaviour.
Same erroneus action also when trying
for the record, the default mono version that comes with MX 19 is:
$ mono -V
Mono JIT compiler version 5.18.0.240 (Debian 5.18.0.240+dfsg-3 Wed Apr 17
16:37:36 UTC 2019)
after adding the official latest stable mono release and upgrading
$ sudo apt upgrade
I landed with
$ mono -V
Mono JIT
#4 rocks! Thanks Jason.
I can confirm, adding the official latest stable mono release to my package
repos
resolved the frequent crashes I used to have with pinta.
For the record, I am using MX Linux (so I used the debian packages for
mono)
$ uname -a
Linux mx 4.19.0-6-amd64 #1 SMP Debian
Indeed, crashing it twice within a few seconds will make the whole
session “crash” – just like doing `killall budgie-panel` twice.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880824
Title:
Another finding:
There's a 3rd case what can happen: Panel crashes but doesn't reopen again.
Could make it crash twice. After the first time it restarted. So I
waited a short while and made it crash again. Didn't reopen anymore.
I would guess, if I hadn't waited, the whole session would have
apport information
** Tags added: apport-collected bionic third-party-packages
** Description changed:
Budgie Panel (or sometimes even the whole session) crashes when dragging
items out of Budgie's task icon list.
Notes: Budgie Panel is placed on bottom on the very bottom screen (of
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1880824/+attachment/5379272/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880824
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1880824/+attachment/5379271/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Managed to reproduce this under 18.04.4, unfortunately.
Differences:
- It only happens sometimes. Seems like there's some (unknown) precondition.
- There's no freezing. Either budgie-panel or the whole session will crash
right away.
** Changed in: budgie-desktop (Ubuntu)
Status: Invalid
Appears to be not reproducible in an Ubuntu Budgie 20.04 amd64 Live
system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880824
Title:
Crashes when dragging items out of Budgie's task icon list
Public bug reported:
Budgie Panel (or sometimes even the whole session) crashes when dragging
items out of Budgie's task icon list.
Notes: Budgie Panel is placed on bottom on the very bottom screen (of 3).
Dragging them downside out of screen causes the crash.
Crash details:
Either budgie-panel
Hi, I posted about this here: https://forums.lenovo.com/t5/Ubuntu
/Lenovo-Yoga-S740-14IIL-Brightness-hotkeys-not-working-on-
Ubuntu-20-04/m-p/5011698
Let's hope someone picks up on this - so far no one has.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
An user called chirag patel solves the problem and posted it on Medium:
https://medium.com/@chiragpatel_52497/unable-to-install-package-name-
snap-package-name-has-install-snap-change-in-progress-b6768f2ce81d
This solves the problem:
Snap is probably still working on something in the background
Thanks, "sudo showkey -s" does not show anything for the brightness key
combination. Neither do the interrupts increase when the brightness key
combination is pressed. So I assume this cannot be fixed from the
software side.
The brightness keys are working on Windows. However, the laptop is quite
Public bug reported:
some sounds are playing over the device (like sound the box makes when i
turn the volume to max)
but chrome sound output does not appear on bluetooth box
this appeard after i upgraded yesterday from 19.10 -> 20.04 via do-
release-upgrade
all pkg's are up to date
tried to
Public bug reported:
After going forward from grub, the display flickers a lot, continuing it
throughout the boot and even in GDM. The display flickers a few times in
the desktop, and after that, the flickering goes away.
So this is mainly a cosmetic thing as the flickering stops after logging
Thanks for the comments. Please find attached the requested file (sudo
acpidump > acpi.log).
However, "watch -n1 cat /proc/interrupts" did not increase when I used
the Fn + F10/F11 (brightness) button. Contrast to that, the (working)
volume hotkeys increased the interrupts. I also ran
ug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-21-generic 5.4.0-21.25
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd
** Attachment added: "xkbcomp.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872311/+attachment/5352616/+files/xkbcomp.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872311
Title:
.4.0-21.25
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: elias 1447 F pulseaudio
/dev/snd/controlC0: elias 1447 F
** Attachment added: "xkbmap.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872311/+attachment/5352615/+files/xkbmap.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872311
Title:
I also want add that I've tested a manually compiled biosdevname v0.7.2
on our oldest hardware, HP Proliant G6 and our newest Dell PE Gen 14.
Intel, Mellanox and Broadcom cards. All works. It would be awesome if
next Ubuntu release got biosdevname v0.7.2 instead of a patched v0.4.1.
Anyways, let
I have the hardware. What do I need to do in order for this to be
accepted and pushed to the repositories?
And a side note is that this is fixed upstream, just upgrading to v0.7.2
will fix the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've now stumbled on this issue twice. It's pretty rare.
For me, I don't think it's directly tied to resuming a session (from
suspend or just from the lock screen).
I'm using nvidia-driver-430 with Geforce 1080 Ti on Ubuntu 18.04.
** Attachment added: "Ubuntu_invisible_letters.png"
I also have FutureMax Dance Mat. I think the main problem is with
Stepmania, however.
I've been using the following patch for Stepmania. It works most of the time.
https://github.com/stepmania/stepmania/pull/1745
Sometimes (after resuming from suspend and such) there are some intermittent
Public bug reported:
Web Extension API, `browser.search.get` throws error `An unexpected error
occurred` on ubuntu's version of firefox 68
Steps to reproduce
1. Extract attached ff-extensions.zip
2. In the extracted folder, run `web-ext run`
3. In address bar type about:debugging. Temporary
Public bug reported:
When I open the "Sound Recorder" program (gnome-sound-recorder) it shows
a list of sound clips that I have recorded earlier. If I click the play
button next to any of the sound clips, the program crashes.
The gnome-sound-recorder version used is 3.28.1-4
Expected behavior:
Public bug reported:
This is for gdebi version 0.9.5.7+nmu2.
When running gdebi-gtk through valgrind, for example like this:
valgrind gdebi-gtk -h
that shows lots of memory errors, for example:
- Conditional jump or move depends on uninitialised value(s)
- Use of uninitialised value of size 8
I just ran into this bug. Started uninstalling everything when I was
removing lamp-server. Thankfully I caught it at about 15% and killed the
session when I started noticing things disappearing. This is a critical
disastrous bug. How has it not been touched in so long?
If it's not going to get
Public bug reported:
Sorry, I Don't more information about this. Thank you
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.9
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
NonfreeKernelModules: overlay dm_mirror
Public bug reported:
After I choose the partition to install Ubuntu, i got the error. I was
trying to install it in my new HD.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.6
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
I'm also affected by this (Mellanox ConnectX-4).
Ubuntu 16.04.5 LTS
kernel 4.15.0-42-generic
biosdevname 0.4.1-0ubuntu9
Is there a packaged version of biosdevname with the patch?
Why does Xenial from 2016 have a biosdevname from 2012?
There are lot newer versions of biosdevname at
Audio recording of this problem.
@0sec
Front... _noise_
_silence_(background-noise-only)_
@3sec
Fron _noise_
_silence_(background-noise-only)_
** Attachment added: "playback -> plug in -> noise -> plug out -> silence; 2x"
This weird behavior isn't new and has been persisting since May (when I
installed Ubuntu on this device for the first time).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803871
Title:
[HP Spectre
x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: elias 1688 F...m pulseaudio
/dev/snd/controlC0: elias 1688 F pulseaudio
CurrentDesktop: Budgie:GNOME
Date: Sun Nov 18 14:37:51 2018
InstallationDate:
Public bug reported:
erro ao processar o pacote libflite1:amd64 (--configure):
O pacote está num mau estado de inconsistência; deve
reinstala-lo antes de tentar configura-lo.
Erros foram encontrados durante o processamento de:
libflite1:amd64
ProblemType: Package
DistroRelease: Ubuntu 16.04
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1803363/+attachment/5213178/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803363
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1803363/+attachment/5213177/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected bionic
** Description changed:
I was looking for the default key for taking a screenshot from
Unity/GNOME settings and found a list of keyboard shortcuts (as in the
attached screenshot).
It turns out that Ctrl+Alt+Print also happens
Public bug reported:
La imagen de ubuntu 18 se grabo en una memoria usb de 16 gb con rufus.
Cuando se estan copiando los datos al disco duros(ssd 240 gb) sale que
la instalacion no puede continuar porque los datos no estan correctos en
el medio.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
yeah, it's a Budgie session (Ubuntu Budgie).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799059
Title:
GNOME Screenshot crashes on "Grab the current window"
To manage notifications about this
Here you are.
** Attachment added: "gdb --args gnome-screenshot -i >log.txt 2>&1"
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1799059/+attachment/5204981/+files/log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
attached a should-is comparison to the original message
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799740
Title:
Moving desktop icons places them with some offset
To manage notifications about
Public bug reported:
Desktop Environment: Budgie
Note: I have HighDPI scaling enabled (200%).
Moving icons on desktop doesn't place them at the position where you
drag them to, but about 100px top-left from the target position.
This "error offset" is constant, though. It does NOT get bigger on
Maybe signing the mainline kernels (kernel.ubuntu.com/~kernel-
ppa/mainline/) could prevent this happening for some users.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788727
Title:
upgrade
Public bug reported:
GNOME Screenshot crashes on "Take screenshot" when "Grab the current window" is
selected.
"Grab the whole screen" and "Select area to grab" are working fine.
Might be related to Budgie.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-screenshot 3.25.0-0ubuntu2
Public bug reported:
" the installer encountered an unrecoverable error. A dsktop sessionwill
be run so that you may investigate the problem or try installingagain.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubiquity 2.18.8.1 [modified: usr/share/ubiquity/apt-setup]
Public bug reported:
My sound was working just fine, then tonight I came to use my notebook,
and noticed that there was no sound from any applications.
Using the ubuntu settings sound test, I was getting audio from both
speaker and headphones, but moving the volume bar doesn't do any
feedback,
Public bug reported:
1)
Description:Ubuntu 17.10
Release:17.10
2)
freecad:
Installed: 0.16+dfsg2-3
Candidate: 0.16+dfsg2-3
Version table:
*** 0.16+dfsg2-3 500
500 http://se.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
100 /var/lib/dpkg/status
3)
I
Public bug reported:
I had Ubuntu installed beside Arch. I finished setting Arch up so I
deleted Ubuntu. This rendered my system unbootable. I'm trying to
install another distro beside Arch to try to correct the problem but no
distro so far has been able to install grub.
ProblemType: Bug
the problem with password occurred. Now
it
only appears to get worse. Right now I am attempting to re-install 16.04
again. I
hope that this one is successful. It just said that installation is
complete and that I
should restart. I will see how this works.
Winston Elias
On Wed, Mar 14, 2018 at 4:47
Public bug reported:
It crashes during file install for Linux 18.04
It said Error 5
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.3
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture:
password. The DVD gets ejected every time I insert it into the drive.
I cannot boot
from the DVD neither can I find the installed version of 18.04.
I need HELP ASAP.
W Elias
On Sun, Mar 11, 2018 at 4:17 PM, Ubuntu Foundations Team Bug Bot <
1754...@bugs.launchpad.net> wrote:
> Thank you f
Public bug reported:
Not sure what the problem is, but the computer refuses to accept
pastword. After many attempts I tried a reinstall that has crashed and
it suggested that I file this report.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.2
ProcVersionSignature: Ubuntu
Yes, I am seeing this behaviour. My mistake - I did not understand that
the -t or --timeout define the length of test using one type of
stressor, not the length of the whole test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Expected behaviour when running
stress-ng --class cpu --sequential 4 --timeout 30s -v --tz
or
stress-ng --class cpu --sequential 4 -t 30 -v --tz
is the test should stop after 30 seconds.
The test goes on until user does CTRL-C in terminal window.
ProblemType: Bug
I might as well just add some facts and my logs.
First of all, I have one Xenial node where open vswitch worked, guessing that
that time open vswitch daemon started before trying to setup network.
And then on other machines it doesn't work cause the daemon isn't started
before trying to setup
Can also confirm that Marks patch worked.
This was two years ago, why haven't this been fixed yet?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448254
Title:
openvswitch systemd unit file
Hi everyone,
You can solve the non-boot issue adding a parameter to kernel. It worked
to me in my dell xps 15 9560 and Ubuntu 17.04.
you must, with root privileges, edit /etc/default/grub and add a parameter to
the default kernel command line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash
As a side note, you can rescue your system if it is currently not
booting.
Press esc during boot to bring grub options and select safe mode (I
think this is the name, it should be the last boot option), it may be
tricky to get the correct timing for pressing esc, and some people say
shift is the
I can confirm this issue.
What can I do? Is there any way of not having to reinstall the whole
thing?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1663926
Title:
Dell XPS 15 9560 (Nvidia 1050)
I am having an old problem it appears. My Dell XPS 1530 suddenly stopped
working on WiFi.
I have tried everything I found in Ubuntu help forums but so far nothing worked.
Also I have another bug with my laptop. On starting a box appears which
states "System program problem Detected."
--
You
Public bug reported:
Description: Ubuntu 16.04 LTS
ekammoun@ekammoun-ThinkPad-E550:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
linux-generic
I'm having a Software Center crash; please see:
https://github.com/awesomeWM/awesome/issues/1828#issuecomment-307533174
Should I create a new issue for it?
** Bug watch added: github.com/awesomeWM/awesome/issues #1828
https://github.com/awesomeWM/awesome/issues/1828
--
You received this bug
Public bug reported:
a message indicate that a kg processs was using some resource when i
have been installing the ubuntu restricted software
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libappindicator3-1 12.10.1+16.04.20170215-0ubuntu1
ProcVersionSignature: Ubuntu
Public bug reported:
Depois que eu instalei o sistema operacional de novo, ele ficou bugado,
e esse problema surgiu depois que reinstalei o ubunto 16.04 lts
ProblemaTipo: Pacote
DistroRelease: Ubuntu 16.04
Pacote: libfreetype6: amd64 2.6.1-0.1ubuntu2.2
ProcVersionSign ature: Ubuntu 4.8.0-36.
@Denny that Ubuntu documentation only seeks to confuse me more... So if
my keyboard input isn't controlled with fcitx, or ibus (I had to install
it) then what was it being controller by? 0_o spooky
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I will reiterate to everyone that ibus is not the default input method
for Ubuntu/Kubuntu/Xubuntu etc. They all use fcitx. If everyone having
this problem could just do as comment #25 suggests I strongly believe
their problem will be solved.
--
You received this bug notification because you are
Joel, Please do the following in a terminal:
sudo apt purge ibus
sudo dpkg-reconfigure fcitx
sudo reboot
Everything should be back to normal after this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
More information: as the bug report in Debian says, changing the driver
to "intel" seems to fix the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677745
Title:
Xcalib not working in any
I am truly sorry for wasting everyone's time with so many junk posts. I
finally figured out what to do instead of messing around with ibus which
isn't even the default input method. it's this simple, go to a terminal
and type
sudo dpkg-reconfigure fcitx
and then reboot. This works perfectly for
Public bug reported:
There is a bug report in Debian already:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851810
Not sure whether it helps to report it here, so just to be sure.
Using Ubuntu 17.04 Beta with latest updates, no matter what is done with
xcalib, there is the same error:
One last thing everyone... you're gonna wanna put that code
ibus-daemon -d -n --desktop=KDE
on your list of autostart programs so it boots up every time the PC
does. Also you will wanna change it if you end up using a different
desktop environment of course (and possibly why I was having errors
1 - 100 of 1203 matches
Mail list logo
