950...@bugs.launchpad.net>
wrote:
>Hey Tommy, I'm in a similar boot to Frederick.
>Thanks for taking the time to list your steps.
>What command did you use to unpack your initrd?
>After copying over the drivers what command or tool did you use to repack it?
>Was it dr
* Mount the iso, find the kernel modules alternatively install the kernel
modules for the same kernel on your ws.
* Unpack the initrd
* Copy over kernel/drivers/net/usb
* Repack initrd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I just took the kernel modules of the same version (available in apt)
and added them to the initrd on the iso. That worked fine.
On July 22, 2022 9:51:42 PM GMT+02:00, Franklin Kramer
<1950...@bugs.launchpad.net> wrote:
>Does anyone have any workarounds for getting usb ethernet ipxe working
>on
** Description changed:
- Initramfs taken from the live iso for PXE boot does not contain USB NIC
+ initrd taken from the live iso for PXE boot does not contain USB NIC
drivers which makes PXE installation/netboot impossible via usb.
+
+ This is the case on 20.04 server iso (both hwe and
Public bug reported:
Initramfs taken from the live iso for PXE boot does not contain USB NIC
drivers which makes PXE installation/netboot impossible via usb.
"kernel/drivers/net/usb" is empty and needs to be included in the
initramfs build.
As most modern thin laptops lack physical rj45
couldN’T, grr
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1921664
Title:
Recent update broke qemu-system-riscv64
Status in binutils package in Ubuntu:
New
Status
That would explain why I could reproduce with personal builds. Glibc
looks very relevant here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1921664
Title:
Recent
UPDATE: On a freshly installed Bionic (minimal install) system I also
had to install libusb-0.1-4
This procedure worked for me to get a Brother DCP-7020 scanner working in
Ubuntu 18.04 Bionic.
For this procedure the user is "bob"
1) Install the latest brscan2 package (I have
Public bug reported:
In Ubuntu 19.04 (and likely earlier) Modem Manager is installed with
filter policy 'strict' as opposed to 'default', which actually makes
Modem Manager _less_ strict regarding explicitly blacklisted ttys (see
man modemmanager).
This means that ttys, that are explicitly
Here's a procedure that worked for me in Ubuntu 18.04 Bionic.
For this procedure the user is "bob"
1) Install the latest brscan2 package (I have brscan2-0.2.5-1.amd64.deb
which I downloaded in 2014)
2) Manually link the drivers brscan2 installed into /usr/lib/x86_64
-linux-gnu/sane/ and
I just upgraded to from Xenial 16.04 to Bionic 18.04 and unfortunately
the scanner broke again.
Unfortunately the changes affect two places -- udev seems to have made
big changes to the scanner section, so I wrote a completely new udev
file, and the sane-dll backend doesn't look in the same
I have the same problem and it looks like this issue brings my server in
real trouble. I deactivated this services completly now and hope it
helps.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
Public bug reported:
When i try to boot a HP laptop, 15-CB011NO, from a USB stick with Ubuntu
18.04 it boots and shows directly the desktop, but then I can not take
any further actions. The mouse moves the cursor but nothing happens when
I click.
I have followed the recommendations what to
Public bug reported:
Since I upgraded to Ubuntu 18.04 I get
~$ openssl des3 -d /tmp/loesenord.htm
enter des-ede3-cbc decryption password:
bad decrypt
140555004862912:error:06065064:digital envelope
routines:EVP_DecryptFinal_ex:bad decrypt:../crypto/evp/evp_enc.c:536:
The encryption was done
I even tried to manually load the module with modeset=1, yes.
Will have to try again, maybe there has been a change since I last tried that
fixes it. But I'm sceptical.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
What do you mean when you say it's working? On 17.10 the display just
freezes when I load the nvidia driver 378 or 384 with modeset=1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
Ubuntu:
New
Bug description:
The URL file:///media/OS/Users/Tommy/Documents/index.html results in
"Network Error It appears you are having trouble viewing:
file:///media/OS/Users/Tommy/Documents/index.html. Please check your
network settings and try refreshing the page." in the Ub
Public bug reported:
The URL file:///media/OS/Users/Tommy/Documents/index.html results in
"Network Error It appears you are having trouble viewing:
file:///media/OS/Users/Tommy/Documents/index.html. Please check your
network settings and try refreshing the page." in the Ubuntu W
Public bug reported:
emacs second top menu line with icons empty.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic i686
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
I just upgraded to Xenial and the situation is the same. However I
wanted to note that the script in comment #27 didn't work for me.
Here's a procedure to get the brscan2 package work in Ubuntu Trusty or
Xenial:
1) Install the latest brscan2 package (I have brscan2-0.2.5-1.amd64.deb
)
2) Copy
Apparently this is not a solved problem, as my fresh 16.04 install hangs on
shutdown with NFS drives mounted.
My fstab:
10.10.10.10:/media/storage1 /nasnfs
noauto,x-systemd.automount,soft,timeo=20,retrans=10 0 0
Un-mounting before shutdown makes it shutdown correctly.
Is
*** This bug is a duplicate of bug 1438612 ***
https://bugs.launchpad.net/bugs/1438612
Hi Hasan,
As you can see, this bug is duplicate. Please make your comment and
"this bug affects me" indication on the other bug.
--
You received this bug notification because you are a member of Ubuntu
with the comments on the "wrong" kernel I had a different scramble
pattern in comment #16 but then just like in #31, comment #17 actually
suspended the laptop with the same pattern of flicker it "normally" does
after resuming from a suspend.
--
You received this bug notification because you are
of all of those suspend attempts, the only one that triggered the
scrambled flickering display was the one where it actually suspended:
comment #31.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Xorg.0.log
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588739/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Xorg.0.log.old
** Attachment added: "Xorg.0.log.old"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588740/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
done for now
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1552417
Title:
[X1100] Flickering after resume from RAM
Status in xorg package in Ubuntu:
Incomplete
Bug
step 10
none
laptop did go into suspend using shell command and I resumed by pressing
keys on the keyboard.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588736/+files/dmesg.txt
--
You received this bug notification because you
step 5
freezer
laptop did not suspend using the shell command so I also chose the
Suspend command from the Gear menu, which triggered a partial suspend
and self-resume (screen went black but power light did not go out and
fan did not stop and screen did not get scrambled)
** Attachment added:
step 9
core
same as before ; no real suspend. shell command then Suspend from gear
menu
launchpad is reporting a timeout error so I"m having trouble attaching dmesg
** Attachment added: "dmesg.txt"
step 8
processors
just like before, no real suspend, no screen issues. Issued shell
command and when it finished chose Suspend from gear menu
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588727/+files/dmesg.txt
--
You received
step 7
platform
just like before, no real suspend, no screen issues. Issued shell
command and when it finished (screen lit up again) and chose Suspend
from gear menu with same result
** Attachment added: "dmesg.txt"
step 6
devices
just like before, shell command did not fully suspend, and neither did choosing
Suspend from Gear menu, but I did both.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588725/+files/dmesg.txt
--
You received this bug
step 11
suspend stats
** Attachment added: "suspend_stats.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588737/+files/suspend_stats.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
merle@AcerA5100:~$ uname -a
Linux AcerA5100 4.5.0-040500rc6-generic #201602281230 SMP Sun Feb 28 17:33:02
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Step 4 wakeup
** Attachment added: "wakeup"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588712/+files/wakeup
--
I see now; I should use the http://kernel.ubuntu.com/~kernel-
ppa/mainline/?C=N;O=D link and I should ignore the
http://people.canonical.com/~kernel/info/kernel-version-map.html
SO I just got back and I will download http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.5-rc6-wily/
--
You received
Yes I followed that link, which identified the mainline kernel 4.4.3 as
the one for xenial. Please tell me which kernel I should have installed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
done for now
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1552417
Title:
[X1100] Flickering after resume from RAM
Status in xorg package in Ubuntu:
Incomplete
Bug
stats (step 11)
** Attachment added: "stats.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588449/+files/stats.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
/var/log/Xorg.0.log.old
** Attachment added: "Xorg.0.log.old"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588451/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in
/var/log/Xorg.0.log (step 12)
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588450/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in
echo none (step 10)
This time entering the sudo sh -c "sync && echo 1 > /sys/power/pm_trace
&& pm-suspend"
command DID actually suspend the laptop, and I resumed the laptop by
pressing a key on the keyboard.
Now the screen is scrambled as it "normally" does after a suspend.
** Attachment
core (step 9)
this time, while the laptop never seemed to go into suspend, the display
is scrambled (I am entering this via vnc). The scramble is in a
different pattern (more consistent than the usual post-suspend scramble)
** Attachment added: "dmesg.txt"
processors (stop 8)
the laptop still did not actually suspend (the screen blanks and
restores but suspend never happens)
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588442/+files/dmesg.txt
--
You received this bug notification
echo platform (step 7)
the laptop still did not suspend
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588441/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
this time I tried issuing the command then choosing Suspend from the
menu then pressing power and choosing suspend from the graphical suspend
button and then I tried holding down the lid switch for many seconds
the laptop will not go into suspend.
** Attachment added: "dmesg.txt"
echo devices (step 6)
the laptop is still not going into suspend
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588440/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
second attempt at step 5
the laptop never actually suspended after issuing
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
so I chose Suspend from the gear menu and the screen blanked briefly and
still did not suspend
** Attachment added: "second attempt"
Installed xenial from a recent daily image
consulted https://wiki.ubuntu.com/Kernel/MainlineBuilds
and selected kernel 4.4.3
Installed kernel using these 3 packages
linux-headers-4.4.3-040403_4.4.3-040403.201602251634_all.deb
oops sorry I need to redo step 5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1552417
Title:
[X1100] Flickering after resume from RAM
Status in xorg package in Ubuntu:
step 4 wakeup file
** Attachment added: "wakeup file step 4"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588422/+files/wakeup
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
step 5
** Attachment added: "dmesg step 5"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588423/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Installed xenial from a recent daily image
consulted https://wiki.ubuntu.com/Kernel/MainlineBuilds
and selected kernel 4.4.3
Installed kernel using these 3 packages
linux-headers-4.4.3-040403_4.4.3-040403.201602251634_all.deb
I believe I can do this, however it will take quite a bit more
preparation and effort (because of the radeon Xpress 1100 bug I cannot
use the display on this laptop after any successful resume from suspend)
I am also testing from a live image with no persistent storage, so I
will need to do
I just booted from today's (02 March 2016) xenial-desktop-amd64.iso. I
had trouble getting the machine to suspend, but once it did and resumed
from suspend, it showed the same flickering screen behavior.
If you need an apport bug collection or any other data from this image,
it should work. Let
Public bug reported:
Same defect as old Bug #318325
same hardware as Bug #1333697
System : Ubuntu 15.10 "wily"
GPU : ATI express X1100
Video driver : radeon
Steps to reproduce :
- choose suspend
- resume from ram
=> the screen will flicker while CPU activity is not high
workaround :
- launch
I have the same hardware as reported in Bug #1333697
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/318325
Title:
[X1100] flickering after resume from ram
Status in xorg
I can confirm the bug still exists in Trusty, and I just tried a Wily
live image and it exists there, too. The affected hardware is getting a
bit old but still seems to work fine with Ubuntu in all other ways.
As I am not Id2ndR should I run apport-collect on a new bug and mark it
as a duplicate
Public bug reported:
I was doing a regular `sudo apt-get update sudo apt-get dist-upgrade`
when it failed for some reason.
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: libqt5webkit5 (not installed)
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux
I'm not against the highlighting of trailing whitespace, most of the
time i do actually want to be notified of it. The problem is that the
syntax highlighting code considers all spaces to be trailing
whitespace while the user is typing them. It's like a bell going off
every time you press the
Why would this flashing behaviour ever be a desirable default?
On 26/03/15 01:12, Benno Schulenberg wrote:
If the trailing-whitespace highlighting annoys you, you can edit
/usr/share/nano/sh.nanorc and remove or comment out the line that says:
color ,green [[:space:]]+$. Problem solved. (You
IN case anyone is tracking this bug -- I wasn't able to use Unity in
14.04 LTS at all with this card because there's no longer a 2D fallback.
I was tired of getting messages warning about losing hardware support
for the 12.04 kernels.
SO I finally worked around the problem by removing the ATI
I have this exact same bug happen in my app: https://github.com/Nevon
/Ubuntu-Dota-2-Match-Ticker
Steps to reproduce:
1. Scroll down in the match ListView until the header disappears
2. Tap on a match in the list
3. Now the header on the new page is missing
If you open a different app and then
Public bug reported:
When running the app on the desktop (not in an emulator), the highlight
from clicking on one of the page head sections appears to overflow (see
the attached screenshot). I don't have access to a real device or a
functioning emulator, so I can't verify if it happens there as
Public bug reported:
After upgrading to 14.10 (fresh install) my NFS drive does no longer
mounts automatically at boot when the network is up and running.
Manually running mount -a mounts the drive as expected and hacking a
mount -a command into mountall-net.conf makes my system function
normally
Public bug reported:
While editing a shell script (.sh file) nano colours trailing spaces
bright green.
It also considers spaces that have just been typed to be trailing
spaces.
This results in constant flashing bright green while typing, which is
both distracting and annoying.
It's at its
66 matches
Mail list logo
