Public bug reported:
The problem only exist with (all conditions must be true)
- Ubuntu 22.04.4 LTS
- kernel >= 6.5.0-14 (6.5.0-14 ist the oldes 6.5 I found in the repos)
- mounted share from a Fritz-Box (works on mount from another linux PC)
If I use kernel 6.2.0-39 (that's the newest Kernel
Public bug reported:
Ubuntu Version 22.04 LTS
Packages: RabbitVCS... & python-dulwich (full version infos below)
Starting this month I notice that the menu entries of RabbitVCS inside nautilus
disapears...
Some inverstigations indicate that it's because I look into a repo working
copy, that
I had already found the reason for this behavior!
The only change in the "drivers/base/power/" Subdirectory is inside main.c line
192.
There is a "while loop" that loops over a list (dpm_list).
The (principal) task of this loop is to call "device_prepare" on every
list-element.
Every element
Public bug reported:
As stated in the summary, my PC can't suspend anymore after kernel upgrade.
When I click suspend from desktop:
- The screen gets blank
- (sometimes) Screen then shows up for a short time, then gets blank again
- Now PC ist "dead", no reaction an keyboard, mouse and so on.
-
I don't know what happens. Because I had installed Version 20.04.1 prior I had
to reinstall a dsk image of my former system and althougth reinstall grub2...
I then update package by package and everything works as it should be..
Very corious, but now all seams to be OK..
Maybe the real reason of
Today I had donloaded the ubuntu-20.04.1-desktop-amd64.io and do a fresh
install.
unfortunaly the problem exist there too :-(
I will do some more tests and inform You about the findings..
(will take some time...)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
That's something I already tried (removing the NV driver), but that didn't help
either.
I belive that some part of the tools needed for kernel preparation is broken..
I will try the instalation of Ubuntu 20.4 LTS next weekend.
As far as I could see now all programms I use are available for this
OMG, Your comment: "#19 and forward assume..."
Points into the right direction.
When I install the "good" kernel-DEBs You provided the problem pops up...
This happens although the "real" kernel deb
(linux-image-unsigned-5.3.0-61-generic_5.3.0-61.55_amd64.deb) was not installed
due to conflicts
OK, Result for #30: BAD
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888570
Title:
poweroff not working after apt upgrade
To manage notifications about this bug go to:
OK, I hope I do it now right.
Instead of using apt, I use
sudo dpkg -i ./*.deb
inside the folder where I have downloaded Your files.
uname -a
Then shows me a date that is close to Your message date (so it feels OK).
The problem with the 2 extra DEBs from Msg 25 are the same, so I can't
install
Hm, the output of
sudo apt install ./*.deb
still states:
Hinweis: »linux-buildinfo-5.3.0-62-generic« wird an Stelle von
»./linux-buildinfo-5.3.0-62-generic_5.3.0-62.56_amd64.deb« gewählt.
which means (I assume) that I did not install the packages You provided,
instead I install the "normal"
After moving the DEBs
linux-cloud-tools-5.3.0-62-generic_5.3.0-62.56_amd64.deb
and
linux-tools-5.3.0-62-generic_5.3.0-62.56_amd64.deb
away.
The installation works.
I assume this is OK, because formerly You suply only 6 files, but now 8, so I
use only the same files as before.
I have to reboot
Sorry this one can't be installed.
Here is the output, in german, but I think You see what happens.
root@GNAspire:~/Schreibtisch/Temp/debs# sudo apt install ./*.deb
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen Fertig
@alexhung,
Thanks, same result: bad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888570
Title:
poweroff not working after apt upgrade
To manage notifications about this bug go to:
OK, it seams I had understood You right.
After installing the 6 deb-packages from #20 the problem still persistist.
You might now provide a kernel with the next step
Or if You tell me the correct git-repro I had to checkout to meake the steps by
my own, I will do the 8 steps myself and tell
Sorry, I did not know what exactly I havee to do now.
As far as I can see, bisect is a tool to do a binary search inside a repro to
find a commit that causes a failure (a special behaviour).
So to use it I have to have a (checked out) repro.
So I believe the commands given above (#19) must be
** 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/1888570
Title:
poweroff not working after apt upgrade
To manage notifications
Just one more information:
Befor the bug ocours I had two kernels that gets maintaind by apt: The one
without "hwe" and the newer hwe versions. Because the non HWE kernel wasn't
used (pulled in via linux-generic).
While searching the problem I found that i can remove this non used kernel by
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1888570/+attachment/5395317/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888570
Title:
I have done as sugested (call apport-collect 1888570). But this was done
while running the kernel that works. Should I install the not working
kernes and report again ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1888570/+attachment/5395319/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1888570/+attachment/5395323/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888570
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1888570/+attachment/5395324/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888570
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1888570/+attachment/5395325/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888570
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1888570/+attachment/5395322/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888570
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1888570/+attachment/5395321/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888570
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1888570/+attachment/5395316/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888570
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1888570/+attachment/5395318/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888570
apport information
** Tags added: apport-collected
** Description changed:
System-Information:
Description: Ubuntu 18.04.4 LTS
Release: 18.04
##
Working packages:
- Kernel 5.3.0.61.114
- linux-firmware 1.173.18
Problem occurs when
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1888570/+attachment/5395313/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888570
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1888570/+attachment/5395314/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1888570/+attachment/5395315/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888570
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1888570/+attachment/5395320/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
System-Information:
Description:Ubuntu 18.04.4 LTS
Release:18.04
##
Working packages:
- Kernel 5.3.0.61.114
- linux-firmware 1.173.18
Problem occurs when upgrading (anyone of) these packages
- Kernel 5.3.0-62.56
-
First: correction of some typos:
replace: 2. What have such megs to do inside boot.log ?
with: 2. What have such msgs to do inside boot.log ?
A, only after sending this bug report, I see that for whatever reason the boot
was done with:
"plymouth:debug"
Because I make a system snapshot before
Public bug reported:
System-Information:
Description:Ubuntu 14.04.6 LTS
Release:14.04
plymouth: 0.8.8-0ubuntu17.2
##
Today I had to reboot my PC bacause Libre-Office-Calc is complainig about a
"file in use by unknown..".
This file resides on
Public bug reported:
Binary package hint: synaptic
I removed some packages (network-manager * and lbnm*).
I do this the 'normal' way (remove the package, but leave the config).
After testing if everything was still OK (I use a manual config for the
network), I want to remove the config files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796236
Title:
Apply isn't possible in Paket-Manager if only removed Paketes are
marked for totaly remove
To manage notifications about this bug go
38 matches
Mail list logo
