Submitted actual kernel bug report:
https://bugzilla.kernel.org/show_bug.cgi?id=215796
** Bug watch added: Linux Kernel Bug Tracker #215796
https://bugzilla.kernel.org/show_bug.cgi?id=215796
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Hans de Goede / @Filipe Laíns
https://lkml.iu.edu/hypermail/linux/kernel/2103.1/04435.html
Who would be the code owner here to fix the issue?
** Summary changed:
- logitech-djreceiver spams Dmesg
+ logitech-djreceiver spams Dmesg (Unexpected input report number 128)
--
You received this
For now
sudo modprobe -r hid_logitech_dj
and
/etc/modprobe.d/blacklist.conf
# Logitech HID driver sucks for G602
# https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936573/
# https://github.com/libratbag/libratbag/issues/832
blacklist hid-logitech-dj
--
You received this bug notification
I tried adding
/etc/rsyslog.d/50-default.conf
:msg, contains, "Unexpected input report number" stop
but it doesn't work :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936573
Title:
There are loads of issue reports that complain about this with Logitech
hardware.
https://linuxlists.cc/l/1/linux-
kernel/t/3934117/logitech_g602_wireless_mouse_kernel_error_messages_in_5.10.11+_kernels
^ This thread _claims_ a fix was put in but it has not been (running
5.13 kernel)
I have
Can confirm all of the above.
https://fostips.com/apt-key-deprecated-right-way-add-repository
https://www.north-47.com/knowledge-base/how-to-securely-install-apps-on-debian-based-linux-distros/
With apt-key being deprecated and a transition to more secure (better)
restriction of repository trust
See https://docs.docker.com/engine/release-notes/18.09/#deprecation-
notices (2019-09-03) deprecation notice was set.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939106
Title:
The aufs
This is not acceptable practice on an LTS distribution. I'm on Ubuntu
18.04 LTS and got hit by this breaking change from docker package
management -- please revert this package from being released to LTS
Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
"me too" - Dell Latitude w/ a Dell WD16 USB-C dock. After recent
firmware updates it got significantly worse and nearly never properly
re-attaches after suspend/resume.
Dell 5400 Latitude:
(0.1.9.1=same, 0.1.7.4=older, 0.1.6.5=older, 0.1.5.1=older, 0.1.4.2=older)
dock:
```
No upgrades for
similar issue in 18.04.4, `gnome-shell 3.28.4`
$ xrandr | grep " connected"
eDP-1 connected (normal left inverted right x axis y axis)
DP-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis)
521mm x 293mm
DP-1-2 connected primary 1920x1080+0+0 (normal left inverted right x
@chilewskirbuu that is a reasonable workaround - NOTE: it would break
dual-boot though, so WARNING: don't use that as a workaround unless you
are sure you are not using dual boot;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Agree w/ @rlaager, this SHOULD NOT be functionally impacting in any way.
The update-grub command is not actually failing, just spewing errors
during os-prober. We want to clean it up (it is cosmetic).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Summary changed:
- [zfs-root] device-mapper: reload ioctl on osprober-linux-sda5 failed: Device
or resource busy
+ [zfs-root] "device-mapper: reload ioctl on osprober-linux-sdaX failed:
Device or resource busy" against devices owned by ZFS
--
You received this bug notification because
Please also see https://github.com/zfsonlinux/zfs/issues/9801 - it has a
full set of technical details related to this topic.
** Bug watch added: Github Issue Tracker for ZFS #9801
https://github.com/zfsonlinux/zfs/issues/9801
--
You received this bug notification because you are a member of
@rlaager ref for "long time ago"? (Looking for release notes and
specific version)
I've been reasonably diligent in monitoring my pool scrub activity, I
would "guess" that maybe in the last 2-3 months I may have lost track.
But also I only upgraded from Ubuntu 16.04 LTS sometime late-2019 Fall
Public bug reported:
FULL REF: https://github.com/zfsonlinux/zfs/issues/9858 (initially
submitted there mistakenly)
==System information==
{{{
TypeVersion/Name
Distribution Name Ubuntu
Distribution Version18.04.3 LTS
Linux Kernel4.15.0-73-generic
Architecturex86_64
ZFS
Certainly, the PPA from `rolfbensch` has the fix (start at
https://gitlab.com/sane-project/backends/issues/7#note_125319290).
https://gitlab.com/sane-project/backends/-/tags/1.0.28, was released on
Jul 31 2019.
At least currently:
https://mirrors.edge.kernel.org/ubuntu/pool/main/s/sane-backends/
Found one! upstream: https://gitlab.com/sane-project/backends/issues/7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731459
Title:
genesys_gl847 scanners produce a black band in scanned images on
(Does the general debian package though care about the Ubuntu apparmor
rules?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786250
Title:
strongswan (charon) is rejected by apparmor to read
(where in Debian/upstream should I report to?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786250
Title:
strongswan (charon) is rejected by apparmor to read /proc//fd
To manage notifications
(also note, since I went mia not expecting to need to track, Christian
took over and did the cleanup - his merge is
https://code.launchpad.net/~paelzer/ubuntu/+source/strongswan/+git/strongswan/+merge/355589)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
which is the correct project to submit this bug to upstream?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731459
Title:
genesys_gl847 scanners produce a black band in scanned images on
Ubuntu
> RE -W/w in `host`
, correct -- even with timeout set, it blocks forever (I tested this several
days ago in the dup'd ticket iirc)
> RE timeout
, good thoughts all - sure let's just stick with 5 seconds then
> RE logic true/false (@Trent)
, thanks yes! that'll do it; clarified now in my mind
We should also consider:
```
# CLEAN
fermulator@fermmy:~$ host -t soa local.
Host local. not found: 3(NXDOMAIN)
fermulator@fermmy:~$ echo $?
1
# BROKEN (host hangs)
fermulator@fermmy:~$ LC_ALL=C /usr/bin/timeout 1 host -t soa local. 2>&1
fermulator@fermmy:~$ echo $?
124
# timeout
fer
PS: I've been running with a hacked /usr/lib/avahi/avahi-daemon-check-dns.sh
for a few days with this code:
```
OUT=`LC_ALL=C /usr/bin/timeout 2 host -t soa local. 2>&1`
```
, works like a charm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Are we sure timeout of 5 seconds is appropriate? (it FEELS too long)
My intuition says that if a DNS query takes longer than 1 second it took too
long ...
However (consider also the "wait" (-W) parameter for the host command itself)
```
-W wait
Timeout: Wait for up to wait
(this is currently in the "openconnect" path despite marked as "invalid"
against that package, bug was submitted originally to that project --
can we move to avahi?)
$ dpkg -S /usr/lib/avahi/avahi-daemon-check-dns.sh
avahi-daemon: /usr/lib/avahi/avahi-daemon-check-dns.sh
$ dpkg -s avahi-daemon
(btw; while we're fixing that script ... fix/change backtics to POSIX
compliant sub-shell'ing $() ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752411
Title:
bind9-host,
Notes;
when "things are working", host does either:
while on VPN:
{{{
$ LC_ALL=C host -t soa local.
Host local. not found: 3(NXDOMAIN)
$ LC_ALL=C dig -t soa local.
; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> -t soa local.
;; global options: +cmd
;; Got answer:
;; WARNING: .local is reserved for
*** This bug is a duplicate of bug 1752411 ***
https://bugs.launchpad.net/bugs/1752411
**accepting duplication**
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786261
Title:
strongswan ipsec
in resolve.conf, and this script hangs.
More :
1. fresh boot
2. script checks:
- "/usr/lib/avahi/avahi-daemon-check-dns.sh" is fine
- "host -t soa local." returns
3. activate strongswan connection = SUCCESS
{{{
fermulator@fermmy:~$ sudo /usr/lib/avahi/avahi-daemon-chec
*** This bug is a duplicate of bug 1752411 ***
https://bugs.launchpad.net/bugs/1752411
The relationship to LP #1752411 certainly feels valid.
(I think I agree to the duplication)
Check this out btw (perhaps better submitted to the other bug) -- but --
despite "host" claiming a default
*** This bug is a duplicate of bug 1752411 ***
https://bugs.launchpad.net/bugs/1752411
$ dpkg --list | grep bind9
ii bind9-host
1:9.11.3+dfsg-1ubuntu1.1 amd64DNS lookup utility
(deprecated)
ii
merge proposal:
https://code.launchpad.net/~fermulator/ubuntu/+source/strongswan/+git/strongswan/+merge/353423
** Merge proposal linked:
https://code.launchpad.net/~fermulator/ubuntu/+source/strongswan/+git/strongswan/+merge/353423
--
You received this bug notification because you
https://git.launchpad.net/~fermulator/ubuntu/+source/strongswan/commit/?h=allow_charon_apparmor_read_proc_fd_LP_%231786250=d0ec74d30d6742d34b3dc72113bbc933c608fffa
** Changed in: strongswan (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because
Patched:
$ git status
On branch allow_charon_apparmor_read_proc_fd_LP_#1786250
commit d0ec74d30d6742d34b3dc72113bbc933c608fffa (HEAD ->
allow_charon_apparmor_read_proc_fd_LP_#1786250)
Author: (SNIP)
Date: Mon Aug 20 09:40:38 2018 -0400
As per LP #1786250, user noted audit failures in
** Changed in: strongswan (Ubuntu)
Assignee: (unassigned) => fermulator (fermulator)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786250
Title:
strongswan (charon) is rejected by appar
@ehoover; great isolation! that's absolutely it
I too noticed it hangs in several other ways randomly.
One other example I had not mentioned was failing here:
{{{
Aug 20 09:02:49 fermmy charon[3698]: 14[IKE] maximum IKE_SA lifetime 56591s
Aug 20 09:02:49 fermmy charon[3698]: 14[IKE] processing
fwiw
{{{
$ dpkg --list | grep avahi-daemon
ii avahi-daemon
0.7-3.1ubuntu1 amd64Avahi mDNS/DNS-SD
daemon
$ dpkg --list | grep resolvconf
ii resolvconf
(yes, the upstream report back-refs this downstream report, myself or
someone else should do the needful communication once upstream is fixed)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786261
couldn't overwrite the existing
$ sudo dpkg -i libsane1_1.0.27-1~experimental3ubuntu2_amd64.deb
Selecting previously unselected package libsane1:amd64.
(Reading database ... 563959 files and directories currently installed.)
Preparing to unpack libsane1_1.0.27-1~experimental3ubuntu2_amd64.deb ...
(had to move the conflicting file)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731459
Title:
genesys_gl847 scanners produce a black band in scanned images on
Ubuntu 17.10+ (and 18.04 LTS)
To
how do we get this fixed upstream?
submitted: https://salsa.debian.org/debian/sane-backends/merge_requests/1
I accepted that Ubuntu 17.10 (non-LTS) had this bug, but it's still
present in 18.04 (outrageous ;o) ... can we downgrade sane-backends on
Ubuntu LTS?
--
repeating: (as per my workaround
** Summary changed:
- genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10
+ genesys_gl847 scanners produce a black band in scanned images on Ubuntu
17.10+ (and 18.04 LTS)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Did this:
```
$ grep include /etc/apparmor.d/usr.lib.ipsec.charon | grep local
include
$ cat /etc/apparmor.d/local/usr.lib.ipsec.charon
# Site-specific additions and overrides for usr.lib.ipsec.charon.
# For more details, please see /etc/apparmor.d/local/README.
#
#
Upstream report: https://wiki.strongswan.org/issues/2724
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786261
Title:
strongswan ipsec fails to finish connection (hangs after installing
DNS
** Description changed:
as a continuation of
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1786250 ...
(that bug can be focused on the apparmor profile issue in Ubuntu +
strongswan)
--
this bug report is for the stuck VPN connection issue
Used to work fine in
Public bug reported:
as a continuation of
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1786250 ...
(that bug can be focused on the apparmor profile issue in Ubuntu +
strongswan)
--
this bug report is for the stuck VPN connection issue
Used to work fine in Ubuntu 16.04 LTS, and
Submitted a "fork" bug report for the connection hang issue
(https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1786261), let
this bug report stay for the charon apparmor profile issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
repeated with more care to ensure profiles are actually unloaded
running this twice, confirms profiles are now not loaded
$ for profile in $(find . | egrep "charon|ipsec" | grep -v local); do sudo
apparmor_parser -R /etc/apparmor.d/$profile; done
apparmor_parser: Unable to remove
** Attachment added: "usr.lib.ipsec.charon"
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1786250/+attachment/5173346/+files/usr.lib.ipsec.charon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
while ipsec is still, here are the contents of the /proc//fd it's trying
to access
```
$ sudo ls -al /proc/3014/fd/
total 0
dr-x-- 2 root root 0 Aug 9 09:51 .
dr-xr-xr-x 9 root root 0 Aug 9 09:51 ..
lr-x-- 1 root root 64 Aug 9 09:51 0 -> 'pipe:[2972727]'
l-wx-- 1 root root 64 Aug
Public bug reported:
Used to work fine in Ubuntu 16.04 LTS, and Ubuntu 17.10.
ii strongswan
5.6.2-1ubuntu2 all IPsec VPN
solution metapackage
A while ago I upgrade to 18.04 LTS and had consistent issues with strongswan
ipsec connectivity VPN.
BASELINE
Also probably worth including the current ipsec.charon profile contents
(even though it's disabled now ...)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786250
Title:
strongswan (charon) is
(PS: as per typical recommendations, I have submitted a unique bug
report for my specific system https://bugs.launchpad.net/dell-
sputnik/+bug/1763968)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
fwiw, I too experience this issue on Dell LATITUDE E4310
$ cat /etc/issue
Linux Mint 18.3 Sylvia \n \l
$ uname -a
Linux fermmy-notebook 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14
17:48:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
--
since this has been closed as "invalid", is this to
o.1
$ sudo ln -s
/home/fermulator/projects/sane-backends/backend/.libs/libsane-genesys.so.1.0.25
$ sudo ln -s
/home/fermulator/projects/sane-backends/backend/.libs/libsane-genesys.so.1.0.25
libsane-genesys.so
$ sudo ln -s
/home/fermulator/projects/sane-backends/backend/.libs/libsane-genesys.so
@jbicha; how can we get this fix delivered into Ubuntu Artful stable? -
this has been fixed since Nov2017, and still yet delivered into Ubuntu
17.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(had this tab open in a really old browser session ... doing some clean
up ...)
retested on Fedora 26, it works! (bug no longer present)
{{{
$ sudo zfs list | grep music
zstorage/music 7.40G 84.9G 7.40G /zstorage/music
}}}
rhythmbox opens, music library on that pool, music plays
{{{
_bah_, on newer systems that have never versions of apt ... looks like
API was broken;
couldn't easily figure out how to achieve a "names only" search, so
hacks
{{{
$ for pkg in $(apt search "libreoffice-style-" | egrep -v "default" | grep
"style-" | awk -F/ '{print $1}'); do sudo apt install
Oh, and, we probably want to know the apt policy like you asked :)
Ran this on the original system (Ubuntu 17.10) I observed it on:
{{{
$ apt policy libreoffice-style-elementary
libreoffice-style-elementary:
Installed: (none)
Candidate: 1:6.0.0~rc3-0ubuntu0.17.10.1~lo4
Version table:
Indeed not! Co-incidentally I uncovered this and when I came back to the
report Olivier you've already guessed it.
{{{
$ apt search libreoffice-style
v libreoffice-style
-
The libreoffice package is affected in all Ubuntu distro's
However it MAY stem from the PPA https://bugs.launchpad.net/~libreoffice
** Project changed: ubuntu-mate => libreoffice (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Reporting back, not experiencing the bug anymore.
How can this be closed as "obsolete"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741511
Title:
GDM3 display manager: logon constantly trying to
** Changed in: gnome-shell (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/1714989
Title:
gnome-shell crashed with SIGSEGV in
*** This bug is a duplicate of bug 1714989 ***
https://bugs.launchpad.net/bugs/1714989
*accepted* - huh; not sure why that didn't turn up in my search results
before submitting
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Got 2x instances (1 from each unique user today)
, here's one online ubuntu-bug report:
https://errors.ubuntu.com/oops/a12896a4-fff3-11e7-b78e-fa163ef911dc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
{{{
[13704.632087] gnome-shell[9051]: segfault at 82 ip 7f3e7e900de2 sp
7fff6078c200 error 4 in libgobject-2.0.so.0.5400.1[7f3e7e8cb000+52000]
}}}
Stack trace is roughly:
* g_type_check_instance_cast() at libgobject-2.0.so.0
* st_label_set_text() at libst-1.0.so
(ran ubuntu-bug on the core file, awaiting UUID to show up in the
system, will post here once it's available)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744849
Title:
gnome-shell segfault in
over the next few days/weeks, since upgrading to Ubuntu 17.10 (gnome-
shell 3.26.2), will monitor for this issue to reproduce
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741511
Title:
GDM3
fun
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741511
Title:
GDM3 display manager: logon constantly trying to "press enter" -
unable to login using PTY
To manage notifications about this bug
since upgrading to Ubuntu 17.04, I'm unable to reproduce the crash any
longer FYI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739525
Title:
gnome-shell segfault at e8 in libgdk-3.so.0
To
Ha; selected LOCK SCREEN just now, and rolled up the GDM login, boom
reproduced.
SUSPECT:
, in order to reproduce
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739525, at the
start of ever session, I've been restarting gnome-shell through gpb with:
```
gdb --args gnome-shell
If it were a physical key stuck issue, the login screen would be
attempting login much faster (there is a key repeat frequency for held
down keys).
I did confirm by "smushing" the keys.
Also, if the user goes to a non-graphical PTY terminal, there are NO
symptoms of "stuck keys".
So it's
Public bug reported:
I've seen this on Fedora (GDM+gnome-shell) in the past (can't remember
how I fixed it, or if it just went away one day with an OS upgrade).
Recently upgraded from Ubuntu 16.04.4 to 17.04, and this issue is
present here now as well.
My setup:
* dual monitors
* multiple
Bah; after sleep + resume, my GDM login had the dreaded "constantly
trying to press enter" problem on it ... (had this in Fedora long time
ago ... can't remember how I fixed it) - anyway - had to
CTRL+ALT+BACKSPACE to kill the gnome-shell and login again ... re-
initiating gdb run
--
You
Someone suggested that -u is deprecated, which means this might be a
documentation fix ...
That said, I still don't see why a user wouldn't be allowed to upload a
bug report to an existing ticket if they own it.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Just installed libwxgtk3.0-0v5-dbg. re-running gnome-shell in gdb again
... will see ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739525
Title:
gnome-shell segfault at e8 in libgdk-3.so.0
To
now i'm getting something
{{{
$ ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
}}}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
When I run it, it opens the "report" thing, (sorry, Ubuntu 170.4 has
experienced an internal error);
same as before, I click "Continue" and it just disappears (nothing output on
the terminal either)
In analyzing the thread manually, this most recent one appears to be
irrelevant to this report
PS: Don't see the stacktrace auto-uploaded .. hmmm. (in the GUI, I saw
it; but couldn't copy it ;/)
PPS:
https://errors.ubuntu.com/user/1e1145eaed4889fbf4b9b34afdec32bef59b5445c5b86e87b5a55d713b285c7f490cd65ed98cd622a50b4e395de9a91482820e11dada93321d414a30066cc930
(do not yet see my most recent
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1739525/+attachment/5030313/+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/1739525
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1739525/+attachment/5030310/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1739525/+attachment/5030309/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
PS: the annoyance of initially running ubuntu-bug didn't tell me how to
go "-u" ...
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1740967
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739525
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1739525/+attachment/5030312/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Note that "-u" _is_ referenced in:
https://help.ubuntu.com/community/ReportingBugs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740967
Title:
-u for "existing bug report" is not in help output of
On the weekend I upgraded to Ubuntu 17.10;
Amazingly, it crashed again :)
This time, apport is working, AND I get goodies in /var/crash.
{{{
fermulator@fermmy:~$ ll /var/crash
total 120364
drwxrwsrwt 2 root whoopsie 4096 Jan 2 19:45 ./
drwxr-xr-x 17 root root 4096 Dec 29
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1739525/+attachment/5030311/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
$ ubuntu-bug --help
Usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash
file]
Options:
-h, --helpshow this help message and exit
-w, --window Click a window as a target for filing a problem
report.
Not sure what to do, apport is running for sure, but still no gnome-
shell crash files are being generated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739525
Title:
gnome-shell segfault at e8
$ ll /var/crash
total 8
drwxrwsrwt 2 root whoopsie 4096 Sep 4 12:12 ./
drwxr-xr-x 18 root root 4096 Feb 11 2017 ../
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
RE 1)
Yes I have PPAs in use: (hopefully it's not a crime ;o) - but, please do let me
know how to isolate one as providing "bad" or perhaps an "old" library?
{{{
/etc/apt/sources.list.d$ find . | egrep "list$"
./wire-desktop.list
./google-earth.list
./webupd8team-ubuntu-atom-xenial.list
apport information
** Description changed:
As requested by vanvugt in #1580605, submitting a crash unique to my
user.
This isn't fun, several times per day a crash:
{{{
$ dmesg -T | grep seg
[Thu Nov 9 09:58:27 2017] gnome-shell[17846]: segfault at e8 ip
7fd954f6d6a2 sp
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1739525/+attachment/5025852/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1739525/+attachment/5025853/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
dmesg full output from most recent crash
** Attachment added: "dmesg_full.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739525/+attachment/5025857/+files/dmesg_full.txt
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1739525/+attachment/5025854/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
here's the full "journalctl -xe" output from a most recent crash
** Attachment added: "journalctl_full.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739525/+attachment/5025856/+files/journalctl_full.txt
--
You received this bug notification because you are a member of
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1739525/+attachment/5025855/+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/1739525
1 - 100 of 242 matches
Mail list logo
