*** Bug 122179 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481835
Title:
[UPSTREAM] Unable to group raster image(s) with drawing object(s)
To
*** Bug 143417 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481835
Title:
[UPSTREAM] Unable to group raster image(s) with drawing object(s)
To
*** Bug 152672 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481835
Title:
[UPSTREAM] Unable to group raster image(s) with drawing object(s)
To
*** Bug 157855 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2036817
Title:
soffice.bin crashed with SIGSEGV in
Ben didn't provide version details in comment 55.
Jeff, thank you for the follow-up, but because this report is about the barely
visible, minuscule window issue, and because there's 60+ comments, let's see if
your issue is already better described elsewhere, or if it needs a fresh start
in a
(In reply to Heiko Tietze from comment #20)
> (In reply to Stéphane Guillou (stragu) from comment #19)
> > Heiko, are these delayed until the next opportunity, or are they just not
> > shown at all?
> Just delayed. GetInvolved will come first and Donate the next program start,
> if no other
(In reply to Heiko Tietze from comment #16)
> The patch hides the Donate and GetInvolved infobar if another one is visible.
Heiko, are these delayed until the next opportunity, or are they just not shown
at all?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
This happened on 3 different laptops at approximately the same time. All
laptops were connected to the same accesspoint SSID (WeWork). All
laptops are Lenovo L15 Gen1 AMD laptops. All run Ubuntu 20.04.4.
Packages are:
linux-image-5.14.0-1036-oem5.14.0-1036.40
Hello,
I installed the 5.11.0-27 but still no sound.
Let's says the kernel is good, are there any settings involved ? Like
kernel startup parameter or any other ones ?
Linux XPS-17-9700 5.11.0-27-generic #29~20.04.1-Ubuntu SMP Wed Aug 11 15:58:17
UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
--
Hello,
can you explain how to install this kernel 5.11.0-19 ?
thanks !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912673
Title:
sounds not working on Dell XPS 17 (9700)
To manage
This bug just affected me. Had to hand compile mod_vroot using the
proftpd 1.3.6c sources
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880683
Title:
unable to load mod_vroot.c
To manage
> Hello Stephane, maybe joining the amavisd-new user's to the clamav
group would be a simpler way around the stricter socket permissions you
are proposing?
Hi Simon,
No, as I said in comment #4, that doesn't work as amavisd-new doesn't
set supplementary IDs, just does a setuid() and set
> I suggest proposing your patch in a Debian bug to get the maintainer's
feedback on it.
I've now raised https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989549
Should we carry on discussion over there?
** Bug watch added: Debian Bug tracker #989549
>From systemd.service(5):
> Type=
> Configures the process start-up type for this service unit.
> One of simple, exec, forking, oneshot, dbus, notify or
> idle:
>
> • If set to simple (the default if ExecStart= is
> specified but neither Type= nor BusName= are),
Thanks.
I notice your first write() is on fd 3 while the 2nd is on stdout (while
for me the first 2 are on fd 3, which in my case is the LDAPS socket).
For the issue to be reproduced, we need the client to be paused after
having send the TLS "client hello".
The first time the breakpoint is hit,
lincvz:
> Thank you for the patch and your investigations. In the next few days, I
> cannot install the patched package on my production machines. I'll let you
> know when I can.
Thanks.
Can you reproduce a similar issue with the modus operandi (using gdb) I
describe above?
(Note that while
> This is a valid issue, but are we certain it's the same one? The
> reporter talked about sched_yield and their backtraces included several
> threads of back_monitor waiting on some kind of lock.
You're right. It may be a different issue (though possibly linked to the
same root cause). In my
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
To manage notifications
> It can be reproduced by running on a client:
>
> gdb --args ldapsearch -H ldaps://ldap.example.com -x
>
> Then in gdb:
>
> break write
> run
> continue
I can no longer reproduce it after I rebuild and install the libldap
package with
Yes,
https://github.com/openldap/openldap/commit/735e1ab14bb055344b4e767a216aa410aa7d1503
can't be directly applied there. There have been other changes in
between in that section including changes in API, so it would take more
effort to backport that fix.
--
You received this bug notification
cherry picking
https://github.com/openldap/openldap/commit/4c1ab16ade18a253dd81df7e6eced4d920ac6a8e
should fix this particular issue but reintroduce
https://bugs.openldap.org/show_bug.cgi?id=8650.
It may be necessary to pick
The important backtrace in there is the one from thread 11:
#0 0x7fb288428474 in read () from /lib/x86_64-linux-gnu/libpthread.so.0
No symbol table info available.
#1 0x7fb2890c4518 in ?? () from /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2
No symbol table info available.
#2
*** This bug is a duplicate of bug 1867678 ***
https://bugs.launchpad.net/bugs/1867678
Public bug reported:
During dist upgrade from ubuntu 19.10 to 20.10 (do-release-upgrade) on hyper-v:
Processing triggers for dbus (1.12.16-2ubuntu2.1) ...
Processing triggers for libgdk-pixbuf2.0-0:amd64
I can reproduce with Thunderbird 78.8.0 on Debian.
IMAP, IMAPS, SMTPS connections go via the configured SOCKS5 proxy, but
LDAPS connections are not proxied.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks @MarkusKuhn for taking care of explaining.
I understand that it is vexing when users complain about a problem
caused by a bug in a third party program.
Still, thunderbird not displaying any hint feels wrong.
I'm also aware that https://en.wikipedia.org/wiki/Robustness_principle
can
Same as Daniel here. I experienced this bug on Linux.
Can reproduce it now by displaying sample e-mail from comment 4 (
https://bugzilla.mozilla.org/show_bug.cgi?id=505024#c4 ) on 68.10.0 (64 bits).
In my case I received automatic invitation e-mails which did not have
any text, just the
I have one instance that kernel panicked when it updated to
0.11-4ubuntu2.6 using auto updates.
However I cannot confirm that I actually rebooted that instance after
installing 0.11-4ubuntu2.5
So far none of my other instances panicked.
--
You received this bug notification because you are a
Update 07 Apr 2020 :
Remmina v1.4.1 from Ubuntu 20.04 beta package still bugs at connection.
But, I have tried with Reminna Snap v1.4.1 (git 9fada695) and it works very
well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Definitive fix under review @ https://codereview.scilab.org/#/c/21179/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765503
Title:
scilab: save, open and ATOMS system is broken in Scilab 6 on
(In reply to Paul van Haren from comment #18)
> Dear Stephane,
>
> I think you're overlooking the observation by Nikolay (close to the bottom of
> comment 11):
>
> # Brief analysis
>
> I believe that root cause of the problem is change of `hid_t` da
*** Bug 16287 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765503
Title:
scilab: save, open and ATOMS system is broken in Scilab 6 on bionic,
(In reply to Paul van Haren from comment #15)
> As per the analysis of Nikolay, the impact of this bug means that ATOMS and
> many other functions are not available to Ubuntu users.
>
> I've tried installing the latest successful nightly build, but that doesn't
> work as the customization for
(In reply to Paul van Haren from comment #15)
> As per the analysis of Nikolay, the impact of this bug means that ATOMS and
> many other functions are not available to Ubuntu users.
>
> I've tried installing the latest successful nightly build, but that doesn't
> work as the customization for
Nikolay why don't you commit you patches on CR ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765503
Title:
scilab: save, open and ATOMS system is broken in Scilab 6 on bionic,
cosmic, disco
Public bug reported:
18.04 LTS still uses v1.0.46 version of pure-ftpd. This version is incompatible
with recent versions of the popular FileZilla client due to TLS 1.3 handling
issues in pure-ftpd when connection using secure FTPES.
18.04 LTS pure-ftpd is thus broken for any clients using
I have also been hit by this bug. Extremely irritating.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292041
Title:
Lockscreen doesn't turn off the screen
To manage notifications about this bug
I confirm the issue in 19.04. I just upgraded from 16.04. I used to get
in fine on eduroam not anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Title:
Problem to connect to WPA2/PEAP
See with just running ldapsearch after upgrade to 16.04:
```
# repeat 10 ldapsearch -x > /dev/null
# tail /var/log/auth.log
Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free
Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free
Apr 19 14:53:01 hostname ldapsearch:
This actually caused downtime for me today because of the apache update.
The process stops apache, tries to stop u-u then exits, leaving apache
down.
When can we expect the fix to be released for xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Major issues appearing when importing qif files have been solved recently
https://bugs.kde.org/show_bug.cgi?id=397824
https://bugs.kde.org/show_bug.cgi?id=403565
Also, a couple of major bugs, leading to crashes of the package have been
solved, incl:
https://bugs.kde.org/show_bug.cgi?id=402750
If you are finding this bug and having an issue after upgrading to 16.04
and keeping upstart, see Bug #1573982 for a fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1163406
Title:
Device-mapper
That fix breaks the upgrade (in my case from xenial to bionic) for users
that use a local mirror over HTTPS as the
_sourcesListEntryDownloadable->url_downloadable doesn't support HTTPS.
It comments out the entries and adds:
2019-02-19 15:13:51,808 DEBUG entry '# deb
Probably same as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815021
Title:
Can't read and write simultaneously from serial port
To
```
$ bash -c 'sleep 1 && : < /dev/tty & read var' < /dev/tty
bash: line 0: read: read error: 0: Resource temporarily unavailable
```
seems to be related and is possibly the same bug. See
https://unix.stackexchange.com/questions/499422/bash-how-can-i-run-
Public bug reported:
i have no detail sorry
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
AptOrdering:
Still crashes with Ubuntu 18.10 beta (12 oct 2018) // amule
1:2.3.2-3build1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711916
Title:
amule crashed with SIGSEGV in wxWindow::DoClientToScreen()
I do not know Linux kernel process, but i would like to know if and when this
fix will appear by defautl into Ubuntu doing a sudo apt upgrade ?
Thanks and sorry for such basic question.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I was just hit again with it today, with metacity 1:3.18.7-0ubuntu0.3 on
16.04.
Here is the crash dump.
** Attachment added: "_usr_bin_metacity.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+attachment/5189891/+files/_usr_bin_metacity.1000.crash
--
You
de
I had to enter the password twice.
Regards,
--
Stephane Peters.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/913323
Title:
Occasional login failure and artefacts
To manage notifications abou
** Changed in: lightdm (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/913323
Title:
Occasional login failure and artefacts
To manage notifications about this
led to terminate process
#8082: Aucun processus de ce type
upstart: Le processus indicator-messages main (8152) a été tué par le signal
TERM
upstart: Le processus indicator-application main (8151) a été tué par le signal
TERM
Regards,
--
Stephane Peters.
--
You received this bug notificat
Public bug reported:
Ubuntu 18.04 LTS / bwbar (1.2.3-3) [universe]
The official package is missing the binary ( /usr/sbin/bwbar )
# service bwbar status
...
...: Starting bandwidth bar daemon: start-stop-daemon: unable to stat
/usr/sbin/bwbar (No such file or directory)
...
# dpkg -L bwbar
/.
It would be interesting to try the linux kernel v4.15, it had solved a boot
freeze on my side.
See : https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: intel-microcode (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746200
Title:
Boot freeze due to intel-microcode
To manage
Tested again with a fresh install of Ubuntu 18.04.
Linux kernel version 4.15.0-20
The boot freeze is still here, it happens just after giving my password,
exactly when clicking on "login" (Gnome Desktop environment).
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Today, I retried "intel-microcode" on Xubuntu 18.04 fresh install and I
was able to reboot 6 times in a row without any freeze.
~$ dmesg | grep microcode
[0.00] microcode: microcode updated early to revision 0xc2, date =
2017-11-16
[0.987572] microcode: sig=0x506e3, pf=0x20,
That procedure also broke 2 things into my Xubuntu 17.10 :
- Ethernet connexion not working any-more
- The Linux kernel version "n-1" is now tagged into the "auto-removable"
category, that would leave me with only one kernel version installed (I
have uninstalled the 4.17 RC1 version).
--
You
First, I uninstalled Virtualbox.
Proprietary Nvidia drivers were never installed on my computer, there is
the "nouveau.modeset=0" parameter into Grub.
Then, I have installed :
linux-image-4.17.0-041700rc1-generic_4.17.0-041700rc1.201804152230_amd64.deb
and
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1764286/+attachment/5117766/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764286
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1764286/+attachment/5117767/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764286
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1764286/+attachment/5117768/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764286
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1764286/+attachment/5117761/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764286
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1764286/+attachment/5117760/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764286
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1764286/+attachment/5117762/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764286
apport information
** Tags added: apport-collected artful
** Description changed:
When running Ubuntu 17.10 on my laptop which has a "Nvidia Geforce GTX
950M" and a "Intel HD Graphics 530" graphic card, the boot process
freezes.
The cause is that the current Linux kernel does not
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1764286/+attachment/5117765/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1764286/+attachment/5117764/+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/1764286
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1764286/+attachment/5117763/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1764286/+attachment/5117758/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764286
Title:
Boot
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1764286/+attachment/5117759/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When running Ubuntu 17.10 on my laptop which has a "Nvidia Geforce GTX
950M" and a "Intel HD Graphics 530" graphic card, the boot process
freezes.
The cause is that the current Linux kernel does not include FOSS drivers for
"Nvidia Geforce GTX 950M".
The solution to avoid
In my case, the freeze occurs very early in the boot process.
In the case of #1759920, the freeze occurs at login.
Maybe the 2 bugs are related, but the behaviour is not the same.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- Regression in 2017-07-07 updates
+ Boot freeze due to intel-microcode
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746200
Title:
Boot freeze due to intel-microcode
To
Today, I installed manually :
sudo dpkg -i intel-microcode_3.20180312.0~ubuntu18.04.1_amd64.deb
No change, the freeze
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746200
Title:
Regression in
Today, I installed manually :
sudo dpkg -i intel-microcode_3.20180312.0~ubuntu18.04.1_amd64.deb
No change, the freeze still occurs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746200
Title:
With or without intel-microcode installed : "journalctl -b | grep ply"
gives no result.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746200
Title:
Regression in 2017-07-07 updates
To manage
Some news :
Last week I saw a "grub" package update so I reinstalled the "intel-
microcode" package, the freezing bug is still there on my configuration
but there is one difference.
With the "intel-microcode" package, at boot there is always a message
that appears during approximately 1 second :
Some news :
- Install of Debian 9.3 Stable 31 Jan 2018 (Linux kernel 4.9) : Boot always
works
- Install of Debian Testing 31 Jan 2018 (Linux kernel 4.14) : Random freeze at
boot
So considering my investigations until here, I consider that "intel-
microcode
- There is nothing about Refind into "journalctl -b".
- I am not mixing DEs, I use only Xfce.
- What does "S3 recovery" mean ? Samsung Galaxy S3 recovery ?
- The bug occurs since the first boot of that Xubuntu install (at that
time it was the 20180108 Intel CPU microcode), so I won't try to
Some tests I just did :
- "journalctl | grep refind > refind.txt" > Empty file
- Currently, I am booting like that : UEFI > Refind > Grub > Linux
kernel
- Chainloading the UEFI directly to Grub (no use of Refind) : gives the
same random bug
- Chainloading the Refind directly to Linux kernel
If I boot a “vanilla” Ubuntu live USB, Does the "last CPU firmware" will
be applied at reboot or will it disappear ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746200
Title:
Regression in
That Bug affects Xubuntu 17.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529276
Title:
Local keyboard layout is selected only after entering full system
encryption key
To manage
Thanks for the help,
I have checked the timestamps into the 3 logs : It always corresponds to the
successful boot.
"journalctl -b" gives text I can't interpret, anyway it always
corresponds to the last boot (successful).
The Bios version is the most up to date one : v301 (13 oct 2016)
The
See attached, the output of :
journalctl -b | grep ERROR > ERROR.txt
** Attachment added: "ERROR.txt"
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+attachment/5045552/+files/ERROR.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
See attached, the output of :
journalctl -b | grep intel > intel.txt
** Attachment added: "intel.txt"
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+attachment/5045553/+files/intel.txt
** Description changed:
The version
See attached, the output of :
journalctl -b | grep error > error.txt
** Attachment added: "error.txt"
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+attachment/5045551/+files/error.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
The version "3.20180108.0+really20170707ubuntu17.10.1" of the package
"intel-microcode" randomly freezes Ubuntu at boot (at a very early stage,
nothing is written on the screen).
The number of hard reset of the computer required looks random but it works at
third boot most
Public bug reported:
Sorry, in french, I have: "l'éxécution de "grub-install /dev/sdb" a échoué.
Cette erreur fatale"
I don't know what else to do...
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.3 [modified:
lib/partman/automatically_partition/question]
Used the workaround in #12, but it is still a major annoyance that
gnome-keyring-daemon does not handle this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771272
Title:
gnome-keyring doesn't
** 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/1695870
Title:
[regression] sssd won't start if autofs is not installed
To manage notifications about this bug go to:
Public bug reported:
The fix for LP# 1566508 (in Ubuntu 14.04 at least) introduces a
regression that prevents sssd from starting if the autofs package is not
installed.
The /etc/init/sssd.conf script now has:
```
start on (filesystem and net-device-up and starting autofs)
```
The "starting
The fix in 14.04 causes sssd to not start on boot when "autofs" is not
installed!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566508
Title:
autofs races with sssd on startup
To manage
Public bug reported:
after updating from ubuntu 14.04 to 16.04, my pc hang and I need to
shutdown manually.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libvirt-bin 1.3.1-1ubuntu10.10
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
Got hit by that one and lost several hours until I found the described
workaround in the duplicate issue. This is really very bad. It prevents
ethernet users from using network-manager-defined VPNs too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
account-plugin-owncloud failed to install
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: account-plugin-owncloud (not installed)
ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
Uname: Linux 4.8.0-28-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
AptOrdering:
Public bug reported:
At times (I have not found the trigger to reproduce it at will), one
terminal window out of many will refuse to receive complex input
sequences (such as the French composite accented character "ê" (which is
typed with "^ + e" on a french keyboard), or IBus/Anthy Japanese
Public bug reported:
I have noticed several issues with keyboard input processing, that can
all seemingly be tied to high CPU usage.
For context, I am using a french keyboard, and also need to type
Japanese, which has me using IBus and Anthy.
I think at some point in Ubuntu, the way input was
Public bug reported:
The very useful autosave feature that runs every five minutes locks up
the editor when it runs, and when it happens, any keystrokes typed
during the interval are lost.
Such that when typing the following (for example) :
abcdefghijklmnopqrstuvwxyz
If autosave runs during
I upgraded to older version 3.18.1-1ubuntu3, and relaunched metacity
using "metacity --replace", and now I have metacity crashes, but they
don't log me out.
Just wondering if the fact I "replaced" metacity while logged in untied
it from gnome-session.
--
You received this bug notification
Install the new kernel 4.4.8 from here
http://linuxdaddy.com/blog/install-kernel-4-4-on-ubuntu/
Solve the problem.
This is a bug into the 4.4.0 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 479 matches
Mail list logo
