No,I can't. I has no account on the gitlab.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962093
Title:
network-manager can't connect to pppoe since version 1.35.90
To manage notifications about
apport information
** Attachment added: "nmcli-dev.txt"
https://bugs.launchpad.net/bugs/1962093/+attachment/5563320/+files/nmcli-dev.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962093
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1962093/+attachment/5563318/+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/1962093
apport information
** Attachment added: "nmcli-con.txt"
https://bugs.launchpad.net/bugs/1962093/+attachment/5563319/+files/nmcli-con.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962093
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1962093/+attachment/5563317/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962093
apport information
** Attachment added: "NetworkManager.conf.txt"
https://bugs.launchpad.net/bugs/1962093/+attachment/5563314/+files/NetworkManager.conf.txt
--
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/1962093/+attachment/5563316/+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: "NetDevice.virbr0.txt"
https://bugs.launchpad.net/bugs/1962093/+attachment/5563313/+files/NetDevice.virbr0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "PciNetwork.txt"
https://bugs.launchpad.net/bugs/1962093/+attachment/5563315/+files/PciNetwork.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962093
apport information
** Attachment added: "NetDevice.enp5s0.txt"
https://bugs.launchpad.net/bugs/1962093/+attachment/5563311/+files/NetDevice.enp5s0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "NetDevice.enp4s1.txt"
https://bugs.launchpad.net/bugs/1962093/+attachment/5563310/+files/NetDevice.enp4s1.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "NetDevice.lo.txt"
https://bugs.launchpad.net/bugs/1962093/+attachment/5563312/+files/NetDevice.lo.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/1962093/+attachment/5563309/+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/1962093
apport information
** Attachment added: "IpAddr.txt"
https://bugs.launchpad.net/bugs/1962093/+attachment/5563308/+files/IpAddr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962093
Title:
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1962093/+attachment/5563307/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected jammy
** Description changed:
System:kubuntu 22.04
I create a Dsl connection with network-manager and it works ideal before I
upgrading the network-manager from 1.35.8X to the higher.
Now I can't connect to the Dsl, the network-manager
Public bug reported:
System:kubuntu 22.04
I create a Dsl connection with network-manager and it works ideal before I
upgrading the network-manager from 1.35.8X to the higher.
Now I can't connect to the Dsl, the network-manager reports errors. I found the
messages in the syslogs as this:
Feb 24
I checked the installed packages. There isn't the boinc-app-seti, but
only the boinc-client 7.9.3+dfsg-5u1,boinc-manager and libboinc7. My
seti@home project software should download from the boinc server. So the
error is from the boinc-client, not from the boinc-app-seti.
--
You received this
Package: boinc-app-seti
Version: 8.00~svn3701-1
ubuntu 18.04 LTS
system arch:X64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771302
Title:
SETI@home: Notice from BOINC : CL file build failure
apport-collect 1771302 only show "
You are already logged in
You are already logged in as alteeno. If this is not you, please log out now."
and nothing else.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Public bug reported:
AMD Radeon R7 260X, when the boinc is running, the SETI@home reports errors
such as "SETI@home: Notice from BOINC Task
ap_13my18ac_B2_P1_00334_20180514_10124.wu_0 postponed for 180 seconds: CL file
build failure".
the einstaine@home use the same card, but no any error
I found someone issue the same problem at here:
https://ubuntuforums.org/showthread.php?t=2330710
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637028
Title:
Ejabberdctl hasn't permission.
To
Public bug reported:
In the kubuntu 14.04, the ejabberd service is working around. But upgrage to
the kubuntu 16.04, the ejabberdctl isn't working, though the ejabberd service
is still running. when use 'sudo ejabberdctl',it reports the following error:
/usr/sbin/ejabberdctl:line
Public bug reported:
I create a windows xp guest with virt-manager. For some reseason, I want to
transfer the smbios information to the guest. So I virsh edit my guest, change
the "" to "" and insert
"
I have the same problem.
dmraid -ay and exit will work, but only exit won't work(wait a long time).
--
raid not boot
https://bugs.launchpad.net/bugs/444364
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Yes, I always use dmraid (fakeraid) in ubuntu from version 6.06 to 9.10 on
serveral PCs.
But only 8.04 is working perfectly. The version 8.10, 9.04, 9.10 always boot
into the busybox, till you typing dmraid -ay and exit.
--
Raid not activated at boot
https://bugs.launchpad.net/bugs/407901
You
I have the same problem from version 8.10 to 9.10 except version 8.04 working
good.
I have 4 hdd for raid 1+0 on AMD 690G+SB650.
--
Raid not activated at boot
https://bugs.launchpad.net/bugs/407901
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I have the same problem with AMD SB650 southbridge.
--
initramfs can't find dmraid device (VIA VT6421)
https://bugs.launchpad.net/bugs/289465
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I creat /boot ext3, / xfs, /home xfs, The installer report the same error
message as above.
When I change the / from xfs to reiserfs, the installer will continue succesed.
--
XFS root filesystem - install fails with noexec or nodev error
https://bugs.launchpad.net/bugs/180157
You received this
I hava the same problem.
--
ERROR: Communication problem with ktorrent, it probably crashed.
https://bugs.launchpad.net/bugs/126378
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for ktorrent in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL
I have the same problem. When I run kvm, it report open /dev/kvm: No such file
or directory
Could not initialize KVM, will disable KVM support
--
KVM kernel interface is not loaded
https://bugs.launchpad.net/bugs/104297
You received this bug notification because you are a member of Ubuntu
Bugs,
Yes, I use the fdisk to part the raid array. And It said the entire
array has 749GB capability. So I use the Patition Manager to parted
the array. When return to kubuntu, there are several files in the
/dev/mapper. But all of them only contain 749GB capability. Because of
no enough time, I delete
I have the same problem.Here is the traceinfo:
(no debugging symbols found)
Using host libthread_db library /lib/tls/i686/cmov/libthread_db.so.1.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no
Public bug reported:
Binary package hint: dmraid
I have four 750GB sata hdd to build raid10.
In the bios, I configured the raid10 array, and It shows the size 1.5TB, but
when I installing the ubuntu by the FakeraidEdgy, at the shell the dmraid -ay
works.But It shows the raid array only have
what you means is change the menu.lst uses kernel /vmlinuz break=bottom
root=/ to replace kernel /vmlinuz break=mount root=/?
I do so, and wait about 3 minutes to entering the initramfs shell.Then I wait
about 20 Sec, nothing happened.
So I use kernel /vmlinuz break=bottom break=mount
scripts/local-top/udev not found. There are only mdrun and dmraid in the
path scripts/local-top/.
Here is the output.txt you wanted.
** Attachment added: sh -x /etc/init.d/dmraid start 2output.txt
http://librarian.launchpad.net/6935773/output.txt
--
dmraid not starting on system boot
sudo /etc/init.d/dmraid start doesn's work.
I guess that the dmraid doesn't work when system booting. Because when I add
break=mount to the kernel option in the /boot/grub/menu.lst, and run dmraid
-ay at the shell then exit when the system booting break, the dmraid works
fine. But without
I have the same problem, and sudo /etc/init.d/dmraid start doesn't work.
When I chroot to /target, run dpkg-reconfigure --all, it report acpid: can't
open /proc/acpi/event: Device or resource busy
invoke-rc.d: initscript acpid, action 'start' failed.
--
dmraid not starting on system boot
38 matches
Mail list logo
