Thanks for helping me - yes, that clarifies it.
Maybe exactly the sentence you write here to explain it to me would be
good to have in the --help and man page?
Closer to the root, to me, these things that are referred to as
"symptom" are more an "area of occurence" where the symptoms appear. For
Public bug reported:
After the update to mantis, I have a problem with (at least - i have not
yet researched further issues) Web-Midi applications running in the
browser.
Up to Kernel 6.2 it works just fine (also when downgrading the kernel to
6.2 in mantis)to use https://app.electra.one/
Also, i tried to report this via ubuntu-bug / apport-bug - but this was
impossible, because for me as a user it is impossible to find out, which
package name or PID I must give apport for the app that identifies as
"Ubuntu Software" in the Dock, because there is nothing called "ubuntu-
software"
Public bug reported:
At every boot (maybe also every new login, haven't tried that), "Ubuntu
Software" pops up and tells me it updated an important component, and
when clicking to review for more information, it's always "UEFI dbx".
I dont think that this thing is always updated (I also didn run
Public bug reported:
the man page of ubuntu-bug/apport-bug (what is the difference? why am I
shown the manpage of apport-bug when typing man ubuntu-bug?) says
running apport-bug without arguments results in showing me a list of
symptoms.
When I try to report a bug in some general program that is
screenshot of the situation
** Attachment added: "IMG_6587.JPG"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2044124/+attachment/5721679/+files/IMG_6587.JPG
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport
Public bug reported:
ubuntu-bug --help says
$ ubuntu-bug --help
usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash
file]
which suggest I can type a symptom after "ubuntu-bug" that I want to report.
But doing something like:
$ ubuntu-bug "Ubuntu Software tells me at
Public bug reported:
When trying to report a bug on "Ubuntu Software" I try to use the "-w"
option to select the window of the application
(because I dont know the program or the package name of the application
running with the icon in the dock saying it's "Ubuntu Software", and it
seems
Public bug reported:
When trying to report a bug on "Ubuntu-Software" (thats the name I start
it from the gnome search). I want to do this by selecting the window of
the application, because the application itself does not tell me it's
name or package.
But after selecting the window I am
confirming my guess:
this error occurs when having somehow "exotic" linux-image-* package
names - even thoug dpkg-deb can build them and dpkg is installing them
without compaints, they lead to an error here.
A custom built mainline kernel without special naming can be installed
without
OK, tracking down this stacktrace I found the problem:
it appears that kerneldetection.py fails when I have a custom built mainline
package installed.
that would make this a bug in "ubuntu-drivers-common"
It appears to be irrelevant that I am *running* the standard Ubuntu
generic kernel - the
Another additional info:
I checked if I can do it on the commandline, but I get a Python
stacktrace instead:
# ubuntu-drivers list
Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 513, in
greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in
Another thing i just tried:
I thought *maybe* this problem is because I was running a custom built
mainline kernel and the drivers GUI doesnt want to change a system with
non-original Ubuntu kernel, but I just rebooted in the standard generic
kernel and the problem persists.
--
You received
ok, sorry it took some time as I was debugging another issue...
Now i would like to go back to the state where nvidia drivers are not
installed and they do not get installed as described so i can create the
debug output, but due to this bug i just reported, I cannot change this
state currently:
oh and forgot to say: actiually the same goes for all other nvidia
driver versions that are shown in the list - its about 10 of them.
Whatever i select, the apply button is inactive.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
I want to switch back from the nvidia driver to nouveau.
In the dialog the last row lets me select the Nouveau driver, but the
"apply" button is inactive and doesnt let me apply the change.
There is also no message or anything that would allow me to understand,
why this is
erties (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1973379
>
> Title:
> "additional drivers" says we are using nvidia drivers but its not
Public bug reported:
after selecting the recommended, tested nvidia driver, and restarting
the system as suggested, no nvidia modules are loaded at all, instead
just nouveau kernel modules are loaded and all the nvidia tools confirm
that no nvidia drivers are being used and running.
But starting
Further information:
It seems the behaviour described does not apply to all
applications/windows.
For example when I have "qjackctl" running, I get the changed cursor
that indicates I can chose that windows, and with this window it works
as expected.
The error message in the console appears
Public bug reported:
I want to report a Bug about the application Studio Controls.
As I did it already quite a few times, I run "ubuntu-bug -w", get a
message that I can select the window of the app I want to report a bug
about after closing this message.
I close the message with a click on the
Public bug reported:
When running "ubuntu-bug firefox", it asks me which package of firefox I
want to report the bug for and presents me a choice between the snap and
the deb version.
But the snap version is not actually installed.
I thing it was when I upgraded recently to 21.10, but I
ound it now.
Thanks :)
--
Henning Sprang
http://www.sprang.de
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1935076
Title:
ubuntu-bug sends huge amounts of internal data t
Public bug reported:
When running ubuntu-bug -w i get the dialog that tells me to select the
window to report a bug about, but after clicking this window, in the
terminal where I started ubuntu-bug -w, i only get:
(apport-gtk:26977): Gdk-CRITICAL **: 00:11:09.451:
I tested a bit more.
I tried again with ubuntu-bug -w and selected thunderbird.
Today I directly get a visible and reacting sudo dialog when reporting a
bug for thunderbird.
I am very sure that I did not get this dialog the last time, only as
described the broken unresponsive one. Because I
Yes I understood that, that's why I explained a bit about jack and that
I never saw an apport activity or the problem with the dmesg dialog
before just because of jackd.
So, I deleted the /var/crash stuff, and locked the screen and back in, as you
suggested, but no problem appeared.
I could
rt doing something about an jackd crash
recently , and this effect described here never appeared before having used
ubuntu-bug -w yesterday.
--
Henning Sprang
http://www.sprang.de
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
see screenshot - it looks like this after:
* reporting a bug with ubuntu-bug
* locking screen
* logging back in
The dialog does not react on clicks or keyboard input, all input apperas to be
going to the underlying app, firefox here.
** Attachment added: "Screenshot from 2021-07-09
Public bug reported:
I reported two bugs today, and both times, after having finished
reporting the bug, locking my screen, and logging back in, suddenly
there was a dialog asking for my sudo password so it can execute dmesg.
But I could neither hit cancel nor could I enter my password, it
as far as I can see in the bluez package source, the midi option is
enabled now, so it *could* be closed...
But even though it's on, I dont get it working, so I cannot confirm for
sure.
Expectation is: when connecting to a device, I get an alsa sequencer
client, but I dont see that happening.
29 matches
Mail list logo
