ages. File bug reports against the
relevant packages explaining what you think needs to change. Mention
the man pages in the bug title. If the bug is closed without action or
marked "won'tfix" (or ignored) then you will have reason to gripe.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
On Friday 08 December 2017 14:26:41 Jonathan Dowland wrote:
> On Fri, Dec 08, 2017 at 07:09:06PM +0100, Menelaos Maglis wrote:
> >>> > Basically, it was a completely inconsistent mess before systemd.
> >>> > Now you at least have a central place where you can configure
> >>> > your system behaviou
On Friday 08 December 2017 13:09:06 Menelaos Maglis wrote:
> >> > Basically, it was a completely inconsistent mess before systemd.
> >> > Now you at least have a central place where you can configure
> >> > your system behaviour.
> >
> > In the past, we had *no consistency*: inittab had one thing,
to...@tuxteam.de wrote:
> Now watch all the old skoolers dashing out of their little caves and
> waving their fists at something which could be read as a provocation
> (I'm myself one of those, just look a bit upthread :)
>
It is not about old or new, but about known and unknown. Unkown exposes
gt;
> It would perhaps be a good idea for the policy to be determined in an
> init-agnostic way.o
>
> > In anycase, it should be a documented configuration option to allow
> > for alternative use cases.
>
> No objection there, and I agree that the release notes should probably
> have covered the policy changes. That ship has now sailed unfortunately.
A bug report against the release notes with a patch is always worth a
try.
--
Brian.
On Fri, Dec 08, 2017 at 07:09:06PM +0100, Menelaos Maglis wrote:
> Basically, it was a completely inconsistent mess before systemd.
> Now you at least have a central place where you can configure your
> system behaviour.
In the past, we had *no consistency*: inittab had one thing, display
manage
Roberto C. Sánchez wrote:
> That is really the problem that I have with this while issue that was
> brought up. I get that it is a "sensible" default to allow users on the
> console (TTY or via DM) permission to reboot the machine. However, when
> an admin has configured the system to disallow t
>> > Basically, it was a completely inconsistent mess before systemd.
>> > Now you at least have a central place where you can configure your
>> > system behaviour.
> In the past, we had *no consistency*: inittab had one thing, display
> managers another, ACPI scripts another...if you wanted a spec
>> > Basically, it was a completely inconsistent mess before systemd.
>> > Now you at least have a central place where you can configure your
>> > system behaviour.
> In the past, we had *no consistency*: inittab had one thing, display
> managers another, ACPI scripts another...if you wanted a spec
>> Perhaps we like the old mess better than the new mess ;-)
>>
>> Please do not try to impose your opinion on others. Free software is
>> free
>> for this reason and we want to stay like this. We respect each others
>> opinion.
>
> I think you are allowing yo
On Fri, 2017-12-08 at 12:17 +0100, deloptes wrote:
> Michael Biebl wrote:
>
> > Basically, it was a completely inconsistent mess before systemd.
> > Now you at least have a central place where you can configure your
> > system behaviour.
>
> This is your opinion - if you can not understand the "m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Dec 08, 2017 at 12:17:16PM +0100, deloptes wrote:
> Michael Biebl wrote:
>
> > Basically, it was a completely inconsistent mess before systemd.
[...]
> This is your opinion - if you can not understand the "mess" it is a mess.
> For most o
On Fri, Dec 08, 2017 at 10:17:36AM +0100, Menelaos Maglis wrote:
>
> It is an improvement to have a consistent (central) way to configure
> this behavior.
>
> It is probably a "good thing" to allow users with physical access to
> reboot/shutdown a desktop/laptop system.
>
> It is probably not a
Michael Biebl wrote:
> Basically, it was a completely inconsistent mess before systemd.
> Now you at least have a central place where you can configure your
> system behaviour.
This is your opinion - if you can not understand the "mess" it is a mess.
For most of us who dislike systemd your same s
>>> I wonder how can such a severe bug make it into a Debian stable
>>> distribution? And is this just an insane default setting on Debian's
>>> side or is it yet another instance of brain-dead systemd behavior?
>>
>> Maybe I am just a brain-dead
On Thu, Dec 07, 2017 at 09:37:25AM -0500, Roberto C. Sánchez wrote:
> On Thu, Dec 07, 2017 at 03:03:44AM -0600, Dave Sherohman wrote:
> >
> > I no longer have any non-systemd machines handy to verify this on, but
> > my memory is that I have *always* been able to use halt/poweroff/reboot
> > comma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Dec 07, 2017 at 08:03:47PM +0100, Michael Biebl wrote:
[...]
> Basically, it was a completely inconsistent mess before systemd.
> Now you at least have a central place where you can configure your
> system behaviour.
Hey, I'm "before systemd
Am 07.12.2017 um 15:37 schrieb Roberto C. Sánchez:
> On Thu, Dec 07, 2017 at 03:03:44AM -0600, Dave Sherohman wrote:
>>
>> I no longer have any non-systemd machines handy to verify this on, but
>> my memory is that I have *always* been able to use halt/poweroff/reboot
>> commands from the console w
On Thu, Dec 07, 2017 at 03:03:44AM -0600, Dave Sherohman wrote:
>
> I no longer have any non-systemd machines handy to verify this on, but
> my memory is that I have *always* been able to use halt/poweroff/reboot
> commands from the console without requiring sudo or entering a password,
> and I've
On Thu, Dec 07, 2017 at 10:02:56AM +, Tixy wrote:
I'm running Jessie (with systemd running but booting with sysvinit) and
trying to execute halt/poweroff/reboot/shutdown from a terminal without
root privileges gives an error saying I must be superuser. Which has
always been my experience in 1
e, if the user is at the console or the local
terminal, implying presence is a pretty accurate guess. That's
why the default configuration comes shipped as it is. If you
are installing an ATM/voting computer/AS400, I'd hope that, as
a system integrator you *know what you are doing* and set the
On Thu, 2017-12-07 at 03:03 -0600, Dave Sherohman wrote:
>
> I no longer have any non-systemd machines handy to verify this on, but
> my memory is that I have *always* been able to use halt/poweroff/reboot
> commands from the console without requiring sudo or entering a password,
> and I've been u
On Thu, Dec 07, 2017 at 11:26:45AM +1300, Ben Caradoc-Davies wrote:
> Special privileges have been granted to console users for as long as I can
> remember, long before systemd, because they have physical access to the
> machine. Console users typically are also permitted to mount, unmount, and
> e
On Wed, 6 Dec 2017 17:35:18 -0500
Michael Stone wrote:
> On Wed, Dec 06, 2017 at 10:52:17PM +0100, Urs Thuermann wrote:
> >Yesterday, my 10 years old son logged into my laptop running Debian
> >jessie using his account, and curiously asked if he is allowed to try
> >the /sbin/reboot command. Kno
not suid root, so I assume[1] it
> communicates to systemd which then reboots the machine without
> checking what user the request comes from.
>
> I wonder how can such a severe bug make it into a Debian stable
> distribution? And is this just an insane default setting on Debian's
&g
On Wednesday, 6 Dec 2017 at 22:52, Urs Thuermann wrote:
> Yesterday, my 10 years old son logged into my laptop running Debian
> jessie using his account, and curiously asked if he is allowed to try
> the /sbin/reboot command.
Security issues etc. aside, I love the fact that your 10 year old is
as
On Wednesday, 6 Dec 2017 at 20:21, Nicholas Geovanis wrote:
> As a former system admin for a university's 370/158 (yes, in the
> Jurassic), all I can say is, wow. That really wouldn't work in an
> American university (big surprise there...). None of that stuff was
> anywhere near a normal human be
Roberto C. Sánchez wrote:
> Then I upgraded, got systemd and it turns out that
> my configuration has been silently broken for a very long time.
to prevent this, keep a list with your customizations and use it as check
list after upgrade
I also see nothing wrong when someone that could press the
On Wed, Dec 06, 2017 at 06:56:12PM -0500, Michael Stone wrote:
>
> Side note: historically, people have always wanted to be able to reboot or
> shutdown the system they were sitting in front of. This led to a lot of
> really horrible solutions, like a bunch of setuid helper programs and
> one-off
On Wed, Dec 06, 2017 at 10:48:11PM +, Brian wrote:
> On Wed 06 Dec 2017 at 22:52:17 +0100, Urs Thuermann wrote:
>
> > Yesterday, my 10 years old son logged into my laptop running Debian
> > jessie using his account, and curiously asked if he is allowed to try
> > the /sbin/reboot command. Kno
On Thu, Dec 07, 2017 at 12:18:30PM +1300, Ben Caradoc-Davies wrote:
> On 07/12/17 11:30, Roberto C. Sánchez wrote:
> > I too consider this a rather serious bug. However, I do not see any
> > evidence in the BTS [0] that such a bug has yet been reported against
> > systemd.
&
On Wed, Dec 6, 2017 at 6:49 PM, David Wright
wrote:
> On Wed 06 Dec 2017 at 15:25:10 (-0800), James H. H. Lampert wrote:
>
> > Now, now, you walk up to the physical console on an AS/400, you're
> > not going to be able to do a PWRDWNSYS from a sign-on screen, nor
> > can do it if signed on as a u
On 07-12-17, Michael Biebl wrote:
>
> As has already been mentioned, active, local users can shutdown/reboot
> the system without requiring a password. This is intended behaviour (for
> the reasons already mentioned) and can indeed be overridden by custom
> polkit rules.
>
Is there anywhere in D
On Wed 06 Dec 2017 at 15:25:10 (-0800), James H. H. Lampert wrote:
> On 12/6/17, 2:53 PM, Michael Lange wrote:
> >uh, I guess you ought to have used your time to check your machine and
> >read some docs instead of figuring out how to best insult the debian
> >developers ;)
> >(scnr)
>
> Now, now,
On Wed, Dec 06, 2017 at 03:25:10PM -0800, James H. H. Lampert wrote:
Now, now, you walk up to the physical console on an AS/400, you're not
going to be able to do a PWRDWNSYS from a sign-on screen, nor can do
it if signed on as a user who doesn't have sufficient authority to do
a PWRDWNSYS. And
On Wed 06 Dec 2017 at 22:52:17 (+0100), Urs Thuermann wrote:
> Yesterday, my 10 years old son logged into my laptop running Debian
> jessie using his account, and curiously asked if he is allowed to try
> the /sbin/reboot command. Knowing I have a Linux system as opposed to
> some crappy Win machi
ann wrote:
>
> (...)
>> I wonder how can such a severe bug make it into a Debian stable
>> distribution? And is this just an insane default setting on Debian's
>> side or is it yet another instance of brain-dead systemd behavior?
>
> Maybe I am just a brain-de
On 12/6/17, 2:53 PM, Michael Lange wrote:
uh, I guess you ought to have used your time to check your machine and
read some docs instead of figuring out how to best insult the debian
developers ;)
(scnr)
Now, now, you walk up to the physical console on an AS/400, you're not
going to be able to
On 07/12/17 11:30, Roberto C. Sánchez wrote:
I too consider this a rather serious bug. However, I do not see any
evidence in the BTS [0] that such a bug has yet been reported against
systemd.
Not a bug. We can file this one alongside "console user has access to
keyboard". Where
Hi,
uh, I guess you ought to have used your time to check your machine and
read some docs instead of figuring out how to best insult the debian
developers ;)
(scnr)
On 06 Dec 2017 22:52:17 +0100
Urs Thuermann wrote:
(...)
> I wonder how can such a severe bug make it into a Debian sta
temd: /bin/systemctl
>
> The /bin/systemctl binary is not suid root, so I assume[1] it
> communicates to systemd which then reboots the machine without
> checking what user the request comes from.
>
> I wonder how can such a severe bug make it into a Debian stable
> distribution?
On Wed, Dec 6, 2017 at 9:52 PM, Urs Thuermann wrote:
> Of course, my son doesn't have any special privileges, no entry in
> /etc/sudoers, etc. But then I see
>
> $ ls -l /sbin/reboot
> lrwxrwxrwx 1 root root 14 Apr 8 2017 /sbin/reboot -> /bin/systemctl
> $ ls -l /bin/systemctl
Sam
On Wed, Dec 06, 2017 at 10:52:17PM +0100, Urs Thuermann wrote:
Yesterday, my 10 years old son logged into my laptop running Debian
jessie using his account, and curiously asked if he is allowed to try
the /sbin/reboot command. Knowing I have a Linux system as opposed to
some crappy Win machine,
ry is not suid root, so I assume[1] it
> communicates to systemd which then reboots the machine without
> checking what user the request comes from.
>
> I wonder how can such a severe bug make it into a Debian stable
> distribution? And is this just an insane default setting on
On 07/12/17 10:52, Urs Thuermann wrote:
Yesterday, my 10 years old son logged into my laptop running Debian
jessie using his account, and curiously asked if he is allowed to try
the /sbin/reboot command. Knowing I have a Linux system as opposed to
some crappy Win machine, I replied "sure, go ahe
can such a severe bug make it into a Debian stable
distribution? And is this just an insane default setting on Debian's
side or is it yet another instance of brain-dead systemd behavior?
Searching the man pages I couldn't find a way to fix this. How can
that be stopped?
[1] Of course
gt; > Last week I made an upgrade as usual, and since reboot the battery
> > lasts half an hour to one hour tops, which led me to think that a
> > bug has been introduced in the latest updates.
> >
> > I am not sure of how to pinpoint which is the package responsible
&g
have a Lenovo T460P, and with stretch I enjoyed a reasonable battery
> life (~4 hours). At the beginning of November I switched to buster,
> and things were still OK.
>
> Last week I made an upgrade as usual, and since reboot the battery
> lasts half an hour to one hour tops, whic
oot the battery
> lasts half an hour to one hour tops, which led me to think that a bug
> has been introduced in the latest updates.
>
> I am not sure of how to pinpoint which is the package responsible for
> that, although I suspect it might be either the ACPI package or the
> ba
(~4 hours). At the beginning of November I switched to buster,
and things were still OK.
Last week I made an upgrade as usual, and since reboot the battery
lasts half an hour to one hour tops, which led me to think that a bug
has been introduced in the latest updates.
I am not sure of how to
e the fan attempts liftoff.
I could attach the output of 'reportbug kernel', but the problem is known and
the bug is described in:
https://bugzilla.kernel.org/show_bug.cgi?id=196129
The bug is present up until it's fix in kernel 4.13.4 or something around that
time. The solution
> El nov 19, 2017, a las 11:51 AM, NIkitushkin Andrey
> escribió:
>
> Hello!
> 1. I have new bug for i965/960M chipset.
> 2. I see: I see https://lists.debian.org/debian-user/2017/02/msg00800.html
> . After use new kernel 4.9 from Debian repositories my system not halt.
Hello!
1. I have new bug for i965/960M chipset.
2. I see: I see https://lists.debian.org/debian-user/2017/02/msg00800.html
. After use new kernel 4.9 from Debian repositories my system not halt. Thanks!
)))
3. Oh! After enables xtables modules for Debian Linux kernel 4.9 my system halt
again
Hello!
1. I have new bug for i965/960M chipset.
2. I see: I see https://lists.debian.org/debian-user/2017/02/msg00800.html
. After use new kernel 4.9 from Debian repositories my system not halt. Thanks!
)))
3. Oh! After enables xtables modules for Debian Linux kernel 4.9 my system halt
again
Hello!
1. I have new bug for i965/960M chipset.
2. I see: I see https://lists.debian.org/debian-user/2017/02/msg00800.html
. After use new kernel 4.9 from Debian repositories my system not halt. Thanks!
)))
3. Oh! After enables xtables modules for Debian Linux kernel 4.9 my system halt
again
Hello!
1. I have new bug for i965/960M chipset.
2. I see: I see https://lists.debian.org/debian-user/2017/02/msg00800.html
. After use new kernel 4.9 from Debian repositories my system not halt. Thanks!
)))
3. Oh! After enables xtables modules for Debian Linux kernel 4.9 my system halt
again
so online ressources.
> I don't see the network involved when you click. It could be involved
> after when you enter something in the search input but maybe there is
> some search init involving network before you enter anything.
> Moreover, if I hit super/windows/apple key it works i
cker.
I'm pretty sure the ssh connection is good. Actually there is no connection
on slave's ssh log. I think it's some bug in orted. Because when I run
orted, it shows some error message. According to the message, the
my_hnp_uri is NULL and then cause some fatal error.
Does anyone
On 2017-11-12, Laurent Lyaudet wrote:
>
> Hello,
>
> Well, find behavior and hidden files was not the intended topic of this
> thread ;)
> I do already know about Ctrl+H, ls -a, etc.
> And indeed my find command is incorrect since I forgot the dot or some
> wildcard at the beginning.
> After corre
ut it was empty.
>
> Regarding the boot errors, I have plenty of them as with any laptop I've
> seen running with Linux since laptops tend to have weird hardware.
> However, despite the same boot errors since I installed Debian on this
> laptop, the bug I'm talking in thi
to my problem.
I also looked at /var/log/gdm3/ but it was empty.
Regarding the boot errors, I have plenty of them as with any laptop I've
seen running with Linux since laptops tend to have weird hardware.
However, despite the same boot errors since I installed Debian on this
laptop, the bug I&#x
On 2017-11-12, Cindy-Sue Causey wrote:
> On 11/12/17, Laurent Lyaudet wrote:
>> deloptes wrote:
>>> I don't use Gnome, because gtk with the concept behind caused a lot of
>>> trouble long time ago and could not convince me that it will ever get
>>> better so I can't help much. But ... there shoul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Nov 12, 2017 at 12:26:40PM -0500, Cindy-Sue Causey wrote:
[...]
> Does "find" find hidden files without being specifically told how to
> do so? The other thing is that maybe you've just been phenomenally
> blessed to have no errors. That *cou
On 11/12/17, Laurent Lyaudet wrote:
> deloptes wrote:
>> I don't use Gnome, because gtk with the concept behind caused a lot of
>> trouble long time ago and could not convince me that it will ever get
>> better so I can't help much. But ... there should be logging facility and
>> you need perhaps
Laurent Lyaudet wrote:
> I think this is a very bad advice.
No it is a wise advise. When you make a change and if you want to be sure it
works - make it on a test system. Otherwise you see what happens!
> You should always be uptodate with security updates since there is
> plenty of people ready
t
2017-11-10 21:47 GMT+01:00 Laurent Lyaudet :
> Hi,
>
> Thanks for the response.
> I did not install any gnome extension or tweaking tools for gnome.
> So I'm afraid the cause is somewhere else.
> Note that if it's a malware, I'm glad you cannot reproduce the bu
Laurent Lyaudet wrote:
>> >> My install is up-to-date with latest security updates (that's the
>> >> first thing I do anytime I start my laptop).
There is a rule: "never touch a running system" which means if something
works let it work. through your process you are exposed to bugs without a
way
2017-11-09 20:03 GMT+01:00 Laurent Lyaudet :
> >On Wed, Nov 08, 2017 at 08:19:11PM +0100, Laurent Lyaudet wrote:
> >>Hello,
> >>
> >>I found a reproducible bug in latest stable Debian on my laptop.
> >>My install is up-to-date with
>On Wed, Nov 08, 2017 at 08:19:11PM +0100, Laurent Lyaudet wrote:
>>Hello,
>>
>>I found a reproducible bug in latest stable Debian on my laptop.
>>My install is up-to-date with latest security updates (that's the first
>>thing I do anytime I s
On Wed, Nov 08, 2017 at 08:19:11PM +0100, Laurent Lyaudet wrote:
>Hello,
>
>I found a reproducible bug in latest stable Debian on my laptop.
>My install is up-to-date with latest security updates (that's the first
>thing I do anytime I start my laptop).
Hello,
I found a reproducible bug in latest stable Debian on my laptop.
My install is up-to-date with latest security updates (that's the first
thing I do anytime I start my laptop).
I'm using Gnome.
Steps to reproduce on my laptop:
- activate the wifi with upper right scree
Am Thu, 26 Oct 2017 13:13:57 +0100 schrieb Darac Marjal:
> [Aside: The debian packaging tool is called "synaptic". "Synaptics" are
> a company producing touchpads. The two are not related]
I know, but I always make this mistake. ;-)
> I believe this is a known bug
notes/ch-information.en.html#apt-unpriv-acquire
>
> By the way... Why is the VirtualBox Guest Utils package not available in
> the official repositories?
>
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794466
However, there is now a backport:
https://packages.debian.org/source/stretch-backports/virtualbox
Regards,
-Roberto
--
Roberto C. Sánchez
th update and upgrade works
without errors. Trying Synaptics leads to the previous behavior. The file
trusted.gpg appears again and with this file, the error returns.
[Aside: The debian packaging tool is called "synaptic". "Synaptics" are
a company producing touchpads. The
I'm still running Debian 8 on all of my systems. Since it is time to
switch to Debian 9, I've tried to have a first look at it. So I've
installed the nonfree DVD-Image 9.2 within a VirtualBox container. All
went fine, until I've tried to update the APT database.
Both, apt and Synaptics updates
into Windows
at any point, everything works in Windows.
Bug: if I boot into Linux after being in Windows (without turning off the
computer first), the microphone will show unplugged. I can keep booting as
many times as I want, the microphone will never show as plugged until I
power the compute
On 10/20/17 12:25, Thomas Schmitt wrote:
the weekly testing ISOs for i386 and amd64 are now equipped with the
new MBR:
https://cdimage.debian.org/mirror/cdimage/weekly-builds/i386/iso-cd/debian-testing-i386-netinst.iso
...
Testers wanted for booting this ISO from USB stick.
Boots correc
Hey,
resolvconf[1] would be the package you are looking for.
Regards,
Rhys Williams
[1] https://packages.debian.org/search?keywords=resolvconf
October 21, 2017 5:30 AM, "vandman" wrote:
> Hi,
> I have a bug to report, but I can not find the package responsible for.
> W
Hi,
I have a bug to report, but I can not find the package responsible for.
When I use reportbug, It says it can not find any package and so to
contact you.
I have a server on witch I set manually all the conf in
/etc/network.interfaces.
As soon as I set up my interfaces with bridge mode and
On Tue 10 Oct 2017 at 21:45:29 (+0200), Tim wrote:
> I experience this bug in jessie as well. However, that bug got fixed in
> stretch. The bug I'm now facing is random (short) periods of a
> black/blank screen. Just as anxiousmac nicely summarized said before:
[…]
> I will t
On Tue, 2017-10-10 at 14:17 -0500, Nicholas Geovanis wrote:
> On Sat, Sep 23, 2017 at 7:48 AM, Roberto C. Sánchez
> wrote:
>
> > I had this exact same problem with Jessie on an HP ProBook 650. The bug
> > was in X.org and was fixed when I upgraded to Stretch. The problem,
On Sat, Sep 23, 2017 at 7:48 AM, Roberto C. Sánchez
wrote:
> I had this exact same problem with Jessie on an HP ProBook 650. The bug
> was in X.org and was fixed when I upgraded to Stretch. The problem, as
> I recall, was that certain display hardware inverts the sense of the
> i
On Sunday, 8 October 2017 11:10:04 UTC+1, Tim wrote:
> First of all, sorry for my late reply: It took me a while before I
> realized this is a mailing list.
[snip]
I have exactly the same problem with the same model of laptop ( HP EliteBook
840)
>From time to time the screen goes blank for 2-
ill take a few seconds before you will see the desktop.
Is the screen really black or just very dark?
Like the screen outputs pure black. I can still adjust the brightness
and this shows a ‘brighter’ or ‘less brighter’ black. It seems no bug
in the brightness settings as in the dual monitor s
he brightness
and this shows a ‘brighter’ or ‘less brighter’ black. It seems no bug
in the brightness settings as in the dual monitor setup I see that the
brightness remained the same after the laptop's screen goes dark.
> What happens if you select a VC, or exit X? … … …
Good suggestion to
Jimmy Johnson wrote:
> Hello,
> Here's an update, testing current kernels for Stretch 4.9.0-3, Buster
> 4.12.0-2 and Sid/Testing 4.13.0-1 they are all working swell, as for the
> regression, as long as I don't look there is none. As far as I'm
> concerned we can
On 02/10/2017 06:58 PM, Jimmy Johnson wrote:
On 02/10/2017 07:54 AM, debian-...@lists.debian.org wrote:
"Re: Bug#1 Freeze"
Jimmy Johnson doc
"Mine is an Intel Mobile GM965/GL960 Integrated Graphics and
it's now working swell with the Sid 4.8.0-2 kernel but not
as quick to
On Thu, 05 Oct 2017, Sergey Storm wrote:
> Hello. I have a problem with keyboard input and I don't know what
> package the bug is in. Bugreport gave me this email address for
> assistance. Help me please.
> I use two languages and switch them using ctrl+shift. But combinations
Hello. I have a problem with keyboard input and I don't know what package
the bug is in. Bugreport gave me this email address for assistance. Help me
please.
I use two languages and switch them using ctrl+shift. But combinations
ctrl+shift+'any letter' do not correctly work either
On 09/23/2017 03:01 AM, Tim wrote:
Hi,
I would like to report a bug for Debian stretch, however, I'm not sure
which package I should file the bug against. Moreover, I haven't found
a way to debug the issue either.
I've recently done a fresh installed of stretch on an HP EliteBo
On Sat 23 Sep 2017 at 10:49:44 (-0400), Cindy-Sue Causey wrote:
> On 9/23/17, Roberto C. Sánchez wrote:
> > On Sat, Sep 23, 2017 at 12:01:31PM +0200, Tim wrote:
> >> Hi,
> >>
> >> I would like to report a bug for Debian stretch, however, I'm not sure
On Sat 23 Sep 2017 at 12:01:31 (+0200), Tim wrote:
> Hi,
>
> I would like to report a bug for Debian stretch, however, I'm not sure
> which package I should file the bug against. Moreover, I haven't found
> a way to debug the issue either.
>
> I've recently
On Saturday 23 September 2017 10:49:44 Cindy-Sue Causey wrote:
> On 9/23/17, Roberto C. Sánchez wrote:
> > On Sat, Sep 23, 2017 at 12:01:31PM +0200, Tim wrote:
> >> Hi,
> >>
> >> I would like to report a bug for Debian stretch, however, I'm not
>
On 9/23/17, Roberto C. Sánchez wrote:
> On Sat, Sep 23, 2017 at 12:01:31PM +0200, Tim wrote:
>> Hi,
>>
>> I would like to report a bug for Debian stretch, however, I'm not sure
>> which package I should file the bug against. Moreover, I haven't found
>>
On Sat, Sep 23, 2017 at 12:01:31PM +0200, Tim wrote:
> Hi,
>
> I would like to report a bug for Debian stretch, however, I'm not sure
> which package I should file the bug against. Moreover, I haven't found
> a way to debug the issue either.
>
> I've recently
On 09/23/2017 05:01 AM, Tim wrote:
Hi,
I would like to report a bug for Debian stretch, however, I'm not sure
which package I should file the bug against. Moreover, I haven't found
a way to debug the issue either.
I've recently done a fresh installed of stretch on an HP EliteBo
Hi,
I would like to report a bug for Debian stretch, however, I'm not sure
which package I should file the bug against. Moreover, I haven't found
a way to debug the issue either.
I've recently done a fresh installed of stretch on an HP EliteBook 840
notebook. Since then, the
Hello Debian.org,
With Debian Buster/Sid and Gnome 3.26.0 have started to loose image icons
in file browsers. Nautilus shows some icons and some generic default icons,
all new icons are default. Dolphin shows nothing other than the type below
the icon. What do i file this bug under using Reportbug
e fix your file.
kf5.kservice.sycoca: The menu spec file contains a Layout or DefaultLayout tag
without the mandatory Merge tag inside. Please fix your file.
Is this a bug? Or do I have to do something?
Thanks for any answers.
Best
Hans
heck dmesg differences between kernel 4 and 3.
I'm no kernel expert. I'm seeking help myself, but the "Chevrolet users'
support group" doesn't seem to be much responsive these days...
'best
Ale
On Sat 09/Sep/2017 20:23:38 +0200 Ramiro Simões Lopes wrote:
>
1401 - 1500 of 5927 matches
Mail list logo
