from:"marcel"

Let me rephrase this. This is not a bug.

This is a misconfiguration of ibus-mozc in the ubuntu distribution that
leads to inconsistencies in switching keyboard layouts when mozc is
involved, not a mozc bug.

Mozc just does what it's been told to.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958492

Title:
  Keyboard layout doesn't switch to japanese when using a Japanese
  (109-key) keyboard and the system language is english

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1958492/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958492] Re: Keyboard layout doesn't switch to japanese when using a Japanese (109-key) keyboard and the system language is english

Tutorials, Videos in youtube, blogs, everyone mentions to explictly
change input mode to "Hiragana" through the menues.

Because their layout is broken!!!

In a japanese setup the key to the left of "1" (tilde "~" in the US keyboard 
layout) IS the input mode switcher.
Since ibus-mozc is *not* properly configured to ensure that that works and 
behaves randomly depending on the currently used keyboard layout, everyone has 
to work around it with the menues. 

This is broken behaviour.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958492

Title:
  Keyboard layout doesn't switch to japanese when using a Japanese
  (109-key) keyboard and the system language is english

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1958492/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958492] Re: Keyboard layout doesn't switch to japanese when using a Japanese (109-key) keyboard and the system language is english

To test, I also added a spanish keyboard layout.

$ gsettings get org.gnome.desktop.input-sources sources
[('ibus', 'mozc-jp'), ('xkb', 'us+intl'), ('xkb', 'jp'), ('xkb', 'es')]


If I'm using the spanish layout and switch to "Japanese (Mozc)" I end up with a 
-non existent- "es (mozc)" setup.
If I'm using the us international and switch to "Japanese (Mozc)" I end up with 
a -non existent- "us+intl (mozc)" setup.
If I'm using the japanese (no mozc) layout and switch to "Japanese (Mozc)" I 
end up with the proper "Japanese (Mozc)" (by chance).


This is totally inconsistent and is not how switching keyboard layouts should 
behave, in my opinion.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958492

Title:
  Keyboard layout doesn't switch to japanese when using a Japanese
  (109-key) keyboard and the system language is english

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1958492/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958492] Re: Keyboard layout doesn't switch to japanese when using a Japanese (109-key) keyboard and the system language is english

In my opinion, this is still a bug.

For arguments' sake, let's say I also have another Japanese input source
with Japanese keyboard layout (no mozc).

ie:
$ gsettings get org.gnome.desktop.input-sources sources
[('ibus', 'mozc-jp'), ('xkb', 'us'), ('xkb', 'jp')]

Then, changing the input source to xkb jp, changes the layout. (ie:
shift-2 is properly a double quote, not like an at mark like in the us
layout, etc).

---> This is the expected behaviour of switching keyboard layouts. <---

To summarise:
If I switch to "Japanese", it switches to a japanese keyboard layout.
If I switch "Japanese (Mozc)" it just activates mozc with the us layout intl 
variant intact. Where did the "japanese" part go?

It's effectively a -non existant- "US-intl (Mozc)" keyboard layout, not
"Japanese (Mozc)" as advertised.

I don't understand the rationale behind the "Japanese" (no mozc)
keyboard layout switching to jp (ie: actually doing setxkbmap jp) but
"Japanese (Mozc)" not doing it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958492

Title:
  Keyboard layout doesn't switch to japanese when using a Japanese
  (109-key) keyboard and the system language is english

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1958492/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958492] Re: Keyboard layout doesn't switch to japanese when using a Japanese (109-key) keyboard and the system language is english

I uploaded a video demonstrating what happens

https://www.youtube.com/watch?v=W_r8nclOKCI

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958492

Title:
  Keyboard layout doesn't switch to japanese when using a Japanese
  (109-key) keyboard and the system language is english

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1958492/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958492] Re: Keyboard layout doesn't switch to japanese when using a Japanese (109-key) keyboard and the system language is english

$ gsettings get org.gnome.desktop.input-sources sources
[('ibus', 'mozc-jp'), ('xkb', 'us+intl')]

I should add that the listed input sources are the same regardless of
what I have in  at /usr/share/ibus/component/mozc.xml.

With "jp" in layout it works properly but with "default" it doesn't.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958492

Title:
  Keyboard layout doesn't switch to japanese when using a Japanese
  (109-key) keyboard and the system language is english

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1958492/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958492] Re: Keyboard layout doesn't switch to japanese when using a Japanese (109-key) keyboard and the system language is english

2022-01-21 Thread Marcel Montes

Also, for what is worth, I ran "ubuntu-bug ibus-mozc", I don't know why
the bug report got filed into this package instead.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958492

Title:
  Keyboard layout doesn't switch to japanese when using a Japanese
  (109-key) keyboard and the system language is english

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1958492/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958492] Re: Keyboard layout doesn't switch to japanese when using a Japanese (109-key) keyboard and the system language is english

2022-01-21 Thread Marcel Montes

Oh, and also please check the image I attached.

The keyboard layout program showing "?" instead of the layout name is a
clear hint that something is not right.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958492

Title:
  Keyboard layout doesn't switch to japanese when using a Japanese
  (109-key) keyboard and the system language is english

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1958492/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958492] Re: Keyboard layout doesn't switch to japanese when using a Japanese (109-key) keyboard and the system language is english

2022-01-21 Thread Marcel Montes

My bad, it's just "Japanese" (I didn't run the installation again just
to check the exact hardcoded text for the bug report).

My point was that the physical actual keyboard is a japanese one with 109 keys
(the usual in japanese keyboards).
The japanese layout has some keys that just plainly don't exist in other
layouts (全角/半角, 変換, 無変換,カタカナ・ひらがな, a \ to the left of the small right shift,
and a yen sign to the left of its small backspace).

Sorry for the confusion.

What I'm saying is that the layout in the OS doesn't change at all.
Note how I never said "I can't type in Japanese" in the bug report. I could if
I -like you said- changed input mode to Hiragana in mozc. But that's not how
you do it with a japanese keyboard.

With a japanese keyboard (and correct layout) you just press the 全角/半角
(zenkaku/hankaku) key which changes input mode between direct input and
the currently/last used kana mode (usually hiragana, but might be
katakana), no need to use menues.

Even if Input Mode was in Direct Input the layout should be in Japanese
regardless of being unable to type in japanese characters.

eg: If I press the key to the right of the P it should type @ like in
the Japanese keyboard, not a [, if I press shift-7 it should be a single
quote not an ampersand, etc.

Like I said, I don't know if it's even a mozc problem, and I fixed it by
explicitly setting the layout to "jp" in ibus/component/mozc.xml which
maybe points to ibus, rather than mozc itself.

One of the first things I said is that mozc probably wasn't the right
place for this bug report.

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958492

Title:
Keyboard layout doesn't switch to japanese when using a Japanese
(109-key) keyboard and the system language is english

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1958492/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958492] Re: Keyboard layout doesn't switch to japanese when using a Japanese (109-key) keyboard and the system language is english

2022-01-19 Thread Marcel Montes

** Description changed:

  Disclaimer:
  This is my first ever ubuntu bug report... and this isn't a mozc bug per-se, 
but more like an overall integration glitch. But this is the closest place I 
could think of.
  
- Change the but report package accordingly, please.
+ Change the bug report package accordingly, please.
  
  Steps to reproduce:
  1) Install Ubuntu 20.04.
    1.1) Select English as the system language.
    1.2) Select "Japanese 109-key" as the keyboard.
    1.3) Select "English (US, intl, dead keys)" as the keyboard layout.
  2) On the newly installed system, run "sudo apt install ibus-mozc"
  3) Add Japanese in "Region & Language" with "Japanese (Mozc)" as input source.
  
  Problem:
  super+space changes the systray icon, but the keyboard layout isn't switched.
  
  Another noticeable error is that when using "Show Keyboard Layout", the
  layout name is displayed as "?" in the window title. (see attached img)
  
  fix:
  Edit /usr/share/ibus/component/mozc.xml and change "default" 
to "jp" as stated in 
https://help.ubuntu.com/community/JapaneseInput
  
  Comments:
  I don't know what mozc "default" layout means. does it get the layout from 
/etc/default/keyboard?
  If it does, it's set to XKBLAYOUT=us and XKBVARIANT=intl (as per installation 
instructions) so no wonder mozc gets confused.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus-mozc 2.23.2815.102+dfsg-8ubuntu1 [modified: 
usr/share/ibus/component/mozc.xml]
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 20 14:50:45 2022
  InstallationDate: Installed on 2022-01-19 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: mozc
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958492

Title:
  Keyboard layout doesn't switch to japanese when using a Japanese
  (109-key) keyboard and the system language is english

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1958492/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958492] Re: Keyboard layout doesn't switch to japanese when using a Japanese (109-key) keyboard and the system language is english

2022-01-19 Thread Marcel Montes

** Description changed:

  Disclaimer:
  This is my first ever ubuntu bug report... and this isn't a mozc bug per-se, 
but more like an overall integration glitch. But this is the closest place I 
could think of.
  
  Change the but report package accordingly, please.
  
  Steps to reproduce:
  1) Install Ubuntu 20.04.
    1.1) Select English as the system language.
    1.2) Select "Japanese 109-key" as the keyboard.
    1.3) Select "English (US, intl, dead keys)" as the keyboard layout.
  2) On the newly installed system, run "sudo apt install ibus-mozc"
  3) Add Japanese in "Region & Language" with "Japanese (Mozc)" as input source.
  
  Problem:
  super+space changes the systray icon, but the keyboard layout isn't switched.
  
  Another noticeable error is that when using "Show Keyboard Layout", the
  layout name is displayed as "?" in the window title. (see attached img)
  
  fix:
  Edit /usr/share/ibus/component/mozc.xml and change "default" 
to "jp" as stated in 
https://help.ubuntu.com/community/JapaneseInput
  
  Comments:
  I don't know what mozc "default" layout means. does it get the layout from 
/etc/default/keyboard?
- If it does, it's set to XKBLAYOUT=us and XKBVARIANT=intl (as per installation 
instructons) so no wonder mozc gets confused.
+ If it does, it's set to XKBLAYOUT=us and XKBVARIANT=intl (as per installation 
instructions) so no wonder mozc gets confused.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus-mozc 2.23.2815.102+dfsg-8ubuntu1 [modified: 
usr/share/ibus/component/mozc.xml]
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 20 14:50:45 2022
  InstallationDate: Installed on 2022-01-19 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: mozc
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958492

Title:
  Keyboard layout doesn't switch to japanese when using a Japanese
  (109-key) keyboard and the system language is english

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1958492/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958492] [NEW] Keyboard layout doesn't switch to japanese when using a Japanese (109-key) keyboard and the system language is english

2022-01-19 Thread Marcel Montes

Public bug reported:

Disclaimer:
This is my first ever ubuntu bug report... and this isn't a mozc bug per-se, 
but more like an overall integration glitch. But this is the closest place I 
could think of.

Change the but report package accordingly, please.

Steps to reproduce:
1) Install Ubuntu 20.04.
  1.1) Select English as the system language.
  1.2) Select "Japanese 109-key" as the keyboard.
  1.3) Select "English (US, intl, dead keys)" as the keyboard layout.
2) On the newly installed system, run "sudo apt install ibus-mozc"
3) Add Japanese in "Region & Language" with "Japanese (Mozc)" as input source.

Problem:
super+space changes the systray icon, but the keyboard layout isn't switched.

Another noticeable error is that when using "Show Keyboard Layout", the
layout name is displayed as "?" in the window title. (see attached img)

fix:
Edit /usr/share/ibus/component/mozc.xml and change "default" 
to "jp" as stated in 
https://help.ubuntu.com/community/JapaneseInput

Comments:
I don't know what mozc "default" layout means. does it get the layout from 
/etc/default/keyboard?
If it does, it's set to XKBLAYOUT=us and XKBVARIANT=intl (as per installation 
instructions) so no wonder mozc gets confused.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ibus-mozc 2.23.2815.102+dfsg-8ubuntu1 [modified: 
usr/share/ibus/component/mozc.xml]
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 20 14:50:45 2022
InstallationDate: Installed on 2022-01-19 (0 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: mozc
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mozc (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "Show Keyboard Layout error"
   
https://bugs.launchpad.net/bugs/1958492/+attachment/746/+files/Screenshot%20from%202022-01-20%2014-12-01.png

** Description changed:

  Disclaimer:
- This is my first ever ubuntu bug report... and this isn't a mozc bug per-se, 
but more like an overall integration glitch. But this is the closest place I 
could think of. 
+ This is my first ever ubuntu bug report... and this isn't a mozc bug per-se, 
but more like an overall integration glitch. But this is the closest place I 
could think of.
  
  Change the but report package accordingly, please.
  
  Steps to reproduce:
  1) Install Ubuntu 20.04.
-   1.1) Select English as the system language.
-   1.2) Selecting "Japanese 109-key" as the keyboard.
-   1.3) Select "English (US, intl, dead keys)" as the keyboard layout.
+   1.1) Select English as the system language.
+   1.2) Select "Japanese 109-key" as the keyboard.
+   1.3) Select "English (US, intl, dead keys)" as the keyboard layout.
  2) On the newly installed system, run "sudo apt install ibus-mozc"
  3) Add Japanese in "Region & Language" with "Japanese (Mozc)" as input source.
  
- Problem: 
+ Problem:
  super+space changes the systray icon, but the keyboard layout isn't switched.
  
  Another noticeable error is that when using "Show Keyboard Layout", the
  layout name is displayed as "?" in the window title. (see attached img)
  
- fix: 
+ fix:
  Edit /usr/share/ibus/component/mozc.xml and change "default" 
to "jp" as stated in 
https://help.ubuntu.com/community/JapaneseInput
- 
  
  Comments:
  I don't know what mozc "default" layout means. does it get the layout from 
/etc/default/keyboard?
  If it does, it's set to XKBLAYOUT=us and XKBVARIANT=intl (as per installation 
instructons) so no wonder mozc gets confused.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus-mozc 2.23.2815.102+dfsg-8ubuntu1 [modified: 
usr/share/ibus/component/mozc.xml]
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 20 14:50:45 2022
  InstallationDate: Installed on 2022-01-19 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: mozc
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958492

Title:
  Keyboard layout doesn't switch to japanese when using a Japanese
  (109-key) keyboard and the system language is english

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1958492/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956252] Re: display turns suddenly off, i need to re-plug the cable

2022-01-03 Thread Marcel Franke

I also tried different versions of the graphic driver.

** Description changed:

  Hi,
  
  Randomly the display turns off and then I need to re-plug the monitor
- afterward it works again. Happens sometimes many times and others not at
- all, randomly.
- 
+ afterwards it works again. Happens sometimes many times and others times
+ not at all, randomly.
  
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  
  nvidia-graphics-drivers-495
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nvidia-driver-495 495.46-0ubuntu2
  Uname: Linux 5.15.9-051509-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  3 21:25:31 2022
  InstallationDate: Installed on 2021-12-05 (29 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: nvidia-graphics-drivers-495
  UpgradeStatus: Upgraded to jammy on 2021-12-18 (16 days ago)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956252

Title:
  display turns suddenly off, i need to re-plug the cable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-495/+bug/1956252/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956252] Re: display turns suddenly off, i need to re-plug the cable

2022-01-03 Thread Marcel Franke

Happens on 20.04, 20.10, 21.04, 21.10, and 22.10 but less often on 22.10

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956252

Title:
  display turns suddenly off, i need to re-plug the cable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-495/+bug/1956252/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956252] [NEW] display turns suddenly off, i need to re-plug the cable

2022-01-03 Thread Marcel Franke

Public bug reported:

Hi,

Randomly the display turns off and then I need to re-plug the monitor
afterwards it works again. Happens sometimes many times and others times
not at all, randomly.

Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04

nvidia-graphics-drivers-495

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-495 495.46-0ubuntu2
Uname: Linux 5.15.9-051509-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu74
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan  3 21:25:31 2022
InstallationDate: Installed on 2021-12-05 (29 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: nvidia-graphics-drivers-495
UpgradeStatus: Upgraded to jammy on 2021-12-18 (16 days ago)

** Affects: nvidia-graphics-drivers-495 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956252

Title:
  display turns suddenly off, i need to re-plug the cable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-495/+bug/1956252/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

2021-12-28 Thread Marcel Brouillet

Hello !
- Not working on UX582lr (although very similar to UX581l.
- Install seems going well. 
- « LOG=DEBUG sudo -E ./asus_touchpad.py » keeps hanging with blinking cursor 
and no output.
Very willing to help, if instructed to do any test. Thank you for writing the 
package.
Marcel.

Ubuntu Studio 21.04 up to date (Linux ux582lr 5.11.0-41-lowlatency
#45-Ubuntu SMP PREEMPT Fri Nov 5 13:55:43 UTC 2021 x86_64 x86_64 x86_64
GNU/Linux)

sudo i2cdetect -l
i2c-3   i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-10  i2c AUX B/DDI B/PHY B   I2C adapter
i2c-1   i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-8   i2c i915 gmbus dpd  I2C adapter
i2c-6   i2c i915 gmbus dpc  I2C adapter
i2c-4   i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-11  i2c AUX C/DDI C/PHY C   I2C adapter
i2c-2   i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-0   smbus   SMBus I801 adapter at efa0  SMBus adapter
i2c-9   i2c AUX A/DDI A/PHY A   I2C adapter
i2c-7   i2c i915 gmbus misc I2C adapter
i2c-5   i2c i915 gmbus dpb  I2C adapter
i2c-12  i2c AUX D/DDI D/PHY D   I2C adapter

~/asus-touchpad-numpad-driver$ sudo ./install.sh
apt is here
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
git is already the newest version (1:2.30.2-1ubuntu1).
libevdev2 is already the newest version (1.11.0+dfsg-1build1).
i2c-tools is already the newest version (4.2-1build1).
python3-libevdev is already the newest version (0.5-3).
0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
Testing interface i2c-3 : failed
Testing interface i2c-1 : failed
Testing interface i2c-4 : failed
Testing interface i2c-2 : sucess

Select models keypad layout:
1) gx701.py
2) m433ia.py
3) ux433fa.py
4) ux581l.py
5) Quit
Please enter your choice 4

What is your keyboard layout?
1) Qwerty
2) Azerty
3) Quit
Please enter your choice [1-3]: 1
Add asus touchpad service in /etc/systemd/system/
Asus touchpad service enabled
Asus touchpad service started

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810183

Title:
  numpad on touchpad doesn't work in ASUS Zenbook 14

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1519545] Re: gpsbabel has usb problems

2021-12-23 Thread Marcel Martin

Thanks so much for the provided workaround. On Ubuntu 20.04,
/etc/default/tlp no longer exists. Instead, I created a file
/etc/tlp.d/50-usb-blacklist.conf containing only this line:

USB_BLACKLIST="091e:0003"

After "systemctl restart tlp", gpsbabel worked fine with my Garmin eTrex
Vista HCx.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519545

Title:
  gpsbabel has usb problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1519545/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1806437]

2021-11-17 Thread marcel

Still there on first generation Lenovo ThinkPad T14 AMD (Ryzen 7 PRO
4750U based) running 5.14.17-301.fc35.x86_64:

Nov 16 15:16:15 fedora kernel: acpi PNP0C14:01: duplicate WMI GUID 
05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
Nov 16 15:16:15 fedora kernel: acpi PNP0C14:02: duplicate WMI GUID 
05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
Nov 16 15:16:15 fedora kernel: acpi PNP0C14:03: duplicate WMI GUID 
05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
Nov 16 15:16:15 fedora kernel: acpi PNP0C14:04: duplicate WMI GUID 
05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
Nov 16 15:16:15 fedora kernel: acpi PNP0C14:05: duplicate WMI GUID 
05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806437

Title:
  acpi PNP0C14:02: duplicate WMI GUID
  05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on
  PNP0C14:01)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1806437/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921515] Re: `SyntaxError` when byte-compiling during `do-release-upgrade` to hirsute

2021-11-16 Thread Marcel Waldvogel

For me, this happened when installing `pypy3` on hirsute.

running pypy3 rtupdate hooks for 7.3
Failed to byte-compile 
/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py:   
File "/
usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py", line 
436
def __init__(self, sourceslist=None, /, files=None):
 ^
SyntaxError: invalid syntax (expected ')')

The problem seems to be that `python3-software-properties` expects
Python>=3.8 (the `/` syntax only became available then, see
https://www.python.org/dev/peps/pep-0570/). However, pypy3 as packaged
with hirsute (7.3.5) only supports Python 3.7. Upgrading to pypy 7.3.6
(https://www.pypy.org/posts/2021/10/pypy-v736-release.html), announced
as supporting Python 3.8, probably would solve this problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921515

Title:
  `SyntaxError` when byte-compiling during `do-release-upgrade` to
  hirsute

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1921515/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1947628] Re: VXLAN support is not present in kernel - Ubuntu 21.10 on Raspberry Pi 4 (64bit)

2021-10-21 Thread Marcel Schnippe

I can confirm this bug. 
(5.13.0-1008-raspi #9-Ubuntu SMP PREEMPT Wed Sep 29 08:27:44 UTC 2021 aarch64 
aarch64 aarch64 GNU/Linux)


>modprobe vxlan
modprobe: FATAL: Module vxlan not found in directory 
/lib/modules/5.13.0-1008-raspi

>updatedb
>locate vxlan.ko
/usr/lib/modules/5.11.0-1019-raspi/kernel/drivers/net/vxlan.ko
/usr/lib/modules/5.11.0-1019-raspi/kernel/net/openvswitch/vport-vxlan.ko

the vlan module (8021q) is also missing: 
>modprobe 8021q
modprobe: FATAL: Module 8021q not found in directory 
/lib/modules/5.13.0-1008-raspi

>locate 8021q.ko
/usr/lib/modules/5.11.0-1019-raspi/kernel/net/8021q/8021q.ko
/usr/lib/modules/5.11.0-1019-raspi/kernel/net/dsa/tag_8021q.ko


** Changed in: linux-raspi (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/1947628

Title:
  VXLAN support is not present in kernel - Ubuntu 21.10 on Raspberry Pi
  4 (64bit)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1947628/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1698656] Re: navigation panel icons missing on standard install of 17.04

2021-05-24 Thread Marcel Waldvogel

In 21.04, the following works:

1) sudo apt install breeze-icon-theme

done.

@Maintainers: Please add some form of dependency on this.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698656

Title:
  navigation panel icons missing on standard install of 17.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/okular/+bug/1698656/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927958] [NEW] Switching power source retains tab, even if it does not exist

2021-05-10 Thread Marcel Waldvogel

Public bug reported:

When switching from a power source (e.g., "Laptop battery") to another
power source (e.g. "AC adapter"), where the latter does not have the tab
which was selected in the former, then no information at all is
displayed.

Ubuntu 21.04, gnome-power-manager 3.32.0-2

Actual behavior
===

1. `gnome-power-statistics` starts with "AC adapter" selected left and 
"Details" tab being shown on the right
2. Click on "Laptop battery" left: Laptop battery "Details" tab is shown on the 
right
3. Click on "History" or "Statistics" tab: The appropriate information for 
"Laptop battery" is shown on the right. So far, so good.
4. Click on "AC adapter" left again: Now, *nothing* is shown on the right. This 
should not happen.

Expected behavior
=
4. Click on "AC adapter": "Details" tab should be shown. (In general: *Any* tab 
should be shown, but here, "Details" is the only one available.)

This is probably a result from trying to fix
https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/766876

** Affects: gnome-power-manager (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927958

Title:
  Switching power source retains tab, even if it does not exist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1927958/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926223] Re: Netboot Loading libc6-udeb failed for unknown reasons (focal) 2020-04-21

2021-04-26 Thread Marcel

I can confirm this bug. It bricked yesterday, right after the changes to the 
libc6-udeb package
https://launchpad.net/ubuntu/focal/amd64/libc6-udeb.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926223

Title:
  Netboot Loading libc6-udeb failed for unknown reasons (focal)
  2020-04-21

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1926223/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1923840] Re: Xorg freeze

2021-04-14 Thread Marcel Vogler

** Changed in: xorg (Ubuntu)
   Status: New => Fix Released

** Changed in: xorg (Ubuntu)
   Status: Fix Released => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923840

Title:
  Xorg freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1923840/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1923840] [NEW] Xorg freeze

2021-04-14 Thread Marcel Vogler

Public bug reported:

After booting there is only a black screen showing a blinking _ in the
top left corner. Nothing happens anymore. It only happens with Linux
version 5.8.0-49-generic. Linux version 5.8.0-48-generic boots fine.

Description:Ubuntu 20.04.2 LTS

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/capabilities/mig'
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.39  Thu Jan 21 21:54:06 
UTC 2021
 GCC version:
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 14 14:25:13 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Today
GraphicsCard:
 NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company TU116 [GeForce GTX 1660 SUPER] [103c:8789]
 Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c9) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company Renoir [103c:87d6]
InstallationDate: Installed on 2021-02-27 (45 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: HP HP Pavilion Gaming Desktop TG01-1xxx
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/19/2020
dmi.bios.release: 15.16
dmi.bios.vendor: AMI
dmi.bios.version: F.10
dmi.board.name: 87D6
dmi.board.vendor: HP
dmi.board.version: SMVB
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 103.9
dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd11/19/2020:br15.16:efr103.9:svnHP:pnHPPavilionGamingDesktopTG01-1xxx:pvr:rvnHP:rn87D6:rvrSMVB:cvnHP:ct3:cvr:
dmi.product.family: 103C_53311M HP Pavilion Desktop PC
dmi.product.name: HP Pavilion Gaming Desktop TG01-1xxx
dmi.product.sku: 27Y73EA#ABD
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal freeze ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923840

Title:
  Xorg freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1923840/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913853] Re: Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging

2021-02-03 Thread Marcel Svitalsky

Seems working fine for me, thx.

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913853

Title:
  Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913853/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913853] Re: Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging

2021-02-01 Thread Marcel Svitalsky

Thanks Kleber, I see now that this is what happens when you check a
checkbox (Pre-released updates) and five years later don't even remember
it. :-)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913853

Title:
  Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913853/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913853] Re: Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging

2021-01-29 Thread Marcel Svitalsky

Unless absolutely necessary I do not wish to boot that broken kernel
again.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913853

Title:
  Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913853/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913853] [NEW] Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging

2021-01-29 Thread Marcel Svitalsky

Public bug reported:

Hi there,
I've updated kernel on my Ubuntu 16.04 from 4.4.0-201-generic to 
4.4.0.202-generic today and it broke my system.
Basic commands, such as pidof, lsof, ps fax (ps -a works) hang indefinitely and 
not even root issued kill -KILL will terminate them. Only thing that helps is 
to kill the shell that started such commands.

I had to reboot back to 4.4.0-201, however during shutdown various stop
jobs hanged as well and after more than 25 minutes I had to go for hard
reboot.

My current—NOT BROKEN—kernel has signature (cat /proc/version_signature):
Ubuntu 4.4.0-201.233-generic 4.4.247

I am attaching the lspci-vnvn.log, also created with the non-broken
kernel.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: xenial

** Attachment added: "lspci-vnvn.log created with the non-broken kernel"
   
https://bugs.launchpad.net/bugs/1913853/+attachment/5458209/+files/lspci-vnvn.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913853

Title:
  Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913853/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913415] Re: kernel BUG at fs/cachefiles/rdwr.c:717! - system completly locks up and requires hard reset

2021-01-27 Thread Marcel Noe

When booting to 5.4.0-59-generic #65-Ubuntu SMP everything works fine. I
therefore guess that this bug was newly introduced between 5.4.0-59 and
5.8.0-40.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913415

Title:
  kernel BUG at fs/cachefiles/rdwr.c:717! - system completly locks up
  and requires hard reset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1913415/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913415] [NEW] kernel BUG at fs/cachefiles/rdwr.c:717! - system completly locks up and requires hard reset

2021-01-27 Thread Marcel Noe

Public bug reported:

This is a virtual machine with PCIe passthrough and home filesystem
mounted from host over NFS. The system also runs FSC to cache the NFS.
The system occurs since the last update - ubuntu live patch is enabled.

The system boots up and launches lightdm. When logging in as normal
user, the system immediately locks up. This also happens when logging in
over ssh as normal user having his home on the NFS share.

When logging in as root over ssh, and running dmesg -w, I see the
following message:

[   46.358431] CacheFiles: 
[   46.358436] CacheFiles: Assertion failed
[   46.358545] [ cut here ]
[   46.358547] kernel BUG at fs/cachefiles/rdwr.c:717!
[   46.358568] invalid opcode:  [#1] SMP PTI
[   46.358572] CPU: 0 PID: 3756 Comm: sshd Tainted: P   O  
5.8.0-40-generic #45~20.04.1-Ubuntu
[   46.358574] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 
02/06/2015
[   46.358594] RIP: 0010:cachefiles_read_or_alloc_pages.cold+0x32/0x4e 
[cachefiles]
[   46.358598] Code: a6 ef 02 e9 48 c7 c7 48 e8 2e c2 e8 9a ef 02 e9 0f 0b 48 
c7 c7 70 db 2e c2 e8 8c ef 02 e9 48 c7 c7 48 e8 2e c2 e8 80 ef 02 e9 <0f> 0b 48 
c7 c7 70 db 2e c2 e8 72 ef 02 e9 48 c7 c7 48 e8 2e c2 e8
[   46.358600] RSP: 0018:b059010d7890 EFLAGS: 00010246
[   46.358603] RAX: 001c RBX: 8b47cf46a770 RCX: 0027
[   46.358605] RDX:  RSI: 0086 RDI: 8b482fa18cd8
[   46.358607] RBP: b059010d7980 R08: 8b482fa18cd0 R09: acdcf730
[   46.358609] R10: acdb4988 R11: b059010d7710 R12: 8b47cb0ed8c0
[   46.358610] R13:  R14: b059010d7b98 R15: b059010d7a24
[   46.358613] FS:  7f351cd26f40() GS:8b482fa0() 
knlGS:
[   46.358615] CS:  0010 DS:  ES:  CR0: 80050033
[   46.358617] CR2: 557fbc630ee0 CR3: 00044cbc6005 CR4: 001606f0
[   46.358622] Call Trace:
[   46.358642]  ? update_load_avg+0x7c/0x640
[   46.358647]  ? native_smp_send_reschedule+0x2a/0x40
[   46.358650]  ? wake_up_bit+0x42/0x50
[   46.358674]  ? fscache_run_op.isra.0+0x5d/0xc0 [fscache]
[   46.358683]  __fscache_read_or_alloc_pages+0x234/0x2f0 [fscache]
[   46.358704]  __nfs_readpages_from_fscache+0x65/0x150 [nfs]
[   46.358720]  nfs_readpages+0xc2/0x1b0 [nfs]
[   46.358724]  ? get_page_from_freelist+0x1b5/0x370
[   46.358728]  ? __alloc_pages_nodemask+0x161/0x2f0
[   46.358732]  read_pages+0x194/0x280
[   46.358736]  page_cache_readahead_unbounded+0x147/0x200
[   46.358741]  __do_page_cache_readahead+0x35/0x40
[   46.358744]  ondemand_readahead+0x148/0x2a0
[   46.358747]  page_cache_sync_readahead+0x78/0xc0
[   46.358752]  generic_file_buffered_read+0x598/0xc50
[   46.358763]  ? __mod_lruvec_state+0x41/0xf0
[   46.358768]  generic_file_read_iter+0xdc/0x140
[   46.358773]  ? _cond_resched+0x19/0x30
[   46.358786]  ? nfs_revalidate_mapping+0xa1/0x290 [nfs]
[   46.358798]  nfs_file_read+0x74/0xb0 [nfs]
[   46.358803]  new_sync_read+0x10c/0x1a0
[   46.358808]  vfs_read+0x161/0x190
[   46.358811]  ksys_read+0x67/0xe0
[   46.358815]  __x64_sys_read+0x1a/0x20
[   46.358820]  do_syscall_64+0x49/0xc0
[   46.358823]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   46.358826] RIP: 0033:0x7f351d116142
[   46.358829] Code: c0 e9 c2 fe ff ff 50 48 8d 3d 3a ca 0a 00 e8 f5 19 02 00 
0f 1f 44 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 0f 05 <48> 3d 00 
f0 ff ff 77 56 c3 0f 1f 44 00 00 48 83 ec 28 48 89 54 24
[   46.358831] RSP: 002b:7ffc63e16e78 EFLAGS: 0246 ORIG_RAX: 

[   46.358834] RAX: ffda RBX: 557fbc621ee0 RCX: 7f351d116142
[   46.358836] RDX: 2000 RSI: 557fbc62eed0 RDI: 0005
[   46.358837] RBP: 7f351d1f24a0 R08: 0005 R09: 7f351d1f0c20
[   46.358839] R10: 557fbc5e4010 R11: 0246 R12: 7f351cd26f40
[   46.358840] R13: 7f351d1f18a0 R14: 0d68 R15: 0d68
[   46.358843] Modules linked in: rfcomm cachefiles xt_multiport 
ip6table_filter ip6_tables xt_conntrack xt_MASQUERADE nf_conntrack_netlink 
nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat 
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter 
bridge stp llc rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd aufs overlay grace 
cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi nvidia_uvm(O) 
nvidia_drm(PO) nvidia_modeset(PO) nls_iso8859_1 intel_rapl_msr 
intel_rapl_common snd_hda_codec_generic ledtrig_audio crct10dif_pclmul 
ghash_clmulni_intel aesni_intel crypto_simd snd_hda_intel cryptd glue_helper 
snd_intel_dspcfg btusb snd_hda_codec btrtl snd_usb_audio btbcm btintel 
snd_hda_core snd_usbmidi_lib snd_hwdep bluetooth mc snd_seq_midi 
snd_seq_midi_event ecdh_generic rapl nvidia(PO) razerkbd(O) snd_pcm ecc joydev 
snd_rawmidi input_leds snd_seq serio_raw efi_pstore snd_seq_device snd_timer 
qxl snd drm_ttm_helper ttm

[Bug 1766230] Re: Strange window matching behaviour between Slack and Chrome

2020-11-25 Thread marcel

Same issue in Ubuntu 20.10 with Slack and Brave browser

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766230

Title:
  Strange window matching behaviour between Slack and Chrome

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766230/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1902525] [NEW] btrfs subvolume list segmentation fault

2020-11-02 Thread Marcel

Public bug reported:

Under Ubuntu 18.04 LTS with HWE-Kernel 5.4.0-52-generic the command

btrfs subvolume list /

sometimes leads to a segmentation fault. Unfortunately I cannot figure
out why some calls of this command work as expected while others (of
exactly the same command) lead to the segmentation fault. On my machine
about every third call leads to the segfault.

In case of the segmentation fault, my syslog contains the following entries:
Nov  2 13:56:11 Sputnik kernel: [153948.460139] btrfs[19583]: segfault at 
7ffcd9d8c391 ip 55d8e5201117 sp 7ffcd5d8bd20 error 4 in 
btrfs[55d8e5195000+a9000]
Nov  2 13:56:11 Sputnik kernel: [153948.460153] Code: 00 00 31 c0 8b 5c 24 14 
39 9c 24 88 00 00 00 0f 86 f2 01 00 00 48 8b 7c 24 08 48 8d 57 68 48 8d 0c 02 
48 83 c0 20 48 89 04 24 <8b> 71 18 8b 79 1c 48 8b 59 08 48 8b 69 10 81 fe 90 00 
00 00 89 74

According to
https://forums.linuxmint.com/viewtopic.php?t=333594
I do not seem to be the only one experiencing this problem.

** Affects: btrfs-progs (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902525

Title:
  btrfs subvolume list segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/btrfs-progs/+bug/1902525/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1896349] Re: PCI/internal sound card not detected

2020-09-21 Thread Fernando Marcel Tarantino Martins

Mr Wang, the computer now showed the same problem! I don't know what
happens.
w how to
I tried to solve it using your link, but I don't know how to proceed to
make the backup you ask and also don't know how to attach the other files.
I'm kind of new using Linux and sometimes it's difficult to understand what
application and what steps I have to do in order to make things work as it
should.

On Mon, Sep 21, 2020 at 8:02 AM Fernando Marcel 
wrote:

> Hi, Mr. Wang.
>
> I don't know how but in the next day it just worked normally.
>
> Thank you anyways! :)
>
> On Mon, Sep 21, 2020 at 12:30 AM Hui Wang <1896...@bugs.launchpad.net>
> wrote:
>
>> Please test this: https://bugs.launchpad.net/ubuntu/+source/linux-
>> firmware/+bug/1892714/comments/46
>> <https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1892714/comments/46>
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1896349
>>
>> Title:
>>   PCI/internal sound card not detected
>>
>> Status in alsa-driver package in Ubuntu:
>>   New
>>
>> Bug description:
>>   Description:  Ubuntu 20.04.1 LTS
>>   Release:  20.04
>>
>>   I can select my default audio hardware
>>
>>   When I test it, doesn't work.
>>
>>   When watching a Youtube video, for example, audio doesn't work as
>>   well.
>>
>>   Thru the command lspci, this shows up:
>>
>>   00:00.0 Host bridge: Intel Corporation Device 8a12 (rev 03)
>>   00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics
>> G7 (rev 07)
>>   00:04.0 Signal processing controller: Intel Corporation Device 8a03
>> (rev 03)
>>   00:0d.0 USB controller: Intel Corporation Ice Lake Thunderbolt 3 USB
>> Controller (rev 03)
>>   00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host
>> Controller (rev 30)
>>   00:14.2 RAM memory: Intel Corporation Device 34ef (rev 30)
>>   00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i
>> 160MHz Wireless Network Adapter (201NGW) (rev 30)
>>   00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP
>> Serial IO I2C Controller #0 (rev 30)
>>   00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP
>> Serial IO I2C Controller #1 (rev 30)
>>   00:16.0 Communication controller: Intel Corporation Management Engine
>> Interface (rev 30)
>>   00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA
>> Controller [RAID mode] (rev 30)
>>   00:1c.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port
>> #5 (rev 30)
>>   00:1d.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port
>> #9 (rev 30)
>>   00:1d.4 PCI bridge: Intel Corporation Device 34b4 (rev 30)
>>   00:1d.6 PCI bridge: Intel Corporation Device 34b6 (rev 30)
>>   00:1f.0 ISA bridge: Intel Corporation Ice Lake-LP LPC Controller (rev
>> 30)
>>   00:1f.3 Multimedia audio controller: Intel Corporation Smart Sound
>> Technology Audio Controller (rev 30)
>>   00:1f.4 SMBus: Intel Corporation Ice Lake-LP SMBus Controller (rev 30)
>>   00:1f.5 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP SPI
>> Controller (rev 30)
>>   01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX330] (rev
>> a1)
>>   02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd.
>> RTS522A PCI Express Card Reader (rev 01)
>>   03:00.0 Non-Volatile memory controller: Intel Corporation Device 0975
>> (rev 03)
>>   04:00.0 Non-Volatile memory controller: Intel Corporation Device 0975
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 20.04
>>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>>   ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
>>   Uname: Linux 5.4.0-47-generic x86_64
>>   ApportVersion: 2.20.11-0ubuntu27.8
>>   Architecture: amd64
>>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
>> '/dev/snd/timer'] failed with exit code 1:
>>   CasperMD5CheckResult: skip
>>   CurrentDesktop: ubuntu:GNOME
>>   Date: Sat Sep 19 19:24:38 2020
>>   InstallationDate: Installed on 2020-09-19 (0 days ago)
>>   InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
>> (20200731)
>>   PackageArchitecture: all
>>   SourcePackage: alsa-driver
>>   Symptom: audio
>>   Title: PCI/internal sound card not detected
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   dmi.bios.date: 02/13/2020
>>   dmi.bios.vendor: Insyd

Re: [Bug 1896349] Re: PCI/internal sound card not detected

2020-09-21 Thread Fernando Marcel Tarantino Martins

Hi, Mr. Wang.

I don't know how but in the next day it just worked normally.

Thank you anyways! :)

On Mon, Sep 21, 2020 at 12:30 AM Hui Wang <1896...@bugs.launchpad.net>
wrote:

> Please test this: https://bugs.launchpad.net/ubuntu/+source/linux-
> firmware/+bug/1892714/comments/46
> 
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1896349
>
> Title:
>   PCI/internal sound card not detected
>
> Status in alsa-driver package in Ubuntu:
>   New
>
> Bug description:
>   Description:  Ubuntu 20.04.1 LTS
>   Release:  20.04
>
>   I can select my default audio hardware
>
>   When I test it, doesn't work.
>
>   When watching a Youtube video, for example, audio doesn't work as
>   well.
>
>   Thru the command lspci, this shows up:
>
>   00:00.0 Host bridge: Intel Corporation Device 8a12 (rev 03)
>   00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics
> G7 (rev 07)
>   00:04.0 Signal processing controller: Intel Corporation Device 8a03 (rev
> 03)
>   00:0d.0 USB controller: Intel Corporation Ice Lake Thunderbolt 3 USB
> Controller (rev 03)
>   00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host
> Controller (rev 30)
>   00:14.2 RAM memory: Intel Corporation Device 34ef (rev 30)
>   00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i
> 160MHz Wireless Network Adapter (201NGW) (rev 30)
>   00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP
> Serial IO I2C Controller #0 (rev 30)
>   00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP
> Serial IO I2C Controller #1 (rev 30)
>   00:16.0 Communication controller: Intel Corporation Management Engine
> Interface (rev 30)
>   00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA
> Controller [RAID mode] (rev 30)
>   00:1c.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port
> #5 (rev 30)
>   00:1d.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port
> #9 (rev 30)
>   00:1d.4 PCI bridge: Intel Corporation Device 34b4 (rev 30)
>   00:1d.6 PCI bridge: Intel Corporation Device 34b6 (rev 30)
>   00:1f.0 ISA bridge: Intel Corporation Ice Lake-LP LPC Controller (rev 30)
>   00:1f.3 Multimedia audio controller: Intel Corporation Smart Sound
> Technology Audio Controller (rev 30)
>   00:1f.4 SMBus: Intel Corporation Ice Lake-LP SMBus Controller (rev 30)
>   00:1f.5 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP SPI
> Controller (rev 30)
>   01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX330] (rev a1)
>   02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A
> PCI Express Card Reader (rev 01)
>   03:00.0 Non-Volatile memory controller: Intel Corporation Device 0975
> (rev 03)
>   04:00.0 Non-Volatile memory controller: Intel Corporation Device 0975
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
>   Uname: Linux 5.4.0-47-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.8
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Sep 19 19:24:38 2020
>   InstallationDate: Installed on 2020-09-19 (0 days ago)
>   InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
> (20200731)
>   PackageArchitecture: all
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Title: PCI/internal sound card not detected
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 02/13/2020
>   dmi.bios.vendor: Insyde
>   dmi.bios.version: F.04
>   dmi.board.asset.tag: Type2 - Board Asset Tag
>   dmi.board.name: 875C
>   dmi.board.vendor: HP
>   dmi.board.version: 10.23
>   dmi.chassis.asset.tag: Chassis Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: HP
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
> dmi:bvnInsyde:bvrF.04:bd02/13/2020:svnHP:pnHPENVYLaptop17m-cg0xxx:pvrType1ProductConfigId:rvnHP:rn875C:rvr10.23:cvnHP:ct10:cvrChassisVersion:
>   dmi.product.family: 103C_5335KV HP Envy
>   dmi.product.name: HP ENVY Laptop 17m-cg0xxx
>   dmi.product.sku: 9XM78UA#ABA
>   dmi.product.version: Type1ProductConfigId
>   dmi.sys.vendor: HP
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1896349/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896349

Title:
  PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1896349/+subscriptions

-- 
ubuntu-bugs mailing list

[Bug 1896349] [NEW] PCI/internal sound card not detected

2020-09-19 Thread Fernando Marcel Tarantino Martins

Public bug reported:

Description:Ubuntu 20.04.1 LTS
Release:20.04

I can select my default audio hardware

When I test it, doesn't work.

When watching a Youtube video, for example, audio doesn't work as well.

Thru the command lspci, this shows up:

00:00.0 Host bridge: Intel Corporation Device 8a12 (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G7 (rev 
07)
00:04.0 Signal processing controller: Intel Corporation Device 8a03 (rev 03)
00:0d.0 USB controller: Intel Corporation Ice Lake Thunderbolt 3 USB Controller 
(rev 03)
00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host 
Controller (rev 30)
00:14.2 RAM memory: Intel Corporation Device 34ef (rev 30)
00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i 160MHz 
Wireless Network Adapter (201NGW) (rev 30)
00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO 
I2C Controller #0 (rev 30)
00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO 
I2C Controller #1 (rev 30)
00:16.0 Communication controller: Intel Corporation Management Engine Interface 
(rev 30)
00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 30)
00:1c.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #5 (rev 
30)
00:1d.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #9 (rev 
30)
00:1d.4 PCI bridge: Intel Corporation Device 34b4 (rev 30)
00:1d.6 PCI bridge: Intel Corporation Device 34b6 (rev 30)
00:1f.0 ISA bridge: Intel Corporation Ice Lake-LP LPC Controller (rev 30)
00:1f.3 Multimedia audio controller: Intel Corporation Smart Sound Technology 
Audio Controller (rev 30)
00:1f.4 SMBus: Intel Corporation Ice Lake-LP SMBus Controller (rev 30)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP SPI 
Controller (rev 30)
01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX330] (rev a1)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI 
Express Card Reader (rev 01)
03:00.0 Non-Volatile memory controller: Intel Corporation Device 0975 (rev 03)
04:00.0 Non-Volatile memory controller: Intel Corporation Device 0975

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 19 19:24:38 2020
InstallationDate: Installed on 2020-09-19 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/13/2020
dmi.bios.vendor: Insyde
dmi.bios.version: F.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 875C
dmi.board.vendor: HP
dmi.board.version: 10.23
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd02/13/2020:svnHP:pnHPENVYLaptop17m-cg0xxx:pvrType1ProductConfigId:rvnHP:rn875C:rvr10.23:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Envy
dmi.product.name: HP ENVY Laptop 17m-cg0xxx
dmi.product.sku: 9XM78UA#ABA
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896349

Title:
  PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1896349/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1854588] Re: gdebi-gtk calls pkexec inappropriately

2020-08-27 Thread Marcel Partap

Thanks for the workarounds! Fantastic that progress is picking up, it
seemed doubtful this would ever be resolved. ⏳

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854588

Title:
  gdebi-gtk calls pkexec inappropriately

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdebi/+bug/1854588/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1666875] Re: anacron does not execute cron.daily on start or restart

2020-07-23 Thread Marcel Krause

Sorry for my misleading earlier post. Both parts were wrong.
1. ConditionACPower=no means to run on battery only; to ignore AC, it must be 
empty.
2. The ANACRON_RUN_ON_BATTERY_POWER flag has no effect when anacron is launched 
via systemd.

So in conclusion, it was mere coincidence that my approach had seemed to
solve the problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666875

Title:
  anacron does not execute cron.daily on start or restart

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1666875/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1666875] Re: anacron does not execute cron.daily on start or restart

2020-07-23 Thread Marcel Krause

The original systemd service file may be restored on system update.
Rather, make an override file /etc/systemd/system/anacron.service.d/on-
ac.conf with

> [Unit]
> ConditionACPower=no

to make systemd always start anacron. However that doesn't help if
anacron will then just flinch, so ensure in /etc/default/anacron:

> ANACRON_RUN_ON_BATTERY_POWER=yes

Hope it helps!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666875

Title:
  anacron does not execute cron.daily on start or restart

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1666875/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1885567] Re: Upgrade fails due to broken pagacke colord, package is not installed in the first place

2020-06-29 Thread Marcel Paul Alda

I figured out the problem, bug can be closed.

Desktop environment was still installed, removed it with

apt-get autoremove --purge $( dpkg-query -l *xubuntu* | grep ii | tr -s
" " | cut -d" " -f2; dpkg-query -l *xfce* | grep 'ii' | tr -s " " | cut
-d" " -f2 )

This fixed my issue as the upgrader no longer tried to install the
package colord.

Sorry for the inconvenience. :slight_smile:

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885567

Title:
  Upgrade fails due to broken pagacke colord, package is not installed
  in the first place

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1885567/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1885567] [NEW] Upgrade fails due to broken pagacke colord, package is not installed in the first place

2020-06-29 Thread Marcel Paul Alda

Public bug reported:

I try to run do-release-upgrade -d on an Ubuntu 18.04 which fails due to
broken packages.

According to main.log, the issue is colord. My issue is the lack of said
package as I have purged it via 'apt purge colord'.

Yet the issue persist and shows up again after trying to push from 18.04
to 20.04.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.37
ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18
Uname: Linux 4.15.0-109-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CrashDB: ubuntu
Date: Mon Jun 29 15:38:36 2020
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2020-06-29 (0 days ago)

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic dist-upgrade

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885567

Title:
  Upgrade fails due to broken pagacke colord, package is not installed
  in the first place

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1885567/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822581] Re: HP 1030 G3 fn-keys not working

2020-06-18 Thread Marcel Munce

Can confirm as well!

Flashed the BIOS and now it works for me, too!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822581

Title:
  HP 1030 G3 fn-keys not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822581] Re: HP 1030 G3 fn-keys not working

2020-06-18 Thread Marcel Munce

Nice! I'll try this as well!
Do you have any special Kernel parameters set?

And how did you flash the bios? Using the softpaq tool?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822581

Title:
  HP 1030 G3 fn-keys not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822581] Re: HP 1030 G3 fn-keys not working

2020-06-18 Thread Marcel Munce

Running 5.4.0-37-generic adding "drm.vblankoffdelay=1
acpi_backlight=vendor" to my grub config did not work, unfortunatelly

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822581

Title:
  HP 1030 G3 fn-keys not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825755] Re: apt-mirror in all versions (including disco and last from github) doesn't mirror Commands-* files

2020-06-11 Thread Marcel Brouwers

Had this problem with apt-mirror on Xenial with Focal clients. Using
apt-mirror 0.5.4-1ubuntu0.18.04.1+testpkg20200428b2 from ppa:slashd/test
solved the problem for me. Thanks for the work on this.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825755

Title:
  apt-mirror in all versions (including disco and last from github)
  doesn't mirror Commands-* files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-mirror/+bug/1825755/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882069] Re: DistUpgradeController.py key 'devRelease' not set correctly

2020-06-04 Thread Marcel Sachtleben

** Branch linked: lp:ubuntu-release-upgrader

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882069

Title:
  DistUpgradeController.py key 'devRelease' not set correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1882069/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882069] Re: DistUpgradeController.py key 'devRelease' not set correctly

2020-06-04 Thread Marcel Sachtleben

Here is the content of /var/log/dist-upgrade/main.log (file path may
differ):

root@snoobeam:/# cat /var/log/dist-upgrade/main.log 
2020-05-28 21:03:34,995 INFO Using config files '['./DistUpgrade.cfg']'
2020-05-28 21:03:34,995 INFO uname information: 'Linux snoobeam.com 
5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64'
2020-05-28 21:03:35,113 INFO apt version: '1.9.4ubuntu0.1'
2020-05-28 21:03:35,113 INFO python version: '3.7.5 (default, Apr 19 2020, 
20:18:17) 
[GCC 9.2.1 20191008]'
2020-05-28 21:03:35,114 INFO release-upgrader version '20.04.19' started
2020-05-28 21:03:35,129 INFO locale: 'en_US' 'UTF-8'
2020-05-28 21:03:35,202 INFO screen could not be run
2020-05-28 21:03:35,271 DEBUG Using 'DistUpgradeViewText' view
2020-05-28 21:03:35,337 DEBUG enable dpkg --force-overwrite
2020-05-28 21:03:35,436 DEBUG creating statefile: 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'
2020-05-28 21:03:36,399 DEBUG lsb-release: 'eoan'
2020-05-28 21:03:36,400 DEBUG _pythonSymlinkCheck run
2020-05-28 21:03:36,402 DEBUG openCache()
2020-05-28 21:03:36,403 DEBUG quirks: running PreCacheOpen
2020-05-28 21:03:36,403 DEBUG running Quirks.PreCacheOpen
2020-05-28 21:03:36,671 DEBUG /openCache(), new cache size 10843
2020-05-28 21:03:36,672 DEBUG need_server_mode(): can not find a desktop meta 
package or key deps, running in server mode
2020-05-28 21:03:36,672 DEBUG checkViewDepends()
2020-05-28 21:03:36,678 DEBUG running doUpdate() (showErrors=False)
2020-05-28 21:03:37,783 DEBUG openCache()
2020-05-28 21:03:38,020 DEBUG /openCache(), new cache size 10843
2020-05-28 21:03:38,020 DEBUG doPostInitialUpdate
2020-05-28 21:03:38,020 DEBUG quirks: running focalPostInitialUpdate
2020-05-28 21:03:38,021 DEBUG running Quirks.focalPostInitialUpdate
2020-05-28 21:03:38,301 DEBUG MetaPkgs: 
2020-05-28 21:03:38,692 DEBUG no PkgRecord found for 'fonts-urw-base35', 
skipping 
2020-05-28 21:03:38,998 DEBUG no PkgRecord found for 'mariadb-client-10.1', 
skipping 
2020-05-28 21:03:38,998 DEBUG no PkgRecord found for 'mariadb-server-10.1', 
skipping 
2020-05-28 21:03:39,016 DEBUG no PkgRecord found for 'pgadmin4-apache2', 
skipping 
2020-05-28 21:03:39,016 DEBUG no PkgRecord found for 'pgdg-keyring', skipping 
2020-05-28 21:03:39,022 DEBUG no PkgRecord found for 'postgresql-12', skipping 
2020-05-28 21:03:39,102 DEBUG Foreign: 
2020-05-28 21:03:39,102 DEBUG Obsolete: apt-transport-https aptitude 
aptitude-common binfmt-support ca-certificates-mono certbot cli-common 
command-not-found-data cpp-7 cpp-8 daemon denyhosts dovecot-ldap dovecot-lmtpd 
dovecot-managesieved dovecot-mysql dovecot-sieve fail2ban fonts-dejavu 
fonts-glyphicons-halflings g++-7 galera-3 gcc-10-base gcc-7 gcc-7-base gcc-8 
gcc-8-base gcc-8-multilib gir1.2-spiceclientglib-2.0 inotify-tools jenkins 
ldap-account-manager ldap-auth-client ldap-auth-config lib32gcc-8-dev lib32mpx2 
libaopalliance-java libapache-pom-java libapache2-mod-php7.2 
libapache2-mod-rpaf libapt-inst2.0 libapt-pkg5.0 libasan4 
libatinject-jsr330-api-java libcdi-api-java libcilkrts5 libcommons-cli-java 
libcommons-io-java libcommons-lang3-java libcommons-parent-java libcrypto++-dev 
libcrypto++6 libcwidget3v5 libdbd-mysql-perl libdbus-glib2.0-cil 
libdbus-glib2.0-cil-dev libdbus2.0-cil libdbus2.0-cil-dev libdouble-conversion3 
libffi7 libfstrm0 libgcc-7-dev libgcc-8-dev 
libgeronimo-annotation-1.3-spec-java libgeronimo-interceptor-3.0-spec-java 
libglib2.0-cil libglib2.0-cil-dev libglib2.0-tests libguava-java libguice-java 
libhawtjni-runtime-java libhiredis0.14 libicu60 libinotifytools0 libip4tc0 
libip6tc0 libjansi-java libjansi-native-java libjemalloc2 libjs-bootstrap 
libjs-requirejs libjson-c3 libjsr305-java liblua5.1-0 liblua5.1-0-dev 
libluajit-5.1-2 libluajit-5.1-common libmaven-parent-java 
libmaven-resolver-java libmaven-shared-utils-java libmaven3-core-java 
libmono-btls-interface4.0-cil libmono-corlib4.5-cil libmono-i18n-west4.0-cil 
libmono-i18n4.0-cil libmono-posix4.0-cil libmono-security4.0-cil 
libmono-system-configuration4.0-cil libmono-system-core4.0-cil 
libmono-system-numerics4.0-cil libmono-system-security4.0-cil 
libmono-system-xml4.0-cil libmono-system4.0-cil libmpx2 libnode64 libnss-ldap 
libpam-ldap libparse-debianchangelog-perl libphodav-2.0-0 libphodav-2.0-common 
libplexus-cipher-java libplexus-classworlds-java 
libplexus-component-annotations-java libplexus-interpolation-java 
libplexus-sec-dispatcher-java libplexus-utils2-java libprotobuf-c1 
libpython-all-dev libpython-dev libpython-stdlib libpython2-dev 
libpython2-stdlib libpython2.7 libpython2.7-dev libpython2.7-minimal 
libpython2.7-stdlib libqt5core5a libqt5glib-2.0-0 libsisu-inject-java 
libsisu-plexus-java libslf4j-java libspice-client-glib-2.0-8 
libspice-client-glib-2.0-dev libstdc++-7-dev libubsan0 libwagon-file-java 
libwagon-http-shaded-java libwagon-provider-api-java libx32gcc-8-dev 
libxapian30 libzip5 linux-headers-5.4.0-33 linux-headers-5.4.0-33-generic

[Bug 1882069] [NEW] DistUpgradeController.py key 'devRelease' not set correctly

2020-06-04 Thread Marcel Sachtleben

*** This bug is a security vulnerability ***

Public security bug reported:

I encountered this bug when execution do-release-upgrade on an Ubuntu 19.10 
machine.
The release upgrade crashed ungracefully not calling abort() which should 
rollback all changes up to that point.
So I ended up with kind of a broken packages and configuration hell on my 
server machine.
I finally was able to perform the release upgrade by using apt / dpkg manually 
and resolving package dependencies and conflicts by hand.

The bug is on actually two places:

DistUpgradeController.py (parameter devRelease not set at all due to
wrong indendation of else block)

DistUpgradeCache.py (using unsafe code within except block: accessing
undefined key 'devRelease' and provoke KeyError)

In general: the idea of except or catch or whatever is not just execute
different code logic in case of exception. It is about doing the most
basic stuff in case anything goes wrong (which should be as exception
(error) safe as possible)

Bad practice:

try
  doSomething();
catch exception
  ignoreException();
  doSomethingElse();

Good practice:

try
  doSomethingUnsafe();
catch exception e
  logAndHandleException(e);
  useAnotherTryIfAdditionalLogicIsRequired();

That kind of bad structure costed me 1 day of error analysis (I am not a
python guy) and another 1 day to revert the things from the failed
upgrade.

The bugs:

Since I can not find any source code git repository, the next lines target the 
python module which can be  found in /usr/lib/python3/dist-packages/DistUpgrade 
(Ubuntu 19.10 / Ubuntu 20.04 LTS)
(line numbers may differ)

Major Bug:

DistUpgradeController.py:138-139 (wrong indentation of else block)

Current:
if self.options:
if self.options.devel_release:
self.config.set("Options","devRelease", "True")
else:
self.config.set("Options","devRelease", "False")

Should be:

if self.options:
if self.options.devel_release:
self.config.set("Options","devRelease", "True")
else:
self.config.set("Options","devRelease", "False")

Minor Bug:

DistUpgradeCache.py:651-694 (except block)

Error arised in lines 667-668

elif self.config.get("Options", "foreignPkgs") == "False" and \
self.config.get("Options", "devRelease") == "True":

cause "devRelease" was not set on "Options" (see Major bug)
except block should not excecute unsafe code cause its job is error handling 
and roll back.
please make the entire block more fail safe (also use additional "try" if 
neccessary)
Since it seems like that accessing keys in python is not safe (reminds me of 
javascript)
it should be always checked if the key does even exist before accessing it.

Thanks for taking care of that.

Edit: I found the attachment feature after writing this report so please
find the DistUpgradeController.py attached containing the major bug.

Please keep me up to date
marcel.sachtle...@snoobeam.com

Best Regards

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: dist-upgrade do-release-upgrade

** Attachment added: "Source file including the Major bug taken from Ubuntu 
server 20.04 LTS environment"
   
https://bugs.launchpad.net/bugs/1882069/+attachment/5380306/+files/DistUpgradeController.py

** Information type changed from Private Security to Public Security

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882069

Title:
  DistUpgradeController.py key 'devRelease' not set correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1882069/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1872541] Re: MySQL client fails to connect, seems to force SSL

2020-05-20 Thread Marcel Lange

Sorry  `--ssl-mode=DISABLED` works for mysqldump as well.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872541

Title:
  MySQL client fails to connect, seems to force SSL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872541/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1872541] Re: MySQL client fails to connect, seems to force SSL

2020-05-20 Thread Marcel Lange

I have the same issue with mysqldump when using port forwarding over
ssh.


mysqldump: Got error: 2026: SSL connection error: error:1425F102:SSL 
routines:ssl_choose_client_version:unsupported protocol when trying to connect


Unfortunately I couldn't figure out a workaround hence `--ssl-mode=DISABLED` is 
not available for mysqldump.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872541

Title:
  MySQL client fails to connect, seems to force SSL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872541/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878060] [NEW] package grub-efi-amd64 2.02-2ubuntu8.15 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1

2020-05-11 Thread Eusebius Marcel

Public bug reported:

Occcured when installing upgrades from Ubuntu 16.04 to 18.04.
1. 'lsb_release -rd' showed version 18.04
2. 'apt-cache policy pkgname' returns 'N: Unable to locate package pkgname'
3. Expected grub to be installed
4. Error message popup instead

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: grub-efi-amd64 2.02-2ubuntu8.15
Uname: Linux 4.20.17-042017-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
Date: Tue May 12 00:31:45 2020
ErrorMessage: installed grub-efi-amd64 package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2019-06-21 (324 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227)
ProcCmdLine: BOOT_IMAGE=/vmlinuz-4.20.17-042017-generic 
root=UUID=179aa94e-f69c-4165-9c45-bcd273911c02 ro quiet splash dis_ucode_ldr 
acpi=force vt.handoff=7
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt  1.6.12
SourcePackage: grub2
Title: package grub-efi-amd64 2.02-2ubuntu8.15 failed to install/upgrade: 
installed grub-efi-amd64 package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to bionic on 2020-05-11 (0 days ago)

** Affects: grub2 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878060

Title:
  package grub-efi-amd64 2.02-2ubuntu8.15 failed to install/upgrade:
  installed grub-efi-amd64 package post-installation script subprocess
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1878060/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877837] Re: osc triggers bug in python3-m2crypto

2020-05-10 Thread Marcel

Direct link to patch is this:

https://gitlab.com/m2crypto/m2crypto/-/commit/d3a43ffe1bfe4c128d6ab7c390419dee68f4ca5a.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877837

Title:
  osc triggers bug in python3-m2crypto

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/m2crypto/+bug/1877837/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877837] [NEW] osc triggers bug in python3-m2crypto

2020-05-10 Thread Marcel

Public bug reported:

Basic usage of osc triggers a bug in python3-m2crypto (focal,
0.31.0-9ubuntu1) package:

 osc co Some:OBS:Repo

results in

 osc: incomplete read


Bug and fix was reported here:

https://github.com/openSUSE/osc/issues/771

Applying the fix mentioned there resolved the problem.

** Affects: m2crypto (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877837

Title:
  osc triggers bug in python3-m2crypto

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/m2crypto/+bug/1877837/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875798] Re: Samba 2:4.3.11+dfsg-0ubuntu0.16.04.26: LDAP request size (81) exceeds (0)

2020-04-29 Thread Marcel Waldvogel

The command for automated downgrades (be careful!) is:

apt list | grep 2:4.3.11+dfsg-0ubuntu0.16.04.26 | grep installed | sed
's,/.*,=2:4.3.8+dfsg-0ubuntu1,' | xargs apt install

If the `apt install` would do what you expect, add '-y' to the end and
run again.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875798

Title:
  Samba 2:4.3.11+dfsg-0ubuntu0.16.04.26: LDAP request size (81) exceeds
  (0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1875798/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875798] Re: Samba 2:4.3.11+dfsg-0ubuntu0.16.04.26: LDAP request size (81) exceeds (0)

2020-04-29 Thread Marcel Waldvogel

Downgrading everything which was 2:4.3.11+dfsg-0ubuntu0.16.04.26 to
2:4.3.8+dfsg-0ubuntu1 worked for us. Here is the command we used:

apt-get install samba=2:4.3.8+dfsg-0ubuntu1 samba-common=2:4.3.8+dfsg-
0ubuntu1 samba-common-bin=2:4.3.8+dfsg-0ubuntu1 libwbclient0=2:4.3.8
+dfsg-0ubuntu1 samba-libs=2:4.3.8+dfsg-0ubuntu1 python-samba=2:4.3.8
+dfsg-0ubuntu1 samba-dsdb-modules=2:4.3.8+dfsg-0ubuntu1 winbind=2:4.3.8
+dfsg-0ubuntu1 samba-vfs-modules=2:4.3.8+dfsg-0ubuntu1
libsmbclient=2:4.3.8+dfsg-0ubuntu1

apt-mark hold samba

If you have other packages installed, you can list all in need of a
downgrade with:

apt list | grep 2:4.3.11+dfsg-0ubuntu0.16.04.26 | grep installed

Looking forward to a new version of the security fix which does not
disable LDAP.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875798

Title:
  Samba 2:4.3.11+dfsg-0ubuntu0.16.04.26: LDAP request size (81) exceeds
  (0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1875798/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875798] Re: Samba 2:4.3.11+dfsg-0ubuntu0.16.04.26: LDAP request size (81) exceeds (0)

2020-04-29 Thread Marcel Waldvogel

This also affects us. Error message went away by downgrading to original
xenial version with

apt-get install samba=2:4.3.8+dfsg-0ubuntu1 samba-common=2:4.3.8+dfsg-0ubuntu1 
samba-common-bin=2:4.3.8+dfsg-0ubuntu1 libwbclient0=2:4.3.8+dfsg-0ubuntu1 
samba-libs=2:4.3.8+dfsg-0ubuntu1 python-samba=2:4.3.8+dfsg-0ubuntu1 
samba-dsdb-modules=2:4.3.8+dfsg-0ubuntu1
apt-mark hold samba

But still not everything is working, keep you posted.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875798

Title:
  Samba 2:4.3.11+dfsg-0ubuntu0.16.04.26: LDAP request size (81) exceeds
  (0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1875798/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822581] Re: HP 1030 G3 fn-keys not working

2020-04-22 Thread Marcel Munce

Yes, I have a Dual Boot Setup with Ubuntu as primary System.

I actually don't know what happened between the time it was working and
then stopped...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822581

Title:
  HP 1030 G3 fn-keys not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825025] Re: dpkg-reconfigure ldap-auth-client ignores values in debconf database

2020-04-15 Thread Marcel Partap

Maybe there's an equivalent setting to?
> console-setup   console-setup/store_defaults_in_debconf_db  boolean false

( found that mentioned in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=352697#27 )

** Bug watch added: Debian Bug tracker #352697
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=352697

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825025

Title:
  dpkg-reconfigure ldap-auth-client ignores values in debconf database

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ldap-auth-client/+bug/1825025/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871463] [NEW] Accessing Subversion Repository with Webbrowser leads to Segmentation fault

2020-04-07 Thread Marcel

Public bug reported:

I am running the Apache HTTP-Server with libapache2-mod-svn on Ubuntu
18.04. The installed packages are the latest provided by the official
Ubuntu repositories.

When accessing my SVN-Repository https://example.org/svn/repo with my
webbrowser, the http-request is suddenly terminated and the error.log of
my Apache server contains the following message:

AH00051: child pid 1697 exit signal Segmentation fault (11), possible
coredump in /etc/apache2

When instead accessing the same SVN-Repository
https://example.org/svn/repo with an SVN-client, everything (like
checkout, update and commit) works as expected.

Unfortunately, I cannot really tell since when I am affected by this
problem, as I use the SVN-functionality of my server only occasionally.

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871463

Title:
  Accessing Subversion Repository with Webbrowser leads to Segmentation
  fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1871463/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822581] Re: HP 1030 G3 fn-keys not working

2020-03-20 Thread Marcel Munce

For some reason it now stopped working again... 
Don't know why.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822581

Title:
  HP 1030 G3 fn-keys not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822581] Re: HP 1030 G3 fn-keys not working

2020-03-19 Thread Marcel Munce

Now running on 5.3.0-42 and the brightness controls are working!

(Mute and Indicator Lights still don't)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822581

Title:
  HP 1030 G3 fn-keys not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822581] Re: HP 1030 G3 fn-keys not working

2020-03-18 Thread Marcel Munce

I'm so sorry. I did not have the time to reinstall Ubuntu on my machine
for testing the kernel.

It's now running on your provided 5.3.0-24 but that does not work either
:-(

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822581

Title:
  HP 1030 G3 fn-keys not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822581] Re: HP 1030 G3 fn-keys not working

2019-11-06 Thread Marcel Munce

Strange. I now tried different Kernels and I just can't get those keys to 
function. 
They just don't create the corresponding ACPI Events...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822581

Title:
  HP 1030 G3 fn-keys not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1846542] Re: Kernel panic 5.3.0-13

2019-10-04 Thread Marcel Westhoff

The kernel didn't logged anything on my system. 
I attached a picture of the output kernel panic.

** Attachment added: "IMG_20191003_202132.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846542/+attachment/5294291/+files/IMG_20191003_202132.jpg

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846542

Title:
  Kernel panic 5.3.0-13

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846542/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1846542] Re: Kernel panic 5.3.0-13

2019-10-04 Thread Marcel Westhoff

The kernel didn't logged anything on my system. 
I attached a picture of the output kernel panic.

** Attachment added: "IMG_20191003_202132.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846542/+attachment/5294290/+files/IMG_20191003_202132.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846542

Title:
  Kernel panic 5.3.0-13

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846542/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1846542] [NEW] Kernel panic 5.3.0-13

2019-10-03 Thread Marcel Westhoff

Public bug reported:

Ubuntu 19.10 Beta -> official download (fresh install, not upgraded)
The installation failed, live system failed with a kernel panic. 
The system will boot properly if the TPM module is disabled. The Laptop is a HP 
Probook 450 G5. 
Can someone tell me how to print out the log of this?

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: kernel-bug

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846542

Title:
  Kernel panic 5.3.0-13

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1846542/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 128789] Re: easytag asks for confirmation every time you change directory

2019-09-09 Thread Marcel

I'm running Linux Mint 19 Tara 64-bit, MATE 1.20.1, EasyTAG 2.4.3.

For some reason many mp3 files are being updated the moment I select a
folder. Saving the files in the "Confirm Directory Change" dialogue does
not seem help preventing to get updated next time I visit the same
folder again.

This behaviour is very annoying since I am sure the tags are okay!

Can you please reopen this bug, and provide a fix or workaround?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/128789

Title:
  easytag asks for confirmation every time you change directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/easytag/+bug/128789/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)

2019-08-13 Thread Paulo Marcel Coelho Aragão

Ops, apologies for the typo, I'm running Xubuntu 18.04.03

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801609

Title:
  Fails to deactivate dpms off mode after user initiated wake-up
  events(not system-suspended, just locked and dpms active)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801609/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)

2019-08-13 Thread Paulo Marcel Coelho Aragão

I'm running Xubuntu 18.0.03, which hasn't reached end-of-life, and this
bug is still present. It was introduced when I upgraded to kernel 5.0
with xorg 1.20.4-1ubuntu3~18.04.1. It can be circumvented using either
of 2 methods:

1. Uninstalling light-locker and installing xscreensaver
or
2. As suggested by @bbethge, created /etc/X11/xorg.conf.d/20-intel.conf:
Section "Device"
   Identifier  "Intel Graphics"
   Driver  "intel"
EndSection

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801609

Title:
  Fails to deactivate dpms off mode after user initiated wake-up
  events(not system-suspended, just locked and dpms active)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801609/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 909859] Re: Pressing CTRL-C durring a "checkinstall --fstrans=0" results in bash: /bin/bash: No such file or directory

2019-08-03 Thread Marcel Partap

Ok for anyone landing in this situation (f.e. by trying to `checkinstall
--fstrans=no ./vmware-product.bundle` ).. a probable cause is that
checkinstall has removed the /lib -> /usr/lib symlink and replaced it by
a directory. Lucky you if you have a tmux session with a root ranger
instance running to recover from that  .. else, you'll probably have to
boot into a recovery system  ..

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/909859

Title:
  Pressing CTRL-C durring a "checkinstall --fstrans=0" results in bash:
  /bin/bash: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/909859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1835639] [NEW] During boot - System bootorder not found

2019-07-06 Thread Marcel Beerli

Public bug reported:

On HP Laptop Elitebook G1 after upgrade from 18.04 to 19.04 I get displayed 
very early on
System Bootorder not found, Initializing defaults  (next line)
Creating boot entry "boot0001" with label "ubuntu" for file 
/EFI/ubuntu/shimx64.efi

then it waits 30sec and boots

Next boot it sais boot0002 and so on


rbeerli@GS6:~$ efibootmgr .v
BootCurrent: 
Timeout: 0 seconds
BootOrder: 0004
Boot* Notebook Hard Drive
Boot0001* Notebook Ethernet
Boot0002* ubuntu
Boot0003* ubuntu
Boot0004* ubuntu

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-terminal 3.32.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul  7 05:45:25 2019
ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
InstallationDate: Installed on 2019-04-03 (94 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to disco on 2019-07-06 (0 days ago)

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835639

Title:
  During boot - System bootorder not found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1835639/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1832653] Re: ejabberd fails to work after upgrade of openssl to v1.1.1 in Ubuntu 18.04 LTS

2019-06-24 Thread Marcel

The latest upgrade of "erlang-p1-tls" fortunately seemed to solve the
problem.

** Changed in: ejabberd (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832653

Title:
  ejabberd fails to work after upgrade of openssl to v1.1.1 in Ubuntu
  18.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1832653/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1833471] Re: Can not enable Wifi Hotspot

Good news.
I created a new user profile and now it works.
Would it be possible to delete a few files on the old profile (gnome control 
center) related to get the old profile working?

thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833471

Title:
  Can not enable Wifi Hotspot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833471/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1833471] Re: Can not enable Wifi Hotspot

I do not think I have gnome shell extensions installed.
nbeerli@galaxy3:~$ sudo apt remove gnome-shell-extensions
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package 'gnome-shell-extensions' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
nbeerli@galaxy3:~$ 

Also no EasyScreenCase

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833471

Title:
  Can not enable Wifi Hotspot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833471/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1833471] Re: Can not enable Wifi Hotspot

Here more info to that:
nbeerli@nbeerli-galaxy3:~$ journalctl -b 0 |grep -A 5 -B 5 "Error looking up 
permission: GDBus.Error" 
Jun 21 12:34:30 nbeerli-galaxy3 dbus-daemon[1045]: [system] Activating via 
systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested 
by ':1.38' (uid=125 pid=1381 comm="/usr/bin/gnome-shell " label="unconfined")
Jun 21 12:34:30 nbeerli-galaxy3 systemd[1]: Starting Fingerprint Authentication 
Daemon...
Jun 21 12:34:30 nbeerli-galaxy3 dbus-daemon[1045]: [system] Successfully 
activated service 'net.reactivated.Fprint'
Jun 21 12:34:30 nbeerli-galaxy3 systemd[1]: Started Fingerprint Authentication 
Daemon.
Jun 21 12:34:30 nbeerli-galaxy3 gnome-shell[1381]: Getting invalid resource 
scale property
Jun 21 12:34:30 nbeerli-galaxy3 gnome-shell[1381]: Error looking up permission: 
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Jun 21 12:34:30 nbeerli-galaxy3 gnome-shell[1381]: JS WARNING: 
[resource:///org/gnome/shell/ui/windowManager.js 1644]: reference to undefined 
property "MetaWindowXwayland"
Jun 21 12:34:31 nbeerli-galaxy3 gnome-session-binary[1367]: Entering running 
state
Jun 21 12:34:31 nbeerli-galaxy3 NetworkManager[1046]:   [1561113271.4458] 
device (vmnet1): driver '(null)' does not support carrier detection.
Jun 21 12:34:31 nbeerli-galaxy3 systemd-udevd[432]: Using default interface 
naming scheme 'v240'.
Jun 21 12:34:31 nbeerli-galaxy3 NetworkManager[1046]:   [1561113271.4461] 
device (vmnet1): driver 'unknown' does not support carrier detection.
--
Jun 21 12:35:13 nbeerli-galaxy3 dbus-daemon[2043]: [session uid=1000 pid=2043] 
Successfully activated service 'org.gnome.evolution.dataserver.AddressBook9'
Jun 21 12:35:13 nbeerli-galaxy3 systemd[2015]: Started Evolution address book 
service.
Jun 21 12:35:13 nbeerli-galaxy3 dropbox.desktop[2401]: dropbox: load fq 
extension 
'/home/nbeerli/.dropbox-dist/dropbox-lnx.x86_64-74.4.115/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so'
Jun 21 12:35:13 nbeerli-galaxy3 dropbox.desktop[2401]: dropbox: load fq 
extension 
'/home/nbeerli/.dropbox-dist/dropbox-lnx.x86_64-74.4.115/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so'
Jun 21 12:35:14 nbeerli-galaxy3 NetworkManager[1046]:   [1561113314.0652] 
agent-manager: req[0x5561c27a58d0, :1.356/org.gnome.Shell.NetworkAgent/1000]: 
agent registered
Jun 21 12:35:14 nbeerli-galaxy3 gnome-shell[2191]: Error looking up permission: 
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Jun 21 12:35:14 nbeerli-galaxy3 dropbox.desktop[2401]: dropbox: load fq 
extension 
'/home/nbeerli/.dropbox-dist/dropbox-lnx.x86_64-74.4.115/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so'
Jun 21 12:35:14 nbeerli-galaxy3 dropbox.desktop[2401]: dropbox: load fq 
extension 
'/home/nbeerli/.dropbox-dist/dropbox-lnx.x86_64-74.4.115/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so'
Jun 21 12:35:14 nbeerli-galaxy3 dropbox.desktop[2401]: dropbox: load fq 
extension 
'/home/nbeerli/.dropbox-dist/dropbox-lnx.x86_64-74.4.115/linuxffi.pthread._linuxffi_pthread.cpython-37m-x86_64-linux-gnu.so'
Jun 21 12:35:14 nbeerli-galaxy3 dropbox.desktop[2401]: dropbox: load fq 
extension 
'/home/nbeerli/.dropbox-dist/dropbox-lnx.x86_64-74.4.115/cpuid.compiled._cpuid.cpython-37m-x86_64-linux-gnu.so'
Jun 21 12:35:14 nbeerli-galaxy3 dropbox.desktop[2401]: dropbox: load fq 
extension 
'/home/nbeerli/.dropbox-dist/dropbox-lnx.x86_64-74.4.115/apex._apex.cpython-37m-x86_64-linux-gnu.so'


Let me know if you need anything else

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833471

Title:
  Can not enable Wifi Hotspot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1833471/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1833471] Re: Can not enable Wifi Hotspot

Here the output from the terminal.
Sorry about the other question: Its the whole session. It varies. Sometimes it 
gets be back to the login page


nbeerli@nbeerli-galaxy3:~$ gnome-control-center

(gnome-control-center:18961): network-cc-panel-WARNING **: 11:26:23.739:
Could not get secrets: No agents were available for this request.

(gnome-control-center:18961): network-cc-panel-WARNING **: 11:26:23.739:
Could not get secrets: No agents were available for this request.

(gnome-control-center:18961): network-cc-panel-WARNING **: 11:26:23.755:
Could not get secrets: No agents were available for this request.

(gnome-control-center:18961): network-cc-panel-WARNING **: 11:26:48.726: Could 
not get secrets: Timeout was reached
nbeerli@nbeerli-galaxy3:~$

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833471

Title:
  Can not enable Wifi Hotspot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1833471/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1833471] Re: Can not enable Wifi Hotspot

2019-06-20 Thread Marcel Beerli

Here the journalctl info
I tested the Hotspot option with or without docking station.
Let me know if you need anything else

** Attachment added: "journal.zip"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1833471/+attachment/5271861/+files/journal.zip

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833471

Title:
  Can not enable Wifi Hotspot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1833471/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1833471] [NEW] Can not enable Wifi Hotspot

2019-06-19 Thread Marcel Beerli

Public bug reported:

Ubuntu 19.04 fresh upgrade
Hotspot was working on Elitebook 740G2 on Ubuntu 16.04
was no longer working on Ubuntu 18.04

When Wifi is enabled, I can connect to wifi router. So wifi works
When choosing "Turn on Wi-Fi Hotspot" it pops up the dialog box if I want to 
Turn on or Cancel, when choosing "Turn on" it crashes (Screen goes black) or it 
clears the "Visible Networks" box, a few seconds later is shows available 
networks again

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-control-center 1:3.32.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
Uname: Linux 5.0.0-17-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 19 23:07:45 2019
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2015-07-19 (1431 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to disco on 2019-06-19 (0 days ago)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833471

Title:
  Can not enable Wifi Hotspot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1833471/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1832653] [NEW] ejabberd fails to work after upgrade of openssl to v1.1.1 in Ubuntu 18.04 LTS

2019-06-12 Thread Marcel

Public bug reported:

Since Ubuntu 18.04 LTS received the upgrade of openssl to version
1.1.1-1ubuntu2.1~18.04.1, ejabberd fails to work.

Attemptions to connect with a client, result in the following warning found in 
ejabberd.log:
Failed to secure c2s connection: TLS failed: client renegotiations forbidden

This seems to result from ejabberd 18.01-2 being incompatible with openssl 
1.1.1, as also reported under the following links:
https://github.com/processone/ejabberd/issues/2614
https://bugs.archlinux.org/task/60154

** Affects: ejabberd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832653

Title:
  ejabberd fails to work after upgrade of openssl to v1.1.1 in Ubuntu
  18.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1832653/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822581] Re: HP 1030 G3 fn-keys not working

2019-05-08 Thread Marcel Munce

Any other idea?

As and additional information: 
On Windows, the keys don't work either right away. A special driver is 
neccessary.
So I guess it's possible to modify the kernel module to generate the right 
events, isn't it?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822581

Title:
  HP 1030 G3 fn-keys not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822581] Re: HP 1030 G3 fn-keys not working

2019-04-26 Thread Marcel Munce

Same. No Output for those keys.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822581

Title:
  HP 1030 G3 fn-keys not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822581] Re: HP 1030 G3 fn-keys not working

2019-04-23 Thread Marcel Munce

HP WMI does generate any output at all for the fn Keys. (Volume seems to
be handled by ACPI, since acpi_listen shows those events)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822581

Title:
  HP 1030 G3 fn-keys not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822581] Re: HP 1030 G3 fn-keys not working

2019-04-23 Thread Marcel Munce

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+attachment/5258155/+files/acpidump.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822581

Title:
  HP 1030 G3 fn-keys not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822581] Re: HP 1030 G3 fn-keys not working

2019-04-22 Thread Marcel Munce

Here is the output.
I chose the keyboard output since the hp modules didn't generate any output.
The events for VOLUME_UP, VOLUME_DOWN and MUTE are working as expected.
The last two outputs are of the BRIGHTNESS_UP and _DOWN combinations (FN+F4 and 
FN+F3) and seem to be exactly the same

** Attachment added: "evtest.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+attachment/5257850/+files/evtest.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822581

Title:
  HP 1030 G3 fn-keys not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822581] Re: HP 1030 G3 fn-keys not working

Running scancode -s showed, that there is no scancode passed for those
combinations.

Maybe this correlates with errors produced by the hp_wmi module
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758442)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822581

Title:
  HP 1030 G3 fn-keys not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1806681] Re: hp_wmi: query 0xd returned error 0x5

Possibility that this error results in some hotkey combinations (brightness 
up/down) not working?
The corresponding combinations create no scan code. 
And hence there not handled by ACPI maybe it's related to the hp_wmi module?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806681

Title:
  hp_wmi: query 0xd returned error 0x5

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1806681/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822581] Re: HP 1030 G3 fn-keys not working

** Package changed: systemd (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822581

Title:
  HP 1030 G3 fn-keys not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]