On Wed, 5 Feb 2025 20:32:32 +
debian-u...@howorth.org.uk wrote:
> Indeed so, and in particular the bit in journalctl's man page where it
> says "The output is paged through less by default ..." !
>
> Piping journalctl's output through less is pointless, I think.
Unless you have --nopager set
Charles Curley wrote:
> On Wed, 5 Feb 2025 15:46:23 +0100
> Franziska Menti wrote:
>
> > Hi Charles
[snip]
> What I had in mind here is something like:
>
> dmesg | less -X
>
> then use the search function (the / key) to search for snd_hda_intel
> and (separately) snd_sof_pci_intel_mtl. Check
On Wed, 5 Feb 2025 15:46:23 +0100
Franziska Menti wrote:
> Hi Charles
>
> Thanks for the tipps where I could start looking to solve my problem.
> > You can check for what packages were upgraded about that time by
> > inspecting (as root) the term.log* files in /var/log/apt. That
> > should he
Hi Charles
Thanks for the tipps where I could start looking to solve my problem.
> You can check for what packages were upgraded about that time by
> inspecting (as root) the term.log* files in /var/log/apt. That should
> help you narrow down the suspect packages.
That is lots of lines and packa
On Fri, 2025-01-31 at 16:12 +0100, Franziska Menti wrote:
> Dear all,
>
> I would like to make a bugreport. This is my first time trying to
> file a bug report. Reportbug is asking me for the name of the package
> in which I found a problem. Since I am a novice, I don't know.
Sorry, I hit the wrong button.
On Fri, 31 Jan 2025 09:02:37 -0700
Charles Curley wrote:
> You did not mention what sort of hardware you are running. Running
> lspci as root should give us what we need. Something like:
root@peregrine:~# lspci -vs 1f.3
:00:1f.3 Audio device: Intel Corporation
On Fri, 31 Jan 2025 16:12:55 +0100
Franziska Menti wrote:
> My debian problem: My inbuilt microphone of my laptop stopped working
> since about one month. It worked smoothly for months before then. I
> believe the issue
> appeared after an update.
You can check for what packages were upgraded ab
Dear all,
I would like to make a bugreport. This is my first time trying to file a
bug
report. Reportbug is asking me for the name of the package in which I
found a
problem. Since I am a novice, I don't know. Also, I wonder if it would be
better to just post my issue in a debian forum an
On Tue, 5 Mar 2024 20:40:31 -0500
Tom wrote:
> Just reminding whomever checks this mailbox, that I am still awaiting
> an answer to this question here.
Well, I'm no expert on KDE. But if you haven't gotten any other
response, as Marco Moock suggested, I'd file it under
kinfocenter. Whoever is r
Just reminding whomever checks this mailbox, that I am still awaiting an
answer to this question here.
Thanks,
On Mon, Feb 26, 2024 at 10:49 PM Tom wrote:
> I originally filed this bug with the KDE team, but they asked me to file
> with Debian. There was a decent amount of discussion which I wi
Am Mon, 26 Feb 2024 22:49:55 -0500
schrieb Tom :
> I originally filed this bug with the KDE team, but they asked me to
> file with Debian. There was a decent amount of discussion which I
> will link here: https://bugs.kde.org/show_bug.cgi?id=481746. I need
> to know how to file this bug. Will I be
I originally filed this bug with the KDE team, but they asked me to file
with Debian. There was a decent amount of discussion which I will link
here: https://bugs.kde.org/show_bug.cgi?id=481746. I need to know how to
file this bug. Will I be filing under a package or one of the other
categories?
T
On Sat 29 Jul 2023 at 11:35:00 -0500, Will Stites wrote:
> Hi. I tried to use reportbug to um, report a bug, but I don't know what
> package is at fault.
Maybe it's a bug; maybe it's not. I have three similar thin clients (t630)
and other ones that do not give any problem.
On 29/07/2023 17:35, Will Stites wrote:
Hi. I tried to use reportbug to um, report a bug, but I don't know what
package is at fault.
Briefly, I installed Debian 12 using debian-12.0.0-amd64-netinst.iso on
a Hewlett-Packard T620 thin client. The installation went all right and
the system b
Hi. I tried to use reportbug to um, report a bug, but I don't know what
package is at fault.
Briefly, I installed Debian 12 using debian-12.0.0-amd64-netinst.iso on
a Hewlett-Packard T620 thin client. The installation went all right and
the system booted into Bookworm. After doing some
another excellent example why your posts are almost always worth reading.
thank you! :)
On Thu, Jan 19, 2023 at 02:00:00PM +0100, DdB wrote:
> Am 19.01.2023 um 13:13 schrieb Greg Wooledge:
> > The fact that this *appears* to work is what causes so much confusion.
> > It will "work" some of the time, but not all of the time, and you'll
> > get different results depending on which direc
On Thu, Jan 19, 2023 at 02:00:00PM +0100, DdB wrote:
[...]
> I was really curious, how Greg would put words to this one. And i gotta
> applaud: Such unambiguous explanations, and so circumspect at the same
> time. Even understanding the basis for confusion, i could learn
> something new from this
Am 19.01.2023 um 13:13 schrieb Greg Wooledge:
> The fact that this *appears* to work is what causes so much confusion.
> It will "work" some of the time, but not all of the time, and you'll
> get different results depending on which directory you're in, on which
> computer.
>
> Bash has two other
On Thu, Jan 19, 2023 at 07:13:46AM -0500, Greg Wooledge wrote:
[...]
> So, just to add to the list of people who've already said it: always
> quote the patterns that you pass to apt list, because you want apt
> to use them directly, without your shell interfering.
And, if in doubt, just replace
On Thu, Jan 19, 2023 at 12:11:43PM +0100, Christoph Brinkhaus wrote:
> For curiosity If have done a small test as below.
> Unfortunately there are a few outputs in German. For this comparisons
> the exact meanings of the German text has no importance at all.
>
> 1. The first command of the origina
Am Thu, Jan 19, 2023 at 11:40:50AM +0100 schrieb to...@tuxteam.de:
Hello Tomas,
> On Thu, Jan 19, 2023 at 11:31:23AM +0100, Christoph Brinkhaus wrote:
> > Am Thu, Jan 19, 2023 at 09:10:30AM +0100 schrieb js-p...@online.de:
> >
> > Hello Julian,
> >
> > > Hello together,
> > > listing packages i
On Thu, Jan 19, 2023 at 11:31:23AM +0100, Christoph Brinkhaus wrote:
> Am Thu, Jan 19, 2023 at 09:10:30AM +0100 schrieb js-p...@online.de:
>
> Hello Julian,
>
> > Hello together,
> > listing packages in apt with ”sudo“ in the title returns different output
> > (bash commands at the end of the em
Am Thu, Jan 19, 2023 at 09:10:30AM +0100 schrieb js-p...@online.de:
Hello Julian,
> Hello together,
> listing packages in apt with ”sudo“ in the title returns different output
> (bash commands at the end of the email). I would fill a bug report, but I'm
> not sure whether to address it to grep
19.01.23, 09:10 +0100, js-p...@online.de:
Hello together,
listing packages in apt with ”sudo“ in the title returns different output (bash
commands at the end of the email). I would fill a bug report, but I'm not sure
whether to address it to grep or apt. How do you see this?
To me it seems t
Am 19.01.2023 um 09:10 schrieb js-p...@online.de:
> Hello together,
> listing packages in apt with ”sudo“ in the title returns different output
> (bash commands at the end of the email). I would fill a bug report, but I'm
> not sure whether to address it to grep or apt. How do you see this?
>
>
Hello together,
listing packages in apt with ”sudo“ in the title returns different output (bash
commands at the end of the email). I would fill a bug report, but I'm not sure
whether to address it to grep or apt. How do you see this?
Kind regards
Julian Schreck
--
$ apt list sudo* vs. $ apt l
On Fri 02 Sep 2022 at 01:03:21 +, jindam, vani wrote:
> hello debian users,
>
> i want to attach files when creating a new issue
> using reportbug. i could not find an option
> to use it.
I rather think adding an attachment is a function of your mail client.
I do it in m
On 02/09/2022 13:03, jindam, vani wrote:
i want to attach files when creating a new issue
using reportbug. i could not find an option
to use it.
If I recall correctly, there is an option to attach files on the very
last screen before submission. You can also reply to the submission
hello debian users,
i want to attach files when creating a new issue
using reportbug. i could not find an option
to use it.
regards,
jindam, vani
On 21/11/21 3:04 am, Lee wrote:
I wanted to create a bug report for meld but couldn't find any info on
how to other than "use reportbug" :(
I see your problem is solved, but for future reference, this page has
info on reporting bugs via email:
https://www.debian.org/Bugs/Re
On 11/20/21, Ulf Volmer wrote:
>
> On 20.11.21 15:04, Lee wrote:
>> I wanted to create a bug report for meld but couldn't find any info on
>> how to other than "use reportbug" :(
>>
>> I've got a brand new install of debian 11 & reportbug d
Hi,
> I've got a brand new install of debian 11 & reportbug dies:
It is possible to report bugs via plain mail, as described in:
https://www.debian.org/Bugs/Reporting
"Sending the bug report via e-mail"
Quick tour:
Use your intended bug title as mail "Subject
On 20.11.21 15:04, Lee wrote:
I wanted to create a bug report for meld but couldn't find any info on
how to other than "use reportbug" :(
I've got a brand new install of debian 11 & reportbug dies:
conn = self._connect_tls_proxy(hostname, conn)
File "/
I wanted to create a bug report for meld but couldn't find any info on
how to other than "use reportbug" :(
I've got a brand new install of debian 11 & reportbug dies:
...
Default preferences file written. To reconfigure, re-run reportbug
with the "--configure"
reference, the text in reportbug is:
Briefly describe the problem (max. 100 characters allowed). This
will be the bug email subject, so keep the summary as concise as
possible, for example: "fails to send email" or "does not start with
-q option specified" (e
Hi,
11 sept. 2021, 18:52 de a...@cityscape.co.uk:
> It's your submission; you can close it, In fact, any user can clos
> it.
>
By the way, how can one see that a bug is closed and not open please?
For example, I know that the bug #958402 [1] has been closed because I received
an email notifica
It doesn't state how the originator of the bug report can close it.
Send a mail to xx-d...@bugs.debian.org. Give a reason for the
closure.
Got it. Thanks for the help.
On Sat 11 Sep 2021 at 12:44:30 -0400, Steve Dondley wrote:
> On 2021-09-11 06:27 AM, Brian wrote:
> > On Fri 10 Sep 2021 at 20:22:43 -0400, Steve Dondley wrote:
> >
> > > On 2021-09-10 08:15 PM, Greg Wooledge wrote:
> > > > On Fri, Sep 10, 2021 at 08:10:41PM -0400, Steve Dondley wrote:
> > > > >
On 2021-09-11 06:27 AM, Brian wrote:
On Fri 10 Sep 2021 at 20:22:43 -0400, Steve Dondley wrote:
On 2021-09-10 08:15 PM, Greg Wooledge wrote:
> On Fri, Sep 10, 2021 at 08:10:41PM -0400, Steve Dondley wrote:
> >
> > > Can I just leave this as is? Or can/should I correct it somehow?
> >
> > Ok, wh
On Fri 10 Sep 2021 at 20:22:43 -0400, Steve Dondley wrote:
> On 2021-09-10 08:15 PM, Greg Wooledge wrote:
> > On Fri, Sep 10, 2021 at 08:10:41PM -0400, Steve Dondley wrote:
> > >
> > > > Can I just leave this as is? Or can/should I correct it somehow?
> > >
> > > Ok, while I was writing that las
On 11/09/2021 01:25, Steve Dondley wrote:
This may happen in a timely manner, or it may not. Your best bet at
this point is to wait a few days and see what happens. If nobody
fixes it up before then, you might consider replying to the bug and
supplying an actual description of the bug.
OK,
This may happen in a timely manner, or it may not. Your best bet at
this point is to wait a few days and see what happens. If nobody
fixes it up before then, you might consider replying to the bug and
supplying an actual description of the bug.
OK, sounds like a plan. I see in the link I pr
On 2021-09-10 08:15 PM, Greg Wooledge wrote:
On Fri, Sep 10, 2021 at 08:10:41PM -0400, Steve Dondley wrote:
> Can I just leave this as is? Or can/should I correct it somehow?
Ok, while I was writing that last email, I got another confirmation:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug
On Fri, Sep 10, 2021 at 08:10:41PM -0400, Steve Dondley wrote:
>
> > Can I just leave this as is? Or can/should I correct it somehow?
>
> Ok, while I was writing that last email, I got another confirmation:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994068
>
> So I'm probably good?
Can I just leave this as is? Or can/should I correct it somehow?
Ok, while I was writing that last email, I got another confirmation:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994068
So I'm probably good?
I used reportbug for the first time. The experience was a little
confusing.
It appears to have gone through because I got an confirmation email:
Email subject:
1.4.11+dfsg.1-4: Please see issue at github:
https://github.com/roundcube/roundcubemail/issues/8198
Email body
On Lu, 27 iul 20, 14:24:03, G Gosselin wrote:
> I’m new to reporting Debian bugs.
>
> Please, what package should I use in report bugs for keyboard/mouse not being
> recognized correctly during boot.
> (Logitech EX110 kb/mouse incorrectly detected as LX710)
Where do you see that?
Kind regards,
I’m new to reporting Debian bugs.
Please, what package should I use in report bugs for keyboard/mouse not being
recognized correctly during boot.
(Logitech EX110 kb/mouse incorrectly detected as LX710)
Same problem has occurred in latest releases of Kali and Raspbian.
Sent from Mail for Windows
On Vi, 28 feb 20, 04:52:24, Richard Owlett wrote:
> On 02/28/2020 02:34 AM, Andrei POPESCU wrote:
> > On Jo, 27 feb 20, 07:30:31, Richard Owlett wrote:
> > > How do I resend it now (I've never knowingly used SMPT)?
> >
> > #328531
>
> I don't see the
). Time will tell.
It's glass half-empty time again, we see :). That page recommends using
reportbug. You did use it for your report; it worked. What's the problem?
--
Brian.
report and exit)?
[Y|n|q|?]? n
Wrote bug report to /tmp/reportbug-timeshift-20200227-5343-vtejhfdd
For how long would it have been reasonable to continue retrying?
How do I resend it now (I've never knowingly used SMPT)?
#328531
I don't see the connection.
Can I send it by e-ma
again later'). Do you want to retry (or else save the report and exit)?
> > [Y|n|q|?]? n
> > Wrote bug report to /tmp/reportbug-timeshift-20200227-5343-vtejhfdd
>
> For how long would it have been reasonable to continue retrying?
> How do I resend it now (I've never
nutes and try again.
For buxtehude.debian.org it's closer to 40 minutes.
How do I resend it now (I've never knowingly used SMPT)?
Usually your MTA takes care of those details, but here a reportbug tried
a direct connection to buxtehude.debian.org ...
I don't know, honestly. Try it
nd try again.
For buxtehude.debian.org it's closer to 40 minutes.
> How do I resend it now (I've never knowingly used SMPT)?
Usually your MTA takes care of those details, but here a reportbug tried
a direct connection to buxtehude.debian.org ...
I don't know, honestly. Try it again in 40 minut
e retry.
n - No, save and exit.
q - Quit.
? - Display this help.
SMTP send failure: (421, b'buxtehude.debian.org: Too much load; please try
again later'). Do you want to retry (or else save the report and exit)?
[Y|n|q|?]? n
Wrote bug report to /tmp/reportbug-timeshift-20200227-5343-vtejhfdd
On Wed 22 May 2019 at 13:32:09 (-0400), nico.schloe...@gmail.com wrote:
> > Try avoid the GUI mode of reportbug.
>
> How do I do this? `reportbug -h` doesn't say anything about it.
Supply 'text' to -u.
$ reportbug -h | grep -i interface
-u INTERFACE, --interfac
Quoting nico.schloe...@gmail.com (2019-05-22 19:32:09)
> Thank you too for the quick reply.
>
> > Try avoid the GUI mode of reportbug.
>
> How do I do this? `reportbug -h` doesn't say anything about it.
On my Debian system `man reportbug` mentions "gtk" in rela
Okay, I couldn't figure out how to change the the order of paths in
`sys.path`, but I went ahead and removed
```
pip3 uninstall pysimplesoap
```
from `~/.local/`. I have no idea what was the difference between my
locally installed version and the system version but reportbug works
now.
T
appear
before '/home/nschloe/.local/lib/python3.7/site-packages' (resp. your
custom Python should be at the very end of sys.path). Obviously this is
the reason why reportbug tries to import some module from your custom
Python3 install which refuses to work. You should definitely fix this,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Jonas,
Thank you too for the quick reply.
> Try avoid the GUI mode of reportbug.
How do I do this? `reportbug -h` doesn't say anything about it.
> If you happen to use reportbug-ng
Nope.
> If literally "nothing happene
Hi Nico,
Quoting Nico Schlömer (2019-05-22 18:25:16)
> Phew, I find it quite difficult to report bugs in Debian.
[ meta complaints snipped ]
> When launching
> ```
> reportbug -B debian
> ```
> (running Ubuntu 19.04) and after two, three clicks I'm getting
Thanks for
Perhaps I've got an incompatible version of a dependency installed in
> > `~/.local/`?
>
> It looks like this.
>
> Here reportbug uses modules from the default system Python3:
>
> > E: You must put some 'source' URIs in your sources.list
> > Traceback (
Hi,
On Wed, 22 May 2019 18:25:16 +0200
Nico Schlömer wrote:
(...)
> Perhaps I've got an incompatible version of a dependency installed in
> `~/.local/`?
It looks like this.
Here reportbug uses modules from the default system Python3:
> E: You must put some 'source' U
Hi everyone,
Phew, I find it quite difficult to report bugs in Debian. The
recommended way [1] is to use the command line tool reportbug instead
of a logging into a bug tracker and clicking "New Issue" like
everywhere else. (I'm sure there has been plenty discussion about that
b
Thanks! Your answer get straight to the ... source of things :-)
I guess the python smptlib does the job in my case.
On 25/12/18 2:36 μ.μ., Thomas Schmitt wrote:
Hi,
aprekates wrote:
But reportbug can send emails to BTS .
How does it do that ?
In principle, i'd say by the SMTP int
Hi,
aprekates wrote:
> But reportbug can send emails to BTS .
> How does it do that ?
In principle, i'd say by the SMTP internet protocol.
man 1 reportbug talks of /usr/bin/sendmail.
I guess the logic can be inspected at
https://sources.debian.org/src/reportbug/7.5.1/reportbug/subm
I dont find any email MTA in my system , and dont
recall ever using or configuring one.
I use only thunderbird for my emails.
But reportbug can send emails to BTS .
How does it do that ?
Alexandros
Howard writes:
> The URL for the Debian Bug project apparently isn't working or has
> changed. I've found two links that are not working. The first one is
> here in ReportBug, where the blue link for "Homepage of reportbug
> project" is broken. (The yellow
On 12/6/2018 8:22 AM, Howard Johnson wrote:
> Aloha,
>
> The URL for the Debian Bug project apparently isn't working or has
> changed. I've found two links that are not working. The first one is
> here in ReportBug, where the blue link for "Homepage of reportb
Aloha,
The URL for the Debian Bug project apparently isn't working or has
changed. I've found two links that are not working. The first one is
here in ReportBug, where the blue link for "Homepage of reportbug
project" is broken. (The yellow tool tip shows the bad URL
Hi Songbird,
thanks for your help! It helped really!
Downgrading to the former version was not possible, due to the dependencies
and meanwhile missing packages in the repo.
So I decided to do the second way: Installing the libssl packages from
unstable, then editing /etc/ssl/openssl.cnf like
hans.ullr...@loop.de wrote:
> Hello list,
>
> I am runnng into a big problem since some days. It is not possible to send
> any mails using kmail (receiving is working well) and
> also reportbug is not working any more. I am using TLS.
...
hi,
likely it was libssl1.1 upg
Hello list,
I am runnng into a big problem since some days. It is not possible to send any
mails using kmail (receiving is working well) and
also reportbug is not working any more. I am using TLS.
When I want to send a mail I get this message:
error:141A318A:SSL
Hi,
Cindy-Sue Causey wrote:
> I test drove it with grub-pc the other day to
> make sure it did what I was about to tell fellow users it does. I had
> to wade thru... 550+ outstanding bugs to get to the part about...
The problem is that both GRUBs are little operating systems which are
specialized
On 2018-07-27, Thomas Schmitt wrote:
> Hi,
>
> Curt wrote:
>> report-bugged by Dan, who somehow cleverly extricated himself from the
>> Catch 22
>
> reportbug just sends a mail to sub...@bugs.debian.org.
> It can be done completely by hand. See
> https://www.de
On 7/27/18, Thomas Schmitt wrote:
> Hi,
>
> Curt wrote:
>> report-bugged by Dan, who somehow cleverly extricated himself from the
>> Catch 22
>
> reportbug just sends a mail to sub...@bugs.debian.org.
> It can be done completely by hand. See
> https://www
Hi,
Curt wrote:
> report-bugged by Dan, who somehow cleverly extricated himself from the
> Catch 22
reportbug just sends a mail to sub...@bugs.debian.org.
It can be done completely by hand. See
https://www.debian.org/Bugs/Reporting
from
"Sending the bug report via e-mail"
up
On 2018-07-27, Freek de Kruijf wrote:
> When I try to use reportbug I get the following error:
> ~# reportbug
> Traceback (most recent call last):
> File "/usr/bin/reportbug", line 44, in
> from reportbug import utils
> File "/usr/lib/python3/dist-pack
When I try to use reportbug I get the following error:
~# reportbug
Traceback (most recent call last):
File "/usr/bin/reportbug", line 44, in
from reportbug import utils
File "/usr/lib/python3/dist-packages/reportbug/utils.py", line 42, in
import apt
ImportEr
On Thu 24/May/2018 03:33:52 +0200 bw wrote:
> On Thu, 24 May 2018, Ben Caradoc-Davies wrote:
>> On 24/05/18 12:40, bw wrote:
>>> Okay, I must have something misconfigured.
Yes, ~/.reportbugrc
>>> [...]
>>> Connecting to packages.debian.org via SMTP...
>>> SMTP send failure: {'m...@packages.debia
On 24/05/18 13:33, bw wrote:
Thanks, I should have included the config, which was setup with
$ reportbug --configure
I chose novice and hit the enter key for defaults. I didn't find any
documentation to show what has changed. Do you know if debian SMTP is
now not supported on repo
On 24/05/18 12:40, bw wrote:
Okay, I must have something misconfigured. I could have sworn it worked
a few months ago.
$ reportbug -k menu
*** Welcome to reportbug. Use ? for help at prompts. ***
Note: bug reports are publicly archived (including the email address of
the submitter).
Detected
Okay, I must have something misconfigured. I could have sworn it worked
a few months ago.
$ reportbug -k menu
*** Welcome to reportbug. Use ? for help at prompts. ***
Note: bug reports are publicly archived (including the email address of
the submitter).
Detected character set: UTF-8
Please
Hi,
On Tue, 5 Dec 2017 19:20:45 +0100
Sophie Loewenthal wrote:
> Hi Michael,
>
> Thanks for the info.
>
> $ python3 -c "import locale; print(locale.nl_langinfo(locale.CODESET))"
> ANSI_X3.4-1968
>
> I’ve not set this Bizarre
>
this looks like somehow LANG is set to C (or maybe something th
Hi,
On Tue, 5 Dec 2017 11:34:57 +0100
Sophie Loewenthal wrote:
> Hi,
>
> Submitting a bug report via reportbug 7.1.7 programme produced:
>
> Traceback (most recent call last):
> File "/usr/bin/reportbug", line 2234, in
> main()
> File "
Submitted to bug tracker:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883577
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883577>
> On 5 Dec 2017, at 11:34, Sophie Loewenthal wrote:
>
> Hi,
>
> Submitting a bug report via reportbug 7.1.7 programme produced:
Hi,
Submitting a bug report via reportbug 7.1.7 programme produced:
Traceback (most recent call last):
File "/usr/bin/reportbug", line 2234, in
main()
File "/usr/bin/reportbug", line 1107, in main
return iface.user_interface()
File "/usr/bin/
Sven Joachim wrote:
> songbird wrote:
>
>> anyone else seeing this?
>>
>> $ reportbug
>> Traceback (most recent call last):
>> File "/usr/bin/reportbug", line 2234, in
>> main()
>> File "/usr/bin/reportbug", line 108
Hi,
On Wed, 15 Feb 2017 15:05:47 -0500
songbird wrote:
> anyone else seeing this?
>
> $ reportbug
> Traceback (most recent call last):
> File "/usr/bin/reportbug", line 2234, in
> main()
> File "/usr/bin/reportbug", line 1084, in main
>
On 2017-02-15 15:05 -0500, songbird wrote:
> anyone else seeing this?
>
> $ reportbug
> Traceback (most recent call last):
> File "/usr/bin/reportbug", line 2234, in
> main()
> File "/usr/bin/reportbug", line 1084, in main
> if newui.i
anyone else seeing this?
$ reportbug
Traceback (most recent call last):
File "/usr/bin/reportbug", line 2234, in
main()
File "/usr/bin/reportbug", line 1084, in main
if newui.initialize():
File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py&qu
On 01/12/2017 08:58 PM, kamaraju kusumanchi wrote:
> On Wed, Jan 11, 2017 at 11:53 PM, David Wright
> wrote:
>> On Wed 11 Jan 2017 at 22:38:48 (-0500), kamaraju kusumanchi wrote:
>>
>>> Just unalias the alias corresponding to edit (the one you set up in
>>>
On Tue, Feb 07, 2017 at 08:38:54AM +, Peter wrote:
> Hi,
>
> I've recently installed Debian Stretch RC2 Testing and was wondering if you
> could help me identify where to report bugs involving the Gnome UI?
>
> I've had a few issues, with things like being unable to resize the mouse
> setting
Hi,
I've recently installed Debian Stretch RC2 Testing and was wondering if you
could help me identify where to report bugs involving the Gnome UI?
I've had a few issues, with things like being unable to resize the mouse
settings window, using touch screen to move a window pops up the on screen
k
On 30/01/17 12:59 AM, Andreas Ronnquist wrote:
On Mon, 30 Jan 2017 00:37:42 -0500,
Frank M wrote:
Tried to file a bug today using reportbug but it crashed:
Traceback (most recent call last):
File "/usr/bin/reportbug", line 2233, in
main()
File "/usr/bin/report
On Mon, 30 Jan 2017 00:37:42 -0500,
Frank M wrote:
>Tried to file a bug today using reportbug but it crashed:
>
>
>Traceback (most recent call last):
> File "/usr/bin/reportbug", line 2233, in
> main()
> File "/usr/bin/reportbug", line 1084, in m
Tried to file a bug today using reportbug but it crashed:
Traceback (most recent call last):
File "/usr/bin/reportbug", line 2233, in
main()
File "/usr/bin/reportbug", line 1084, in main
if newui.initialize():
File "/usr/lib/python3/dist-packages/repor
On Sun, Jan 22, 2017 at 2:32 PM, Cindy-Sue Causey
wrote:
> A critical malfunction of the otherwise ever increasingly user
> friendly reportbug is a huge, nasty disruption in the forward motion
> of successful Debian maintenance and releases. The catch-22 is that
> Debian users need.
On Sun, Jan 22, 2017 at 11:47:39AM -0800, Gary Roach wrote:
> On 01/22/2017 11:32 AM, Cindy-Sue Causey wrote:
>
> Thanks for the compilation. Tho Python3.5 complaint is mine. Since reportbug
> is a python package, I will bet that python is the problem. I have filed a
> bug report b
1 - 100 of 353 matches
Mail list logo
