In my case Gnome Extensions works under Wayland but it crashes under
Xorg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966502
Title:
gjs-console crashed with SIGSEGV
To manage notifications
*** This bug is a duplicate of bug 1966502 ***
https://bugs.launchpad.net/bugs/1966502
** This bug has been marked a duplicate of bug 1966502
gjs-console crashed with SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1966502 ***
https://bugs.launchpad.net/bugs/1966502
Public bug reported:
I get this crash when trying to execute gnome-extensions-app.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gjs 1.72.0-1
ProcVersionSignature: Ubuntu 5.14.0-1024.26-oem
Public bug reported:
I got this error and the upgrade from Ubuntu 21.10 to 22.04 aborted with
a black screen. I could recover from the boot recovery menu and the dpkg
reconstruct option.
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: ubuntu-release-upgrader-core 1:22.04.7
** Bug watch added: gitlab.gnome.org/GNOME/NetworkManager-fortisslvpn/-/issues
#36
https://gitlab.gnome.org/GNOME/NetworkManager-fortisslvpn/-/issues/36
** Also affects: network-manager-fortisslvpn (Fedora) via
https://gitlab.gnome.org/GNOME/NetworkManager-fortisslvpn/-/issues/36
I fixed it by purging everything and reinstalling. The actual place for
the log is:
/var/lib/dkms/virtualbox/6.1.6/5.4.0-39-generic/x86_64/log/make.log
This one already shows the successful compilation after the purge.
** Changed in: virtualbox (Ubuntu)
Status: Incomplete => Invalid
--
Public bug reported:
Upgrading from 19.10 to 20.04 produced this error, virtualbox-dkms could
not be upgraded.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: virtualbox-dkms (not installed)
ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
Uname: Linux 5.4.0-39-generic x86_64
Public bug reported:
My wifi card (ath10k) is not working any more after this update:
Start-Date: 2020-03-16 14:42:57
Commandline: aptdaemon role='role-commit-packages' sender=':1.13453'
Install: linux-image-5.3.0-42-generic:amd64 (5.3.0-42.34, automatic),
linux-headers-5.3.0-42-generic:amd64
I confirm that timidity works after removing the timidity user. So
instead of removing timidity all together, another workaround for this
bug is to remove the timidity user and make sure the audio group is
empty.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Currently ssmtp is unmaintained at Debian and so probably will disappear
soon from the repositories:
https://wiki.debian.org/sSMTP
A very similar program to substitute it, already in the repositories, is
msmtp:
https://wiki.debian.org/msmtp
The above setup works perfectly with this other
On comment #10, with a session restart it is enough for the fix to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640409
Title:
show my login name in menu bar not working.
To manage
Public bug reported:
Steps to reproduce:
Configure ssmtp to send through gmail following these instructions:
mailhub=smtp.gmail.com:587
AuthUser=myemailaddr...@gmail.com
AuthPass=MyPassword
UseTLS=YES
UseSTARTTLS=YES
rewriteDomain=gmail.com
hostname=localhost
FromLineOverride=YES
>From the
Krister, see bug 1713615
** Changed in: aptdaemon
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1204022
Title:
Unable to locate a file for the
Daniel, why do you say it is unmaintained? I see an active Debian
maintainer:
https://tracker.debian.org/pkg/timidity
and in Sourceforge there is a new upstream version from October 2018.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I do use it, to play midi files and to convert them to other formats.
But if it is an abandoned project, I will have to look for alternatives.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793640
I still have this problem in Ubuntu 19.04 develpment version. Here is a
Debian bug about this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901931
** Bug watch added: Debian Bug tracker #901931
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901931
--
You received this bug
Public bug reported:
Steps to reproduce:
1) Open unity-control-center ("settings")
2) Click on "Details"
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: unity-control-center 15.04.0+19.04.20190209-0ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic
Result of:
dpkg -l > dpkgl.txt
** Attachment added: "dpkgl.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1793640/+attachment/5204898/+files/dpkgl.txt
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: pulseaudio (Ubuntu)
Status:
** This bug is no longer a duplicate of bug 1781294
No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell
XPS 13 9360/9370]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, I undup, the sound card is the same, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781294
Title:
No sound card detected by PulseAudio and ALSA, but is visible in lspci
[Dell XPS 13
Daniel, I did what you suggest in #10 and no change.
** Changed in: pulseaudio (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/1781294
Title:
No sound
Bug #1784485 is also reporting sound problems with the same audio card
as the systems in this bug, but I'm not sure if it can be duplicated to
this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm closing this bug a I haven't seen the issue for a long time.
** No longer affects: emacs
** No longer affects: lilypond
** Changed in: lilypond (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have a XPS 13 9370 with the same card and I'm seeing exactly the same.
My card was being detected correctly in Ubuntu 18.04 but stopped being
detected when I upgraded to the Ubuntu 18.10 development version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
In my case if I do:
sudo alsa force-reload
the sound card is detected. If I'm plugged into the Dell dock station it
keeps detecting only a USB headphone (and it works through that both
with pulseaudio and alsa).
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1781294 ***
https://bugs.launchpad.net/bugs/1781294
** This bug has been marked a duplicate of bug 1781294
No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell
XPS 13 9360]
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1781294 ***
https://bugs.launchpad.net/bugs/1781294
I've changed the title because according to lspci the audio device is
actually Intel Corporation Sunrise Point-LP HD Audio (rev 21)
** Summary changed:
- [XPS 13 9370, Realtek ALC3271, Speaker, Internal]
*** This bug is a duplicate of bug 1792537 ***
https://bugs.launchpad.net/bugs/1792537
** This bug is no longer a duplicate of bug 1785498
g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
** This bug has been marked a duplicate of bug 1792537
Public bug reported:
Steps to reproduce:
Upgrade from 18.04 to 18.10 with unity-ubuntu-desktop and lightdm
What should happen:
Lightdm initial screen should show "Ubuntu 18.10"
What happens:
Lightdm initial screen shows "Ubuntu 18.04"
See this merge request:
Public bug reported:
After upgrading to the 18.10 development version from 18.04 only "Dummy
sound" is shown. The speakers are not recognized, but plugging
headphones works. The system was working well in 18.04.
With:
sudo alsa force-reload
the speakers start to be shown in the sound system
You have a very old release from 2013 and now it is impossible to
upgrade it the current releases. It would be recommended in this case to
save all your data and documents and do a clean new install.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Incomplete
--
You
Can anybody please nominate this bug for bionic because it produces an
error when trying to upgrade from 18.04 to 18.10? See:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1790693
and
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1793164
--
*** This bug is a duplicate of bug 1785498 ***
https://bugs.launchpad.net/bugs/1785498
** This bug has been marked a duplicate of bug 1785498
g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1785498 ***
https://bugs.launchpad.net/bugs/1785498
It looks like this is this problem:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1785498
Curiously, I upgrade another 18.04 system to 18.10 and did not see this
problem. Are appstream and
Public bug reported:
While trying to upgrade from 18.04 to the development version 18.10
using "update-manager -d" the upgrade aborts before "getting new
packages". A windows pops up with the following information:
Error during upgrade
A problem occurred during the update. This is usually some
I should say I don't see any network connectivity problem as the above
mentioned windows suggests.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793164
Title:
appstreamcli error when upgrading
** Tags removed: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763748
Title:
Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working
in DELL XPS 13 9370
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763748
Title:
Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working
in DELL XPS 13 9370
I finally could get back to my laptop, and I have tried Kau-Heng's
patched kernel 4.15.0-22 . I confirm that the webcam now works as
expected. Thanks a lot Kay-Heng and Mario.
I will apply now for a SRU for all supported Ubuntu versions.
--
You received this bug notification because you are a
More comments coming from DELL:
"Yesterday, a new Dell internal document was created which contained a
temporary work around to downgrade the camera firmware to 1.0 ( the file
RomainDurritcague shared ). This internal document is about to be deleted as
this fix wasn't meant to be shared yet.
A solution has been proposed by Dell France:
http://dl.free.fr/uYeYUDXjo
Untar the archive and then go inside the folder, and you should be able
to execute: sudo ./rts_uvc -v 0x0bda -p 0x58f4 --download
170606_6BF129N2_58F4_v7605.rfw
It should say a huge "PASS" and after rebooting the camera
As I said, this at least in my case was caused because I was using mutt
before the sidebar was coded into the main version (I was using
something called "patched" mutt). This file is not needed any more and
can be removed manually and the bug is gone.
It you think this is a bug please open a bug
@jay-z The reason is quite simply that there are drivers for this webcam
available for Windows but not for Linux.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763748
Title:
Integrated Webcam
@asgard2, open please another bug report with your system information.
Try also to disable all add-ons and see if you see the crash, just in
case it is not caused by an add-on. I was affected by this bug but I
haven't seen this crash for months. This bug report is expired and
nobody will pay
See this forum:
https://www.dell.com/community/Linux-General/Dell-xps-13-9370-Webcam-
support/td-p/6032049
Dell is downgrading the firmware by plainly substituting the whole
screen with another screen that has the integrated webcam with firmware
1.00.
--
You received this bug notification
As I say in message #5, I tried 4.17rc1 and the webcam was still not
working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763748
Title:
Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4)
I found an application that detects the camera, vokoscreen. But neither
cheese nor skype can detect it. So I will close this as invalid and
investigate somewhere else.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a
I tried also the 4.13 kernel, and the webcam is not working there either
(not detected by applications, detected by the system). This is strange
because this webcam was working for me in Ubuntu 17.10.
The microphone of the webcam is working normally.
--
You received this bug notification
I tried the 4.17rc1 mainline kernel and same thing, webcam detected by
the system but not by applications.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765058
Title:
Regression: 046d:08da
Public bug reported:
The 046d:08da Logitech, Inc. QuickCam Messanger webcam that was being
detected fine in Ubuntu 17.10 is not being detected in bionic by
applications. It is detected fine by the system, but Cheese for instance
reports "No device detected", and I've tried with other applications
** Tags added: kernel-bug-exists-upstream-4.17rc1
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765058
Title:
Regression: 046d:08da Logitech, Inc. QuickCam
I tried this last one, and webcam still not detected. But now syslog
seems to show the 1.00 firmware. This is the output of "dmesg | grep
uvcvideo":
dmesg | grep uvcvideo
[2.148721] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (0bda:58f4)
[2.149311] uvcvideo: UVC non compliance -
Thanks Key-Heng, I tried your kernel but in my system there is no
change. The webcam is still using the 1.50 firmware and is not detected
by the system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Kai-Heng Feng (kaihengfeng):
>Is the webcam firmware upgradable under Linux? I can't reproduce the issue on
>the XPS 9370 at my hand >because it's with older firmware.
As far as I can tell the only way to upgrade the firmware is to
completely change the screen, at least this is what Dell is
I've tried with a 4.17rc1 kernel recompiled with the patch mentioned in
#2 but no change, the webcam does not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763748
Title:
Integrated Webcam
Dear Stefano, I think the problem is there is no appropriate driver in
the Linux kernel for the 1.50 firmware, and the installed webcam has
that firmware.
I'm trying now to recompile the 4.17.rc1 kernel with the patch I mention
in #2. I will try this patched kernel and see if the webcam works.
** Summary changed:
- Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in
DELL XPS 13 9370
+ Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in
DELL XPS 13 9370 with firmware 1.50
** Description changed:
The webcam is detected by the system, but
I tried the following upstream kernel:
Linux XPS-13-9370 4.17.0-041700rc1-generic #201804152230 SMP Mon Apr 16
02:33:40 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
and the bug is reproducible.
** Tags added: kernel-bug-exists-upstream-4.17.rc1
--
You received this bug notification because you are
Another piece of information. This webcam is working with the 1.0
firmware, but not with the 1.5 firmware that the Dell XPS 13 9370 ships
right now. Some affected user have reported the issue and they have
changed the screen for them with a webcam with the 1.0 firmware, and the
webcam started
Public bug reported:
The webcam is detected by the system, but no applications detect it.
sudo lsusb -v: (relevant part)
Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.01
It seems that there is a patch being worked out:
https://www.mail-archive.com/linux-media@vger.kernel.org/msg127992.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763748
Title:
Integrated
This is caused by the following file:
/etc/Muttrc.d/sidebar.rc
It looks like a remaining from when I used a patched version of mutt, to
have a sidebar. The sidebar has been now been added as a feature of
normal mutt, so probably this is not needed. I have moved this file out
of that directory,
Public bug reported:
I have Mutt configured to use the sidebar. When I start mutt, the
following error is reported:
Press any key to continue...ar.rc, line 4: ifdef: unknown command
Error in /usr/lib/mutt/source-muttrc.d|, line 5: source: errors in
/etc/Muttrc.d/sidebar.rc
Error in /etc/Muttrc,
Yes, this is present in 17.10.
** Tags added: artful
** Changed in: appmenu-qt (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-session (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I've checked and everything seems OK, at least for Catalan. Thanks
@seb128 and @gunnarhj.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749673
Title:
Fcitx translation to Catalan not imported
To
Thanks @Sebastien and @Gunnar. As for @Sebastien's question, the place
where I don't see any of my Transifex translations is:
https://translations.launchpad.net/ubuntu/bionic/+source/fcitx/+pots/fcitx/ca/+translate?show=untranslated
Same thing for other packages like "systemd", which I
Public bug reported:
Fcitx is translated into Catalan in Transifex. But these translations
are not imported into Launchpad. Is there anything special that has to
be done for the import to happen?
** Affects: fcitx (Ubuntu)
Importance: Undecided
Status: New
--
You received this
** Bug watch added: GNOME Bug Tracker #787731
https://bugzilla.gnome.org/show_bug.cgi?id=787731
** Changed in: nautilus
Importance: Medium => Unknown
** Changed in: nautilus
Status: Confirmed => Unknown
** Changed in: nautilus
Remote watch: GNOME Bug Tracker #703179 => GNOME Bug
Same for me. I really don't understand how /etc/resolv.conf should be
managed in Ubuntu 17.04. I have the setup described in comment #7. I
tried to have only network-manager manage /etc/resolv.conf, but then I
loose name resolution in containers.
I think we should open a new bug report, as this
@ventrical, it's:
/usr/share/unity-greeter/unknown_badge.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716986
Title:
Unity session entry in lightdm has a white circle logo
To manage
I'm experiencing this same issue.
A workaround that works for me is to remove my vpn domain from
/etc/resolv.conf. The last line of this file looks as follows after a
successful VPN connection:
search Home myvpndomain
where the last term is the domain of my vpn (vpn.bla.com). The workaround is
*** This bug is a duplicate of bug 1703046 ***
https://bugs.launchpad.net/bugs/1703046
** This bug has been marked a duplicate of bug 1703046
indicator-printers-service crashed with SIGSEGV in
__GI_strtol_l_internal()
--
You received this bug notification because you are a member of
I have tried this functionality in Ubuntu 17.10 with Unity and the
original behavior seems to be back. Can anybody confirm if this is still
an issue?
** Changed in: gtk
Importance: Medium => Undecided
** Changed in: gtk
Status: Expired => New
** Changed in: gtk
Remote watch: GNOME
** Bug watch added: Debian Bug tracker #875855
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875855
** Also affects: gnome-activity-journal (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875855
Importance: Unknown
Status: Unknown
--
You received this bug
Public bug reported:
After upgrading to 17.10 from 17.04, and switching back to lightdm from
gdm3 to be able to start the Unity 7 desktop, the entry in the login
screen for Unity 7 has a white circle as a logo (the Ubuntu logo is now
assigned to the default Gnome option). A logo should be created
@kralph Good to know! I will close the bug when Emacs 25 arrives to the
repositories.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292630
Title:
24.3; Emacsclient freezes if mutt attaches a
@cpollok , maybe you should open a new bug report with the information
of your system if this is still an issue for you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924647
Title:
Ignore my comment #12, just got the Firefox freeze using the
4.10.0-22-generic kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656065
Title:
Firefox and plugin-container (Chrome_ChildThr):
Since upgrading the kernel to 4.10.0-22-generic in Ubuntu 17.04 I
haven't seen this bug any more. I think Firefox was also triggering a
general system freeze through a problem in the kernel. See bug #1674838
and the many messages relating it to a firefox freeze.
--
You received this bug
** Changed in: ubuntu
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686329
Title:
System freezes randomly after upgrading to ubuntu 17.04
To manage
I'm seeing a similar crash with this message:
[ 5486.157823] Chrome_ChildThr[20218]: segfault at 0 ip 7fa357e6ec10 sp
7fa34c0fe7f0 error 6 in libxul.so[7fa3571c+401a000]
The page triggering this is:
http://www.lavanguardia.com
Just scrolling down the page I can reproduce this 100%
My setup:
Ubuntu 17.04.
Firefox: 53.0.3+build1-0ubuntu0.17.04.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656065
Title:
Firefox and plugin-container (Chrome_ChildThr): segfault at 0 ip
I've seen this bug in the scenario described in comment #218. In my
case, there was always a frozen Firefox around, but all the other
processes running in the system where also reacting slowly or frozen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm getting a freeze with the same symptoms described in this bug
report, but with this message
May 31 02:37:27 walter kernel: [410240.819651] NMI watchdog:
BUG: soft lockup - CPU#14 stuck for 22s! [JS Helper:23856]
I'm running 4.10.0-21-generic.
I will duplicate my bug report (bug #1677491)
*** This bug is a duplicate of bug 1674838 ***
https://bugs.launchpad.net/bugs/1674838
I got this freeze again with 4.10.0-21-generic x8_64 kernel. When it
freezes I have the following message in syslog:
May 31 02:32:03 walter kernel: [409916.803508] NMI watchdog: BUG: soft
lockup - CPU#14
Sorry, but checking my logs my stuck message has not "[ksmd:64]" at the
end, but something different, I think "js" something. Right now I don't
have any to put the exact string.
I keep getting lockups with the 4.10 kernel series, I've updated to
4.10.0.20 now but I got one with 4.10.0.19.
I ran
Thanks dsmythies, I have actually not much idea on what is going on. I
will try 4.11 longer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677491
Title:
System freeze
To manage notifications
I got now this freeze with 4.10.0-19. I'm seeing this message in syslog:
NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [ksmd:64]
Please see this forum message #5 and #10 just in case it may help, there
is a patch applied in 4.11 RC 6:
https://ubuntuforums.org/showthread.php?t=2354739
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677491
Title:
System freeze
To manage notifications about this bug go to:
I've been running 4.10.0-15 for a couple of days and I don't see this
freeze any more, so I'm closing for the time being.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I did not get these freezes with the kernels 4.10.0-13 or the upstream
kernel 4.11.0-041100rc5-generic which I'm running right now.
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a
I'm using the previous kernel now, 4.10.0-13-generic #15-Ubuntu, and
after some hours I haven't seen the freeze. I saw it again using the
kernel reported in this bug:
linux-image-4.10.0-14-generic 4.10.0-14.16
I will run the 4.10.0-13 kernel a while longer to see if I see the
freeze again.
--
Public bug reported:
I'm getting a system freeze, consisting of all applications slowing down
and stopping to respond. This starts happening after some hours of
normal functioning of the system. A reboot recovers the system until the
next freeze. It doesn't seem that any application is exhausting
Forget about comment #25, can't access "mail.google.com" from a
particular wifi network (eduroam), maybe there is a new bug there but I
will investigate further.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Does this bug affect the access to google accounts? After updating to
zeisty, I can access "www.google.com", but "mail.googl.com", for
instance, times out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm closing this bug as it affects long out of maintanance versions of
Ubuntu and hasn't been reported on current versions
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I reflashed eventually and did not have sound, so this is clearly a
hardware problem. Since my phone was still under warranty, I sent it for
repair. So closing this bug as invalid, if anybody has a similar problem
please open a new bug with the information of his/her device.
** Changed in:
Thanks @dobey, indeed, I don't see this any more, so closing the bug.
** Changed in: hundredpapercuts
Status: Confirmed => Invalid
** Changed in: indicator-bluetooth (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
pat-mcgowan: I installed a couple of games exactly for what you way,
trying to turn the volume on and off to see if I got back the sound, but
it didn't work out.
I wait a couple of days more and reflash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks pat-mcgowan, I attach the two files. "syslog" I truncated to the
last lines. I started playing music in youtube to see if any message is
logged, before that I took a quick look and I think there were only the
usual messages related to starting device and such.
I checked and the device does
1 - 100 of 2375 matches
Mail list logo
