from:"Can"

[Touch-packages] [Bug 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image

2024-04-16 Thread Talha Can Havadar

Hi Lukas,
I tested the package in your ppa with following configuration:

```
network:
ethernets:
all:
dhcp4: true
match:
name: e*
optional: true
version: 2
```

With the version `1.0-2build1` it hit the timeout even though I set all
the interfaces on my DUT(arm64) optional.

Here is the log of journalctl for relevant occurance:
```
Apr 16 11:47:11 kria systemd[1]: Starting systemd-networkd-wait-online.service 
- Wait for Network to be Configured...
Apr 16 11:49:11 kria systemd-networkd-wait-online[1055]: Timeout occurred while 
waiting for network connectivity.
Apr 16 11:49:11 kria systemd[1]: systemd-networkd-wait-online.service: Main 
process exited, code=exited, status=1/FAILURE
Apr 16 11:49:11 kria systemd[1]: systemd-networkd-wait-online.service: Failed 
with result 'exit-code'.
Apr 16 11:49:11 kria systemd[1]: Failed to start 
systemd-networkd-wait-online.service - Wait for Network to be Configured.
```

But after installing the version `1.0-2ubuntu1~ppa3`, 
`systemd-networkd-wait-online` is not triggered since all interfaces set to 
optional. Therefore no timeout
```
ubuntu@kria:~$ apt policy netplan.io
netplan.io:
  Installed: 1.0-2ubuntu1~ppa3
  Candidate: 1.0-2ubuntu1~ppa3
  Version table:
 *** 1.0-2ubuntu1~ppa3 500
500 https://ppa.launchpadcontent.net/slyon/lp2060311/ubuntu noble/main 
arm64 Packages
100 /var/lib/dpkg/status
 1.0-2build1 500
500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages
```

```
ubuntu@kria:~$ journalctl -u systemd-networkd-wait-online --no-pager -b
-- No entries --
```

It looks like the package you have fixes the issue

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2060311

Title:
  Setting "optional: true" to overcome he timeout "Job systemd-networkd-
  wait-online" does no longer work with latest noble image

Status in Netplan:
  In Progress
Status in Ubuntu on IBM z Systems:
  New
Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in netplan.io source package in Noble:
  Confirmed
Status in systemd source package in Noble:
  Confirmed

Bug description:
  Especially on s390x (but not limited to s390x) it's often the case that a 
system has network devices that are not necessarily connected during boot-up 
and one gets such a 2 min timeout:
  "Job systemd-networkd-wait-online. Start running (1min 59s / no limit)"

  In the past I could avoid that by setting "optional: true" post-install (no 
perfect, but worked),
  but this does no longer seem to work using the latest noble ISO image (Apr 
5th).

  Setting 'optional: true' in /etc/netplan/50-cloud-init.yaml looks like
  this for me:

  # This file is generated from information provided by the datasource.  Changes
  # to it will not persist across an instance reboot.  To disable cloud-init's
  # network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  ethernets:
  enP1p0s0:
  optional: true
  dhcp4: true
  enP1p0s0d1:
  optional: true
  dhcp4: true
  enP2p0s0:
  optional: true
  dhcp4: true
  enP2p0s0d1:
  optional: true
  dhcp4: true
  encc000: {}
  version: 2
  vlans:
  encc000.2653:
  addresses:
  - 10.11.12.15/24
  gateway4: 10.11.12.1
  id: 2653
  link: encc000
  nameservers:
  addresses:
  - 10.11.12.1

  ... can be set fine (also --dry-run does not moan, except about
  dhcp4).

  This worked in the past on noble, but also on older Ubuntu releases
  like jammy.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2020150] Re: no sound after selecting motherboard audio jack after headphones plugged in to front panel

2023-05-18 Thread Can Yildirim

** Description changed:

  # Symptom
  
  No sound coming from line out (motherboard jack) while headphones are
  plugged in(front panel) even after selecting Line out(motherboard jack)
  in sound settings.
  
  # Workaround
  
  run `alsamixer` in terminal
  press F6 to choose sound card
  select HD-Audio Generic
  use left/right arrow keys to select "Auto Mute Mode"
  use up/down to set to "Disabled"
  ESC to close
  run `sudo alsactl store` to save the current settings
  
  # System info
  Ubuntu 22.04 LTS
  
  I have ASUS X570 E Gaming motherboard (SupremeFX S1220A) (I'm assuming
  thats the same chip as Realtek ALC1220A)
  
  $ apt list --installed | grep alsa
  alsa-base/jammy,jammy,now 1.0.25+dfsg-0ubuntu7 all [installed,automatic]
  alsa-topology-conf/jammy,jammy,now 1.2.5.1-2 all [installed,automatic]
  alsa-ucm-conf/jammy-updates,jammy-updates,now 1.2.6.3-1ubuntu1.5 all 
[installed,automatic]
  alsa-utils/jammy,now 1.2.6-1ubuntu1 amd64 [installed,automatic]
  gstreamer1.0-alsa/jammy,now 1.20.1-1 amd64 [installed,automatic]
  
  # Personal remarks
  Auto Mute Mode on alsamixer should be disabled by default or a way to 
configure it via the Sound Settings GUI in Ubuntu
  
- I don't see any scenario where a user selected Audio output should be
+ I don't see any scenario where a user-selected Audio output should be
  muted and current behavior.
  
  the current issue I'm describing is exactly the same as "User Journey 2: 
Changing output port from panel UI"
  in this Ubuntu Design doc: 
https://docs.google.com/document/d/1Vb1jUVLoHXBK9drley6Vd5bYGguBbCTEWVcZz7R-LFI/edit#heading=h.8h8mt4f5unfz
+ 
+ # Another issue related to user experience with this same User Journey as 
above:
+ after using the workaround when the volume level on the headphones is high 
and the volume on the speakers was low, and you change the audio device from 
headphones to the speakers, the audio volume would be very loud on the speakers 
for a fraction of a second (perceived as a loud pop)

** Description changed:

  # Symptom
  
  No sound coming from line out (motherboard jack) while headphones are
  plugged in(front panel) even after selecting Line out(motherboard jack)
  in sound settings.
  
  # Workaround
  
  run `alsamixer` in terminal
  press F6 to choose sound card
  select HD-Audio Generic
  use left/right arrow keys to select "Auto Mute Mode"
  use up/down to set to "Disabled"
  ESC to close
  run `sudo alsactl store` to save the current settings
  
  # System info
  Ubuntu 22.04 LTS
  
  I have ASUS X570 E Gaming motherboard (SupremeFX S1220A) (I'm assuming
  thats the same chip as Realtek ALC1220A)
  
  $ apt list --installed | grep alsa
  alsa-base/jammy,jammy,now 1.0.25+dfsg-0ubuntu7 all [installed,automatic]
  alsa-topology-conf/jammy,jammy,now 1.2.5.1-2 all [installed,automatic]
  alsa-ucm-conf/jammy-updates,jammy-updates,now 1.2.6.3-1ubuntu1.5 all 
[installed,automatic]
  alsa-utils/jammy,now 1.2.6-1ubuntu1 amd64 [installed,automatic]
  gstreamer1.0-alsa/jammy,now 1.20.1-1 amd64 [installed,automatic]
  
  # Personal remarks
  Auto Mute Mode on alsamixer should be disabled by default or a way to 
configure it via the Sound Settings GUI in Ubuntu
  
  I don't see any scenario where a user-selected Audio output should be
  muted and current behavior.
  
- the current issue I'm describing is exactly the same as "User Journey 2: 
Changing output port from panel UI"
+ the current issue I'm describing is exactly the same as "User Journey #2: 
Changing output port from panel UI"
  in this Ubuntu Design doc: 
https://docs.google.com/document/d/1Vb1jUVLoHXBK9drley6Vd5bYGguBbCTEWVcZz7R-LFI/edit#heading=h.8h8mt4f5unfz
  
  # Another issue related to user experience with this same User Journey as 
above:
  after using the workaround when the volume level on the headphones is high 
and the volume on the speakers was low, and you change the audio device from 
headphones to the speakers, the audio volume would be very loud on the speakers 
for a fraction of a second (perceived as a loud pop)

** Description changed:

  # Symptom
  
  No sound coming from line out (motherboard jack) while headphones are
  plugged in(front panel) even after selecting Line out(motherboard jack)
  in sound settings.
  
  # Workaround
  
  run `alsamixer` in terminal
  press F6 to choose sound card
  select HD-Audio Generic
  use left/right arrow keys to select "Auto Mute Mode"
  use up/down to set to "Disabled"
  ESC to close
  run `sudo alsactl store` to save the current settings
  
  # System info
  Ubuntu 22.04 LTS
  
  I have ASUS X570 E Gaming motherboard (SupremeFX S1220A) (I'm assuming
  thats the same chip as Realtek ALC1220A)
  
  $ apt list --installed | grep alsa
  alsa-base/jammy,jammy,now 1.0.25+dfsg-0ubuntu7 all [installed,automatic]
  alsa-topology-conf/jammy,jammy,now 1.2.5.1-2 all [installed,automatic]
  alsa-ucm-conf/jammy-updates,jammy-updates,now 1.2.6.3-1ubuntu1.5 all 
[installed,automatic]
  alsa-utils/jammy,now

[Touch-packages] [Bug 2020150] [NEW] no sound after selecting motherboard audio jack after headphones plugged in to front panel

2023-05-18 Thread Can Yildirim

Public bug reported:

# Symptom

No sound coming from line out (motherboard jack) while headphones are
plugged in(front panel) even after selecting Line out(motherboard jack)
in sound settings.

# Workaround

run `alsamixer` in terminal
press F6 to choose sound card
select HD-Audio Generic
use left/right arrow keys to select "Auto Mute Mode"
use up/down to set to "Disabled"
ESC to close
run `sudo alsactl store` to save the current settings

# System info
Ubuntu 22.04 LTS

I have ASUS X570 E Gaming motherboard (SupremeFX S1220A) (I'm assuming
thats the same chip as Realtek ALC1220A)

$ apt list --installed | grep alsa
alsa-base/jammy,jammy,now 1.0.25+dfsg-0ubuntu7 all [installed,automatic]
alsa-topology-conf/jammy,jammy,now 1.2.5.1-2 all [installed,automatic]
alsa-ucm-conf/jammy-updates,jammy-updates,now 1.2.6.3-1ubuntu1.5 all 
[installed,automatic]
alsa-utils/jammy,now 1.2.6-1ubuntu1 amd64 [installed,automatic]
gstreamer1.0-alsa/jammy,now 1.20.1-1 amd64 [installed,automatic]

# Personal remarks
Auto Mute Mode on alsamixer should be disabled by default or a way to configure 
it via the Sound Settings GUI in Ubuntu

I don't see any scenario where a user selected Audio output should be
muted and current behavior.

the current issue I'm describing is exactly the same as "User Journey 2: 
Changing output port from panel UI"
in this Ubuntu Design doc: 
https://docs.google.com/document/d/1Vb1jUVLoHXBK9drley6Vd5bYGguBbCTEWVcZz7R-LFI/edit#heading=h.8h8mt4f5unfz

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: alsa headphones no-sound realtek-alc1220a sound-settings

** Tags removed: alc1220a
** Tags added: realtek-alc1220a

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2020150

Title:
  no sound after selecting motherboard audio jack after headphones
  plugged in to front panel

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  # Symptom

  No sound coming from line out (motherboard jack) while headphones are
  plugged in(front panel) even after selecting Line out(motherboard
  jack) in sound settings.

  # Workaround

  run `alsamixer` in terminal
  press F6 to choose sound card
  select HD-Audio Generic
  use left/right arrow keys to select "Auto Mute Mode"
  use up/down to set to "Disabled"
  ESC to close
  run `sudo alsactl store` to save the current settings

  # System info
  Ubuntu 22.04 LTS

  I have ASUS X570 E Gaming motherboard (SupremeFX S1220A) (I'm assuming
  thats the same chip as Realtek ALC1220A)

  $ apt list --installed | grep alsa
  alsa-base/jammy,jammy,now 1.0.25+dfsg-0ubuntu7 all [installed,automatic]
  alsa-topology-conf/jammy,jammy,now 1.2.5.1-2 all [installed,automatic]
  alsa-ucm-conf/jammy-updates,jammy-updates,now 1.2.6.3-1ubuntu1.5 all 
[installed,automatic]
  alsa-utils/jammy,now 1.2.6-1ubuntu1 amd64 [installed,automatic]
  gstreamer1.0-alsa/jammy,now 1.20.1-1 amd64 [installed,automatic]

  # Personal remarks
  Auto Mute Mode on alsamixer should be disabled by default or a way to 
configure it via the Sound Settings GUI in Ubuntu

  I don't see any scenario where a user selected Audio output should be
  muted and current behavior.

  the current issue I'm describing is exactly the same as "User Journey 2: 
Changing output port from panel UI"
  in this Ubuntu Design doc: 
https://docs.google.com/document/d/1Vb1jUVLoHXBK9drley6Vd5bYGguBbCTEWVcZz7R-LFI/edit#heading=h.8h8mt4f5unfz

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should say nothing

2023-02-02 Thread Mehmet Can Cömert

My current user experience is like following:
I just updated kept-back packages by mistake today by using apt install 
command. 
I thought it was due to a wrong mark of Manuel tag in apt and marked them with 
apt-mark auto again.
Then after a bit search in internet I realized that it is due to a phased 
update policy, which makes sense.

I think either message should not shown at all (as suggested above)
or if you want to show the list, please state somehow that this is only info 
and we do not have to do something about it, such as:
The following packages have been kept back as a part of phased update policy of 
Ubuntu:

Just stating packages are kept back, gives the impression that something
is broken in the dependency resolution.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1988819

Title:
  When apt keeps back packages due to phased updates, it should say
  nothing

Status in apt package in Ubuntu:
  Triaged

Bug description:
  After phased updates have been introduced, it may happen that apt
  upgrade shows packages as upgradable but ends up not upgrading them.
  In this case the packages are indicated as being "kept back".

  Unfortunately, the feedback provided about this to the user is not
  very informative. The user sees the packages being kept back and
  thinks something is going wrong on the system.

  When packages are kept back because of phased updates, apt should say
  so e.g., it should say that the upgrade is delayed.

  Incidentally note that aptitude does not respect phased updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.7
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Sep  6 10:05:14 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (933 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2002355] [NEW] package libssl-dev 3.0.2-0ubuntu1.7 [modified: usr/include/openssl/aes.h usr/include/openssl/asn1.h usr/include/openssl/asn1_mac.h usr/include/openssl/asn1t.h usr/

2023-01-09 Thread Ahmet Can Ustaoğlu

Public bug reported:

openssl lib

ProblemType: Package
DistroRelease: Ubuntu 22.04
ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
Uname: Linux 5.15.0-57-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.3
AptOrdering:
 libssl-dev:i386: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Jan 10 00:43:30 2023
DpkgTerminalLog:
 Preparing to unpack .../libssl-dev_3.0.2-0ubuntu1.7_i386.deb ...
 Unpacking libssl-dev:i386 (3.0.2-0ubuntu1.7) over (1.0.1f-1ubuntu2.27) ...
 [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/libssl-dev_3.0.2-0ubuntu1.7_i386.deb (--unpack):
  trying to overwrite shared '/usr/include/openssl/aes.h', which is different 
from other instances of package libssl-dev:i386
ErrorMessage: trying to overwrite shared '/usr/include/openssl/aes.h', which is 
different from other instances of package libssl-dev:i386
InstallationDate: Installed on 2023-01-03 (5 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: openssl
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package jammy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/2002355

Title:
  package libssl-dev 3.0.2-0ubuntu1.7 [modified:
  usr/include/openssl/aes.h usr/include/openssl/asn1.h
  usr/include/openssl/asn1_mac.h usr/include/openssl/asn1t.h
  usr/include/openssl/bio.h usr/include/openssl/blowfish.h
  usr/include/openssl/bn.h usr/include/openssl/buffer.h
  usr/include/openssl/camellia.h usr/include/openssl/cast.h
  usr/include/openssl/cmac.h usr/include/openssl/cms.h
  usr/include/openssl/comp.h usr/include/openssl/conf.h
  usr/include/openssl/conf_api.h usr/include/openssl/crypto.h
  usr/include/openssl/des.h usr/include/openssl/dh.h
  usr/include/openssl/dsa.h usr/include/openssl/dtls1.h
  usr/include/openssl/e_os2.h usr/include/openssl/ebcdic.h
  usr/include/openssl/ec.h usr/include/openssl/ecdh.h
  usr/include/openssl/ecdsa.h usr/include/openssl/engine.h
  usr/include/openssl/err.h usr/include/openssl/evp.h
  usr/include/openssl/hmac.h usr/include/openssl/lhash.h
  usr/include/openssl/md4.h usr/include/openssl/md5.h
  usr/include/openssl/modes.h usr/include/openssl/obj_mac.h
  usr/include/openssl/objects.h usr/include/openssl/ocsp.h
  usr/include/openssl/opensslv.h usr/include/openssl/ossl_typ.h
  usr/include/openssl/pem.h usr/include/openssl/pem2.h
  usr/include/openssl/pkcs12.h usr/include/openssl/pkcs7.h
  usr/include/openssl/rand.h usr/include/openssl/rc2.h
  usr/include/openssl/rc4.h usr/include/openssl/ripemd.h
  usr/include/openssl/rsa.h usr/include/openssl/safestack.h
  usr/include/openssl/seed.h usr/include/openssl/sha.h
  usr/include/openssl/srp.h usr/include/openssl/srtp.h
  usr/include/openssl/ssl.h usr/include/openssl/ssl2.h
  usr/include/openssl/ssl3.h usr/include/openssl/stack.h
  usr/include/openssl/symhacks.h usr/include/openssl/tls1.h
  usr/include/openssl/ts.h usr/include/openssl/txt_db.h
  usr/include/openssl/ui.h usr/include/openssl/whrlpool.h
  usr/include/openssl/x509.h usr/include/openssl/x509_vfy.h
  usr/include/openssl/x509v3.h] failed to install/upgrade: trying to
  overwrite shared '/usr/include/openssl/aes.h', which is different from
  other instances of package libssl-dev:i386

Status in openssl package in Ubuntu:
  New

Bug description:
  openssl lib

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  Uname: Linux 5.15.0-57-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  AptOrdering:
   libssl-dev:i386: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Jan 10 00:43:30 2023
  DpkgTerminalLog:
   Preparing to unpack .../libssl-dev_3.0.2-0ubuntu1.7_i386.deb ...
   Unpacking libssl-dev:i386 (3.0.2-0ubuntu1.7) over (1.0.1f-1ubuntu2.27) ...
   [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/libssl-dev_3.0.2-0ubuntu1.7_i386.deb (--unpack):
trying to overwrite shared '/usr/include/openssl/aes.h', which is different 
from other instances of package libssl-dev:i386
  ErrorMessage: trying to overwrite shared '/usr/include/openssl/aes.h', which 
is different from other instances of package libssl-dev:i386
  InstallationDate: Installed on 2023-01-03 (5 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:

[Touch-packages] [Bug 1976006] [NEW] Bluetooth sound card not detected . I can't connect to my samsung galaxy buds+ via bluetooth . But I can connect to apple mouse via bluetooth

2022-05-27 Thread Can

Public bug reported:

Bluetooth sound card not detected . I can't connect to my samsung galaxy
buds+ via bluetooth . But I can connect to apple mouse via bluetooth

Galaxy Buds + is visible in bluetooth devices, but it's switch can't be
on

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu 1545 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri May 27 22:20:45 2022
InstallationDate: Installed on 2022-04-18 (39 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/06/2018
dmi.bios.release: 1.47
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.47
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ironman_SK
dmi.board.vendor: KBL
dmi.board.version: V1.47
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.21
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:br1.47:efr1.21:svnAcer:pnAspireE5-576G:pvrV1.47:rvnKBL:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion:sku:
dmi.product.family: Aspire E 15
dmi.product.name: Aspire E5-576G
dmi.product.sku: 
dmi.product.version: V1.47
dmi.sys.vendor: Acer

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1976006

Title:
  Bluetooth sound card not detected . I can't connect to my samsung
  galaxy buds+ via bluetooth . But I can connect to apple mouse via
  bluetooth

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Bluetooth sound card not detected . I can't connect to my samsung
  galaxy buds+ via bluetooth . But I can connect to apple mouse via
  bluetooth

  Galaxy Buds + is visible in bluetooth devices, but it's switch can't
  be on

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1545 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 27 22:20:45 2022
  InstallationDate: Installed on 2022-04-18 (39 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2018
  dmi.bios.release: 1.47
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.47
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ironman_SK
  dmi.board.vendor: KBL
  dmi.board.version: V1.47
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:br1.47:efr1.21:svnAcer:pnAspireE5-576G:pvrV1.47:rvnKBL:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion:sku:
  dmi.product.family: Aspire E 15
  dmi.product.name: Aspire E5-576G
  dmi.product.sku: 
  dmi.product.version: V1.47
  dmi.sys.vendor: Acer

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1895573] Re: systemd[1]: Failed to start Process error reports when automatic reporting is enabled.

2020-09-14 Thread Mert Can Demir

Forgot the mention that I'm on 20.10, upgraded from 20.04.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1895573

Title:
  systemd[1]: Failed to start Process error reports when automatic
  reporting is enabled.

Status in apport package in Ubuntu:
  New

Bug description:
  htop always shows 100% CPU for /sbin/init/splash

  When I look the journalctl, I have always seen `systemd[1]: Failed to
  start Process error reports when automatic reporting is enabled.`
  thing.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1895573] Re: systemd[1]: Failed to start Process error reports when automatic reporting is enabled.

2020-09-14 Thread Mert Can Demir

Masking apport-autoreport.service and apport.service solves the issue.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1895573

Title:
  systemd[1]: Failed to start Process error reports when automatic
  reporting is enabled.

Status in apport package in Ubuntu:
  New

Bug description:
  htop always shows 100% CPU for /sbin/init/splash

  When I look the journalctl, I have always seen `systemd[1]: Failed to
  start Process error reports when automatic reporting is enabled.`
  thing.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1895573] [NEW] systemd[1]: Failed to start Process error reports when automatic reporting is enabled.

2020-09-14 Thread Mert Can Demir

Public bug reported:

htop always shows 100% CPU for /sbin/init/splash

When I look the journalctl, I have always seen `systemd[1]: Failed to
start Process error reports when automatic reporting is enabled.` thing.

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

** Attachment added: "journalctl_no_full.txt"
   
https://bugs.launchpad.net/bugs/1895573/+attachment/5410802/+files/journalctl_no_full.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1895573

Title:
  systemd[1]: Failed to start Process error reports when automatic
  reporting is enabled.

Status in apport package in Ubuntu:
  New

Bug description:
  htop always shows 100% CPU for /sbin/init/splash

  When I look the journalctl, I have always seen `systemd[1]: Failed to
  start Process error reports when automatic reporting is enabled.`
  thing.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1567107] Re: [Hyper-V] hyperv_keyboard module needed for Generation 2 VMs

2017-08-12 Thread can avar

** Also affects: initramfs-tools
   Importance: Undecided
   Status: New

** No longer affects: initramfs-tools

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1567107

Title:
  [Hyper-V] hyperv_keyboard module needed for Generation 2 VMs

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released

Bug description:
  Because Generation 2 virtual machines in Hyper-V are presented with a
  minimal set of EFI hardware, the kernel module "hyperv_keyboard" must
  be present to interact with the console keyboard. On systems with disk
  encryption, the user will be prompted for the key to decrypt the disk,
  but cannot enter the password because no keyboard driver is present.

  This issue appears to exist in all Ubuntu releases that support EFI
  and are therefore eligible to be used as Generation 2 VMs, most
  recently tried with the April 5 ISO of the day for 16.04 (pre-
  release).

  This module *is* present when the grub menu is presented and later when the 
kernel is fully loaded.
  FYI, if some mechanism requires a mouse or touch, the hid_hyperv module will 
also be needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1567107/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1567107] Re: [Hyper-V] hyperv_keyboard module needed for Generation 2 VMs

2017-08-12 Thread can avar

https://bugs.launchpad.net/bugs/1567107

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1567107

Title:
  [Hyper-V] hyperv_keyboard module needed for Generation 2 VMs

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released

Bug description:
  Because Generation 2 virtual machines in Hyper-V are presented with a
  minimal set of EFI hardware, the kernel module "hyperv_keyboard" must
  be present to interact with the console keyboard. On systems with disk
  encryption, the user will be prompted for the key to decrypt the disk,
  but cannot enter the password because no keyboard driver is present.

  This issue appears to exist in all Ubuntu releases that support EFI
  and are therefore eligible to be used as Generation 2 VMs, most
  recently tried with the April 5 ISO of the day for 16.04 (pre-
  release).

  This module *is* present when the grub menu is presented and later when the 
kernel is fully loaded.
  FYI, if some mechanism requires a mouse or touch, the hid_hyperv module will 
also be needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1567107/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1598556] [NEW] package isc-dhcp-client 4.3.3-5ubuntu12 failed to install/upgrade: end of file on stdin at conffile prompt

2016-07-03 Thread Can Yildiz

Public bug reported:

Error occured while doing release upgrade from 15.10 to 16.04 desktop
version

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: isc-dhcp-client 4.3.3-5ubuntu12
ProcVersionSignature: Ubuntu 4.2.0-41.48-generic 4.2.8-ckt11
Uname: Linux 4.2.0-41-generic x86_64
NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jul  3 10:45:20 2016
DhclientLeases:
 
ErrorMessage: end of file on stdin at conffile prompt
InstallationDate: Installed on 2015-09-04 (302 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-41-generic.efi.signed 
root=UUID=394a7cec-3436-4743-b236-ff62b2f11441 ro quiet splash acpi_osi= 
vt.handoff=7
SourcePackage: isc-dhcp
Title: package isc-dhcp-client 4.3.3-5ubuntu12 failed to install/upgrade: end 
of file on stdin at conffile prompt
UpgradeStatus: Upgraded to xenial on 2016-07-03 (0 days ago)
mtime.conffile..etc.dhcp.dhclient.conf: 2015-11-23T10:24:22.137341

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1598556

Title:
  package isc-dhcp-client 4.3.3-5ubuntu12 failed to install/upgrade: end
  of file on stdin at conffile prompt

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  Error occured while doing release upgrade from 15.10 to 16.04 desktop
  version

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu12
  ProcVersionSignature: Ubuntu 4.2.0-41.48-generic 4.2.8-ckt11
  Uname: Linux 4.2.0-41-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jul  3 10:45:20 2016
  DhclientLeases:
   
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2015-09-04 (302 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-41-generic.efi.signed 
root=UUID=394a7cec-3436-4743-b236-ff62b2f11441 ro quiet splash acpi_osi= 
vt.handoff=7
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-client 4.3.3-5ubuntu12 failed to install/upgrade: end 
of file on stdin at conffile prompt
  UpgradeStatus: Upgraded to xenial on 2016-07-03 (0 days ago)
  mtime.conffile..etc.dhcp.dhclient.conf: 2015-11-23T10:24:22.137341

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1598556/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume

2015-04-20 Thread Can Kavaklıoğlu

Thanks for great work. I would like to report another system this fix is
working on.

Debian on Monster Huma H3

Apparently Multicom Xishan W230S is sold in Turkey under Monster Huma
H3. You need to change the first line of the script to

SUPPORTED_SYSTEM_PRODUCT_NAMES = [W230SS, HUMA H3]

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1313904

Title:
  [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after
  suspend/resume

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  No sound in headphones jack after suspend/resume.
  But sound in headphones jack is OK after cold boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  Uname: Linux 3.15.0-031500rc2-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mik2139 F pulseaudio
   /dev/snd/controlC1:  mik2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Apr 28 23:20:59 2014
  InstallationDate: Installed on 2014-04-26 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Вбудоване аудіо - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mik2139 F pulseaudio
   /dev/snd/controlC1:  mik2139 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image

[Touch-packages] [Bug 2020150] Re: no sound after selecting motherboard audio jack after headphones plugged in to front panel

[Touch-packages] [Bug 2020150] [NEW] no sound after selecting motherboard audio jack after headphones plugged in to front panel

[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should say nothing

[Touch-packages] [Bug 2002355] [NEW] package libssl-dev 3.0.2-0ubuntu1.7 [modified: usr/include/openssl/aes.h usr/include/openssl/asn1.h usr/include/openssl/asn1_mac.h usr/include/openssl/asn1t.h usr/

[Touch-packages] [Bug 1976006] [NEW] Bluetooth sound card not detected . I can't connect to my samsung galaxy buds+ via bluetooth . But I can connect to apple mouse via bluetooth

[Touch-packages] [Bug 1895573] Re: systemd[1]: Failed to start Process error reports when automatic reporting is enabled.

[Touch-packages] [Bug 1895573] Re: systemd[1]: Failed to start Process error reports when automatic reporting is enabled.

[Touch-packages] [Bug 1895573] [NEW] systemd[1]: Failed to start Process error reports when automatic reporting is enabled.

[Touch-packages] [Bug 1567107] Re: [Hyper-V] hyperv_keyboard module needed for Generation 2 VMs

[Touch-packages] [Bug 1567107] Re: [Hyper-V] hyperv_keyboard module needed for Generation 2 VMs

[Touch-packages] [Bug 1598556] [NEW] package isc-dhcp-client 4.3.3-5ubuntu12 failed to install/upgrade: end of file on stdin at conffile prompt

[Touch-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume

13 matches

Site Navigation

Mail list logo

Footer information