[Bug 1811064] [NEW] warning message of cryptsetup
Public bug reported: as posted here . : https://answers.launchpad.net/ubuntu/+source/ubuntu-meta/+question/677407 https://askubuntu.com/questions/1061087/cryptsetup-warning-failed-to-detect-canonical-device-of or in 15 other places this bug has been around since 12.04 maybe it's time to do something about it? no the fstab is clean : UUID=c013eec5-803b-11e8-ba28-7085c23e997f none swap sw 0 0 UUID=beb5eb23-803b-11e8-ba28-7085c23e997f / btrfs defaults 0 0 UUID=c013eec4-803b-11e8-ba28-7085c23e997f /srv xfs defaults 0 0 UUID=beb5eb22-803b-11e8-ba28-7085c23e997f /boot ext4 defaults 0 0 UUID=beb5eb24-803b-11e8-ba28-7085c23e997f /home ext4 defaults 0 0 UUID=78c4371d-5fc9-415f-a8a8-ba4a40cca1b6 /var/lib/docker btrfs defaults0 1 UUID=b7cc90c8-d941-412c-bb51-e15b2a62e13b /media/stock ext4defaults 0 2 and some NFS share the expected behavior should be that it doesn't read that any crypt is reported in fstab and so cryptsetup should stay silent like explained here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671056 if the user need to say something to cryptsetup to tell it that it shouldn't be active for the moment or to give reference to cryptsetup to reassure it about where everything is but still doesn't need to act on anything... And yes I need overlayroot for testing and unfortunately it depends on cryptsetup. ** Affects: cryptsetup (Ubuntu) Importance: Undecided Status: New ** Also affects: cryptsetup (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811064 Title: warning message of cryptsetup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1811064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768088] Re: can't activate 2 independent reachable interface
It has been resolved with a restart of service systemd-network. still a bug or not? I guess yes since netplan shoulkd apply directly the policy and create them. ** Description changed: + ubuntu: 18.04 + systemd: + Installed: 237-3ubuntu10 + Candidate: 237-3ubuntu10 + netplan.io: + Installed: 0.36.1 + Candidate: 0.36.1 + network: - version: 2 - renderer: networkd - ethernets: - ens3: - addresses: [192.168.3.30/25] - dhcp4: no - routes: -- to: 0.0.0.0/0 - via: 192.168.3.1 - metric: 100 - table: 101 + version: 2 + renderer: networkd + ethernets: + ens3: + addresses: [192.168.3.30/25] + dhcp4: no + routes: + - to: 0.0.0.0/0 + via: 192.168.3.1 + metric: 100 + table: 101 - routing-policy: -- from: 192.168.3.0/25 - table: 101 + routing-policy: + - from: 192.168.3.0/25 + table: 101 - ens7: - addresses: [192.168.5.24/25] - dhcp4: no - gateway4: 192.168.5.1 - nameservers: - addresses: [1.1.1.1] + ens7: + addresses: [192.168.5.24/25] + dhcp4: no + gateway4: 192.168.5.1 + nameservers: + addresses: [1.1.1.1] this doesn't activate a proper rule for table 101: - 0: from all lookup local - 32766: from all lookup main - 32767: from all lookup default + 0: from all lookup local + 32766: from all lookup main + 32767: from all lookup default - in place of - 0: from all lookup local + in place of + 0: from all lookup local 32765: from 192.168.3.0/25 lookup 101 - 32766: from all lookup main - 32767: from all lookup default + 32766: from all lookup main + 32767: from all lookup default - - the file in /etc/systemd/network contains the correct information: + the file in /etc/systemd/network contains the correct information: [Match] Name=ens3 [Network] Address=192.168.3.30/25 [Route] Destination=0.0.0.0/0 Gateway=192.168.3.1 Metric=100 Table=101 [RoutingPolicyRule] From=192.168.3.0/25 Table=101 the ens3 is reachable from 3.0 but not from anywhere else - with ifupdown on another system both interfaces would be reachable from everywhere on the private subnets. + with ifupdown on another system both interfaces would be reachable from everywhere on the private subnets. up ip route add default table 101 dev enp8s0 via 192.168.3.1 up ip rule add from 192.168.3.0/25 lookup 101 down ip rule del from 192.168.3.0/25 down ip route del default table 101 via 192.168.3.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768088 Title: can't activate 2 independent reachable interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1768088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768088] [NEW] can't activate 2 independent reachable interface
Public bug reported: network: version: 2 renderer: networkd ethernets: ens3: addresses: [192.168.3.30/25] dhcp4: no routes: - to: 0.0.0.0/0 via: 192.168.3.1 metric: 100 table: 101 routing-policy: - from: 192.168.3.0/25 table: 101 ens7: addresses: [192.168.5.24/25] dhcp4: no gateway4: 192.168.5.1 nameservers: addresses: [1.1.1.1] this doesn't activate a proper rule for table 101: 0: from all lookup local 32766: from all lookup main 32767: from all lookup default in place of 0: from all lookup local 32765: from 192.168.3.0/25 lookup 101 32766: from all lookup main 32767: from all lookup default the file in /etc/systemd/network contains the correct information: [Match] Name=ens3 [Network] Address=192.168.3.30/25 [Route] Destination=0.0.0.0/0 Gateway=192.168.3.1 Metric=100 Table=101 [RoutingPolicyRule] From=192.168.3.0/25 Table=101 the ens3 is reachable from 3.0 but not from anywhere else with ifupdown on another system both interfaces would be reachable from everywhere on the private subnets. up ip route add default table 101 dev enp8s0 via 192.168.3.1 up ip rule add from 192.168.3.0/25 lookup 101 down ip rule del from 192.168.3.0/25 down ip route del default table 101 via 192.168.3.1 ** Affects: netplan.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768088 Title: can't activate 2 independent reachable interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1768088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579712] Re: Refresh hangs indefinitely, appstreamcli using 100% CPU
answers here since nobody have mentioned the 0.10 version. http://askubuntu.com/questions/854168/how-i-can-fix-appstream-cache- update-completed-but-some-metadata-was-ignored-d -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579712 Title: Refresh hangs indefinitely, appstreamcli using 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1579712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579712] Re: Refresh hangs indefinitely, appstreamcli using 100% CPU
vigilian@docker:/tmp/asfix$ sudo dpkg -i *.deb (Lecture de la base de données... 234098 fichiers et répertoires déjà installés.) Préparation du dépaquetage de appstream_0.9.4-1ubuntu1_amd64.deb ... Dépaquetage de appstream (0.9.4-1ubuntu1) sur (0.9.4-1ubuntu1) ... Préparation du dépaquetage de libappstream3_0.9.4-1ubuntu1_amd64.deb ... Dépaquetage de libappstream3:amd64 (0.9.4-1ubuntu1) sur (0.9.4-1ubuntu1) ... Paramétrage de libappstream3:amd64 (0.9.4-1ubuntu1) ... Paramétrage de appstream (0.9.4-1ubuntu1) ... AppStream cache update completed, but some metadata was ignored due to errors. Traitement des actions différées (« triggers ») pour man-db (2.7.5-1) ... Traitement des actions différées (« triggers ») pour libc-bin (2.23-0ubuntu5) ... vigilian@docker:/tmp/asfix$ sudo appstreamcli refresh --force AppStream cache update completed, but some metadata was ignored due to errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579712 Title: Refresh hangs indefinitely, appstreamcli using 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1579712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579712] Re: Refresh hangs indefinitely, appstreamcli using 100% CPU
even with the fix on my production server I still have some problems. : @docker:~$ sudo apt update [sudo] Mot de passe de vigilian : Atteint:1 http://ppa.launchpad.net/x2go/stable/ubuntu xenial InRelease Atteint:2 http://be.archive.ubuntu.com/ubuntu xenial InRelease Réception de:3 http://be.archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB] Atteint:4 http://download.virtualbox.org/virtualbox/debian xenial InRelease Réception de:5 http://be.archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB] Atteint:6 https://apt.dockerproject.org/repo ubuntu-xenial InRelease Réception de:7 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [441 kB] Réception de:8 http://be.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages [433 kB] Réception de:9 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 DEP-11 Metadata [303 kB] Réception de:10 http://be.archive.ubuntu.com/ubuntu xenial-updates/main DEP-11 64x64 Icons [186 kB] Réception de:11 http://be.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 DEP-11 Metadata [121 kB] Réception de:12 http://be.archive.ubuntu.com/ubuntu xenial-updates/universe DEP-11 64x64 Icons [145 kB] Réception de:13 http://be.archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 DEP-11 Metadata [2.516 B] Réception de:14 http://be.archive.ubuntu.com/ubuntu xenial-backports/main amd64 DEP-11 Metadata [208 B] Réception de:15 http://be.archive.ubuntu.com/ubuntu xenial-backports/universe amd64 DEP-11 Metadata [212 B] Réception de:16 http://be.archive.ubuntu.com/ubuntu xenial-backports/multiverse amd64 DEP-11 Metadata [212 B] Réception de:17 https://download.01.org/gfx/ubuntu/16.04/main xenial InRelease [3.651 B] Réception de:18 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB] Réception de:19 http://security.ubuntu.com/ubuntu xenial-security/main amd64 DEP-11 Metadata [68,2 kB] Réception de:20 http://security.ubuntu.com/ubuntu xenial-security/main DEP-11 64x64 Icons [48,0 kB] Réception de:21 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 DEP-11 Metadata [19,4 kB] Réception de:22 http://security.ubuntu.com/ubuntu xenial-security/universe DEP-11 64x64 Icons [25,6 kB] Réception de:23 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 DEP-11 Metadata [212 B] 2.103 ko réceptionnés en 5s (392 ko/s) AppStream cache update completed, but some metadata was ignored due to errors. Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait All packages are up to date. W: https://download.01.org/gfx/ubuntu/16.04/main/dists/xenial/InRelease: Signature by key 09D6EF97BFB38E916EF060E756A3DEF863961D39 uses weak digest algorithm (SHA1) vigilian@docker:~$ sudo apt dist-upgrade Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Calcul de la mise à jour... Fait 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour. @docker:~$ sudo apt update Atteint:1 http://ppa.launchpad.net/x2go/stable/ubuntu xenial InRelease Atteint:2 http://download.virtualbox.org/virtualbox/debian xenial InRelease Atteint:3 http://be.archive.ubuntu.com/ubuntu xenial InRelease Atteint:4 http://be.archive.ubuntu.com/ubuntu xenial-updates InRelease Atteint:5 http://be.archive.ubuntu.com/ubuntu xenial-backports InRelease Atteint:6 https://apt.dockerproject.org/repo ubuntu-xenial InRelease Réception de:7 https://download.01.org/gfx/ubuntu/16.04/main xenial InRelease [3.651 B] Atteint:8 http://security.ubuntu.com/ubuntu xenial-security InRelease 3.651 o réceptionnés en 0s (4.899 o/s) Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait All packages are up to date. W: https://download.01.org/gfx/ubuntu/16.04/main/dists/xenial/InRelease: Signature by key 09D6EF97BFB38E916EF060E756A3DEF863961D39 uses weak digest algorithm (SHA1) as you see I still have this bug but not all the time. I've already
RE: [Bug 1575248] Re: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update"
Ok. Does that joepardize the instalaltion or not? -Message d'origine- De : boun...@canonical.com [mailto:boun...@canonical.com] De la part de Krino Hoogestraat Envoyé : lundi 28 novembre 2016 19:27 À : c_cromph...@hotmail.com Objet : [Bug 1575248] Re: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update" Bug still persists after update: 20161128 18:00 GMT. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1575248 Title: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update" To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1575248/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575248 Title: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update" To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1575248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically
I don't have any mail monitoring Atteint:1 http://ppa.launchpad.net/x2go/stable/ubuntu xenial InRelease Atteint:2 http://be.archive.ubuntu.com/ubuntu xenial InRelease Réception de:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB] Atteint:4 http://download.virtualbox.org/virtualbox/debian xenial InRelease Réception de:5 http://be.archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB] Réception de:6 http://be.archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB] Atteint:7 https://apt.dockerproject.org/repo ubuntu-xenial InRelease Réception de:8 http://security.ubuntu.com/ubuntu xenial-security/main amd64 DEP-11 Metadata [66,9 kB] Réception de:9 http://security.ubuntu.com/ubuntu xenial-security/main DEP-11 64x64 Icons [43,3 kB] Réception de:10 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 DEP-11 Metadata [19,4 kB] Réception de:11 http://security.ubuntu.com/ubuntu xenial-security/universe DEP-11 64x64 Icons [25,6 kB] Réception de:12 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 DEP-11 Metadata [212 B] Réception de:13 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 DEP-11 Metadata [293 kB] Réception de:14 http://be.archive.ubuntu.com/ubuntu xenial-updates/main DEP-11 64x64 Icons [182 kB] Réception de:15 http://be.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 DEP-11 Metadata [119 kB] Réception de:16 http://be.archive.ubuntu.com/ubuntu xenial-updates/universe DEP-11 64x64 Icons [137 kB] Réception de:17 http://be.archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 DEP-11 Metadata [2.520 B] Réception de:18 http://be.archive.ubuntu.com/ubuntu xenial-backports/main amd64 DEP-11 Metadata [208 B] Réception de:19 http://be.archive.ubuntu.com/ubuntu xenial-backports/universe amd64 DEP-11 Metadata [212 B] Réception de:20 http://be.archive.ubuntu.com/ubuntu xenial-backports/multiverse amd64 DEP-11 Metadata [212 B] Réception de:21 https://download.01.org/gfx/ubuntu/16.04/main xenial InRelease [3.651 B] 1.200 ko réceptionnés en 0s (1.221 ko/s) AppStream cache update completed, but some metadata was ignored due to errors. Lecture des listes de paquets... Fait W: https://download.01.org/gfx/ubuntu/16.04/main/dists/xenial/InRelease: Signature by key 09D6EF97BFB38E916EF060E756A3DEF863961D39 uses weak digest algorithm (SHA1) So I don't know your patch is already deployed but seems not -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644498 Title: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1644498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638210] [NEW] saidar segmentation fault
Public bug reported: Erreur de segmentation (core dumped) ** Affects: libstatgrab (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638210 Title: saidar segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libstatgrab/+bug/1638210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990214] Re: Wrong keyboard layout by graphical login
how can't it be a priority number one it stills sucks on 14.04.3 and 15.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990214 Title: Wrong keyboard layout by graphical login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/990214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 828731] Re: kdump functionality not working as expected when /boot is a separate partition
same bug than before in trusty. /boot on sde5 and / is on sdd2 can you release a fix please. I need to evaluate my kernel panic FAST! thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/828731 Title: kdump functionality not working as expected when /boot is a separate partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/828731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1001177] [NEW] compiz desktop wall problem with edge flipping
Public bug reported: Hi, My system 12.04 Since the update of two or three days ago, compiz has jsut been reconfigured or something because - edge flipping doesn t work anymore at all, - I can´t drag a window when i m viewing all the workspaces on my screen from one to another, - the windows in the workspace, on the presentation fo all the workspaces, are presented in a clean distinct presentation of each window,( don t know how to describe otherwise), - Eve if I replace unity or if I activate or deactivate desktop wall in compiz I don t think that it doesn t change a thing. So for me clearly the package is broken or something ** Affects: compiz-core Importance: Undecided Status: New ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: compiz desktopwall unityz ** Also affects: compiz-core Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1001177 Title: compiz desktop wall problem with edge flipping To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-core/+bug/1001177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1001183] [NEW] can reach console mode + nvidia current
Public bug reported: Since I ve installed the nvidia current or even if I try to install the nvidia drivers manually, I can reach the console mode anymore ... All I can get is a graphical problem ä line of color. My system 12.04 ** Affects: ubuntu Importance: Undecided Status: New ** Description changed: - Since I ve installed the nvidia current or even if I try to install the - nvidia drivers manually, I can reach the console mode anymore ... All I - can get is a graphical problem ä line of color + Since I ve installed the nvidia current or even if I try to install the nvidia drivers manually, I can reach the console mode anymore ... All I can get is a graphical problem ä line of color. + My system 12.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1001183 Title: can reach console mode + nvidia current To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1001183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1001177] Re: compiz desktop wall problem with edge flipping
seems resolved with a fresh installation of the nvidia drivers-current -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1001177 Title: compiz desktop wall problem with edge flipping To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-core/+bug/1001177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1001183] Re: can reach console mode + nvidia current
Discussion for more information -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1001183 Title: can't reach console mode TTY + nvidia current To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1001183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1001183] Re: can reach console mode + nvidia current
https://answers.launchpad.net/ubuntu/+question/197677 Link ** Summary changed: - can reach console mode + nvidia current + can't reach console mode TTY + nvidia current -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1001183 Title: can't reach console mode TTY + nvidia current To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1001183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68355] Re: no boot on a P4
conflict when I upgrade to edgy. The system of upgrade didn't uninstall the 686 version completely. So, some component like linux-686 and linux headers were installed. Uninstall it and the problem will be solved. ** Changed in: linux-source-2.6.17 (Ubuntu) Assignee: (unassigned) = vigilian Status: Unconfirmed = Fix Committed -- no boot on a P4 https://launchpad.net/bugs/68355 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68355] no boot on a P4
Public bug reported: Binary package hint: linux-image-2.6.17-10-generic - Update from dapper to edgy with the gksudo command-line - configuration hardware: - P4 2.0ghz northwood core - dell dimension 8200 (RDRAM) - The update install the 2 version of the kernel (i386 and generic), I tried to boot on the generic but it blocks on the loading of ACPI index it's the only line on the screen of usplash. - I go to ALT+F1 screen and I see 2 errors: it doesn't find the mdadm.conf and there is no screen for usplash 640*480. But the package mdadm and usplash are installed and work properly on the i386. Thanks to help ++ ** Affects: linux-source-2.6.17 (Ubuntu) Importance: Undecided Status: Unconfirmed -- no boot on a P4 https://launchpad.net/bugs/68355 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68360] don't work properly
Public bug reported: - update dapper to edgy - the tomboy start tup at the boot of gnome but there is no icon in the gnome-panel and in the menu. The ALT-F11 bindings works so I can see the list of the notes. -When I launch tomboy in the terminal there is a error message: Tomboy can not remote the dbus-message. or something like that. I will edit this message later to do a cut and paste of the message. ** Affects: tomboy (Ubuntu) Importance: Undecided Assignee: vigilian Status: Unconfirmed ** Tags added: tomboy ** Tags added: edgy ** Tags removed: tomboy -- don't work properly https://launchpad.net/bugs/68360 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68360] Re: don't work properly
sorry, wrong package ** Changed in: linux-source-2.6.17 (Ubuntu) Sourcepackagename: linux-source-2.6.17 = tomboy Assignee: (unassigned) = vigilian Status: Unconfirmed = Rejected ** Changed in: tomboy (Ubuntu) Status: Rejected = Unconfirmed -- don't work properly https://launchpad.net/bugs/68360 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
