[Touch-packages] [Bug 1539688] [NEW] Bluetooth stops working after the OTA9 update
Public bug reported: After the OTA9 update, the system stops working with Kenwood KCA-BT200 Bluetooth car radio adapter (handsfree+audio streaming): please check attached file for further details. Build name: OTA9 Ubuntu image part 20160123.1 Ubuntu build description: ubuntu 15.04 - armhf (20160123-115651) device image part : 20160108-ef-c96d8 device build description: VEGETA01.A-S23A_BQ_L100EN_2009_160123 Customization image part: 2016011-926-36-vivid available for further test and to supply additional details. Thanks and Regards D ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth handsfree ** Attachment added: "detailed description before/after" https://bugs.launchpad.net/bugs/1539688/+attachment/4559299/+files/160129_%20Bluetooth%20after%20the%20OTA9%20update.pdf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539688 Title: Bluetooth stops working after the OTA9 update Status in bluez package in Ubuntu: New Bug description: After the OTA9 update, the system stops working with Kenwood KCA-BT200 Bluetooth car radio adapter (handsfree+audio streaming): please check attached file for further details. Build name: OTA9 Ubuntu image part 20160123.1 Ubuntu build description: ubuntu 15.04 - armhf (20160123-115651) device image part : 20160108-ef-c96d8 device build description: VEGETA01.A-S23A_BQ_L100EN_2009_160123 Customization image part: 2016011-926-36-vivid available for further test and to supply additional details. Thanks and Regards D To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1539446] Today scope hangs-on after OTA9 update
Hello, thank you for interest. Hoping it could help. Regards & thanks. Danilo On Friday, 29 January 2016 15:08:47 CET, Kyle Nitzsche wrote: > Hi Danilo - sorry you are having this problem and thanks for reporting > it! > > If you can get the following files and attach them to the bug, > this will help debug this issue: > * /home/phablet/.cache/upstart/scope-registry.log > * Any .crash files in /var/crash/ > > Because this occurs when swiping from one scope to another, I wonder > whether this is a Unity8 problem, so I had added that to this bug. > > I have not been able to reproduce this on a BQ 4.5. My today scope is: > com.canonical.scopes.dashboard 4.1.0 > > > ** Also affects: unity8 (Ubuntu) >Importance: Undecided >Status: New > -- Sent using Dekko from my Ubuntu phone device ** Attachment added: "scope-registry.log.1.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4559475/+files/scope-registry.log.1.gz ** Attachment added: "scope-registry.log.2.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4559476/+files/scope-registry.log.2.gz ** Attachment added: "scope-registry.log.3.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4559477/+files/scope-registry.log.3.gz ** Attachment added: "scope-registry.log.4.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4559478/+files/scope-registry.log.4.gz ** Attachment added: "scope-registry.log.5.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4559479/+files/scope-registry.log.5.gz ** Attachment added: "scope-registry.log.6.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4559480/+files/scope-registry.log.6.gz ** Attachment added: "scope-registry.log.7.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4559481/+files/scope-registry.log.7.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1539446 Title: Today scope hangs-on after OTA9 update Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 available for testing and further info supply Regards and thanks To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1539446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1539446] Today scope hangs-on after OTA9 update
Splitted sending. Dekko is hanging if too much files are attached to each message. BR. Danilo On Friday, 29 January 2016 15:08:47 CET, Kyle Nitzsche wrote: > Hi Danilo - sorry you are having this problem and thanks for reporting > it! > > If you can get the following files and attach them to the bug, > this will help debug this issue: > * /home/phablet/.cache/upstart/scope-registry.log > * Any .crash files in /var/crash/ > > Because this occurs when swiping from one scope to another, I wonder > whether this is a Unity8 problem, so I had added that to this bug. > > I have not been able to reproduce this on a BQ 4.5. My today scope is: > com.canonical.scopes.dashboard 4.1.0 > > > ** Also affects: unity8 (Ubuntu) >Importance: Undecided >Status: New > -- Sent using Dekko from my Ubuntu phone device ** Attachment added: "_opt_click.ubuntu.com_com.ubuntu.telegram_2.0.4.0_lib_arm-linux-gnueabihf_bin_telegram.32011.crash" https://bugs.launchpad.net/bugs/1539446/+attachment/4559487/+files/_opt_click.ubuntu.com_com.ubuntu.telegram_2.0.4.0_lib_arm-linux-gnueabihf_bin_telegram.32011.crash ** Attachment added: "_opt_click.ubuntu.com_dekko.dekkoproject_0.5.8_lib_arm-linux-gnueabihf_bin_dekko.32011.crash" https://bugs.launchpad.net/bugs/1539446/+attachment/4559488/+files/_opt_click.ubuntu.com_dekko.dekkoproject_0.5.8_lib_arm-linux-gnueabihf_bin_dekko.32011.crash ** Attachment added: "_usr_bin_mediaplayer-app.32011.crash" https://bugs.launchpad.net/bugs/1539446/+attachment/4559489/+files/_usr_bin_mediaplayer-app.32011.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1539446 Title: Today scope hangs-on after OTA9 update Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 available for testing and further info supply Regards and thanks To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1539446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1539446] Today scope hangs-on after OTA9 update
2ND sending. On Friday, 29 January 2016 15:08:47 CET, Kyle Nitzsche wrote: > Hi Danilo - sorry you are having this problem and thanks for reporting > it! > > If you can get the following files and attach them to the bug, > this will help debug this issue: > * /home/phablet/.cache/upstart/scope-registry.log > * Any .crash files in /var/crash/ > > Because this occurs when swiping from one scope to another, I wonder > whether this is a Unity8 problem, so I had added that to this bug. > > I have not been able to reproduce this on a BQ 4.5. My today scope is: > com.canonical.scopes.dashboard 4.1.0 > > > ** Also affects: unity8 (Ubuntu) >Importance: Undecided >Status: New > -- Sent using Dekko from my Ubuntu phone device -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1539446 Title: Today scope hangs-on after OTA9 update Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 available for testing and further info supply Regards and thanks To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1539446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539446] Re: Today scope hangs-on after OTA9 update
** Attachment added: "_usr_bin_system-settings.32011.crash" https://bugs.launchpad.net/bugs/1539446/+attachment/4559491/+files/_usr_bin_system-settings.32011.crash ** Attachment added: "_usr_bin_unity8-dash.32011.crash" https://bugs.launchpad.net/bugs/1539446/+attachment/4559492/+files/_usr_bin_unity8-dash.32011.crash ** Attachment added: "_usr_bin_unity8.32011.crash" https://bugs.launchpad.net/bugs/1539446/+attachment/4559493/+files/_usr_bin_unity8.32011.crash ** Attachment added: "_usr_bin_webbrowser-app.32011.crash" https://bugs.launchpad.net/bugs/1539446/+attachment/4559494/+files/_usr_bin_webbrowser-app.32011.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1539446 Title: Today scope hangs-on after OTA9 update Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 available for testing and further info supply Regards and thanks To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1539446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1539446] Today scope hangs-on after OTA9 update
Hi, Here is the file you requested. Sorry for delay in answering. Hoping it could help. On Tuesday, 9 February 2016 17:47:12 CET, Kyle Nitzsche wrote: > Hi Danlio, > > Could you please attached the "myclicks" file produced by this command: > click list > myclicks > -- Sent using Dekko from my Ubuntu phone device ** Attachment added: "myclicks" https://bugs.launchpad.net/bugs/1539446/+attachment/4568070/+files/myclicks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1539446 Title: Today scope hangs-on after OTA9 update Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 available for testing and further info supply Regards and thanks To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1539446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1539446] Today scope hangs-on after OTA9 update
Hello once again. My knoledgevabout linux systems andvubuntu is really poor, so I trust on your info. About your comments on location, it is right, my position detection & fps options are always off. Bsyyery saving and don't need it all. But I noticed that OTA9 is not allowing me to choose location services enabling anymore... Nearby scope: Really I don't remember if it was on or off at tha time. Pls tell me if I couldvhelp in a deeper way. Ciao D On Tuesday, 9 February 2016 18:16:52 CET, Kyle Nitzsche wrote: > So I continue to propose that this is not due to the Today scope. > > There are three exceptions in the scope-registry log files, here are > some comments on them. > > == 1) scope-registrylog.3 has: > Location object not found: "unity::scopes::NotFoundException: > SearchMetadata::location() (name = location)" > > This is the normal log result by Day Scope when location data is > disabled. The exception is caught, and the scope responds appropriately. > This log message should be modified to indicate the exception is handled > and it is a normal condition. > > == 2&3) scope-registrylog.1 has: > > unity::ResourceException: > /build/buildd/net-cpp-1.2.0+15.04.20150415.2/src/core/net/http/impl/curl/request.h@220 > > - operator(): Timeout was reached > query complete, status: error > > ReplyObject::push(VariantMap): > unity::InvalidArgumentException: > CategorisedResult::set_category(): Category must not be null > 522 [2016-01-29 00:01:19.303367] ERROR: unity-scope-nearby: > ReplyObject::push(): ReplyObject::push(VariantMap): > unity::InvalidArgumentException: > CategorisedResult::set_category(): Category must not be nul > > This one is a concern since a result must have a non-null category. But > this in the nearby-scope (or quite possibly one of the child scopes that > give it data), not the today scope. It appears to immediately follow a > network error. > -- Sent using Dekko from my Ubuntu phone device -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1539446 Title: Today scope hangs-on after OTA9 update Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 available for testing and further info supply Regards and thanks To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1539446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1539446] Today scope hangs-on after OTA9 update
Additional info: Also if GPS is correctly catching my position, if enabled,. Nearby scope goes on showing me a wrong position. seems that it doesn't care about real fps data or fake. Thk D On Tuesday, 9 February 2016 18:16:52 CET, Kyle Nitzsche wrote: > So I continue to propose that this is not due to the Today scope. > > There are three exceptions in the scope-registry log files, here are > some comments on them. > > == 1) scope-registrylog.3 has: > Location object not found: "unity::scopes::NotFoundException: > SearchMetadata::location() (name = location)" > > This is the normal log result by Day Scope when location data is > disabled. The exception is caught, and the scope responds appropriately. > This log message should be modified to indicate the exception is handled > and it is a normal condition. > > == 2&3) scope-registrylog.1 has: > > unity::ResourceException: > /build/buildd/net-cpp-1.2.0+15.04.20150415.2/src/core/net/http/impl/curl/request.h@220 > > - operator(): Timeout was reached > query complete, status: error > > ReplyObject::push(VariantMap): > unity::InvalidArgumentException: > CategorisedResult::set_category(): Category must not be null > 522 [2016-01-29 00:01:19.303367] ERROR: unity-scope-nearby: > ReplyObject::push(): ReplyObject::push(VariantMap): > unity::InvalidArgumentException: > CategorisedResult::set_category(): Category must not be nul > > This one is a concern since a result must have a non-null category. But > this in the nearby-scope (or quite possibly one of the child scopes that > give it data), not the today scope. It appears to immediately follow a > network error. > -- Sent using Dekko from my Ubuntu phone device -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1539446 Title: Today scope hangs-on after OTA9 update Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 available for testing and further info supply Regards and thanks To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1539446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1539446] Re: Today scope hangs-on after OTA9 update
Hi Kyle, Yes, the phone is still freezing and restarts really often ( about 3-5 times per day) it happens especially when you awake it from stby: 1- swipe the main screen, 2- tap the unlock code (4 figures mode) 3- the Today screen opens, (see below) 3alternative- sometimes else it freeezes/crashes in this alternative way: 4- Today screen opens regularly, but e.g. I want to reach the app scope (or another alternative scope instead of wait the full today's update end, so I swipe Rhs to Lhs, the screens slides really slowly and/or it doesn't move fluently smooth. It freezes, and in a short while (20secs) the Scope App restarts or the full Ubuntu boot loading screens appear. freezing at point 3: sometimes it freezes in this status White screen. only the small "bubbles" on the top screen showing which scope are you on, are showed on display. the remainin screen is White. the red bar is bouncing left-right on the screen feet). here too It freezes, and in a short while (20secs) the Scope App restarts or the full Ubuntu boot loading screens appear. Hoping to being usefull. I will try to test removing all favourite scopes and I will come back with updates Ciao D Il 09.02.2016 21:17 Kyle Nitzsche ha scritto: > Danilo, are you still seeing the freezing and restarting? What happens > if you unfavorite all your scopes: does the freeze happen if you tap the > Ubuntu logo? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1539446 [1] > > Title: > Today scope hangs-on after OTA9 update > > Status in Today Scope: > New > Status in unity8 package in Ubuntu: > New > > Bug description: > really often from Yesterday night (OTA9 updated at 11 p.m.) the Today > scope freeze the screen and no other actiion is possibile to achieve. > the system restart itself after 20-30 seconds . > > it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. > when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. > > no more possibility to acces vertical "courtains" menu > (notifications, blutooth, netwoorks a.s.o.) neither any of the other > icons. > > If you send a call to the device SIM number, you can ear (frpm the > sender device speaker) the usual network ringigng tone, but nothing > happens on the Ubuntu phone . After the self reboot, the lost call is > correctly notified on the notification menu. > > device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 > > available for testing and further info supply > > Regards and thanks > > To manage notifications about this bug go to: > https://bugs.launchpad.net/today-scope/+bug/1539446/+subscriptions [2] -- Saluti Danilo Montevecchi 349-3767797 Connetti gratis il mondo con la nuova indoona: hai la chat, le chiamate, le video chiamate e persino le chiamate di gruppo. E chiami gratis anche i numeri fissi e mobili nel mondo! Scarica subito l’app Vai su https://www.indoona.com/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1539446 Title: Today scope hangs-on after OTA9 update Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 available for testing and further info supply Regards and thanks To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1539446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1539446] Today scope hangs-on after OTA9 update
Hi Kyle I had removed all that additional scopes and using the phone in this way, I never more experienced any of the noticed hangs or freeze. I used it not so much indeed in the last days, this is thevreason 'cause it takes so long to me to answer you. Also keeping many apps / tasks active, the recalling/ awakening of the Today scope is always reactive and the app scope ( theonly one still active) recall is 100% smooth and fluid. Side effect: No possibility to give you the file you requested " just after freezing" 😉 Let we see in the short future. Cross fingers. Ciao D On Tuesday, 9 February 2016 21:17:53 CET, Kyle Nitzsche wrote: > Danilo, are you still seeing the freezing and restarting? What happens > if you unfavorite all your scopes: does the freeze happen if you tap the > Ubuntu logo? > -- Sent using Dekko from my Ubuntu phone device -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1539446 Title: Today scope hangs-on after OTA9 update Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 available for testing and further info supply Regards and thanks To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1539446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1539446] Today scope hangs-on after OTA9 update
I have it in my todo list. 😋 Step1 : Keep actual setup for a while more (end of this week? Too long?). And check if freezing still happens. Step2 : Add the previous scopes, in the same order they was before the cleaning (oops not sure about the previous order appearance. Sorry, my fault 😖 😖 ) and check device/ OS reactions. Is it OK for you too? Rgards. D On Thursday, 11 February 2016 20:27:41 CET, Kyle Nitzsche wrote: > HI Danilo, > > Awesome! But, if there is a problem, if the freeze happens again, it > would be great if you can provide the scope-registry.log file. > > Also, If you can associate a particular scope (or app) with the freeze, > that would be helpful. For example, you could try bringing back the > scopes you removed one-by-one and then seeing if there are freezes. If > so, please comment this bug. > -- Sent using Dekko from my Ubuntu phone device -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1539446 Title: Today scope hangs-on after OTA9 update Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 available for testing and further info supply Regards and thanks To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1539446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1539446] Today scope hangs-on after OTA9 update
Hi, This is the scenario: A message coming from telegram. Notification already deleted without access phone ( courtain menu). - accessed phone (4 figures code). - today scope on screen - swipe left to right. To access unity A tap on telegram icon to open it. Today scope disappear and white screen waiting for unknown event ( no rounding Ubuntu logo, neither some other vital sign.) - after around 20 secs, system reboots from the raw (Ubuntu in letters and rounding dots). Don't know if it could be related to the topic, but this is the only "strange and unusual" event of the last days, after all other scopes removal. Thanks abdicate regards. D On Wednesday, 10 February 2016 15:12:44 CET, Kyle Nitzsche wrote: > HI Danilo, > > Thanks for your responses! > > Can you please get the following file right after the "freeze" > and attach it to this bug: > /home/phablet/.cache/upstart/scope-registry.log > > Cheers > -- Sent using Dekko from my Ubuntu phone device -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1539446 Title: Today scope hangs-on after OTA9 update Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 available for testing and further info supply Regards and thanks To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1539446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539446] Re: Today scope hangs-on after OTA9 update
** Attachment added: "scope-registry.log" https://bugs.launchpad.net/bugs/1539446/+attachment/4570344/+files/scope-registry.log ** Attachment added: "scope-registry.log.1.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4570345/+files/scope-registry.log.1.gz ** Attachment added: "scope-registry.log.2.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4570346/+files/scope-registry.log.2.gz ** Attachment added: "scope-registry.log.3.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4570347/+files/scope-registry.log.3.gz ** Attachment added: "scope-registry.log.4.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4570348/+files/scope-registry.log.4.gz ** Attachment added: "scope-registry.log.5.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4570349/+files/scope-registry.log.5.gz ** Attachment added: "scope-registry.log.6.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4570350/+files/scope-registry.log.6.gz ** Attachment added: "scope-registry.log.7.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4570351/+files/scope-registry.log.7.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1539446 Title: Today scope hangs-on after OTA9 update Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 available for testing and further info supply Regards and thanks To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1539446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1539446] Re: Today scope hangs-on after OTA9 update
Hi Kyle. I'm not totally agree with your deductions. as I sad, it is the only "bad & strange event" of the last days. but: the "Today scope bug" (let me call it so, don't be scared about) happens **recalling the Today scope** (by Unity Ubuntu logo, or the floating Today window (if the all open app view is active) as well, and in both this events, the screen remain with the today scope visualized (showed) and no other activity is possible on the device. the last noticed "bug" shows a totally white screen, coming, it seems, form a "transition limbo" (a software environment, not the dance :-) ) from the Today scope (that was on the screen before) and the Telegram one (that is trying to come, but it hangs-on in a unknown way.) they are two different behaviours. Perhaps my emotional involving in being part of a developing project brought me to notice you also a mosquito landing on the screen. thinking it could be useful to solve the issue. Please apologize me. Let me know your comments about. Sorry once again. Danilo Il 12.02.2016 21:44 Kyle Nitzsche ha scritto: > Hi Danilo, thanks for the persistence and the logs and etc! > > So, several times this failure has occurred when tapping on a Unity > icon: > > * comment 18: > "- swipe left to right. To access unity > A tap on telegram icon to open it." > > * initial description: > "as well, if you touch the Ubuntu logo icon in the Unity view" > > I am thinking this means it is not related to the today scope. > > I will email some Unity engineers and bring this to their attention. > > NOTE: there is a telegram crash file (among others). > > Thanks! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1539446 [1] > > Title: > Today scope hangs-on after OTA9 update > > Status in Today Scope: > New > Status in unity8 package in Ubuntu: > New > > Bug description: > really often from Yesterday night (OTA9 updated at 11 p.m.) the Today > scope freeze the screen and no other actiion is possibile to achieve. > the system restart itself after 20-30 seconds . > > it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. > when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. > > no more possibility to acces vertical "courtains" menu > (notifications, blutooth, netwoorks a.s.o.) neither any of the other > icons. > > If you send a call to the device SIM number, you can ear (frpm the > sender device speaker) the usual network ringigng tone, but nothing > happens on the Ubuntu phone . After the self reboot, the lost call is > correctly notified on the notification menu. > > device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 > > available for testing and further info supply > > Regards and thanks > > To manage notifications about this bug go to: > https://bugs.launchpad.net/today-scope/+bug/1539446/+subscriptions [2] -- Saluti Danilo Montevecchi 349-3767797 Connetti gratis il mondo con la nuova indoona: hai la chat, le chiamate, le video chiamate e persino le chiamate di gruppo. E chiami gratis anche i numeri fissi e mobili nel mondo! Scarica subito l’app Vai su https://www.indoona.com/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1539446 Title: Today scope hangs-on after OTA9 update Status in Canonical System Image: New Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 available for testing and further info
Re: [Touch-packages] [Bug 1539446] Re: Today scope hangs-on after OTA9 update
Additional comment: - in the "Today scope bug" is the only "Scopes" app that is self restarting after a while. but: - in the noticed "today to Telegram bug" is the full system that is restarting (ubuntu letters and rounding dots) Regards D Il 12.02.2016 21:44 Kyle Nitzsche ha scritto: > Hi Danilo, thanks for the persistence and the logs and etc! > > So, several times this failure has occurred when tapping on a Unity > icon: > > * comment 18: > "- swipe left to right. To access unity > A tap on telegram icon to open it." > > * initial description: > "as well, if you touch the Ubuntu logo icon in the Unity view" > > I am thinking this means it is not related to the today scope. > > I will email some Unity engineers and bring this to their attention. > > NOTE: there is a telegram crash file (among others). > > Thanks! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1539446 [1] > > Title: > Today scope hangs-on after OTA9 update > > Status in Today Scope: > New > Status in unity8 package in Ubuntu: > New > > Bug description: > really often from Yesterday night (OTA9 updated at 11 p.m.) the Today > scope freeze the screen and no other actiion is possibile to achieve. > the system restart itself after 20-30 seconds . > > it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. > when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. > > no more possibility to acces vertical "courtains" menu > (notifications, blutooth, netwoorks a.s.o.) neither any of the other > icons. > > If you send a call to the device SIM number, you can ear (frpm the > sender device speaker) the usual network ringigng tone, but nothing > happens on the Ubuntu phone . After the self reboot, the lost call is > correctly notified on the notification menu. > > device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 > > available for testing and further info supply > > Regards and thanks > > To manage notifications about this bug go to: > https://bugs.launchpad.net/today-scope/+bug/1539446/+subscriptions [2] -- Saluti Danilo Montevecchi 349-3767797 Connetti gratis il mondo con la nuova indoona: hai la chat, le chiamate, le video chiamate e persino le chiamate di gruppo. E chiami gratis anche i numeri fissi e mobili nel mondo! Scarica subito l’app Vai su https://www.indoona.com/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1539446 Title: Today scope hangs-on after OTA9 update Status in Canonical System Image: New Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - available for testing and further info supply Regards and thanks EDIT 13feb2016 : removed Device s/n To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539446] Re: Today scope hangs-on after OTA9 update
** Description changed: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . - it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. + it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. - device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 + device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - available for testing and further info supply Regards and thanks + + EDIT 13feb2016 : removed Device s/n -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1539446 Title: Today scope hangs-on after OTA9 update Status in Canonical System Image: New Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - available for testing and further info supply Regards and thanks EDIT 13feb2016 : removed Device s/n To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1539446] Re: Today scope hangs-on after OTA9 update
You are right, sorry for misuse of the launchpad bug reporting. About adding new scopes/load I already started Yesterday, adding messages & calls ones. the Today-to-Apps screen sliding bacomes immediantly more dificulty for the device, with istantaneous brake-release on the sliding action between windows/scopes. but no unreversible locks or freezing, up to now. I will keep you in touch. BR D Il 15.02.2016 10:21 Albert Astals Cid ha scritto: > I agree the "today to Telegram bug" is a different thing, so you should > not have mentioned it here, otherwise you are just making it harder to > fix the original bug you reported, mixing things that don't have > anything to do with eachother is the perfect recipe to not getting > anything fixed. > > So please let's go back to "Today scope bug" itself only in this > launchpad bug. > > You say you can not reproduce it anymore if you only have the Today > scope as a favorite scope, is that right? > > If so, can you add scopes one by one and see when you start reproducing > it again? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1539446 [1] > > Title: > Today scope hangs-on after OTA9 update > > Status in Canonical System Image: > New > Status in Today Scope: > New > Status in unity8 package in Ubuntu: > New > > Bug description: > really often from Yesterday night (OTA9 updated at 11 p.m.) the Today > scope freeze the screen and no other actiion is possibile to achieve. > the system restart itself after 20-30 seconds . > > it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. > when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. > > no more possibility to acces vertical "courtains" menu > (notifications, blutooth, netwoorks a.s.o.) neither any of the other > icons. > > If you send a call to the device SIM number, you can ear (frpm the > sender device speaker) the usual network ringigng tone, but nothing > happens on the Ubuntu phone . After the self reboot, the lost call is > correctly notified on the notification menu. > > device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - > > available for testing and further info supply > > Regards and thanks > > EDIT 13feb2016 : removed Device s/n > > To manage notifications about this bug go to: > https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539446/+subscriptions [2] -- Saluti Danilo Montevecchi 349-3767797 Connetti gratis il mondo con la nuova indoona: hai la chat, le chiamate, le video chiamate e persino le chiamate di gruppo. E chiami gratis anche i numeri fissi e mobili nel mondo! Scarica subito l’app Vai su https://www.indoona.com/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1539446 Title: Today scope hangs-on after OTA9 update Status in Canonical System Image: New Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - available for testing and further info supply Regards and thanks EDIT 13feb2016 : removed Device s/n To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867735] [NEW] Can't login after computer locks on idle
Public bug reported: After a leave my computer on idle and try to put my password to login the screen starts to blink whenever I click on the screen. The workaround I found is to click on the switch user button to log back in but some windows are closed on this process. Also when the screen is locked I'm able to see the windows running on the user profile without unlocking ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: login 1:4.8.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:49:09 2020 InstallationDate: Installed on 2019-12-24 (83 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: shadow UpgradeStatus: Upgraded to focal on 2020-03-15 (1 days ago) ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1867735 Title: Can't login after computer locks on idle Status in shadow package in Ubuntu: New Bug description: After a leave my computer on idle and try to put my password to login the screen starts to blink whenever I click on the screen. The workaround I found is to click on the switch user button to log back in but some windows are closed on this process. Also when the screen is locked I'm able to see the windows running on the user profile without unlocking ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: login 1:4.8.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:49:09 2020 InstallationDate: Installed on 2019-12-24 (83 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: shadow UpgradeStatus: Upgraded to focal on 2020-03-15 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1867735/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445376] Re: A2DP skips when conneted to handsfree device
Hi all, Me too Ican notice a great improvement by updating OTA13. Many thanks fo make my phone being able to: -pair immediantly with in-car hands free kac bt200. -downloading and sync contacts phonebooks. I can also browse contacts from my car dissplay controller, and start a call too. - starting as well as receiving a call by ringing tone and muting car audi systems. But phone call audio still does not work. I neinther both direction. I always need to switch manually from bt audio to phone internal speaker. Always BQ E5 HD Ota 13. BR D -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1445376 Title: A2DP skips when conneted to handsfree device Status in Canonical System Image: Incomplete Status in bluez package in Ubuntu: Confirmed Bug description: When I connect my Aquaris E4.5 to my car's handsfree device (Funkwerk Ego Flash) via Bluetooth I experience a skipping problem when playing sound files through A2DP. Half a second for each second there is a pause. The rest of that half second seems to clear a buffer which results in "extra fast" audio. To illustrate, listening to a podcast I would expect to hear something like "bla bla bla". However, what I do get to hear sounds more like "flapflapflap - pause - flapflapflap - pause - ...". When I connect my Aquaris to my A2DP speakers at home, the audio is perfect. Also, handsfree telephony in my car works like a charm. So I guess it's just the combination of A2DP while connected to the handsfree device which causes the trouble. In the past I've used several phones with the Funkwerk device (always with handsfree *and* A2DP functionality) including an N900 running Maemo. There have never been any problems with those. OS build number 21 KRILIN01A-S15A_BQ_L100EN_2021_150410 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1543179] Re: Audio does not get routed to BT headset/speaker
Same on my bq E5 hd (otq 13, as well as the previous 11.12 & 10, only ota9 was fully working wella) paired with car kenwood kca bt200 hands free + hifi bt interface. Audio hici is working but with some glitch. If a call is coming ( as,well as,generated) the system establish a connection, as it sould be, but no call audio (neither micro is wotking) Bt volume is different from zero. Need to switch manually to phone speaker to talk. If the call is terminated, the bt system restarts to play music. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1543179 Title: Audio does not get routed to BT headset/speaker Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: STEPS: 1. Flash the latest daily rc-proposed image to a phone 2. Connect a bluetooth headset to the phone 3. Connect a speaker to the phone. EXPECTED: I expect the devices to connect and play audio ACTUAL: Speakers just connect and instantly disconnect Headsets don't get trusted and disconnect instantly, Once you trust it and then turn the headset off and back on again it connect can accept calls but the audio from both the mic and earpiece don't function. Image: 242 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543179/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573762] Re: Ubuntu 16.04 LTS - webbrowser-app does not launch
** Also affects: webbrowser-app Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1573762 Title: Ubuntu 16.04 LTS - webbrowser-app does not launch Status in Oxide: Confirmed Status in webbrowser-app: New Status in webbrowser-app package in Ubuntu: Confirmed Bug description: When trying to launch the webbrowser-app, it flashes for a second and then disappears, launching it from terminal shows this error : (webbrowser-app:9153): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. file:///usr/share/webbrowser-app/webbrowser/ContentPickerDialog.qml:22:1: module "Ubuntu.Content" is not installed file:///usr/share/webbrowser-app/webbrowser/ContentDownloadDialog.qml:22:1: module "Ubuntu.Content" is not installed file:///usr/share/webbrowser-app/ContentHandler.qml:20:1: module "Ubuntu.Content" is not installed file:///usr/share/webbrowser-app/webbrowser/DownloadHandler.qml:20:1: module "Ubuntu.DownloadManager" is not installed [0422/170822:ERROR:oxide_qt_gl_context_dependent.cc(82)] Unable to create adopted GL context for platform: xcb - unexpected result from QPlatformNativeInterface::nativeResourceForContext shm_open() failed: Permission denied [0422/170822:ERROR:gl_context_glx.cc(59)] Failed to create GL context with glXCreateContextAttribsARB. [0422/170822:ERROR:gpu_info_collector.cc(47)] gfx::GLContext::CreateGLContext failed [0422/170822:ERROR:gpu_info_collector.cc(115)] Could not create context for info collection. [0422/170822:ERROR:oxide_browser_main_parts.cc(299)] gpu::CollectContextGraphicsInfo failed qml: Loaded 5 UA override(s) from file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-mobile.js Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior 2, swapInterval 1, profile 0) Aborted This issue occurs when using the NVIDIA graphics adapter, when switching to Intel graphics, webbrowser-app launches as expected. Ubuntu 16.04 LTS (installation date : 2016-04-21) | Intel i7-4710MQ + HD Graphics 4600 | NVIDIA GTX 860M (drivers version 361.42) webbrowser-app : 0.23+16.04.20160413-0ubuntu1 500 | 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1573762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539688] Re: Bluetooth stops working after the OTA9 update
OTA 13 update: BT MICRO 06 "in ear" handsfree device works correctly. (no music, indeed, but personally i don't care). it is possible to start/close a call, to answer an incoming one without touching the phone. Thanks! -- KCA BT200 handsfree+audio car system from Kenwood, some improvement, but calls audio still not working at all. 1.Pairing : OK (code imput () necessary, before it was not necessary) 2.Phonebook downloading: OK (it takes a while -longer than with previous BB phone), but it works nice. 3.Battery/network signal levels on BT device display: sometimes it works, sometimes is showing a cross (X). (check also point 10.) 4.Possible to browse phonebook from BT display/controls: as above. (but when it works, it scrolls faster than previous BB device, no stucking lags, Thanks). (check also point 10.) 5.Possible to start a call using BT device controls: NO 6.Possible to answer an incoming call using BT device controls: NO 7. starting a call via the Ub/phone keyboard, the phone display shows a "BT audio on" symbol, but no evidences from BT display, neither sounds comes out from BT handsfree device speaker. 8.same as if I answer an incoming call by Ub/phone: it displays me "BT audio ON" symbol, but no display/audio "life signs" from BT device. In both cases, if I switch Ub/phone audio to phone speaker a conversation can take place. 9. self reconnection at car engine ---> BT device power up : Yes, always, but check also points 3 & 4) 10. Audio (music player) : available and without any "suddenly mute" events, but only if point 3 is a (X), and point 4 is "no data". It seems to me that the "quality audio" protocol and the "hands free/phone book manager" protocols cannot exist at the same time. if the phone data are available, audio quality is disabled. Moreover i see no possiblity to select which one to be used by Ub/pone Bluetooth config menu. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539688 Title: Bluetooth stops working after the OTA9 update Status in bluez package in Ubuntu: New Bug description: After the OTA9 update, the system stops working with Kenwood KCA-BT200 Bluetooth car radio adapter (handsfree+audio streaming): please check attached file for further details. Build name: OTA9 Ubuntu image part 20160123.1 Ubuntu build description: ubuntu 15.04 - armhf (20160123-115651) device image part : 20160108-ef-c96d8 device build description: VEGETA01.A-S23A_BQ_L100EN_2009_160123 Customization image part: 2016011-926-36-vivid available for further test and to supply additional details. Thanks and Regards D To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539688] Re: Bluetooth stops working after the OTA9 update
ERRATA CORRIGE: in ear device is BTMICRO 04, sorry -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539688 Title: Bluetooth stops working after the OTA9 update Status in bluez package in Ubuntu: New Bug description: After the OTA9 update, the system stops working with Kenwood KCA-BT200 Bluetooth car radio adapter (handsfree+audio streaming): please check attached file for further details. Build name: OTA9 Ubuntu image part 20160123.1 Ubuntu build description: ubuntu 15.04 - armhf (20160123-115651) device image part : 20160108-ef-c96d8 device build description: VEGETA01.A-S23A_BQ_L100EN_2009_160123 Customization image part: 2016011-926-36-vivid available for further test and to supply additional details. Thanks and Regards D To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445376] Re: A2DP skips when conneted to handsfree device
According to testplan/bluettoth debugging: /var/log/syslog may I add my own "syslog" file: the other requested file ( home/phablet/.cache/upstart/application- legacy-ubuntu-system-settings-.log) is not available. Full BT related bugs descriptions: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539688 https://bugs.launchpad.net/canonical-devices-system-image/+bug/1562299 My device: BQ E5 Aquaris HD. OS build number: OTA11 (but i'm sure to had updated to OTA 13, last night... :-? ) U/Image part: 20150524.1 U/build decritpion: 15.04 -armhf (20160524-114729) Dev Image part: 20160524-63b1875 Dev.build descr.:VEGETA01A-S23A_BQ_L100EN_2013_160524 Customization Image part: 20160505-975-38-9 ** Attachment added: "syslog file" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1445376/+attachment/4675874/+files/syslog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1445376 Title: A2DP skips when conneted to handsfree device Status in Canonical System Image: Incomplete Status in bluez package in Ubuntu: Confirmed Bug description: When I connect my Aquaris E4.5 to my car's handsfree device (Funkwerk Ego Flash) via Bluetooth I experience a skipping problem when playing sound files through A2DP. Half a second for each second there is a pause. The rest of that half second seems to clear a buffer which results in "extra fast" audio. To illustrate, listening to a podcast I would expect to hear something like "bla bla bla". However, what I do get to hear sounds more like "flapflapflap - pause - flapflapflap - pause - ...". When I connect my Aquaris to my A2DP speakers at home, the audio is perfect. Also, handsfree telephony in my car works like a charm. So I guess it's just the combination of A2DP while connected to the handsfree device which causes the trouble. In the past I've used several phones with the Funkwerk device (always with handsfree *and* A2DP functionality) including an N900 running Maemo. There have never been any problems with those. OS build number 21 KRILIN01A-S15A_BQ_L100EN_2021_150410 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445376] Re: A2DP skips when conneted to handsfree device
ERRATA CORRIGE: U/Image part: 20160524.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1445376 Title: A2DP skips when conneted to handsfree device Status in Canonical System Image: Incomplete Status in bluez package in Ubuntu: Confirmed Bug description: When I connect my Aquaris E4.5 to my car's handsfree device (Funkwerk Ego Flash) via Bluetooth I experience a skipping problem when playing sound files through A2DP. Half a second for each second there is a pause. The rest of that half second seems to clear a buffer which results in "extra fast" audio. To illustrate, listening to a podcast I would expect to hear something like "bla bla bla". However, what I do get to hear sounds more like "flapflapflap - pause - flapflapflap - pause - ...". When I connect my Aquaris to my A2DP speakers at home, the audio is perfect. Also, handsfree telephony in my car works like a charm. So I guess it's just the combination of A2DP while connected to the handsfree device which causes the trouble. In the past I've used several phones with the Funkwerk device (always with handsfree *and* A2DP functionality) including an N900 running Maemo. There have never been any problems with those. OS build number 21 KRILIN01A-S15A_BQ_L100EN_2021_150410 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1674605] Re: resolving short local hostnames doesn't work, fqdn are fine
I assume I'm affected by the same issue. I also use my router (Mikrotik) to set up short aliases for hosts. This works generally: $ dig +short anton @10.0.0.1 10.0.0.12 In my /etc/resolv.conf, systemd-resolved is enabled: $ tail -n 1 /etc/resolv.conf nameserver 127.0.0.53 When running "systemd-resolve --status", I can see that the DNS server is correctly set up for the interface via DHCP: Link 4 (wlx0013ef8b0189) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.0.0.1 However, it is not being used to resolve the shortnames: $ dig +short anton @10.0.0.1 10.0.0.12 $ dig +short anton @127.0.0.53 $ dig +short anton -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1674605 Title: resolving short local hostnames doesn't work, fqdn are fine Status in systemd package in Ubuntu: Confirmed Bug description: Hi, I have a local "dummy" DNS server on my router which registers DHCP clients with the hostnames that they have. But resolving these hostnames doesn't work on zesty unless fqdn is used, otherwise there's a timeout that says: root@zesty:# host deckard ;; connection timed out; no servers could be reached but root@zesty:/mnt# host deckard.tyrell deckard.tyrell has address 192.168.1.239 Yesterday I had a resolv.conf with "search tyrell" and shortnames worked then, but today it's gone again. Besides right after a reboot it fails like this: u@zesty:~$ host deckard Host deckard not found: 2(SERVFAIL) and after restarting systemd-resolved I get the timeout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1674605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895429] [NEW] Chrome crashes
Public bug reported: Every time I wake up from hibernating my laptop Chrome and other applications crashes de view (but if I move the mouse over the image crash the view refresh at the same point as the mouse moves). That also happens within VSCode and other applications. The temporary solution I've found is kill chrome the application and start again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 06:15:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-45-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia, 440.100, 5.4.0-47-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-45-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-47-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3f19] Subsystem: Lenovo GM108M [GeForce MX110] [17aa:3f19] InstallationDate: Installed on 2020-05-30 (105 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81S9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=697d5095-40bc-4850-89a0-df85f2b4aa2b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: ASCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IWL dmi.modalias: dmi:bvnLENOVO:bvrASCN44WW:bd03/18/2020:svnLENOVO:pn81S9:pvrLenovoIdeaPadS145-15IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IWL: dmi.product.family: IdeaPad S145-15IWL dmi.product.name: 81S9 dmi.product.sku: LENOVO_MT_81S9_BU_idea_FM_IdeaPad S145-15IWL dmi.product.version: Lenovo IdeaPad S145-15IWL dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu ** Attachment added: "Example of how Chrome crashes" https://bugs.launchpad.net/bugs/1895429/+attachment/5410284/+files/Screenshot%20from%202020-09-12%2013-22-28.png -- 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/1895429 Title: Chrome crashes Status in xorg package in Ubuntu: New Bug description: Every time I wake up from hibernating my laptop Chrome and other applications crashes de view (but if I move the mouse over the image crash the view refresh at the same point as the mouse moves). That also happens within VSCode and other applications. The temporary solution I've found is kill chrome the application and start again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Pro
[Touch-packages] [Bug 1895429] Re: Chrome crashes
Another Chrome crash bug example ** Attachment added: "Screenshot from 2020-09-13 10-27-17.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1895429/+attachment/5410443/+files/Screenshot%20from%202020-09-13%2010-27-17.png -- 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/1895429 Title: Chrome crashes Status in xorg package in Ubuntu: New Bug description: Every time I wake up from hibernating my laptop Chrome and other applications crashes de view (but if I move the mouse over the image crash the view refresh at the same point as the mouse moves). That also happens within VSCode and other applications. The temporary solution I've found is kill chrome the application and start again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 06:15:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-45-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia, 440.100, 5.4.0-47-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-45-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-47-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3f19] Subsystem: Lenovo GM108M [GeForce MX110] [17aa:3f19] InstallationDate: Installed on 2020-05-30 (105 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81S9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=697d5095-40bc-4850-89a0-df85f2b4aa2b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: ASCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IWL dmi.modalias: dmi:bvnLENOVO:bvrASCN44WW:bd03/18/2020:svnLENOVO:pn81S9:pvrLenovoIdeaPadS145-15IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IWL: dmi.product.family: IdeaPad S145-15IWL dmi.product.name: 81S9 dmi.product.sku: LENOVO_MT_81S9_BU_idea_FM_IdeaPad S145-15IWL dmi.product.version: Lenovo IdeaPad S145-15IWL dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1895429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878970] [NEW] Ubuntu 20.04 - AOC HDMI Monitor
Public bug reported: This is a fresh install of Ubuntu 20.04 on a Dell Inspiron 5590. I've just bought a monitor AOC 22B1H and I'm using as a second monitor plugged in HDMI. For 3 times the system crashed and I had to do a hard reboot for no reason apparently. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 15 15:02:09 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:0957] Subsystem: Dell GP108M [GeForce MX250] [1028:0957] InstallationDate: Installed on 2020-05-04 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=1a490b05-de14-4d4f-8795-c0fe269ac8cb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0XRXN9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/15/2020:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5590 dmi.product.sku: 0957 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu -- 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/1878970 Title: Ubuntu 20.04 - AOC HDMI Monitor Status in xorg package in Ubuntu: New Bug description: This is a fresh install of Ubuntu 20.04 on a Dell Inspiron 5590. I've just bought a monitor AOC 22B1H and I'm using as a second monitor plugged in HDMI. For 3 times the system crashed and I had to do a hard reboot for no reason apparently. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 15 15:02:09 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:0957] Subsystem: Dell GP108M [GeForce MX250] [1028:0957] InstallationDate: Installed on 2020-
[Touch-packages] [Bug 1880594] [NEW] Ubuntu-server slow after upgrade to 20.04
Public bug reported: After upgrading to 20.04 my ubuntu-server seems very slow. Also using tab to autocomplete commands takes ~10 Seconds to complete ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-server 1.450 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 25 19:57:43 2020 InstallationDate: Installed on 2020-03-10 (75 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-04-26 (29 days ago) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1880594 Title: Ubuntu-server slow after upgrade to 20.04 Status in ubuntu-meta package in Ubuntu: New Bug description: After upgrading to 20.04 my ubuntu-server seems very slow. Also using tab to autocomplete commands takes ~10 Seconds to complete ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-server 1.450 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 25 19:57:43 2020 InstallationDate: Installed on 2020-03-10 (75 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-04-26 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1880594/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1227149] Re: USB audio sound card not recognized after update to Linux 3.12-rc1-saucy
I have a usb audio device that i was using regularly and suddenly stopped being recognized. The system can't even identify its ID's anymore (ID :fffe). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1227149 Title: USB audio sound card not recognized after update to Linux 3.12-rc1-saucy Status in alsa-driver package in Ubuntu: Confirmed Bug description: Not sure where this report should go, I think it concerns the Linux kernel 3.12-rc1-saucy from http://kernel.ubuntu.com/~kernel- ppa/mainline/ After installing above mentioned kernel (switching from 3.11.1) I can no longer use my USB sound card. (It is an external D/A converter and speaker amplifier.) The sound settings dialog only lists "Dummy Output". (My onboard soundcard is disabled in BIOS.) Dmesg: usb 1-1.1.2: new full-speed USB device number 13 using ehci-pci usb 1-1.1.2: New USB device found, idVendor=08bb, idProduct=2706 usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-1.1.2: Product: USB Audio DAC usb 1-1.1.2: Manufacturer: Burr-Brown from TI input: Burr-Brown from TI USB Audio DACas /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.2/input/input9 hid-generic 0003:08BB:2706.0007: input,hidraw4: USB HID v1.00 Device [Burr-Brown from TI USB Audio DAC ] on usb-:00:1a.0-1.1.2/input2 snd_usb_audio: `-2' invalid for parameter `index' and /etc/modprobe.d/alsa-base.conf indeed does have this line: options snd-usb-audio index=-2 The kernel apparently sees my USB amplifier, but it is not listed in the Sound settings, even though there is no other sound device present. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.12.0-031200rc1-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Sep 18 15:14:53 2013 InstallationDate: Installed on 2012-11-02 (319 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: Upgraded to raring on 2013-09-01 (16 days ago) dmi.bios.date: 08/22/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F14 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF14:bd08/22/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1227149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2053228] Re: software-properties-gtk does not start
For me it still not working, or it takes a while to be added to the
updates?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2053228
Title:
software-properties-gtk does not start
Status in software-properties package in Ubuntu:
Fix Released
Bug description:
On a new install with the new format sources.list software-properties-gtk
does not start:
corrado@corrado-n4-nn-0215:~$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
corrado@corrado-n4-nn-0215:~$
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056213] [NEW] Unable to open Software & Updates
Public bug reported:
I receive the error below when trying to open, after update
software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, in
__init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42 [modified:
usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py]
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 5 20:42:48 2024
InstallationDate: Installed on 2023-09-14 (173 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2056213
Title:
Unable to open Software & Updates
Status in software-properties package in Ubuntu:
New
Bug description:
I receive the error below when trying to open, after update
software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42 [modified:
usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py]
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 5 20:42:48 2024
InstallationDate: Installed on 2023-09-14 (173 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2056213/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1866923] Re: Wifi connection says it's connected but this is not true after the computer goes into a sleep status
I'm having the same error no ubuntu 20.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1866923 Title: Wifi connection says it's connected but this is not true after the computer goes into a sleep status Status in network-manager package in Ubuntu: Confirmed Bug description: The wifi is connected and working correctly when powered on, however when I close the laptop lid, which I think puts it to sleep, and then reopen it, it says it's connected according to the icon but this is not true. A workaround is turning on Airplane mode and then switching it back on again. It then reconnects and is then fine again. Unless I close the lid and then the process repeats again. I guess this is to do with the wifi driver but I don't know what package it is so I just picked network-manager, sorry - I'm trying :) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 10 19:29:03 2020 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.68.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.68.0/24 dev wlp1s0 proto kernel scope link src 192.168.68.18 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1866923/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1870851] [NEW] When closing the lid or suspending and turning on, wifi goes to airplane mode
Public bug reported: when computer is suspended or the lid is closed it goes to airplane mode ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 01:09:56 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-12-24 (102 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-03-15 (20 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s25 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- ---- wlo1 wifi unavailable none none /org/freedesktop/NetworkManager/Devices/3 -- ---- p2p-dev-wlo1 wifi-p2p unavailable none none /org/freedesktop/NetworkManager/Devices/4 -- ---- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 disconnected started none enabled enabled disabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1870851 Title: When closing the lid or suspending and turning on, wifi goes to airplane mode Status in network-manager package in Ubuntu: New Bug description: when computer is suspended or the lid is closed it goes to airplane mode ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 01:09:56 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-12-24 (102 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-03-15 (20 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s25 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- ---- wlo1 wifi unavailable none none /org/freedesktop/NetworkManager/Devices/3 -- ---- p2p-dev-wlo1 wifi-p2p unavailable none none /org/freedesktop/NetworkManager/Devices/4 -- ---- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 disconnected started none enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870851/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1870851] Re: When closing the lid or suspending and turning on, wifi goes to airplane mode
I've added an attachment. Line 8536 is from today when I was trying to replicate the error. Think you can start from this point down ** Attachment added: "Journal.log file" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870851/+attachment/5348435/+files/jornal.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1870851 Title: When closing the lid or suspending and turning on, wifi goes to airplane mode Status in network-manager package in Ubuntu: Incomplete Bug description: when computer is suspended or the lid is closed it goes to airplane mode ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 01:09:56 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-12-24 (102 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-03-15 (20 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s25 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- ---- wlo1 wifi unavailable none none /org/freedesktop/NetworkManager/Devices/3 -- ---- p2p-dev-wlo1 wifi-p2p unavailable none none /org/freedesktop/NetworkManager/Devices/4 -- ---- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 disconnected started none enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870851/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871185] Re: urls in ubuntu-bugs dialog not really clickable
adding more information to the bug it doesn't work with email links also ** Attachment added: "email link not clickable" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1871185/+attachment/5360523/+files/Screenshot%20from%202020-04-25%2021-52-18.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1871185 Title: urls in ubuntu-bugs dialog not really clickable Status in apport package in Ubuntu: In Progress Bug description: when ubuntu-bug report suggests filing a bug report directly in launchpad for snap packages, the displayed url is clickable but the url stops at the first + symbol. see attachment. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.8 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CrashReports: 640:1000:124:8919925:2020-03-29 20:16:13.456640958 +0200:2020-03-29 20:16:14.456640958 +0200:/var/crash/_usr_bin_python3.7.1000.crash CurrentDesktop: XFCE Date: Mon Apr 6 19:50:16 2020 InstallationDate: Installed on 2020-03-18 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1871185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638301] [NEW] systemctl start auto-completion it's not working
Public bug reported: When i try to auto-complete the "systemctl start " the following error message is shown in bash: Unit org.freedesktop.network1.busname could not be found. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 10:42:37 2016 InstallationDate: Installed on 2015-06-20 (499 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Dell System Vostro 3450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic root=UUID=7468e7be-a2e1-48dd-ba72-244c33698364 ro cgroup_enable=memory swapaccount=1 quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-19 (12 days ago) dmi.bios.date: 07/22/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0GG0VM dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/22/2011:svnDellInc.:pnDellSystemVostro3450:pvr:rvnDellInc.:rn0GG0VM:rvrA01:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System Vostro 3450 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Summary changed: - systemctl start command shows a error message on "auto-complation" + systemctl start auto-completion it's not working -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1638301 Title: systemctl start auto-completion it's not working Status in systemd package in Ubuntu: New Bug description: When i try to auto-complete the "systemctl start " the following error message is shown in bash: Unit org.freedesktop.network1.busname could not be found. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 10:42:37 2016 InstallationDate: Installed on 2015-06-20 (499 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Dell System Vostro 3450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic root=UUID=7468e7be-a2e1-48dd-ba72-244c33698364 ro cgroup_enable=memory swapaccount=1 quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-19 (12 days ago) dmi.bios.date: 07/22/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0GG0VM dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/22/2011:svnDellInc.:pnDellSystemVostro3450:pvr:rvnDellInc.:rn0GG0VM:rvrA01:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System Vostro 3450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1638301/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1594627] Re: "apt show" reports misleading conflicts
** Changed in: apt (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/apt/+question/295517 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1594627 Title: "apt show" reports misleading conflicts Status in apt package in Ubuntu: Invalid Bug description: Packages are reported to conflict with themselves when they actually conflict with a different architecture version of themselves. For example (and as illustrated below using "apt show" and "apt-cache depends") musepack-tools is reported to conflict with musepack-tools (according to "apt show") but in reality (as revealed by "apt-cache depends") conflicts with musepack-tools:i386. That is misleading and concerning when read for the first time by probably anyone and apparently a known issue: http://askubuntu.com/questions/106203/why-do-some-packages-conflict- with-themselves I consider it a bug and file so accordingly. "apt show", should not mislead as it does, but show at least the same output as "apt-cache depends" does here. Example runs: $ apt show musepack-tools Package: musepack-tools State: installed Automatically installed: no Version: 2:0.1~r459-1ubuntu3 Priority: optional Section: universe/sound Maintainer: Ubuntu Developers Architecture: amd64 Uncompressed Size: 342 k Depends: libc6 (>= 2.15), libcue1, libmpcdec6 (>= 1:0.1~r435), libreplaygain1 (>= 1.0~r412) Conflicts: musepack-tools Description: MusePack commandline utilities Musepack is an audio compression format with a strong emphasis on high quality. It's not lossless, but it is designed for transparency, so that you won't be able to hear differences between the original wave file and the much smaller MPC file. It is based on the MPEG-1 Layer-2 / MP2 algorithms, but since 1997 it has rapidly developed and vastly improved and is now at an advanced stage in which it contains heavily optimized and patentless code. This package contains various commandline utilities for MusePack files: * mpcenc (encoder) * mpcdec (decoder) * mpccut (cut MPC files without reencoding) * mpcgain (gain calculation) * mpc2sv8 (conversion to MusePack SV8 from older SV) Homepage: http://www.musepack.net $ apt-cache depends musepack-tools musepack-tools Depends: libc6 Depends: libcue1 Depends: libmpcdec6 Depends: libreplaygain1 Conflicts: musepack-tools:i386 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.14 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Tue Jun 21 10:56:12 2016 InstallationDate: Installed on 2015-09-04 (290 days ago) InstallationMedia: Linux Mint 17.2 "Rafaela" - Release amd64 20150627 SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1594627/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638301] Re: systemctl start auto-completion it's not working
@pitti, exactly! You've described it better than me :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1638301 Title: systemctl start auto-completion it's not working Status in systemd package in Ubuntu: Incomplete Bug description: When i try to auto-complete the "systemctl start " the following error message is shown in bash: Unit org.freedesktop.network1.busname could not be found. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 10:42:37 2016 InstallationDate: Installed on 2015-06-20 (499 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Dell System Vostro 3450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic root=UUID=7468e7be-a2e1-48dd-ba72-244c33698364 ro cgroup_enable=memory swapaccount=1 quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-19 (12 days ago) dmi.bios.date: 07/22/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0GG0VM dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/22/2011:svnDellInc.:pnDellSystemVostro3450:pvr:rvnDellInc.:rn0GG0VM:rvrA01:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System Vostro 3450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1638301/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574020] Re: Can't use networkmanager from lightdm
Hi. Same problem here with a clean install. I have a NAS mounted via fstab and it cannot get mounted on boot because of that (I suspect). Very annoying. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1574020 Title: Can't use networkmanager from lightdm Status in network-manager package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: New Bug description: After upgrading to 16.04 desktop (unity) (clean install) from 14.04, (so not really upgrading, but you get the point) I noticed that lightdm with unity-greeter (all stock, nothing changed) can't connect to WiFi with network-manager. WiFi works after loggin it, but it should be working before also, if not, what's the point in having an icon there :) I get the following message: Failed to add/activate connection. - (1) Insufficient privileges. - see image. This worked fine in 14.04. I have noticed this problem in both my desktop (Broadcom WiFi) and Laptop (Intel WiFi) - So it has nothing to be with the chip. Feel free to ask for more info. Edit: From syslog: Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed Apr 23 16:50:46 desktop NetworkManager[979]: [1461423046.1662] audit: op="connection-add-activate" pid=1275 uid=108 result="fail" reason="Insufficient privileges." Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720827] Re: Tab selection shouldn't have a "resize" effect
This is also applies to communitheme. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1720827 Title: Tab selection shouldn't have a "resize" effect Status in Ubuntu theme: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: When alternating between tabs in Systems Settings -> Sound, for instance, we can notice that the tabs get resized after a tab is selected, which looks like a small visual glitch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1720827/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720827] [NEW] Tab selection shouldn't have a "resize" effect
Public bug reported: When alternating between tabs in Systems Settings -> Sound, for instance, we can notice that the tabs get resized after a tab is selected, which looks like a small visual glitch. ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1720827 Title: Tab selection shouldn't have a "resize" effect Status in ubuntu-themes package in Ubuntu: New Bug description: When alternating between tabs in Systems Settings -> Sound, for instance, we can notice that the tabs get resized after a tab is selected, which looks like a small visual glitch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1720827/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720828] [NEW] Outline effect should be disabled for tabs
Public bug reported: When opening System Settings -> Appearance, for instance, the selected tab has by default an orange outline effect that I don't think should be displayed for tabs at all. ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Attachment added: "tabs.png" https://bugs.launchpad.net/bugs/1720828/+attachment/4960555/+files/tabs.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1720828 Title: Outline effect should be disabled for tabs Status in ubuntu-themes package in Ubuntu: New Bug description: When opening System Settings -> Appearance, for instance, the selected tab has by default an orange outline effect that I don't think should be displayed for tabs at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1720828/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720834] [NEW] Insufficient padding in horizontal panes causes a resize of the panes when alternating between toggle buttons
Public bug reported: In Ubuntu Software, when clicking on "Updates", the horizontal pane that holds the buttons "All", "Installed," and "Updates" gets resized vertically in order to accommodate the "Refresh" button that gets shown in the "Updates" section, which causes a small visual glitch. The same effect happens in System Monitor when alternating between the "Processes" section and "Resources" and/or "Filesystem." ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1720834 Title: Insufficient padding in horizontal panes causes a resize of the panes when alternating between toggle buttons Status in ubuntu-themes package in Ubuntu: New Bug description: In Ubuntu Software, when clicking on "Updates", the horizontal pane that holds the buttons "All", "Installed," and "Updates" gets resized vertically in order to accommodate the "Refresh" button that gets shown in the "Updates" section, which causes a small visual glitch. The same effect happens in System Monitor when alternating between the "Processes" section and "Resources" and/or "Filesystem." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1720834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721115] Re: Wrong style is applied to breadcrumbs depending on navigation flow
** Attachment added: "all-settings-not-rounded-2.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1721115/+attachment/4961720/+files/all-settings-not-rounded-2.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1721115 Title: Wrong style is applied to breadcrumbs depending on navigation flow Status in ubuntu-themes package in Ubuntu: New Bug description: To reproduce: 1. Open System Settings -(notice the All Settings breadcrumb is correctly all rounded) 2. Click on Appearance - (notice the All Settings breadcrumb is now incorrectly rounded on the right side) 3. Mouse hover the All Settings breadcrumb - (notice the correct style is applied now) 4. Click on the All Settings breadcrumb and mouse hover it - (notice the style is incorrect again, because it is still flat on the right side when it should be rounded again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1721115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721115] [NEW] Wrong style is applied to breadcrumbs depending on navigation flow
Public bug reported: To reproduce: 1. Open System Settings -(notice the All Settings breadcrumb is correctly all rounded) 2. Click on Appearance - (notice the All Settings breadcrumb is now incorrectly rounded on the right side) 3. Mouse hover the All Settings breadcrumb - (notice the correct style is applied now) 4. Click on the All Settings breadcrumb and mouse hover it - (notice the style is incorrect again, because it is still flat on the right side when it should be rounded again) ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Attachment added: "all-settings-not-rounded.png" https://bugs.launchpad.net/bugs/1721115/+attachment/4961719/+files/all-settings-not-rounded.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1721115 Title: Wrong style is applied to breadcrumbs depending on navigation flow Status in ubuntu-themes package in Ubuntu: New Bug description: To reproduce: 1. Open System Settings -(notice the All Settings breadcrumb is correctly all rounded) 2. Click on Appearance - (notice the All Settings breadcrumb is now incorrectly rounded on the right side) 3. Mouse hover the All Settings breadcrumb - (notice the correct style is applied now) 4. Click on the All Settings breadcrumb and mouse hover it - (notice the style is incorrect again, because it is still flat on the right side when it should be rounded again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1721115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720834] Re: Insufficient padding in horizontal panes causes a resize of the panes when alternating between toggle buttons
Thanks a lot for the feedback, Daniel! I have just tested it on 17.10 and it doesn't happen anymore in Gnome; it happens only in 16.04 and Unity. If it might be fixed in 16.04, I can take some screenshots and post them later. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1720834 Title: Insufficient padding in horizontal panes causes a resize of the panes when alternating between toggle buttons Status in ubuntu-themes package in Ubuntu: Incomplete Bug description: In Ubuntu Software, when clicking on "Updates", the horizontal pane that holds the buttons "All", "Installed," and "Updates" gets resized vertically in order to accommodate the "Refresh" button that gets shown in the "Updates" section, which causes a small visual glitch. The same effect happens in System Monitor when alternating between the "Processes" section and "Resources" and/or "Filesystem." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1720834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656142] [NEW] package python-setuptools 20.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
Public bug reported: Ran into this bug while trying to install dependencies for Theano ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-setuptools 20.7.0-1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Thu Jan 12 16:28:48 2017 Dependencies: python-pkg-resources 20.7.0-1 DuplicateSignature: package:python-setuptools:20.7.0-1 Setting up python-imaging (3.1.2-0ubuntu1) ... /var/lib/dpkg/info/python-imaging.postinst: 6: /var/lib/dpkg/info/python-imaging.postinst: pycompile: not found dpkg: error processing package python-imaging (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2017-01-11 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.18 SourcePackage: python-setuptools Title: package python-setuptools 20.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-setuptools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1656142 Title: package python-setuptools 20.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in python-setuptools package in Ubuntu: New Bug description: Ran into this bug while trying to install dependencies for Theano ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-setuptools 20.7.0-1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Thu Jan 12 16:28:48 2017 Dependencies: python-pkg-resources 20.7.0-1 DuplicateSignature: package:python-setuptools:20.7.0-1 Setting up python-imaging (3.1.2-0ubuntu1) ... /var/lib/dpkg/info/python-imaging.postinst: 6: /var/lib/dpkg/info/python-imaging.postinst: pycompile: not found dpkg: error processing package python-imaging (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2017-01-11 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.18 SourcePackage: python-setuptools Title: package python-setuptools 20.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1656142/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1992369] Re: DejaVu Serif Italic capital letters and digits broken
Not sure where the problem is exactly but it can be reproduced like Juha suggested. On Xubuntu 22.04 if you go to Settings -> Appearance -> Fonts and set "Hinting" to "Medium" or "Full" and have FREETYPE_PROPERTIES="truetype:interpreter-version=35", all the DejaVuSerif...Italic fonts appear to break. Either changing the interpreter version to 38 or 40 [0] or setting "hinting" to "Slight" seems to be a workaround. [0] - https://freetype.org/freetype2/docs/reference/ft2-properties.html#interpreter-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fontforge package in Ubuntu: New Status in fonts-dejavu package in Ubuntu: Confirmed Status in gnome-font-viewer package in Ubuntu: Confirmed Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---==> ii fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1992369] Re: DejaVu Serif Italic capital letters and digits broken
I just noticed that this font (and many others) are marked as "experimental" even in the most recent version of the source [0] [1]. So it might be broken in some scenarios. I opened an issue to clarify if that might be the case [2]. Meanwhile, if you change your XFCE font settings like mentioned above, does it help? [0] - https://git.launchpad.net/ubuntu/+source/fonts-dejavu/tree/README.md?h=applied/ubuntu/kinetic [1] - https://github.com/dejavu-fonts/dejavu-fonts/blob/master/README.md [2] - https://gitlab.freedesktop.org/freetype/freetype/-/issues/1193 ** Bug watch added: gitlab.freedesktop.org/freetype/freetype/-/issues #1193 https://gitlab.freedesktop.org/freetype/freetype/-/issues/1193 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fontforge package in Ubuntu: New Status in fonts-dejavu package in Ubuntu: Confirmed Status in gnome-font-viewer package in Ubuntu: Confirmed Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---==> ii fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1992369] Re: DejaVu Serif Italic capital letters and digits broken
It turns out the font files in our package are probably corrupt. I tested with the files from the original source [0] and the problem doesn't happen. I also replaced the broken ones with the original ones, cleaned my font cache and the problem appears to be gone. Will try to find out when it happened. [0] - https://github.com/dejavu-fonts/dejavu-fonts/releases -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fontforge package in Ubuntu: New Status in fonts-dejavu package in Ubuntu: Confirmed Status in gnome-font-viewer package in Ubuntu: Invalid Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---==> ii fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1992369] Re: DejaVu Serif Italic capital letters and digits broken
These fonts are working fine in Focal (fonts-dejavu- extra_2.37-1_all.deb) and broken in Jammy, Kinetic and Lunar (fonts- dejavu-extra_2.37-2build1_all.deb). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fontforge package in Ubuntu: New Status in fonts-dejavu package in Ubuntu: Confirmed Status in gnome-font-viewer package in Ubuntu: Invalid Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---==> ii fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1992369] Re: DejaVu Serif Italic capital letters and digits broken
Digging a bit more on that, the problem might be the font build system. The most recent fonts-dejavu-extra package is shared across Jammy, Kinetic and Lunar and it appears to be broken on all of them. Rebuilding the package on Kinetic seems to be enough to fix the problem. But that's not true for Jammy. So I suppose whatever was broken (maybe it fontforge?) was fixed in the version we use in Kinetic. A no-change build is probably enough to fix the issue on Kinetic and Lunar. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fontforge package in Ubuntu: New Status in fonts-dejavu package in Ubuntu: Confirmed Status in gnome-font-viewer package in Ubuntu: Invalid Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---==> ii fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003892] [NEW] libcap2 seems to not work correctly when linked with -Bsymbolic-functions
Public bug reported: Ubuntu will include -Wl,-Bsymbolic-functions in the build flags by default. This option seems to break libcap2. One of the autopkgtests that is supposed to prevent an exploitation instance using capabilities fails: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz The solution is to exclude this flag from the set of flags: debian/rules: export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions Debian seems to not be affected by that as they don't include this flag in their build: https://buildd.debian.org/status/fetch.php?pkg=libcap2&arch=amd64&ver=1%3A2.66-3&stamp=1671660323&raw=0 ** Affects: libcap2 (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/2003892 Title: libcap2 seems to not work correctly when linked with -Bsymbolic- functions Status in libcap2 package in Ubuntu: New Bug description: Ubuntu will include -Wl,-Bsymbolic-functions in the build flags by default. This option seems to break libcap2. One of the autopkgtests that is supposed to prevent an exploitation instance using capabilities fails: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz The solution is to exclude this flag from the set of flags: debian/rules: export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions Debian seems to not be affected by that as they don't include this flag in their build: https://buildd.debian.org/status/fetch.php?pkg=libcap2&arch=amd64&ver=1%3A2.66-3&stamp=1671660323&raw=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2003892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003892] Re: libcap2 seems to not work correctly when linked with -Bsymbolic-functions
Note: when testing this package with autopkgtest (or sbuild) locally, you need to remove the .git directory (if there is one) or the build will fail. One of the make files will detect the directory exists and set the environment variable DYNAMIC to no. Because of that, static binaries will be generated and the command chrpath in debian/rules will fail. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/2003892 Title: libcap2 seems to not work correctly when linked with -Bsymbolic- functions Status in libcap2 package in Ubuntu: New Bug description: Ubuntu will include -Wl,-Bsymbolic-functions in the build flags by default. This option seems to break libcap2. One of the autopkgtests that is supposed to prevent an exploitation instance using capabilities fails: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz The solution is to exclude this flag from the set of flags: debian/rules: export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions Debian seems to not be affected by that as they don't include this flag in their build: https://buildd.debian.org/status/fetch.php?pkg=libcap2&arch=amd64&ver=1%3A2.66-3&stamp=1671660323&raw=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2003892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003892] Re: libcap2 seems to not work correctly when linked with -Bsymbolic-functions
More cases where the same linker flags caused issues https://bugs.launchpad.net/ubuntu/+source/openblas/+bug/1860601 https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1898006 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/2003892 Title: libcap2 seems to not work correctly when linked with -Bsymbolic- functions Status in libcap2 package in Ubuntu: New Bug description: Ubuntu will include -Wl,-Bsymbolic-functions in the build flags by default. This option seems to break libcap2. One of the autopkgtests that is supposed to prevent an exploitation instance using capabilities fails: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz The solution is to exclude this flag from the set of flags: debian/rules: export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions Debian seems to not be affected by that as they don't include this flag in their build: https://buildd.debian.org/status/fetch.php?pkg=libcap2&arch=amd64&ver=1%3A2.66-3&stamp=1671660323&raw=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2003892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1998207] Re: netplan network-manager plugin tries to save temporary connections
The same problem happens if you spin up an OpenVPN server and kill it. An yaml file will be created for the tun interface used by the server. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1998207 Title: netplan network-manager plugin tries to save temporary connections Status in netplan: Triaged Status in network-manager package in Ubuntu: Triaged Bug description: *** Note: This bug is mostly about comment #10, now *** When creating an OpenVPN connection, a temporal connection called tunN is created. For instance, after activating a connection called vpntest, I have: NAME UUID TYPE DEVICE vpntest 458856e6-8f0f-4dc6-82f2-dd72868252a0 vpn ens3 tun0 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 tun tun0 tun0 is created/removed after activating/deactivating vpntest and should not really be saved, but I see netplan adding it in /etc/netplan. And while doing so the plugin also reports some errors (I see these when stopping the connection): Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] BUG: the profile cannot be stored in keyfile format without becoming unusable: cannot access file: No such file or directory Nov 28 16:16:57 ubuntu NetworkManager[11752]: ((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) to "/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection": keyfile writer produces an invalid connection: cannot access file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1998207/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003892] Re: libcap2 seems to not work correctly when linked with -Bsymbolic-functions
More specifically, this test [1] is failing. It uses clone() to create a process in a new user namespace and apparently it should fail. I can't reproduce it with a LXD arhmf container on my own environment. All the tests pass. [1] - https://git.launchpad.net/ubuntu/+source/libcap2/tree/tests/uns_test.c -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/2003892 Title: libcap2 seems to not work correctly when linked with -Bsymbolic- functions Status in libcap2 package in Ubuntu: In Progress Bug description: Ubuntu will include -Wl,-Bsymbolic-functions in the build flags by default. This option seems to break libcap2. One of the autopkgtests that is supposed to prevent an exploitation instance using capabilities fails: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz The solution is to exclude this flag from the set of flags: debian/rules: export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions Debian seems to not be affected by that as they don't include this flag in their build: https://buildd.debian.org/status/fetch.php?pkg=libcap2&arch=amd64&ver=1%3A2.66-3&stamp=1671660323&raw=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2003892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003892] Re: libcap2 seems to not work correctly when linked with -Bsymbolic-functions
The problem is reproducible on Focal (kernel 5.4) in an armhf LXD container. The armhf architecture seems to be the only one using hosts with kernel 5.4. I believe the best approach is to skip only the test that is failing rather than the entire test script. So we will need to patch d/t/upstream-root. Once we upgrade the hosts used for armhf tests we can drop the patch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/2003892 Title: libcap2 seems to not work correctly when linked with -Bsymbolic- functions Status in libcap2 package in Ubuntu: In Progress Bug description: Ubuntu will include -Wl,-Bsymbolic-functions in the build flags by default. This option seems to break libcap2. One of the autopkgtests that is supposed to prevent an exploitation instance using capabilities fails: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz The solution is to exclude this flag from the set of flags: debian/rules: export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions Debian seems to not be affected by that as they don't include this flag in their build: https://buildd.debian.org/status/fetch.php?pkg=libcap2&arch=amd64&ver=1%3A2.66-3&stamp=1671660323&raw=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2003892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003892] Re: libcap2 seems to not work correctly when linked with -Bsymbolic-functions
** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/libcap2/+git/libcap2/+merge/436832 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/2003892 Title: libcap2 seems to not work correctly when linked with -Bsymbolic- functions Status in libcap2 package in Ubuntu: In Progress Bug description: Ubuntu will include -Wl,-Bsymbolic-functions in the build flags by default. This option seems to break libcap2. One of the autopkgtests that is supposed to prevent an exploitation instance using capabilities fails: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz The solution is to exclude this flag from the set of flags: debian/rules: export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions Debian seems to not be affected by that as they don't include this flag in their build: https://buildd.debian.org/status/fetch.php?pkg=libcap2&arch=amd64&ver=1%3A2.66-3&stamp=1671660323&raw=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2003892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006744] [NEW] libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict
Public bug reported: I enabled lunar-proposed today (with APT::Default-Release "lunar- proposed";) and got the error below during update: Preparing to unpack .../39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (22.3.4-1ubuntu1) over (22.2.5-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-AkyzpG/39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Then it will be broken: root@deleteme-lunar:~# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libgl1-mesa-dri : Depends: libglapi-mesa (= 22.2.5-0ubuntu1) but 22.3.4-1ubuntu1 is installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). root@deleteme-lunar:~# apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: libicu71 libpython3.10-minimal libpython3.10-stdlib python3.10 python3.10-minimal Use 'apt autoremove' to remove them. The following additional packages will be installed: libgl1-mesa-dri The following packages will be upgraded: libgl1-mesa-dri 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 62 not fully installed or removed. Need to get 0 B/7806 kB of archives. After this operation, 809 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 81205 files and directories currently installed.) Preparing to unpack .../libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (22.3.4-1ubuntu1) over (22.2.5-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Errors were encountered while processing: /var/cache/apt/archives/libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) How to reproduce: 1. Spin up a Lunar VM 2. Enable -proposed 3. Install libgl1-mesa-dri and libgl1-amber-dri 4. Add APT::Default-Release "lunar-proposed"; to /etc/apt/apt.conf.d/somefile 5. Try to upgrade ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2006744 Title: libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict Status in mesa package in Ubuntu: New Bug description: I enabled lunar-proposed today (with APT::Default-Release "lunar- proposed";) and got the error below during update: Preparing to unpack .../39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (22.3.4-1ubuntu1) over (22.2.5-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-AkyzpG/39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Then it will be broken: root@deleteme-lunar:~# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libgl1-mesa-dri : Depends: libglapi-mesa (= 22.2.5-0ubuntu1) but 22.3.4-1ubuntu1 is installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). root@deleteme-lunar:~# apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: libicu71 libpython3.10-minimal libpython3.10-stdlib python3.10 python3.10-minimal Use 'apt autoremove' to remove them. The following additional packages will be installed: libgl1-mesa-dri The following packages will be upgraded: libgl1-mesa-dri 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 62 not fully installed or removed. Need to get 0 B/7806 kB of archives. After this operation, 809 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 81205 files and directories currently installed.) Preparing to unpack .../libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ... Unpacking libgl1
[Touch-packages] [Bug 1998207] Re: netplan network-manager plugin tries to save temporary connections
After taking another look at this I noticed that the function where we create the Netplan YAML is called when the connection is created AND when the connection is going down as though it was being updated. The first time it's called the parameters is_volatile, is_nm_generated and is_external are all set to true so we skip the libnetplan calls. Although when it's called when the connection is going down they are all false. And that's when the Netplan file is created and network-manager gets to a point in the code it shouldn't reach, so it crashes and the files are never removed. Not sure if calling the plugin writer in this case is a bug or not as the connection is volatile and is going to be deleted anyway. Maybe lost tracking of the connection nature (volatile, nm_generated and external) is the actual bug, not sure yet. One way to work around this is generating Netplan YAMLs regardless if the connection is volatile. If network-manager will create a file for it we could create a file for Netplan too. In fact, after removing the conditions to call libnetplan, the files are created and deleted when the OpenVPN client and/or server is stopped. Note that from network-manager 1.42.0 on, even the loopback interface can be represented as a connection, so we will have a Netplan file for it as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1998207 Title: netplan network-manager plugin tries to save temporary connections Status in netplan: Triaged Status in network-manager package in Ubuntu: Triaged Bug description: *** Note: This bug is mostly about comment #10, now *** When creating an OpenVPN connection, a temporal connection called tunN is created. For instance, after activating a connection called vpntest, I have: NAME UUID TYPE DEVICE vpntest 458856e6-8f0f-4dc6-82f2-dd72868252a0 vpn ens3 tun0 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 tun tun0 tun0 is created/removed after activating/deactivating vpntest and should not really be saved, but I see netplan adding it in /etc/netplan. And while doing so the plugin also reports some errors (I see these when stopping the connection): Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] BUG: the profile cannot be stored in keyfile format without becoming unusable: cannot access file: No such file or directory Nov 28 16:16:57 ubuntu NetworkManager[11752]: ((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) to "/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection": keyfile writer produces an invalid connection: cannot access file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1998207/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007698] [NEW] Please merge 1.9.12p2-1 into lunar
Public bug reported: PPA available at https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/sudo/+git/sudo/+merge/437505 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2007698 Title: Please merge 1.9.12p2-1 into lunar Status in sudo package in Ubuntu: New Bug description: PPA available at https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007698] Re: Please merge 1.9.12p2-1 into lunar
Autopkgtests are passing (tested on ppc64 and amd64) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2007698 Title: Please merge 1.9.12p2-1 into lunar Status in sudo package in Ubuntu: New Bug description: PPA available at https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007698] Re: Please merge 1.9.13p1-1 into lunar
** Summary changed: - Please merge 1.9.12p2-1 into lunar + Please merge 1.9.13p1-1 into lunar ** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/sudo/+git/sudo/+merge/437587 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2007698 Title: Please merge 1.9.13p1-1 into lunar Status in sudo package in Ubuntu: New Bug description: PPA available at https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007698] Re: Please merge 1.9.13p1-1 into lunar
** Attachment added: "sudo autopkgtests" https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+attachment/5648890/+files/autopkgtests.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2007698 Title: Please merge 1.9.13p1-1 into lunar Status in sudo package in Ubuntu: New Bug description: PPA available at https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007698] Re: Please merge 1.9.13p1-1 into lunar
Hi Marc, thanks a lot for taking a look at this. I misunderstood how the changelog must be constructed. I believe the Build-Conflicts can just be dropped as the problem with fakeroot was fixed (LP: #1915250) and sudo doesn't require root to be built anymore (and the file permissions seem to be correct in my PPA). I updated the merge request. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2007698 Title: Please merge 1.9.13p1-1 into lunar Status in sudo package in Ubuntu: New Bug description: PPA available at https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008123] [NEW] Please merge 7.88.1-1 into lunar
Public bug reported: PPA https://launchpad.net/~danilogondolfo/+archive/ubuntu/curl/ ** Affects: curl (Ubuntu) Importance: Undecided Status: New ** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/curl/+git/curl/+merge/437707 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2008123 Title: Please merge 7.88.1-1 into lunar Status in curl package in Ubuntu: New Bug description: PPA https://launchpad.net/~danilogondolfo/+archive/ubuntu/curl/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2008123/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data
It doesn't seem to be caused by a race between networkd and
NetworkManager.
I reproduced the issue with qemu here and I see the name resolution
failure happening few seconds before NetworkManager started.
>From /var/log/cloud-init.log:
2023-03-09 19:17:58,443 - util.py[DEBUG]: Getting data from failed
Traceback (most recent call last):
...
cloudinit.url_helper.UrlError: HTTPConnectionPool(host='boot.linuxgroove.com',
port=80): Max retries exceeded with url: /ubuntu/23.04/meta-data (Caused by
NewConnectionError(':
Failed to establish a new connection: [Errno -3] Temporary failure in name
resolution'))
>From systemd's journal
Mar 09 19:18:01 ubuntu systemd[1]: Starting NetworkManager.service - Network
Manager...
(edit)
resolved wasn't running as well
2023-03-09T19:18:01.712656+00:00 ubuntu systemd[1]: Starting systemd-
resolved.service - Network Name Resolution...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2008952
Title:
DNS failure while trying to fetch user-data
Status in cloud-init:
Triaged
Status in netplan:
New
Status in subiquity:
New
Status in systemd package in Ubuntu:
New
Bug description:
In testing netboot + autoinstall of the new ubuntu desktop subiquity
based installer for 23.04 I found cloud-init is failing to retrieve
user-data because it can't resolved the hostname in the URL. This
same configuration does work for 22.04 based subiquity, so seems a
regression.
From the ipxe config:
imgargs vmlinuz initrd=initrd \
ip=dhcp \
iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso
\
fsck.mode=skip \
layerfs-path=minimal.standard.live.squashfs \
autoinstall \
'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \
That fails, but if we replace boot.linuxgroove.com with the IP it
works.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data
As /etc/resolv.conf is a symlink, is it possible that the nameservers received via DHCP in the early boot stages are never stored in /etc/resolv.conf? cloud-init tries to resolve that address before resolved is started and there is nothing at /etc/resolv.conf. Does that make sense? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: New Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data
** Changed in: netplan Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data
** Attachment added: "systemd_journal.txt" https://bugs.launchpad.net/cloud-init/+bug/2008952/+attachment/5654392/+files/systemd_journal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data
** Attachment added: "timeline.txt" https://bugs.launchpad.net/cloud-init/+bug/2008952/+attachment/5654394/+files/timeline.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data
I attached some logs that might be useful. After checking it again I realized that the syslog timestamps are a little off when compared to the systemd journal. As shown in the timeline.txt (attached), cloud-init and systemd-resolved are starting at the same time. So the name resolution might not be working yet when cloud-init needs it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data
** Attachment added: "cloud-init.log" https://bugs.launchpad.net/cloud-init/+bug/2008952/+attachment/5654393/+files/cloud-init.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055148] Re: NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan
I can confirm the problem. Here is a reproducer: # nmcli con add ifname dummy0 type dummy ipv4.dns 1.1.1.1#lxd Error: Failed to add 'dummy-dummy0' connection: Message recipient disconnected from message bus without replying This is the crash related to this issue: Mar 15 09:46:40 noble-vm NetworkManager[7091]: /etc/netplan/90-NM-2116bb84-fa09-461a-a923-e04bc2648898.yaml:8:9: Error in network definition: malformed address '1.1.1.1#lxd', must be X.X.X.X or X:X:X:X:X:X:X:X Mar 15 09:46:40 noble-vm NetworkManager[7091]: - 1.1.1.1#lxd Mar 15 09:46:40 noble-vm NetworkManager[7091]: ^ Mar 15 09:46:40 noble-vm NetworkManager[7051]: [1710496000.8273] BUG: the profile cannot be stored in keyfile format without becoming unusable: cannot access file: No such file or directory Mar 15 09:46:40 noble-vm NetworkManager[7051]: ** Mar 15 09:46:40 noble-vm NetworkManager[7051]: nm:ERROR:src/core/settings/plugins/keyfile/nms-keyfile-writer.c:551:_internal_write_connection: assertion failed: (unreachable) Mar 15 09:46:40 noble-vm NetworkManager[7051]: Bail out! nm:ERROR:src/core/settings/plugins/keyfile/nms-keyfile-writer.c:551:_internal_write_connection: assertion failed: (unreachable) Mar 15 09:46:40 noble-vm systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=6/ABRT Mar 15 09:46:40 noble-vm systemd[1]: NetworkManager.service: Failed with result 'core-dump'. Mar 15 09:46:41 noble-vm systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 1. Mar 15 09:46:41 noble-vm systemd[1]: Starting NetworkManager.service - Network Manager... I also noticed another crash already reported here https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057490 Mar 15 09:45:30 noble-vm systemd[1]: Stopping NetworkManager.service - Network Manager... Mar 15 09:45:30 noble-vm NetworkManager[6790]: [1710495930.0746] caught SIGTERM, shutting down normally. Mar 15 09:45:30 noble-vm NetworkManager[6790]: ** Mar 15 09:45:30 noble-vm NetworkManager[6790]: nm:ERROR:src/core/nm-policy.c:2937:dispose: assertion failed: (!c_list_is_empty(&priv->policy_auto_activate_lst_head)) Mar 15 09:45:30 noble-vm NetworkManager[6790]: Bail out! nm:ERROR:src/core/nm-policy.c:2937:dispose: assertion failed: (!c_list_is_empty(&priv->policy_auto_activate_lst_head)) Mar 15 09:45:30 noble-vm NetworkManager[6790]: [1710495930.0751] exiting (success) Mar 15 09:45:31 noble-vm systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=6/ABRT Mar 15 09:45:31 noble-vm systemd[1]: NetworkManager.service: Failed with result 'core-dump'. Mar 15 09:45:31 noble-vm systemd[1]: Starting NetworkManager.service - Network Manager... ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2055148 Title: NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan Status in netplan: New Status in netplan.io package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: From: https://discourse.ubuntu.com/t/blog-netplan-developer- diaries/35932/11 Hi all, NetworkManager connections with an explicit DoT (DNS over TLS) configuration are not supported with Netplan, but NetworkManager does feed back the DoT DNS info with server address and Server Name Indication (SNI) in the form server_address#SNI, e.g. 1.2.3.4#dns.myhome.com as nameserver addresses to Netplan. As a result, subsequent Netplan config applications fail because DNS servers don’t have the expected dotted decimal (IPv4) or colon’ed hex (IPv6) form. ``` nmcli> describe ipv4.dns === [dns] === [NM property description] Array of IP addresses of DNS servers. For DoT (DNS over TLS), the SNI server name can be specified by appending "#example.com" to the IP address of the DNS server. This currently only has effect when using systemd-resolved. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2055148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055148] Re: NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan
So, I believe the best solution here would be to add options to DNS addresses, similar to what we do with IP addresses. Something like this nameservers: addresses: - 1.2.3.4: sni: domain port: 1234 interface: eth123 - 1.1.1.1 with this we'd fully support both Network Manager and networkd backends. Right now NM seems to support only the SNI parameter (1.2.3.4#domain) but networkd supports more: "111.222.333.444:9953%ifname#example.com" for IPv4 and "[:::]:9953%ifname#example.com" for IPv6. Alternatively, to keep things simpler, we could just accept the string 1.2.3.4#domain (and possibly the full notation used by networkd too). What do you think, Lukas? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2055148 Title: NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan Status in netplan: New Status in netplan.io package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: From: https://discourse.ubuntu.com/t/blog-netplan-developer- diaries/35932/11 Hi all, NetworkManager connections with an explicit DoT (DNS over TLS) configuration are not supported with Netplan, but NetworkManager does feed back the DoT DNS info with server address and Server Name Indication (SNI) in the form server_address#SNI, e.g. 1.2.3.4#dns.myhome.com as nameserver addresses to Netplan. As a result, subsequent Netplan config applications fail because DNS servers don’t have the expected dotted decimal (IPv4) or colon’ed hex (IPv6) form. ``` nmcli> describe ipv4.dns === [dns] === [NM property description] Array of IP addresses of DNS servers. For DoT (DNS over TLS), the SNI server name can be specified by appending "#example.com" to the IP address of the DNS server. This currently only has effect when using systemd-resolved. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2055148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059651] Re: network-manager gets uninstalled on apt full-upgrade
Please refer to https://lists.ubuntu.com/archives/ubuntu- devel/2024-March/042954.html for more information about the current state of upgrades. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2059651 Title: network-manager gets uninstalled on apt full-upgrade Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: network-manager gets uninstalled on apt full-upgrade I've tried two Noble systems this evening and both got their network- manager packages removed. So wifi is gone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2060241] Re: prosposed migration audit 1:3.1.2-2.1build1 vs network-manager 1.46.0-1ubuntu1
Probably fixed in the last network-manager upload: debian/tests/control: add Depends: python3-gi for nm_netplan.py (LP: #2060221) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/2060241 Title: prosposed migration audit 1:3.1.2-2.1build1 vs network-manager 1.46.0-1ubuntu1 Status in audit package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: The autopkgest for network-manager fail due to the missing module dependency: 3988s autopkgtest [18:31:02]: test nm_netplan.py: [--- 3988s Traceback (most recent call last): 3988s File "/tmp/autopkgtest.Q1jKoU/build.9D4/src/debian/tests/nm_netplan.py", line 18, in 3988s import gi 3988s ModuleNotFoundError: No module named 'gi' 3988s autopkgtest [18:31:02]: test nm_netplan.py: ---] 3989s autopkgtest [18:31:03]: test nm_netplan.py: - - - - - - - - - - results - - - - - - - - - - 3989s nm_netplan.pyFAIL non-zero exit status 1 --- [1] [1] https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/amd64/n/network-manager/20240404_183130_7a1cc@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/2060241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055333] Re: netplan.io 0.106.1-7ubuntu0.22.04.2 fails to manage additional loopback addresses on Ubuntu 2204 Jammy
To get you configuration working you need to remove the match and set- name stanzas (which were never required really). Using the definition ID as the interface name (the "lo" inside "ethernets") is enough to configure an interface using its name. And by removing that it will work on Jammy. As you noticed, there seem to be some change in behavior in newer versions of systemd. The configuration that uses match.macaddress I wouldn't expect to work actually works on Noble. Although, I've found this by accident: --- Apr 15 14:14:58 noble (udev-worker)[382]: dummy123: Could not set WakeOnLan to off, ignoring: Operation not supported Apr 15 14:14:58 noble (udev-worker)[382]: dummy123: Failed to rename network interface 3 from 'dummy123' to 'lo': File exists Apr 15 14:14:58 noble (udev-worker)[382]: dummy123: Failed to process device, ignoring: File exists --- I also have a dummy interface in my configuration and it doesn't have a permanent mac address as well. Although, udev apparently tried to apply the set-name from ethernets.lo to this interface as if the match.macaddress matched both. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2055333 Title: netplan.io 0.106.1-7ubuntu0.22.04.2 fails to manage additional loopback addresses on Ubuntu 2204 Jammy Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Attempting to add additional loopback addresses to 22.04 jammy fails with the latest netplan.io package. Previous versions (.104) work correctly as well as newer versions (0.107) in 23.10 mantic. Behavior does not change if default loopback addresses are or are not present in the address list (127.0.0.1/8 and ::1/128). Netplan is configured via cloudinit in our environment but for simplicity I'll provide output from a manual configuration on a test vm in virtual box. root@ubuntu-jammy-test:~# cat /etc/netplan/10-loopback.yaml network: version: 2 ethernets: lo: addresses: - 10.10.10.10/32 match: macaddress: 00:00:00:00:00:00 set-name: lo root@ubuntu-jammy-test:~# netplan apply WARNING:root:Cannot call Open vSwitch: ovsdb-server.service is not running. root@ubuntu-jammy-test:~# ip addr show lo 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever root@ubuntu-jammy-test:~# networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 enp0s3 etherroutableconfigured 2 links listed. root@ubuntu-jammy-test:~# apt-get install -y --allow-downgrades netplan.io=0.104-0ubuntu2 libnetplan0=0.104-0ubuntu2 Reading package lists... Done Building dependency tree... Done Reading state information... Done Suggested packages: network-manager | wpasupplicant openvswitch-switch The following packages will be DOWNGRADED: libnetplan0 netplan.io 0 upgraded, 0 newly installed, 2 downgraded, 0 to remove and 0 not upgraded. Need to get 0 B/181 kB of archives. After this operation, 163 kB disk space will be freed. dpkg: warning: downgrading netplan.io from 0.106.1-7ubuntu0.22.04.2 to 0.104-0ubuntu2 (Reading database ... 69845 files and directories currently installed.) Preparing to unpack .../netplan.io_0.104-0ubuntu2_amd64.deb ... Unpacking netplan.io (0.104-0ubuntu2) over (0.106.1-7ubuntu0.22.04.2) ... dpkg: warning: downgrading libnetplan0:amd64 from 0.106.1-7ubuntu0.22.04.2 to 0.104-0ubuntu2 Preparing to unpack .../libnetplan0_0.104-0ubuntu2_amd64.deb ... Unpacking libnetplan0:amd64 (0.104-0ubuntu2) over (0.106.1-7ubuntu0.22.04.2) ... Setting up libnetplan0:amd64 (0.104-0ubuntu2) ... Setting up netplan.io (0.104-0ubuntu2) ... Processing triggers for libc-bin (2.35-0ubuntu3.6) ... Processing triggers for man-db (2.10.2-1) ... Processing triggers for dbus (1.12.20-2ubuntu4.1) ... Scanning processes... Scanning linux images... Running kernel seems to be up-to-date. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. No VM guests are running outdated hypervisor (qemu) binaries on t
[Touch-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
I just updated and rebooted but I'm also still seeing the same problem:
Failed to backup /etc/group: Operation not supported. It's reproducible
with "apt install tomcat10".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Fix Committed
Status in zfs-linux package in Ubuntu:
Fix Released
Status in systemd source package in Noble:
Fix Committed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Oh the new kernel wasn't built with the new zfs-dkms =/
II: dkms-build downloading zfs (zfs-dkms_2.2.2-0ubuntu7_all.deb)
II: fetching
https://launchpad.net/ubuntu/+archive/primary/+files/zfs-dkms_2.2.2-0ubuntu7_all.deb
II: fixing
https://launchpadlibrarian.net/718392332/zfs-dkms_2.2.2-0ubuntu7_all.deb
II: following
http://launchpadlibrarian.net/718392332/zfs-dkms_2.2.2-0ubuntu7_all.deb
II: dkms-build-configure dkms-build-configure--zfs found, executing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Fix Committed
Status in zfs-linux package in Ubuntu:
Fix Released
Status in systemd source package in Noble:
Fix Committed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Kernel -31 fixed the problem for me. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in zfs-linux package in Ubuntu:
Fix Released
Status in systemd source package in Noble:
Fix Released
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
I can confirm this is an issue, although it's not caused by Network Manager so I'll go ahead and set it as invalid. After trying to do a "do-release-upgrade -d" from a brand new installation of Jammy 22.04.4, gnome-shell crashed and interrupted the upgrade. After that, this is what "dpkg --list | grep systemd" looks like: ii dbus-user-session 1.14.10-4ubuntu4 amd64simple interprocess messaging system (systemd --user integration) ii gnome-logs42.0-1 amd64viewer for the systemd journal ii libnss-systemd:amd64 249.11-0ubuntu3.12 amd64nss module providing dynamic user and group name resolution ii libpam-systemd:amd64 249.11-0ubuntu3.12 amd64system and service manager - PAM module ii libsystemd-shared:amd64 255.4-1ubuntu8 amd64systemd shared private library ii libsystemd0:amd64 255.4-1ubuntu8 amd64systemd utility library ii networkd-dispatcher 2.1-2ubuntu0.22.04.2 all Dispatcher service for systemd-networkd connection status changes ii python3-systemd 235-1build4 amd64Python 3 bindings for systemd ii systemd 255.4-1ubuntu8 amd64system and service manager ii systemd-dev 255.4-1ubuntu8 all systemd development files ii systemd-hwe-hwdb 249.11.5 all udev rules for hardware enablement (HWE) ii systemd-oomd 249.11-0ubuntu3.12 amd64Userspace out-of-memory (OOM) killer ii systemd-sysv 249.11-0ubuntu3.12 amd64system and service manager - SysV links ii systemd-timesyncd 255.4-1ubuntu8 amd64minimalistic service to synchronize local time with NTP servers and /etc/resolv.conf is a broken link as systemd-resolved is not installed and /run/systemd/resolve doesn't exist: /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf ** Changed in: network-manager (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.appor
[Touch-packages] [Bug 2058976] Re: Configuration files for networkd are created when NetworkManager is the default renderer
I have found another case where reloading networkd will not be enough to
apply the configuration. I'm not sure if it's the same root cause but it
looks similar so I'll use this ticket to document it.
The scenario looks like this (it's all done in a LXD VM running
Oracular):
1) Start with the default ethernet configuration
2) Add the ethernet interface to a bond and apply
3) Remove the bond from the configuration and apply
4) Add the interface back to the bond and apply
5) At this point the configuration will not be applied anymore and one needs to
either restart networkd or delete the bond.
It smells like some state is not being dropped and causing the issue.
Details on how to reproduce:
Start with this config:
network:
version: 2
ethernets:
enp5s0:
dhcp4: true
Add a bond:
network:
version: 2
ethernets:
enp5s0: {}
bonds:
bond0:
dhcp4: true
interfaces:
- enp5s0
Apply the config and observe it worked as intended.
Now restore the initial config and netplan apply again:
network:
version: 2
ethernets:
enp5s0:
dhcp4: true
At this point enp4s0 will get an IP address and the bond0 interface will
be left behind as netplan apply will not delete it.
Now add the bond back and netplan apply again:
network:
version: 2
ethernets:
enp5s0: {}
bonds:
bond0:
dhcp4: true
interfaces:
- enp5s0
At this point the configuration will not by applied anymore.
The bond state will get stuck at "State: no-carrier (configuring)".
One needs to either delete the bond or restart networkd to make it work again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2058976
Title:
Configuration files for networkd are created when NetworkManager is
the default renderer
Status in Netplan:
New
Status in systemd package in Ubuntu:
New
Bug description:
This is happening in a UC image created with a gadget that disables
console-conf:
$ ubuntu-image snap --snap=network-manager=22 --snap pc_22.snap
The snaps are:
$ snap list
Name Version RevTracking Publisher Notes
core22 202403211344 latest/edge canonical✓ base
network-manager 1.36.6-987622/stablecanonical✓ -
pc 22-0.3 x1 --
gadget
pc-kernel5.15.0-102.112.1+1 1731 22/beta canonical✓
kernel
snapd2.62+git2017.g1afc063e 21490 latest/edge canonical✓ snapd
On first boot, the content in /etc/netplan is:
ubuntu@ubuntu:~$ cat /etc/netplan/00-default-nm-renderer.yaml
network:
renderer: NetworkManager
ubuntu@ubuntu:~$ cat /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
ethernets:
ens3:
dhcp4: true
match:
macaddress: '52:54:00:12:34:56'
set-name: ens3
version: 2
But we have a configuration file for systemd-networkd that should not be
there:
ubuntu@ubuntu:~$ cat /run/systemd/network/10-netplan-ens3.link
[Match]
PermanentMACAddress=52:54:00:12:34:56
[Link]
Name=ens3
WakeOnLan=off
ubuntu@ubuntu:~$ networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 ens3 etherroutableconfigured
While having to:
ubuntu@ubuntu:~$ sudo cat
/run/NetworkManager/system-connections/netplan-ens3.nmconnection
[connection]
id=netplan-ens3
type=ethernet
interface-name=ens3
[ethernet]
wake-on-lan=0
[ipv4]
method=auto
[ipv6]
method=ignore
ubuntu@ubuntu:~$ nmcli c
NAME UUID TYPE DEVICE
netplan-ens3 bec3d02a-c9e5-3283-92ab-ee43a4246c85 ethernet ens3
ubuntu@ubuntu:~$ nmcli d
DEVICE TYPE STATE CONNECTION
ens3ethernet connected netplan-ens3
lo loopback unmanaged --
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2058976/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor
Hi Sebastian, thanks for your bug report. I can see the following error in your syslog.log: [1700508393.5530] BUG: the profile cannot be stored in keyfile format without becoming unusable: invalid connection: ipv4.dns: This property is not allowed for "method=disabled" What steps did you follow to setup the connection? I want to understand how you managed to set the ipv4.dns property with ipv4.method set to disabled using the GUI interface. May I ask you to watch the Network Manager's journal while you reproduce the crash and add the relevant part of the logs here? journalctl -u NetworkManager.service -f Also, you will probably find a YAML in /etc/netplan that was created for the problematic connection. Can you find it, remove all the keys and IPs from it, and paste it here? I'm running netplan.io 0.107-5ubuntu0.1 and I can create Wireguard connections just fine. But maybe you are using some settings that's triggering another bug that we are not aware of. Thank you. ** Changed in: network-manager (Ubuntu) Status: New => Triaged ** Changed in: network-manager (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2044014 Title: networkmanager crashes on configuring wireguard connection via nm- connection-editor Status in network-manager package in Ubuntu: Triaged Bug description: when configuring a new wireguard connection both via nm-connection-editor and the settings app, NetworkManager crashes and restarts, with the error message "Message recipient disconnected from message bus without replying". Currently, I'm unable to add wireguard connections at all. Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821 Ubuntu 23.10 network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64 netplan.io/now 0.107-5ubuntu1~ppa3 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 20:10:40 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-15 (2015 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via dev enp0s31f6 proto dhcp src metric 100 /24 dev enp0s31f6 proto kernel scope link src metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago) http_proxy: http://:3128 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled disabled missing disabled no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor
Hi, I can't find anything wrong in your configuration. And that makes me wonder if you have another YAML with the same wg0 interface in it. We recently fixed a bug in Network Manager that was leading to duplication in the configuration. You might have been affected by this bug when you upgraded to Mantic. If you grep /etc/netplan by the interface name, do you see more than one file? Something like this "sudo grep wg0 /etc/netplan/*". If you find the same interface in more than one file, try to remove them and create the connection again using the GUI. The problem might be that you have multiple YAMLs with the same interface. Netplan will merge them in a single configuration and the result might be a broken config. Let me know if it helps. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2044014 Title: networkmanager crashes on configuring wireguard connection via nm- connection-editor Status in network-manager package in Ubuntu: Triaged Bug description: when configuring a new wireguard connection both via nm-connection-editor and the settings app, NetworkManager crashes and restarts, with the error message "Message recipient disconnected from message bus without replying". Currently, I'm unable to add wireguard connections at all. Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821 Ubuntu 23.10 network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64 netplan.io/now 0.107-5ubuntu1~ppa3 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 20:10:40 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-15 (2015 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via dev enp0s31f6 proto dhcp src metric 100 /24 dev enp0s31f6 proto kernel scope link src metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago) http_proxy: http://:3128 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled disabled missing disabled no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2044270] Re: Wi-Fi connection lost and reestablished every 3 minutes after upgrade from Lubuntu 22.10 to 23.10
Hello, thanks for your bug report. Can you collect and attach the Network Manager's systemd journal? You can get it with "journalctl -u NetworkManager > network-manager.log" It will help us to identify the problem. Thank you! ** Changed in: network-manager (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2044270 Title: Wi-Fi connection lost and reestablished every 3 minutes after upgrade from Lubuntu 22.10 to 23.10 Status in network-manager package in Ubuntu: Triaged Bug description: In Lubuntu 22.10 (Kinetic) Wi-Fi connection on my laptop was stable. A couple of days ago I upgraded Lubuntu (installed it afresh) to 23.10 (Mantic Minotaur). Now the connection is lost every couple of minutes and reestablished again in 3-20 seconds automatically. The same issue with two different internet providers (two different routers). Network manager version as told by command "apt-cache policy network- manager" is 1.44.2-1ubuntu1.2. My laptop model is Digma CITI E401. sudo lshw -class network *-network description: Wireless interface physical id: e bus info: mmc@2:0001:1 logical name: wlan0 serial: 80:5e:4f:02:97:70 capabilities: ethernet physical wireless configuration: broadcast=yes driver=rtl8723bs driverversion=6.5.0-13-generic ip=192.168.0.13 multicast=yes wireless=IEEE 802.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044270/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045886] [NEW] Please merge 8.5.0-1 into noble
Public bug reported: tracking bug ** Affects: curl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2045886 Title: Please merge 8.5.0-1 into noble Status in curl package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2045886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045886] Re: Please merge 8.5.0-1 into noble
hmm an autopkgtest is segfaulting (also in Debian) 2813s ldap_send_server_request 2813s ## Something failed, gathering logs 2813s 2813s ## syslog 2813s Segmentation fault (core dumped) ... 2813s curl-ldapi-test FAIL non-zero exit status 139 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2045886 Title: Please merge 8.5.0-1 into noble Status in curl package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2045886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046158] Re: Updating wireguard-peer.allowed-ips gets wrong default netmask for IPv6 addresses
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2046158
Title:
Updating wireguard-peer.allowed-ips gets wrong default netmask for
IPv6 addresses
Status in netplan.io package in Ubuntu:
New
Status in network-manager package in Ubuntu:
New
Bug description:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only
connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer: NetworkManager
addresses:
- "10.0.0.2/24"
mode: "wireguard"
port: 51820
keys:
private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
peers:
- keys:
public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
allowed-ips:
- "10.0.0.1/32"
networkmanager:
uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
name: "con-wg0"
passthrough:
ipv6.addr-gen-mode: "default"
ipv6.method: "disabled"
ipv6.ip6-privacy: "-1"
proxy._: ""
which gets rendered as
# cat /run/NetworkManager/system-connections/netplan-wg0.nmconnection
[connection]
id=con-wg0
type=wireguard
uuid=b5edee2d-c736-4827-bae3-c95e349cb73b
interface-name=wg0
[wireguard]
private-key=KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E=
listen-port=51820
[wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=]
allowed-ips=10.0.0.1/32;
[ipv4]
method=manual
address1=10.0.0.2/24
[ipv6]
#Netplan: passthrough override
method=disabled
#Netplan: passthrough setting
addr-gen-mode=default
[proxy]
Now the UI modifies the "allowed-ips" setting to ["10.0.0.1",
"2001::1"]. Notably the addresses do *not* have a netmask, neither in
the original config nor that update. Unfortunately that update cannot
be done on the CLI:
# nmcli con modify con-wg0
"wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=.allowed-ips"
"2001::1"
Error: invalid or not allowed setting 'wireguard-peer': 'wireguard-peer' not
among [connection, wireguard, match, ipv4, ipv6, hostname, link, tc, proxy].
So it has to happen via D-Bus:
"/org/freedesktop/NetworkManager/Settings/5","org.freedesktop.NetworkManager.Settings.Connection","Update",[{"connection":{"id":{"v":"con-
wg0","t":"s"},"interface-
name":{"v":"wg0","t":"s"},"permissions":{"t":"as","v":[]},"timestamp":{"t":"t","v":1702299778},"type":{"v":"wireguard","t":"s"},"uuid":{"v":"04237010-9663-4064-aa06-bcde279b67da","t":"s"},"autoconnect":{"v":true,"t":"b"},"autoconnect-
slaves":{"v":-1,"t":"i"}},"wireguard":{"listen-
port":{"v":51820,"t":"u"},"peers":{"v":[{"public-
key":{"t":"s","v":"2CvDKtc8k94LLpabq6rZdYh1Co8fzjhoAD61ESMfjSc="},"allowed-
ips":{"t":"as","v":["10.0.0.1/32","2001::1"]}}],"t":"aa{sv}"},"private-
key":{"v":"iDM1BknhsROJt8TpJnBNNHVCAqWnfqZEkL20+sVfXlA=","t":"s"}},"ipv4":{"address-
data":{"t":"aa{sv}","v":[{"address":{"t":"s","v":"10.0.0.2"},"prefix":{"t":"u","v":24}}]},"addresses":{"v":[[33554442,24,0]],"t":"aau"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"manual","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"t":"aau","v":[]},"dns":{"v":[],"t":"au"}},"ipv6":{"address-
data":{"t":"aa{sv}","v":[]},"addresses":{"v":[],"t":"a(ayuay)"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"disabled","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"v":[],"t":"a(ayuayu)"},"ignore-
auto-dns":{"v":false,"t":"b"},"ignore-auto-
routes":{"v":false,"t":"b"},"dns":{"v":[],"t":"aay"}},"proxy":{}}]]
But this generates a wrong "/32" default netmask in the netplan config
for the IPv6 address:
allowed-ips:
- "10.0.0.1/32"
- "2001::1/32"
On Fedora, with NM's default .nmconnection files, such a netmask is
not added on this call. The netplan backend should do that (not
second-guessing NM) or at least default to /128 for an IPv6 address.
Doing this D-Bus call with `busctl` is a nuisance. If you need a
reproducer at this level, I can spend an hour or so trying to stitch
it together, but I hope your unit tests make this easier somehow.
This was fine until 22.10, but with NM's new "netplan by default"
backend this regressed.
DistroRelease: Ubuntu 23.10
Package: network-manager 1.44.2-1ubuntu1.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2046158/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046158] Re: Updating wireguard-peer.allowed-ips gets wrong default netmask for IPv6 addresses
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2046158
Title:
Updating wireguard-peer.allowed-ips gets wrong default netmask for
IPv6 addresses
Status in netplan.io package in Ubuntu:
New
Status in network-manager package in Ubuntu:
New
Bug description:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only
connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer: NetworkManager
addresses:
- "10.0.0.2/24"
mode: "wireguard"
port: 51820
keys:
private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
peers:
- keys:
public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
allowed-ips:
- "10.0.0.1/32"
networkmanager:
uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
name: "con-wg0"
passthrough:
ipv6.addr-gen-mode: "default"
ipv6.method: "disabled"
ipv6.ip6-privacy: "-1"
proxy._: ""
which gets rendered as
# cat /run/NetworkManager/system-connections/netplan-wg0.nmconnection
[connection]
id=con-wg0
type=wireguard
uuid=b5edee2d-c736-4827-bae3-c95e349cb73b
interface-name=wg0
[wireguard]
private-key=KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E=
listen-port=51820
[wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=]
allowed-ips=10.0.0.1/32;
[ipv4]
method=manual
address1=10.0.0.2/24
[ipv6]
#Netplan: passthrough override
method=disabled
#Netplan: passthrough setting
addr-gen-mode=default
[proxy]
Now the UI modifies the "allowed-ips" setting to ["10.0.0.1",
"2001::1"]. Notably the addresses do *not* have a netmask, neither in
the original config nor that update. Unfortunately that update cannot
be done on the CLI:
# nmcli con modify con-wg0
"wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=.allowed-ips"
"2001::1"
Error: invalid or not allowed setting 'wireguard-peer': 'wireguard-peer' not
among [connection, wireguard, match, ipv4, ipv6, hostname, link, tc, proxy].
So it has to happen via D-Bus:
"/org/freedesktop/NetworkManager/Settings/5","org.freedesktop.NetworkManager.Settings.Connection","Update",[{"connection":{"id":{"v":"con-
wg0","t":"s"},"interface-
name":{"v":"wg0","t":"s"},"permissions":{"t":"as","v":[]},"timestamp":{"t":"t","v":1702299778},"type":{"v":"wireguard","t":"s"},"uuid":{"v":"04237010-9663-4064-aa06-bcde279b67da","t":"s"},"autoconnect":{"v":true,"t":"b"},"autoconnect-
slaves":{"v":-1,"t":"i"}},"wireguard":{"listen-
port":{"v":51820,"t":"u"},"peers":{"v":[{"public-
key":{"t":"s","v":"2CvDKtc8k94LLpabq6rZdYh1Co8fzjhoAD61ESMfjSc="},"allowed-
ips":{"t":"as","v":["10.0.0.1/32","2001::1"]}}],"t":"aa{sv}"},"private-
key":{"v":"iDM1BknhsROJt8TpJnBNNHVCAqWnfqZEkL20+sVfXlA=","t":"s"}},"ipv4":{"address-
data":{"t":"aa{sv}","v":[{"address":{"t":"s","v":"10.0.0.2"},"prefix":{"t":"u","v":24}}]},"addresses":{"v":[[33554442,24,0]],"t":"aau"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"manual","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"t":"aau","v":[]},"dns":{"v":[],"t":"au"}},"ipv6":{"address-
data":{"t":"aa{sv}","v":[]},"addresses":{"v":[],"t":"a(ayuay)"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"disabled","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"v":[],"t":"a(ayuayu)"},"ignore-
auto-dns":{"v":false,"t":"b"},"ignore-auto-
routes":{"v":false,"t":"b"},"dns":{"v":[],"t":"aay"}},"proxy":{}}]]
But this generates a wrong "/32" default netmask in the netplan config
for the IPv6 address:
allowed-ips:
- "10.0.0.1/32"
- "2001::1/32"
On Fedora, with NM's default .nmconnection files, such a netmask is
not added on this call. The netplan backend should do that (not
second-guessing NM) or at least default to /128 for an IPv6 address.
Doing this D-Bus call with `busctl` is a nuisance. If you need a
reproducer at this level, I can spend an hour or so trying to stitch
it together, but I hope your unit tests make this easier somehow.
This was fine until 22.10, but with NM's new "netplan by default"
backend this regressed.
DistroRelease: Ubuntu 23.10
Package: network-manager 1.44.2-1ubuntu1.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2046158/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046158] Re: Updating wireguard-peer.allowed-ips gets wrong default netmask for IPv6 addresses
Hi Martin, thanks so much for your bug report.
I can confirm it's a problem in libnetplan. I created a small fix for it
https://github.com/canonical/netplan/pull/428
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => High
** Changed in: netplan.io (Ubuntu)
Status: New => Confirmed
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2046158
Title:
Updating wireguard-peer.allowed-ips gets wrong default netmask for
IPv6 addresses
Status in netplan.io package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu:
Invalid
Bug description:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only
connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer: NetworkManager
addresses:
- "10.0.0.2/24"
mode: "wireguard"
port: 51820
keys:
private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
peers:
- keys:
public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
allowed-ips:
- "10.0.0.1/32"
networkmanager:
uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
name: "con-wg0"
passthrough:
ipv6.addr-gen-mode: "default"
ipv6.method: "disabled"
ipv6.ip6-privacy: "-1"
proxy._: ""
which gets rendered as
# cat /run/NetworkManager/system-connections/netplan-wg0.nmconnection
[connection]
id=con-wg0
type=wireguard
uuid=b5edee2d-c736-4827-bae3-c95e349cb73b
interface-name=wg0
[wireguard]
private-key=KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E=
listen-port=51820
[wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=]
allowed-ips=10.0.0.1/32;
[ipv4]
method=manual
address1=10.0.0.2/24
[ipv6]
#Netplan: passthrough override
method=disabled
#Netplan: passthrough setting
addr-gen-mode=default
[proxy]
Now the UI modifies the "allowed-ips" setting to ["10.0.0.1",
"2001::1"]. Notably the addresses do *not* have a netmask, neither in
the original config nor that update. Unfortunately that update cannot
be done on the CLI:
# nmcli con modify con-wg0
"wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=.allowed-ips"
"2001::1"
Error: invalid or not allowed setting 'wireguard-peer': 'wireguard-peer' not
among [connection, wireguard, match, ipv4, ipv6, hostname, link, tc, proxy].
So it has to happen via D-Bus:
"/org/freedesktop/NetworkManager/Settings/5","org.freedesktop.NetworkManager.Settings.Connection","Update",[{"connection":{"id":{"v":"con-
wg0","t":"s"},"interface-
name":{"v":"wg0","t":"s"},"permissions":{"t":"as","v":[]},"timestamp":{"t":"t","v":1702299778},"type":{"v":"wireguard","t":"s"},"uuid":{"v":"04237010-9663-4064-aa06-bcde279b67da","t":"s"},"autoconnect":{"v":true,"t":"b"},"autoconnect-
slaves":{"v":-1,"t":"i"}},"wireguard":{"listen-
port":{"v":51820,"t":"u"},"peers":{"v":[{"public-
key":{"t":"s","v":"2CvDKtc8k94LLpabq6rZdYh1Co8fzjhoAD61ESMfjSc="},"allowed-
ips":{"t":"as","v":["10.0.0.1/32","2001::1"]}}],"t":"aa{sv}"},"private-
key":{"v":"iDM1BknhsROJt8TpJnBNNHVCAqWnfqZEkL20+sVfXlA=","t":"s"}},"ipv4":{"address-
data":{"t":"aa{sv}","v":[{"address":{"t":"s","v":"10.0.0.2"},"prefix":{"t":"u","v":24}}]},"addresses":{"v":[[33554442,24,0]],"t":"aau"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"manual","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"t":"aau","v":[]},"dns":{"v":[],"t":"au"}},"ipv6":{"address-
data":{"t":"aa{sv}","v":[]},"addresses":{"v":[],"t":"a(ayuay)"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"disabled","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"v":[],"t":"a(ayuayu)"},"ignore-
auto-dns":{"v":false,"t":"b"},"ignore-auto-
routes":{"v":false,"t":"b"},"dns":{"v":[],"t":"aay"}},"proxy":{}}]]
But this generates a wrong "/32" default netmask in the netplan config
for the IPv6 address:
allowed-ips:
- "10.0.0.1/32"
- "2001::1/32"
On Fedora, with NM's default .nmconnection files, such a netmask is
not added on this call. The netplan backend should do that (not
second-guessing NM) or at least default to /128 for an IPv6 address.
Doing this D-Bus call with `busctl` is a nuisance. If you need a
reproducer at this level, I can spend an hour or so trying to stitch
it together, but I hope your unit tests make this easier somehow.
This was fine until 22.10, but with NM's new "netplan by default"
backend this regressed.
DistroRelease: Ubuntu 23.10
Package: network-manager 1.44.2-1ubuntu1.2
To manage notifications about this bug go to:
https://bugs.launchpad.ne
[Touch-packages] [Bug 2046436] Re: Ubuntu won't boot after enabling jumbo packets on network device
Hi, If you press ESC when the splash screen shows up, do you see the console? We need to know where it's getting stuck to better understand the problem. If you manage to see the console during boot, can you describe what you see? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2046436 Title: Ubuntu won't boot after enabling jumbo packets on network device Status in network-manager package in Ubuntu: New Bug description: Ubuntu Desktop 23.10 Asrock IMB-X1714 main board, with Intel I226V and I226LM ethernet controllers network-manager 1.44.2-1ubuntu1.2 When enabling jumbo packets on a wired network device by setting MTU to 9000, Ubuntu will not boot anymore. The Ubuntu splash screen, with rotating wheel, appears, at a lower resolution than ordinary, but freezes after a few seconds. I can only revert this by disabling the ethernet devices in BIOS. After that Ubuntu will boot normally. I can then manually edit the .yaml configuration files in /etc/netplan to disable jumbo packets again. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Dec 14 11:04:19 2023 IfupdownConfig: InstallationDate: Installed on 2023-12-13 (1 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) IpRoute: default via 192.168.0.1 dev enp4s0 proto dhcp src 192.168.0.208 metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.208 metric 100 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled missing enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2046436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045886] Re: Please merge 8.5.0-2 into noble
** Summary changed: - Please merge 8.5.0-1 into noble + Please merge 8.5.0-2 into noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2045886 Title: Please merge 8.5.0-2 into noble Status in curl package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2045886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045886] Re: Please merge 8.5.0-2 into noble
The problem seems to be fixed in 8.5.0-2 by https://github.com/curl/curl/commit/fa6e123929de94064f1b1cb135f30b0a945ba399 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2045886 Title: Please merge 8.5.0-2 into noble Status in curl package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2045886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045886] Re: Please merge 8.5.0-2 into noble
** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/curl/+git/curl/+merge/457830 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2045886 Title: Please merge 8.5.0-2 into noble Status in curl package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2045886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1746419] Re: bond parameters are not changed by 'netplan apply'
** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1746419 Title: bond parameters are not changed by 'netplan apply' Status in netplan: Triaged Status in nplan package in Ubuntu: Invalid Status in systemd package in Ubuntu: Won't Fix Bug description: I have a yaml file as follows: network: version: 2 ethernets: bonddevs: match: name: ens[78] bonds: bond0: interfaces: [bonddevs] parameters: mode: active-backup mii-monitor-interval: 1 addresses: - 10.10.10.1/24 Say I decide that 1s is too frequent for the MII interval, and I want to change the interval to 2s. If I change that in the yaml, then run # netplan generate # netplan apply # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)" MII Polling Interval (ms): 1000 In other words, the change has not been applied. Running netplan --debug apply prints: DEBUG:device bond0 operstate is up, not replugging So I wondered if bringing the bond down would help. It does not: # ip link set dev bond0 down # netplan apply # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)" MII Polling Interval (ms): 1000 However, deleting the link works: # ip link del dev bond0 # netplan apply # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)" MII Polling Interval (ms): 2000 This is counter-intuitive behaviour. Ideally, I would like a regular netplan apply to work without deleting the bond. However, a changed to the docs to make this clear would be OK. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nplan 0.32~17.10.1 ProcVersionSignature: User Name 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Wed Jan 31 05:47:42 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: nplan UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1746419/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051576] [NEW] Please merge 1.9.15p5-3 into noble
Public bug reported: tracking bug ** Affects: sudo (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2051576 Title: Please merge 1.9.15p5-3 into noble Status in sudo package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2051576/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
