I can confirm that this config file:
https://raw.githubusercontent.com/MidnightCommander/mc/master/misc/mc.ext.ini.in
with the suggested substitution, fixes the problem - deb open/view -
with the version of mc binary mentioned above.
--
You received this bug notification because you are a member
package content and inspected the mc.ext.ini file and it does not
contain @EXTHELPERSDIR@ string, but contains the path already:
/usr/lib/mc/ext.d/package.sh
== 0 ==> llr mc_3%3a4.8.30-1build2_amd64.deb
548K -rw-r--r-- 1 attila attila 546K ápr1 12:33
mc_3%3a4.8.30-1build2_amd64.deb
== 0 ==&g
Hi,
It is similar, but I opened only for "deb" extension (but other
extensions can also be problematic, I did not check).
The original configuration came with the package is:
```bash
[deb]
Regex=\.u?deb$
Open=%cd %p/deb://
View=%view{ascii} /usr/lib/mc/ext.d/package.sh view deb
```
According to
24.04
== 0 ==> apt-cache policy mc
mc:
Installed: 3:4.8.30-1build2
Candidate: 3:4.8.30-1build2
Thanks,
Attila
** Affects: mc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
n.firefox file as root in
order to include the local profile I have created as it was not enabled
by default in the apparmor profile file in firefox package. My
modification:
# Site-specific additions and overrides. See local/README for details.
# Attila - 20240712 - Enable with "if exi
Thanks to macg3, the workaround you suggested works for me on kernel
5.4.0-99.112. There is one correction. The name of the audio driver is
snd_usb_audio and not snd-usb-audio. So in my case after a fresh boot
the webcam did not work, and after executing:
sudo modprobe -r snd_usb_audio
sudo modpro
I use Ubuntu 20.04. Latest kernel with working webcam is still 5.4.0-91
for me. Just tried the new 5.4.0-97.110 and webcam is not working as in
all other kernel versions after 5.4.0-91.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
I confirm problem with 21.04 and 21.10
I can not get a screenshot where the pc halts.
I took a picture and attached here.
On the same computer installer starts from USB without problem.
Thanks
** Attachment added: "IMG_20211029_220959.jpg"
https://bugs.launchpad.net/ubuntu/+source/casper/+b
Public bug reported:
sent a report
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity 20.10.13
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50
Arch
As an addenda (and because the current version is still 78.*) I have to mention
the real problem with this bug.
If Thunderbird is used long enough to accumulate 1 temporary files in the
TEMP directory, so it has all the files from nsemail.eml to nsemail-.eml,
Thunderbird will suddenly st
Public bug reported:
```
GNU Image Manipulation Program version 2.10.22
git-describe: GIMP_2_10_20-217-g0c8a7891f7
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFF
UPDATE: To correct the bug description: After a reboot @ the login
screen, touchscreen works. But after entering my password and log in to
the desktop, touchscreen stops working (no matter whether it's the
'Ubuntu' or 'Ubuntu on Wayland' session).
--
You received this bug notification because you
UPDATE: I tried switching to 'Ubuntu on Wayland' but touchscreen still
does not work after login.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909944
Title:
Dell XPS 13 9333 Synaptics touch screen
Public bug reported:
I freshly installed Ubuntu 20.10 and noticed that the touch screen does
not work. Tried xinput --list and then xinput disable/enable [correct-
id] but with no avail.
However, if I close the laptop lid and open it, after the system resumes
from sleep, the touch screen starts w
: stashed password to try
later in open session
sep 16 09:09:47 weird-stuff lightdm[1193]: pam_unix(lightdm:session): session
opened for user attila by (uid=0)
sep 16 09:09:47 weird-stuff lightdm[1193]: gkr-pam: gnome-keyring-daemon
started properly and unlocked keyring
sep 16 09:20:35 weird-stuff
I have the same issue on ubuntu 20.04 with Ryzen 5 3600 + Nvidia GTX
1050ti. It freezes several times per a day. (kernel: 5.4.0-47). I tried
using lightdm instead of gdm3 but it is the same.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
.md files are text files, right? the corruption there may be non-obvious
(e.g. a couple of characters), while the programs processing mp3 or png
files can go awry even when one bit gets corrupted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
RyanNerd, this is script is a great remedy, thanks for sharing it!
I have been looking for fixing this problem for some time!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673344
Title:
Ubuntu 16.0
I had the same issue with the latest stable 64-bit kernel. However
upgrading to the latest proposed 5.4.0-1014.14 kernel
(https://launchpad.net/ubuntu/+source/linux-raspi/5.4.0-1014.14) fixed
it, and now the V3D driver works by default. I tried only with 64-bit,
on a Raspberry Pi 4 Model B Rev 1.4.
Public bug reported:
Ubuntu LTS versions affected.
"Passwordless" authentications with Yubikeys using Firefox don't work
with FIDO2.
Tested both with the yubikey software packages from the bionic/universe
repo and those from the vendor https://www.yubico.com/
** Affects: evolution (Ubuntu)
Public bug reported:
Suggesting a TPM2-Tools version 4.x compatible ACA server software
solution similar to or like: https://github.com/nsacyber/HIRS to be
included in Ubuntu LTS versions.
** Affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification b
Public bug reported:
Looking up user's public certificates in AD/LDAP fail while looking up
with regular ldapsearch works without any issues.
ldapsearch -LLL -b DC=company,DC=com -H ldap://ADDC.company.com -Q -N
'(cn=username)' userCertificate -z 10 -o ldif-wrap=no
dn: CN=username,OU=CA,OU=User,
I guess a possible workaround could be is installing it in safe graphics
mode, then blacklisting nouveau or installing the official NVIDIA
drivers. I haven't tried this yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
I tried booting in normal mode but with "nosplash debug" options, and it
froze with lots of these messages:
nouveau :01:00.0: fifo: runlist 0 update timeout
nouveau :01:00.0: tmr: stalled at
So it seems the freeze is caused by nouveau (the laptop has a NVIDIA
GeForce GTX
It also shuts down while checking the disk.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874624
Title:
Unable to boot 20.04 LTS installer on Dell XPS 15 9560
To manage notifications about this
I have the same issue on my Dell XPS 15 9560. As soon as the graphical
interface would start, the system either shuts down or freezes
completely.
However, it does work if I boot Ubuntu in "safe graphics" mode, but this
way changing the display brightness and connecting external displays
don't work
update:
after reinstalling the package, and delete the local store + cookies it started
to work
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Public bug reported:
hw: AMD 6 core FX-6100, 8GB RAM
OS: Xubuntu, 16.04LTS, 64bit
chromium bowser (80.0.3987.163-0ubuntu0.16.04.1)
apt-cache policy chromium-browser
chromium-browser:
Installed: 80.0.3987.163-0ubuntu0.16.04.1
Candidate: 80.0.3987.163-0ubuntu0.16.04.1
Version table:
*** 80.
I I did it!
1.) I opened the /etc/xdg/autostart/spice-vdagent.desktop file with "sudo
gedit".
2.) I modified the file to:
[Desktop Entry]
Name=Spice vdagent
Comment=Agent for Spice guests
Exec=/usr/bin/spice-vdagent
Terminal=false
Type=Application
Categories=
X-GNOME-Autostart-Phase=Initializat
Hi Yas and everyone on this page!
I'm totally 'rookie' in the world of Ubuntu LinuX.. I just some weeks ago
arrived from "Bill's World" :D and firstly must to say a big sorry about my
English. I have some important question about your "bug solution". Repeat: I'm
really 'rookie' so please don't l
this is super annoying! since i've installed debian 10, for me it seems
like it happens everywhere randomly, or at least in most apps/contexts
that i'm using. it happened around 5-10 times while editing this comment
in Chromium.
my key repeat rate and delay are probably not typical:
$ gsettings g
Public bug reported:
I can experience very high CPU usage by dbus-daemon and delayed opening of
programs like leafpad and vlc. CPU usage of dbus-daemon is 100% of a CPU core
for 3 to 5 minutes if I do one of the below operations:
a) launching leafpad from thunar to open a text file (double-click
Public bug reported:
New to Linux/UBUNTU but expert in Windows/programming.
Evidently my Device/Display options are very limited, when I connect a
projector the second display can use only a low resolution, much below the
projectors capability. I tried to check for the video driver and I got er
I have found that if I set the reboot once at 15 min, the server works
for 5-6 days. If the reboots are done once at 10 min, the server get
stuck in 24-48h max. Now I'm testing the reboots once at 20min, it
should take 10 days or more until is stuck.
Also, I have tried all "reboot=" grub options,
I have activated RuntimeWatchdogSec=20s and ShutdownWatchdogSec=1min in
/etc/systemd/system.conf and set the reboot, the server get stuck in
105min.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17834
The test server get stuck after ~9h, here is the debug log.
** Attachment added: "shutdown-log-process.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5241740/+files/shutdown-log-process.txt
--
You received this bug notification because you are a member of Ubu
Tested with multiple OSs, all stuck: Ubuntu 14, Fedora 29, Arch Linux
current 2019.02.01.
We received a detailed note from the next level of support with HPE and
decided to test with Ubuntu 16 (our production one) and set "ps -ef >>
/shutdown-log.txt" in to the debug.sh script. Maybe we can see so
This get stuck in max 5 hours. We'll try to install a non systemd
Ubuntu, like v14 to test it.
** Attachment added: "centos7.PNG"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5240612/+files/centos7.PNG
--
You received this bug notification because you are a memb
We installed Centos 7 and started the reboot test now. If this fail
again then is a hardware issue, if not, then it can be from Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783499
Title:
s
That was already tested and no luck.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783499
Title:
systemd: Failed to send signal
To manage notifications about this bug go to:
https://bugs.launchpad
I have disabled the acpi services (acpid.path, acpid.service,
acpid.socket and set up the reboot once at 5 min. The server get stuck
after 13h.
Something else to try?
** Attachment added: "reboot-acpi-off.zip"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/52401
After 5 hours of reboot the server is stuck. See the attached debug log
and ILO capture.
** Attachment added: "Ubuntu-18.zip"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5238635/+files/Ubuntu-18.zip
--
You received this bug notification because you are a member
We sent all the logs and captures data to HPE and they asked to update
the BIOS to the latest one. We already using the latest firmware, 4
months past the recommended firmware. Also, we have 200 servers with
Windows 10 doing same test - reboot after each test and there are no
hangs. HPE stated that
*** This bug is a duplicate of bug 1813663 ***
https://bugs.launchpad.net/bugs/1813663
Yes, the main issue is the displays turn black.
However, I think that both causes (closing the laptop lid and locking) are
equally important.
--
You received this bug notification because you are a member
Public bug reported:
I have a Dell Latitude E7470 laptop with a docking station and two
external monitors.
I made a system update yesterday (without restart), and I tried to work
today.
When the laptop lid is laid off, all displays are black and stays that
way. When it's open, it works fine. If
After 36h of rebooting, the system is stuck. Attached is the debug log.
** Attachment added: "shutdown-logsysd237.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5232412/+files/shutdown-logsysd237.txt
--
You received this bug notification because you are a mem
We will notify them if the systemd does not fix the issue. So far, after
the systemd upgrade, the server reboots fine in 24h test (reboot once at
5 min).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
reboot=pci does not help, it get stuck after 19 hours (reboot once at 5
min). Attached is the debug log. On ILO we get the same as I sent in my
first post - see capture from the arhive.
We'll update systemd to 237 and test it.
** Attachment added: "shutdown-log-reboot-pci.txt"
https://bugs.la
I did not tried reboot=pci, will try now. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783499
Title:
systemd: Failed to send signal
To manage notifications about this bug go to:
https://b
Here at Mozilla, we have 200 servers running on HP Moonshot system, all
have same hardware configuration and Ubuntu 16.04.2. The OS is not up to
date, we use it as is was released. We using a program to tests Firefox
source code and after each test we reboot the servers using
/sbin/reboot. After a
Public bug reported:
during an isnstall, grub2 faild
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
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CasperVersion: 1.394
** Changed in: normalize-audio (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041819
Title:
K3B doesn't recognize normalize-audio is installed
To manage
I tested this today against K3b 2.0.3 and normalize-audio 0.7.7 and now
it seems 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/1041819
Title:
K3B doesn't recognize normalize-audio is instal
** Description changed:
The 'fits.jar' archive that is built for Debian (ver. 1.15.2-1) from
source has a problem locating the version information resource in the
- JAR, causing Fits.version() calls to throw unexpected
+ JAR, crashing on Fits.version() calls with an unexpected
NullPointerExc
** Description changed:
-
- The 'fits.jar' archive that is built for Debian (ver. 1.15.2-1) from source
has a problem locating the version information resource in the JAR, causing
Fits.version() calls to throw unexpected NullPointerException, and likely
breaking any code that tries to call Fit
Public bug reported:
The 'fits.jar' archive that is built for Debian (ver. 1.15.2-1) from source has
a problem locating the version information resource in the JAR, causing
Fits.version() calls to throw unexpected NullPointerException, and likely
breaking any code that tries to call Fits.versi
Downgrading the kernel is sufficient too, aka if you boot with kernel
version 4.13.0 through GRUB, and then remove everything related to
4.15.0, the driver will work fine.
There was a 340 issue with the 4.13 kernel update too back in January,
and it was fixed in a couple of days
(https://bugs.laun
When I reboot, the issue is the same as on the previous occasion - Only
a black screen shows up with a blinking cursor, no login screen.
Solution posted in the linked issue works for this issue too - Choose
Advanced Options in GRUB and boot with an older kernel version
(4.13.0-45 for me). I proceed
Same error, happened to me while updating software, which included the
kernel update 4.15.0-24. I had (and have till I reboot) version
4.13.0-45.
I had a similar issue a while ago, also related to updating the kernel,
which rendered the Nvidia driver unusable for a few days until the
driver was up
*** This bug is a duplicate of bug 1769819 ***
https://bugs.launchpad.net/bugs/1769819
The same happens to me too. Uploaded a crash report:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1775222
--
You received this bug notification because you are a member of Ubuntu
Mate edition 64 bit system I using too with Liblouis 3.5.0
version and Orca master branch development version without any problem, enabled
contracted braille setting and hungarian grade 2 Braille.
Attila
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
.
Actual result:
Screen reader entire unusable.
I tested this issue with Ubuntu 18.04 Mate edition beta release I386
architecture version in a KVM virtual machine.
Attila
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: orca 3.27.91-1ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic
I installed version 0.49 from Debian. I had to purge version 0.47 (from
Ubuntu) first. That way I could update the index. So the following steps
worked for me: purge the Ubuntu package, then install the Debian
version.
The answer of knarf on ubuntuforums.org says:
"The xapian index is used for the
I haven't tried the Debian version yet. I don't know how to do that but
I will try and search for a guide.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543899
Title:
update-apt-xapian-index crashe
UPDATES that could have caused the work-space switcher to malfunction:
Start-Date: 2018-02-01 00:51:22
Commandline: (hidden)
Upgrade: libwebkit2gtk-4.0-37:i386 (2.18.5-0ubuntu0.16.04.1,
2.18.6-0ubuntu0.16.04.1), gir1.2-webkit2-4.0:i386 (2.18.5-0ubuntu0.16.04.1,
2.18.6-0ubuntu0.16.04.1), libjava
RE: 64-bit version OS
Hi christopher,
So, you're recommending that I abandon this bug report? Meaning that
there is no hope of being fixed? :)
I will consider shifting to 64-bit, I did in the past, only that some
thoughts are still holding me back.
Many thanks!
--
You received this bug notifi
Hi again, Christopher,
Thanks for the tip! /var/log/apt is only listing some updates from the
2nd February, so that is now too helpful.
I however found my way around in Ubuntu Software Center and was able to
locate the updates by date, however, I can't exactly recall which day it
was that ruined
RE: http://cdimage.ubuntu.com/daily-live/current/
I am currently using a 32 bit version still (because of an older version
of truecrypt).
Do you, Christopher, think that if I set up bionic-desktop-amd64.iso on
a usb stick and boot to try out Ubuntu, I will be able to test the
desktop work-space s
Hi Christopher, I would like, however I can not remember, sorry. If I am
not mistaking, there was an update (the update window popped up) with
only a few KB in size... the usual "Ubuntu base" ?
If there is any way of me figuring out how o answer your question,
please let me know and I will do my b
Every time I turn my machine on, I get 2 or 3 dialogue windows saying "System
program problem detected."
This is a bit annoying. Can anyone help me resolve this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
I forgot to mention that if I am on a workspace and I click the browser
on my launchpad (the browser is already open on another workspace) then
actually nothing happens now...I used to be sent to the workspace the
browser is open, however NOW... nothing... I have to manually switch to
the workspace
I Created this new report because 787055 is not solved and the bug
appears to be exist.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746513
Title:
lot of rx-dropped packets on bridge interface
To
Public bug reported:
we see a lot of dropped rx packets on almost all bridge interface.
Related physical interfaces has much less dropped rx packets.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-112-generic 4.4.0-112.135
ProcVersionSignature: Ubuntu 4.4.0-112.135-generi
False alarm, I messed up... Sorry guys!
** Changed in: postgresql-9.5 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744035
Title:
Failed to start PostgreSQL
Public bug reported:
OS Release:
taiga@16sv:~$ sudo lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename: xenial
Postgre version:
taiga@16sv:~$ sudo apt-cache policy postgresql
postgresql:
Installed: 9.5+173
yes, it's not a bug, but a serious security issue.
thanks for fixing it finally!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/589722
Title:
when paused it should not inhibit the screensaver
To ma
root@HPp:/home/ata# update-apt-xapian-index -vf
Reading plugin /usr/share/apt-xapian-index/plugins/aliases.py.
Reading plugin /usr/share/apt-xapian-index/plugins/app-install.py.
Reading plugin /usr/share/apt-xapian-index/plugins/apttags.py.
Reading plugin /usr/share/apt-xapian-index/plugins/catalog
The workaround of Ulli Horlacher (framstag) doesn't work for me.
root@HPp:/home/ata# locale
LANG=hu_HU.UTF-8
LANGUAGE=hu:en
LC_CTYPE="hu_HU.UTF-8"
LC_NUMERIC=hu_HU.UTF-8
LC_TIME=hu_HU.UTF-8
LC_COLLATE="hu_HU.UTF-8"
LC_MONETARY=hu_HU.UTF-8
LC_MESSAGES="hu_HU.UTF-8"
LC_PAPER=hu_HU.UTF-8
LC_NAME=hu_H
I still have this problem with Ubuntu 16.04.3 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543899
Title:
update-apt-xapian-index crashed with UnicodeDecodeError in record():
'utf-8' codec c
Unfortunatelly latest Ubuntu Mate development release affected too this issue
related.
I now installed with Ubuntu Mate Bionic code named development release my KVM
virtual machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
No, just opening it from (gnome) dash. Actually it crashed only once (at
the very first time), last couple of opens were hassle-free.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726286
Title:
gno
** 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/1720620
Title:
o2 micro sd card reader unrecognised lenovo y520
To manage notifica
Regards
Attila Kovacs
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: cardreader lenovo o2 sd y520
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720620
Title
Public bug reported:
Applicatin crashes on login
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shared-mime-info 1.5-2ubuntu0.1
Uname: Linux 4.13.4-041304-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Sep 27 09:34:46 2017
ErrorMessage: telepítve post-i
** Attachment added: "/var/log/plymouth-debug.log"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1542000/+attachment/4889848/+files/plymouth-debug.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Attachment added: "/var/log/boot.log"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1542000/+attachment/4889846/+files/boot.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1542000
T
I am having this system crash again, so I enabled debugging (see
https://wiki.ubuntu.com/Plymouth#Debugging for details).
I will attach the following log files:
/var/log/plymouth-debug.log
/var/log/boot.log
ata@HPp:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description
Public bug reported:
Gulietta
** Affects: debian-installer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687831
Title:
kutyád neve
To man
menu system, independent you have the panel, or any
Mate application.
Actual result:
If I press the SUPER+S keystroke, nothing happening.
Attila
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: mate-indicator-applet 1.18.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10
Same bug in 16.04.2 as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671464
Title:
package desktop-file-utils 0.22-1ubuntu5.1 failed to install/upgrade:
end of file on stdin at conffile pro
Public bug reported:
The bug appeared while installing the bootloader. The crash report said
that the bootloader could not be installed to the desired destination
(sdac, the system drive).
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.3 [modified:
lib/partman/automatical
I am still getting this bug just after logging in to Xubuntu. My packages are
up-to-date.
$ uname -a
Linux HPp 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
I got this bug again.
Ubuntu 16.04.1 LTS
$ uname -a
Linux HPp 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
It happens right after login.
$ uname -a
Linux HPp 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1542000
Ti
Public bug reported:
ubiquity crashed instead for finishing the installation.
it already was inte main installation and I'd expect only to ask to removing
the livecd image but it crashed instead.
After the crash one can repeat the installtion but it crashes again.
br,
/istvan
ProblemType: Bug
I still have this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1542000
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug go to:
https
Update:
I noticed that after the system hangs (e.g. plugging in a HDMI device
while on battery), upon subsequent restarts the system fails to resume
on battery, no matter what kernel I load.
Once I fully shutdown and cold start, resume starts to work.
As if it has to do with some internal state l
Hi again,
Not sure how related, but when I plug in a HDMI device the system hangs
if and only if I'm on battery.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638131
Title:
Resume fails while on b
Hi Joseph,
Thanks for writing back.
I did try with switching between upstream 4.8.0 and 4.8.6 and back, neither
fixed it.
However once I booted into my old 3.19 kernel the symptom went away.I may also
add that the laptop had been shut down beforehand for a good number of hours
(not plugged in).
Public bug reported:
Symptoms
Suspend seems to work.
Resume only works while not on battery.
This used to work before some recent kernel update.
However trying some of the older kernels now does not fix the problem: the
symptoms are the same.
ProblemType: Bug
DistroRelease: Ubuntu 16.0
1 - 100 of 1337 matches
Mail list logo
