I tried reproducing this with 2.39.2+18.04 on 18.04 by setting the
following as root:
#!/bin/bash
export LANG=en_US.UTF-8
export LC_ADDRESS=ru_RU.UTF-8
export LC_IDENTIFICATION=ru_RU.UTF-8
export LC_MEASUREMENT=ru_RU.UTF-8
export LC_MONETARY=ru_RU.UTF-8
export LC_NAME=ru_RU.UTF-8
export LC_NUMERIC
Just hit this on an Dell E5250
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753518
Title:
package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 failed to
install/upgrade: installed grub-efi-amd64-sig
Am Freitag, 29. Januar 2010 10:57:30 schrieb Harald Sitter:
> Where do you disconnect? via what toolbar?
Yes, I attached some screenshots to show what I mean. When I do
disconnect the network via the toolbar (red disconnect-button) it
immediately reconnects (behaves like a */etc/init.d/networking
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/34312579/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/34312580/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/34312581/ProcStatus.txt
--
Networ
Public bug reported:
Binary package hint: kdenetwork
- latest KDE 4.3
- Ubuntu 9.10 (latest karmic)
kdenetwork:
Installiert: 4:4.3.2-0ubuntu4
Kandidat: 4:4.3.2-0ubuntu4
Versions-Tabelle:
*** 4:4.3.2-0ubuntu4 0
wired network using dhcp:
Network always auto-reconnects after diconnecting vi
I close this bug as it is no problem in hardy anymore!
** Summary changed:
- [gutsy] network needs restart to work
+ closed: [gutsy] network needs restart to work
--
closed: [gutsy] network needs restart to work
https://bugs.launchpad.net/bugs/152285
You received this bug notification because y
My problem is solved with the latest kernel & restricted nvidia driver
update as well , so I won't open an new bug report!
Stephan
--
After update to linux-kernel-2.6.22-13 X-Server failed to load nvidia module.
https://bugs.launchpad.net/bugs/151936
You received this bug notification because yo
** Attachment added: "uname-a.log"
http://launchpadlibrarian.net/9966600/uname-a.log
--
[gutsy] network needs restart to work
https://bugs.launchpad.net/bugs/152285
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bug
** Attachment added: "version.log"
http://launchpadlibrarian.net/9966603/version.log
--
[gutsy] network needs restart to work
https://bugs.launchpad.net/bugs/152285
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bug
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/9966598/lspci-vvnn.log
--
[gutsy] network needs restart to work
https://bugs.launchpad.net/bugs/152285
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubun
Public bug reported:
I have got a new PC (asrock AliveNF7G-HDready with AMD X2 BE-2350) and
installed a dual boot feisty/gutsy 64bit system. In gutsy the first
thing I do after startup is :
sudo /etc/init.d/networking restart
or the network (dsl router) takes about two minutes to connect (for ea
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/9966597/dmesg.log
--
[gutsy] network needs restart to work
https://bugs.launchpad.net/bugs/152285
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs ma
> Nicolas Joyard: not sure this is the same bug because you have the
message "Nvidia: no matching device section", I think you should check
your xorg.conf first, it might be incorrect.
Thanks for the promt response. I checked my xorg.conf and it the relevant part
(I think) reads:
section "Device
I run gutsy on an asrock aliveNF7G-HDready motherboard (onboard
graphic: GeForce 7050; nForce 630A chipset) with the NVIDIA restricted
module (the new one for 70xx cards). Everything is fine with kernel
2.6.22-12-generic, 2.6.22-13-generic in gutsy and kernel
2.6.20-16-generic in feisty (dual boot
Am Mittwoch, 4. April 2007 00:37 schrieb Brian Murray:
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. Unfortunately we can't fix it, because your description doesn't yet
> have enough information. Please include the following additional
> information, if you ha
Public bug reported:
I installed Feisty Fawn kubuntu (daily build of 29.03.07), the system was
updated daily since then. I choose partitioning by user, letting the installer
overwrite my old partitions (/, /home, /tmp, /var, /usr and two! swap
partitions on different disks, each 500 MB large).
16 matches
Mail list logo
